This one is pretty straight forward.. Memory Corruption .. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and leave it running for at least 5 passes.
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and leave it running for at least 5 passes.
Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.
Try removing any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DEBUG_FLR_IMAGE_TIMESTAMP: 4a8cb33c
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0xAB_nt!MiCheckSessionPoolAllocations+10b
BUCKET_ID: 0xAB_nt!MiCheckSessionPoolAllocations+10b
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c000001d, 9517e742, 883304f4, 0}
Probably caused by : hardware ( win32k!OffTextOut+80 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED
BUCKET_ID: IP_MISALIGNED
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 1, 82cd97b7}
Probably caused by : memory_corruption ( nt!MiUnlinkFreeOrZeroedPage+174 )
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {eb094c0, 2, 1, 82ca41e7}
Probably caused by : ntkrnlmp.exe ( nt!KiSearchForNewThread+2ed )
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 1, 82ca2e2d}
Probably caused by : memory_corruption ( nt!MmZeroPageThread+3d8 )
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 1, 82ca4e2d}
Probably caused by : memory_corruption ( nt!MmZeroPageThread+3d8 )
Followup: MachineOwner
---------
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, 86cde7ea, a3418b70, a3418750}
Probably caused by : ntkrnlmp.exe ( nt!PfFbBufferListFlushStandby+7a )
Followup: MachineOwner
---------
These drivers are out of date and need to be updated ..
Quote
