Beneath this BSOD lies another

[RedMoggie]

Hi Folks,

Have been getting random BSODs over the past few weeks, minidumps attached plus system info. Nothing seems to cause them in terms of my actions. The BSODs are all very similar according to BlueScreenView. Hibernation and sleep not enabled.

So far:
-Have cleaned the internals (cpu temp dropped by 10 degrees but BSODs continue).
-Have tested the RAM and hard drive again and again, all fine.
-PC always boots up fine after BSOD.
-No major hardware/software installations during unstable period, though usual updates from MS, Kaspersky etc.

Have spent a long time browsing for solutions e.g. Error message on a blue screen on a computer that is running Windows 7 or Windows Server 2008 R2: "STOP: 0x0000000A" but not installed anything as yet.

Please advise, as I have started veering away from sites that help me and towards those that might sell me a new desktop!

 

[zigzag3143]

Hi Folks,

Have been getting random BSODs over the past few weeks, minidumps attached plus system info. Nothing seems to cause them in terms of my actions. The BSODs are all very similar according to BlueScreenView. Hibernation and sleep not enabled.

So far:
-Have cleaned the internals (cpu temp dropped by 10 degrees but BSODs continue).
-Have tested the RAM and hard drive again and again, all fine.
-PC always boots up fine after BSOD.
-No major hardware/software installations during unstable period, though usual updates from MS, Kaspersky etc.

Have spent a long time browsing for solutions e.g. Error message on a blue screen on a computer that is running Windows 7 or Windows Server 2008 R2: "STOP: 0x0000000A" but not installed anything as yet.

Please advise, as I have started veering away from sites that help me and towards those that might sell me a new desktop!

Couldnt be more obvious. memory corruption. To test it download memtestx886 and burn it to a cd, then run it for at least 5 passes.

let us know if you need help

ken

Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Wed May 26 21:24:34.600 2010 (GMT-4)
System Uptime: 0 days 5:23:20.286
BugCheck A, {8f944008, 2, 1, 82ec8418}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+3e2 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Tue May 25 20:54:07.656 2010 (GMT-4)
System Uptime: 0 days 9:36:53.342
BugCheck A, {440084, 2, 1, 82e4e0e9}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+1ed )
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Mon May 24 13:55:38.766 2010 (GMT-4)
System Uptime: 0 days 6:51:41.311
BugCheck A, {4e8, 2, 1, 82e430e9}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+1ed )
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun May 23 19:49:04.056 2010 (GMT-4)
System Uptime: 0 days 0:31:12.742
BugCheck A, {c5debf88, 2, 0, 82e520cb}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+1cf )
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun May 23 19:16:38.525 2010 (GMT-4)
System Uptime: 0 days 5:28:00.211
BugCheck A, {c56fedb6, 0, 0, 82ec2272}
Probably caused by : memory_corruption ( nt!MiLogPageAccess+d9 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  WinRAR.exe

 

[RedMoggie]

Many thanks for such a quick reply Ken, should have tried here first!
I presume that Win 7's own RAM checker ain't up to much then? Have run it several times and been given clean bill of health...