My computer started freezing up at random points (it would always happen whenever I opened FireFox, but it also happens at other times too). I understand this can be RAM, drivers, or even hardware. I haven't installed any new hardware lately so I tried singling out the RAM by operating on one stick then swapping it out with the other one. It froze with either stick installed. I noticed when it froze it would give 1 beep and that was it.
Since then it has given me some BSODs. The last two were BAD_POOL_HEADER and something like MEMORY_MANAGEMENT.
I downloaded the windows debug program and ran it along with the !analyze -v command. I don't know what to do or try at this point. Below are the results from the minidump file when analyzed with WinDbg. Thank you in advance for any help you can give.
Dump 1:
Dump 2:
Since then it has given me some BSODs. The last two were BAD_POOL_HEADER and something like MEMORY_MANAGEMENT.
I downloaded the windows debug program and ran it along with the !analyze -v command. I don't know what to do or try at this point. Below are the results from the minidump file when analyzed with WinDbg. Thank you in advance for any help you can give.
Dump 1:
Code:
[COLOR=Blue]Loading Dump File [C:\Windows\Minidump\Mini072909-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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0x8203e000 PsLoadedModuleList = 0x82155c70
Debug session time: Wed Jul 29 20:41:39.514 2009 (GMT-10)
System Uptime: 0 days 7:06:22.530
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {21, 95424000, 1010, 0}
*** WARNING: Unable to verify timestamp for SYMEFA.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEFA.SYS
Probably caused by : SYMEFA.SYS ( SYMEFA+387d2 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000021, the data following the pool block being freed is corrupt. Typically this means the consumer (call stack ) has overrun the block.
Arg2: 95424000, The pool pointer being freed.
Arg3: 00001010, The number of bytes allocated for the pool block.
Arg4: 00000000, The corrupted value found following the pool block.
Debugging Details:
------------------
BUGCHECK_STR: 0x19_21
POOL_ADDRESS: GetPointerFromAddress: unable to read from 82175868
Unable to read MiSystemVaType memory at 82155420
95424000
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8212b184 to 8210bb0d
STACK_TEXT:
877bf874 8212b184 00000019 00000021 95424000 nt!KeBugCheckEx+0x1e
877bf8e8 867bd7d2 95424000 6a544c53 877bf910 nt!ExFreePoolWithTag+0x17f
WARNING: Stack unwind information not available. Following frames may be wrong.
877bf8f8 86788e40 95424008 877bf930 92508d58 SYMEFA+0x387d2
877bf910 8678a5cd 92508d58 00000001 8589de10 SYMEFA+0x3e40
877bf940 8678a753 00000001 92508d58 a69a4df0 SYMEFA+0x55cd
877bf958 8678a8c5 877bf98c 00000000 a69a4df0 SYMEFA+0x5753
877bf96c 8678bf3a 00000001 877bf98c 00000000 SYMEFA+0x58c5
877bf980 8678c5ee 877bf9a4 00000000 a432d5b8 SYMEFA+0x6f3a
877bf9a8 8678c881 8af278f8 00000000 00000000 SYMEFA+0x75ee
877bf9bc 86794320 00000001 8af278f8 00000015 SYMEFA+0x7881
877bfc0c 86792750 8af278f8 00000015 aa156958 SYMEFA+0xf320
877bfc28 8679282d 00000000 aa156958 00000000 SYMEFA+0xd750
877bfc4c 8679f464 8af278f8 867b10a8 867b5350 SYMEFA+0xd82d
877bfc84 867bee4b aa156958 867cd05c 00000000 SYMEFA+0x1a464
877bfcb0 867c2bba 8570785c 87fd868a 82082906 SYMEFA+0x39e4b
877bfd00 867c3039 85707850 857b50f0 877bfd44 SYMEFA+0x3dbba
877bfd10 8674eba6 857b50f0 855b0db8 85707850 SYMEFA+0x3e039
877bfd44 820e3e22 00000000 00000000 83d66ad0 fltmgr!FltpProcessGenericWorkItem+0x38
877bfd7c 82213c42 857b50f0 8902ec82 00000000 nt!ExpWorkerThread+0xfd
877bfdc0 8207cefe 820e3d25 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
SYMEFA+387d2
867bd7d2 ?? ???
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: SYMEFA+387d2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: SYMEFA
IMAGE_NAME: SYMEFA.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 48f51c60
FAILURE_BUCKET_ID: 0x19_21_SYMEFA+387d2
BUCKET_ID: 0x19_21_SYMEFA+387d2
Followup: MachineOwner
---------
[/COLOR]
Code:
[COLOR=Red]
[COLOR=Blue]Loading Dump File [C:\Windows\Minidump\Mini073009-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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0x8200e000 PsLoadedModuleList = 0x82125c70
Debug session time: Thu Jul 30 10:33:47.104 2009 (GMT-10)
System Uptime: 0 days 0:13:17.075
Loading Kernel Symbols
...............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {30, 87f01250, bec86000, a63b1074}
Probably caused by : memory_corruption ( nt!MiPerformFixups+1b5 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00000030, The subtype of the bugcheck.
Arg2: 87f01250
Arg3: bec86000
Arg4: a63b1074
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_30
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 821eec08 to 820dbb0d
STACK_TEXT:
b18a7b4c 821eec08 0000001a 00000030 87f01250 nt!KeBugCheckEx+0x1e
b18a7b94 82211402 87f01250 142c0000 00000001 nt!MiPerformFixups+0x1b5
b18a7bb8 8208ab50 87f01250 00000000 00000124 nt!MiRelocateImagePfn+0xfe
b18a7c1c 82085f74 9f83b988 b18a7c78 9d39ba80 nt!MiWaitForInPageComplete+0x17d
b18a7cd0 820a8246 6e4eb57c a637b988 00000000 nt!MiDispatchFault+0xd81
b18a7d4c 8205bdb4 00000000 6e4eb57c 00000001 nt!MmAccessFault+0x1fe6
b18a7d4c 771f9892 00000000 6e4eb57c 00000001 nt!KiTrap0E+0xdc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0669e580 00000000 00000000 00000000 00000000 0x771f9892
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiPerformFixups+1b5
821eec08 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiPerformFixups+1b5
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 49e0199e
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x1a_30_nt!MiPerformFixups+1b5
BUCKET_ID: 0x1a_30_nt!MiPerformFixups+1b5
Followup: MachineOwner
---------
[/COLOR]
[/COLOR]