|
Answer» OS: Windows 7
Model: HP G62 Notebook PC
Processor: Intel(R) Core(TM) i3 CPU M330 @ 2.13 Ghz
Installed RAM: 4.00 BG (3.80 GB usable)
System Type: 64-bit operating system
Hello, so in recent months, I will randomly get a blue screen with an error message at the top, today I actually took time to remember what it said which was "BAD_POOL_CALLER". It literally happened just a few hours ago today, so I ran the dump file from today through WinDbg, but unfortunately, I don't know what any of it means, so I am hoping someone will be able to interpret it for me..I can also provide the WinDbg for the other two dump files I have in my "Minidump" folder if needed. Thank you!!
Edit: I also ran a memory check and once it had restarted and I logged back in, my computer said there were no problems found in the memory. I have also attached all three dump files located in my "Minidump" folder if you need to look at them.
Here is what WinDbg had to say about today's dump file:
Quote Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\051211-47580-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02e0e000 PsLoadedModuleList = 0xfffff800`03053650
Debug session time: Thu May 12 18:19:59.559 2011 (UTC - 5:00)
System Uptime: 0 days 21:36:51.518
Loading Kernel Symbols
....................................... ........................
....................................... .........................
....................................... .........................
.............
Loading User Symbols
Loading unloaded module list
.........................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C2, {7, 109b, 0, fffff8a00e279010}
GetPointerFromAddress: unable to read from fffff800030bd100
GetUlongFromAddress: unable to read from fffff8000302ba18
GetUlongFromAddress: unable to read from fffff8000302ba18
Probably caused by : memory_corruption ( nt!MiDeleteSegmentPages+112 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 000000000000109b, (reserved)
ARG3: 0000000000000000, Memory contents of the pool block
Arg4: fffff8a00e279010, Address of the block of pool being deallocated
Debugging Details:
------------------
GetUlongFromAddress: unable to read from fffff8000302ba18
GetUlongFromAddress: unable to read from fffff8000302ba18
POOL_ADDRESS: fffff8a00e279010
BUGCHECK_STR: 0xc2_7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002fb8be9 to fffff80002e8dd00
STACK_TEXT:
fffff880`03bfca38 fffff800`02fb8be9 : 00000000`000000c2 00000000`00000007 00000000`0000109b 00000000`00000000 : nt!KeBugCheckEx
fffff880`03bfca40 fffff800`02e54a52 : 00000000`00000000 fffff8a0`0e279810 fffffa80`075e08f0 fffff800`0318433d : nt!ExDeferredFreePool+0x1201
fffff880`03bfcaf0 fffff800`0312e5fb : fffffa80`075e0870 00000000`00000011 00000000`0008c081 fffffa80`03dc6d10 : nt!MiDeleteSegmentPages+0x112
fffff880`03bfcbc0 fffff800`02edb0a1 : fffffa80`075e0878 00000000`00000001 00000000`00000000 fffff8a0`00000631 : nt!MiSegmentDelete+0x7b
fffff880`03bfcc00 fffff800`02edaf65 : 00000000`00000000 00000000`00000080 fffffa80`03b61990 fffffa80`00000012 : nt!MiProcessDereferenceList+0x131
fffff880`03bfccc0 fffff800`0312a32e : 00008003`00780709 00000000`00000001 00000000`00f8009a fffff8a0`04ca81c0 : nt!MiDereferenceSegmentThread+0x10d
fffff880`03bfcd40 fffff800`02e7f666 : fffff880`009ea180 fffffa80`03b85040 fffff880`009f4fc0 00000000`00000002 : nt!PspSystemThreadStartup+0x5a
fffff880`03bfcd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiDeleteSegmentPages+112
fffff800`02e54a52 4c8b8424d0000000 mov r8,qword ptr [rsp+0D0h]
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!MiDeleteSegmentPages+112
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd5b
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0xc2_7_nt!MiDeleteSegmentPages+112
BUCKET_ID: X64_0xc2_7_nt!MiDeleteSegmentPages+112
Followup: MachineOwner
---------
[recovering disk space - old attachment deleted by admin]QuoteIMAGE_NAME: memory_corruption
A. If you have more than one RAM module installed, try starting/running computer with one RAM stick at a time.
NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A
B. If you have only one RAM stick installed...
...run memtest...
1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-....iso.zip file.
3. Inside, you'll find memtest86+-....iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:
8. Locate memtest86+-....iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:
10. Once the CD is created, boot from it, and memtest will automatically start to run.
The running program will look something like this depending on the size and number of ram modules installed:
It's recommended to run 5-6 passes. Each pass contains very same 8 tests.
This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.
The FOLLOWING image is the test results area:
The most important item here is the “errors” line. If you SEE ANY errors, even one, most likely, you have bad RAM.
This may be a dumb question but do I physically take one out RAM stick, start it up and then switch if there are no errors with that one? If not..what is the alternative?Exactly. Use the computer with that one stick for couple of hours, or so...OK, thank you! I will test that out today and see if there are any problems.Ok, haven't had time to do the RAM test, but am doing it now..I just had another BSoD crash not too long ago.. *sigh* I will let you know how the RAM test goes.
Edit: Here is what WinDbg said about the dump file created from today's BSoD
Quote
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\051711-73304-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*c:\mss*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02e57000 PsLoadedModuleList = 0xfffff800`0309c650
Debug session time: Tue May 17 13:55:12.515 2011 (UTC - 5:00)
System Uptime: 0 days 20:18:46.555
Loading Kernel Symbols
....................................... ........................
....................................... .........................
....................................... .........................
............
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C2, {7, 109b, 0, fffff8a011fa7010}
GetPointerFromAddress: unable to read from fffff80003106100
GetUlongFromAddress: unable to read from fffff80003074a18
GetUlongFromAddress: unable to read from fffff80003074a18
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteFcb+3a3 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 000000000000109b, (reserved)
Arg3: 0000000000000000, Memory contents of the pool block
Arg4: fffff8a011fa7010, Address of the block of pool being deallocated
Debugging Details:
------------------
GetUlongFromAddress: unable to read from fffff80003074a18
GetUlongFromAddress: unable to read from fffff80003074a18
POOL_ADDRESS: fffff8a011fa7010
BUGCHECK_STR: 0xc2_7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80003001be9 to fffff80002ed6d00
STACK_TEXT:
fffff880`095d68a8 fffff800`03001be9 : 00000000`000000c2 00000000`00000007 00000000`0000109b 00000000`00000000 : nt!KeBugCheckEx
fffff880`095d68b0 fffff880`01c8d1b3 : fffff8a0`11fa7010 00000000`00000000 fffffa80`084d0590 fffffa80`084d0590 : nt!ExDeferredFreePool+0x1201
fffff880`095d6960 fffff880`01c09972 : fffff800`03074260 fffff880`095d6b01 fffff880`095d69e1 fffff8a0`11fa7010 : Ntfs!NtfsDeleteFcb+0x3a3
fffff880`095d69c0 fffff880`01c8f63c : fffffa80`084d0590 fffffa80`04c0d180 fffff8a0`11fa7010 fffff8a0`11fa73a8 : Ntfs!NtfsTeardownFromLcb+0x1e2
fffff880`095d6a50 fffff880`01c110e2 : fffffa80`084d0590 fffffa80`084d0590 fffff8a0`11fa7010 fffff880`095d6c00 : Ntfs!NtfsTeardownStructures+0xcc
fffff880`095d6ad0 fffff880`01c9f193 : fffffa80`04c0d180 fffff800`03074260 fffff8a0`6366744e 00000000`00000009 : Ntfs!NtfsDecrementCloseCounts+0xa2
fffff880`095d6b10 fffff880`01c8e357 : fffffa80`084d0590 fffff8a0`11fa7140 fffff8a0`11fa7010 fffffa80`04c0d180 : Ntfs!NtfsCommonClose+0x353
fffff880`095d6be0 fffff800`02ee1021 : 00000000`00000000 fffff800`031cd000 fffff800`030d5801 00000000`00000002 : Ntfs!NtfsFspClose+0x15f
fffff880`095d6cb0 fffff800`0317332e : fffff880`00000002 fffffa80`05c689a0 00000000`00000080 fffffa80`03b7d890 : nt!ExpWorkerThread+0x111
fffff880`095d6d40 fffff800`02ec8666 : fffff880`03b63180 fffffa80`05c689a0 fffffa80`04083060 fffff880`01c10a20 : nt!PspSystemThreadStartup+0x5a
fffff880`095d6d80 00000000`00000000 : fffff880`095d7000 fffff880`095d1000 fffff880`095d69e0 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
Ntfs!NtfsDeleteFcb+3a3
fffff880`01c8d1b3 4c893b mov qword ptr [rbx],r15
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: Ntfs!NtfsDeleteFcb+3a3
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d79997b
FAILURE_BUCKET_ID: X64_0xc2_7_Ntfs!NtfsDeleteFcb+3a3
BUCKET_ID: X64_0xc2_7_Ntfs!NtfsDeleteFcb+3a3
Followup: MachineOwner
---------
The IMAGE_NAME has changed from the first dump file I posted..it now says "IMAGE_NAME: Ntfs.sys" What exactly does that mean?That's a system file.....could be caused by almost anything.
Let's see what you got from RAM test.Well, I've tested each stick of RAM, and I think I may have found the faulty one...The first one I tested, I ran the computer all day on it, and there was no problem and almost no difference in computer speed. I then changed sticks, and as soon as my computer had booted up and logged in, my computer started to run significantly slower and was extremely laggy. There was no error message, but the speed of the computer was different. What should I do now?Run the computer with the stick #1 only for a day, or so.
See, if you'll be getting any more BSODs.
If not, do the same with stick #2.I have been running the computer with #1 for the past 2-3 days. No BSoD'sVery well then.
You can try running the computer on stick #2 only for couple of days and see how it goes, or simply replace it.Ok, I will do the switch tonight then, run it through the weekend and let you know. Thanks for all of the help so far!You're very welcome Ok, so I did the switch two nights ago, and so far, there has been no BSoD...so I guess I was wrong about the supposed "bad stick" being #2. Initially after boot up and logging in, it ran slow, but now it seems to be pretty normal speed. What should I do now?? Should I let it run another day on #2 or do something else?There are some cases, where the RAM may be not seated properly, or contacts were not properly working and reseating RAM may help.
Put the other stick in and see how it goes.
|
