Help with BSoD issues

usasma · 06 Nov 2010

I find it awfully ironic that we have to be happy that the system has BSOD'd
But, I'll take what I can get!

The memory dumps point to memory corruption. As you had issues with the memory in dual channel mode, this is reasonable. But, the issues can be with other memory on the system (CPU, mobo, video, etc) - or it can be an issue with the Windows Memory Manager (unlikely, but possible).

So, let's take a look at the mobo:
I presume that you have an Athlon II X4. As such, is it one of those listed at this link?: http://www.asrock.com/mb/cpu.asp?Model=M3A770DE If not, the CPU may not be compatible with the mobo

Please check the memory compatibility list here to see if your RAM is compatible: http://www.asrock.com/mb/memory/M3A770DE.pdf

Then, visit the OCZ website and find the timings/settings/voltages that are recommended for your system - and then go into the BIOS and reset the timings/settings/voltages to those values (in other words, DON'T use the Auto setting in the BIOS for your RAM)

I'd also rerun the MemTest at least overnight (although 24 hours would be better in this case).
I would also run Prime95 according to these directions:

Prime95 download site: Free Software - GIMPS
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.

BSOD BUGCHECK SUMMARY

Code:


Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Nov  6 08:00:26.067 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:47.551
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  SearchIndexer.
Bugcheck code 0000000A
Arguments 00000000`00000028 00000000`00000002 00000000`00000000 fffff800`02abe518
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Nov  6 07:57:06.344 2010 (UTC - 4:00)
System Uptime: 0 days 0:18:49.829
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
Bugcheck code 0000000A
Arguments 00000000`00000028 00000000`00000002 00000000`00000000 fffff800`02ab3518
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Nov  4 09:16:41.258 2010 (UTC - 4:00)
System Uptime: 0 days 0:06:40.727
Probably caused by : memory_corruption ( nt!MiCompressRelocations+235 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
Bugcheck code 00000050
Arguments fffff8a0`07b08000 00000000`00000001 fffff800`02d99419 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

twa · 09 Nov 2010

Damn you're fast (or as the case might be, I'm slow). Thank you very much for all your help it's much appreciated :)

usasma said:

So, let's take a look at the mobo:
I presume that you have an Athlon II X4. As such, is it one of those listed at this link?: ASRock > Products > M3A770DE > CPU Support List If not, the CPU may not be compatible with the mobo

It's there, it's ADX640WFK42GM

usasma said:

Please check the memory compatibility list here to see if your RAM is compatible: http://www.asrock.com/mb/memory/M3A770DE.pdf

Hmm. My RAM is OCZ3G1333LV4GK, and is not listed. OCZ3G1333LV6GK is however? The 6 in the part numer refers AFAICT to tripple ram configurations (3 x 2GB) while the 4 refers to dual ram configuration (2 x 2GB). I can't really tell any other differences...
OCZ DDR3 PC3-10666 Gold Low Voltage Dual Channel OCZ Technology
OCZ DDR3 PC3-10666 Gold Low-Voltage Triple Channel OCZ Technology

usasma said:

Then, visit the OCZ website and find the timings/settings/voltages that are recommended for your system - and then go into the BIOS and reset the timings/settings/voltages to those values (in other words, DON'T use the Auto setting in the BIOS for your RAM)

I'll do that and run MEMTEST tonight... Then Prime95.

Again, thank you usama!!

twa · 09 Nov 2010

Hmm.

Setting the CAS - TRCD - TRP - TRAS to 9 - 9 - 9 - 12. The rest of the timings i have no idea about. Leaving them at auto

The memory clock only has options to set it in 400 MHz DDR3_800, 533 MHz DDR3_1066, 667 MHz DDR3_1333 or 800 MHz DDR3_1600. OCZ specifyes my ram as 1333 MHz DDR3? So i set it to 667 MHz DDR3_1333, right?

There is also options to set Memory Controller Mode to "ganged" or "unganged". Setting it to ganged and trying dual channel again...

Bank Interleaving, again no idea whatthis is, so leaving it at auto. And Channel interleaving is default HASH 2, leaving it at that...

Oh and of course RAM voltage set to 1.65 manually. I'll let you know what gives when i have results...

usasma · 09 Nov 2010

FWIW - I have no knowledge of the details of the settings. All I know is that we've had some success with doing this when the Auto setting doesn't work (and we seem to be blaming RAM).

Good luck!

twa · 06 Dec 2010

Hello again

Problem is not resolved, not even near. Tried messing about with the bios setting as described by both OCZ support forums and ASrock but to no avail. Reverted to bios defaults. Resently i haven't even been able to boot into windows, even in safe mode. It's working right now, for the first time in 2-3 weeks so I'm really hoping to find the culprit...

Atached BSoD info, and I will try to enable drive verifier once again, hoping to gather enough information to shed some light on the issue. But I will likely only be replying from my work comp, so please be patient

usasma · 06 Dec 2010

We have pretty much ruled out issues with 3rd party drivers - so this has to be:
- compatibility
- hardware
- Windows

You can check compatibility for hardware and software here: Windows 7 Compatibility: Software Programs & Hardware Devices: Find Updates, Drivers, & Downloads

Windows issues can be isolated by reinstalling Windows "cleanly" - without any extra programs, just Windows and any drivers that aren't detected by Windows.

BSOD BUGCHECK SUMMARY

Code:


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov 30 12:06:06.375 2010 (UTC - 5:00)
System Uptime: 0 days 0:10:35.906
Probably caused by : memory_corruption
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  conhost.exe
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff960`002ebd7b 00000000`00000000 ffffffff`ffffffff
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Nov 29 14:14:29.296 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:59.750
Probably caused by : memory_corruption ( nt!MiCaptureAndResetWorkingSetAccessBits+97 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
Bugcheck code 0000000A
Arguments fffff680`00041730 00000000`00000000 00000000`00000000 fffff800`02bc2ef7
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Nov 29 14:03:31.163 2010 (UTC - 5:00)
System Uptime: 0 days 0:05:06.631
Probably caused by : memory_corruption ( nt!MiDeletePfnList+c8 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  chrome.exe
Bugcheck code 0000000A
Arguments fffff680`00043e68 00000000`00000000 00000000`00000000 fffff800`02a8de58
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Nov 29 13:57:52.042 2010 (UTC - 5:00)
System Uptime: 0 days 0:53:05.558
Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3a2 )
BUGCHECK_STR:  0x1a_403
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
Bugcheck code 0000001A
Arguments 00000000`00000403 fffff680`00037af8 97200000`384f8867 fffff680`0003b482
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Nov 29 13:03:45.189 2010 (UTC - 5:00)
System Uptime: 0 days 0:21:54.250
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  MsMpEng.exe
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`0003a324 00000000`00000002 00000000`0002e97a
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Nov 26 13:18:08.552 2010 (UTC - 5:00)
System Uptime: 0 days 0:05:38.021
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  SearchFilterHo
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`00578280 00000000`0000ffff 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Nov 26 13:11:56.886 2010 (UTC - 5:00)
System Uptime: 0 days 0:10:50.586
Probably caused by : memory_corruption ( nt!MiSwapWslEntries+6a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  SearchFilterHo
Bugcheck code 0000000A
Arguments fffff6fb`40040010 00000000`00000000 00000000`00000000 fffff800`02afe9fa
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Nov 13 14:32:48.978 2010 (UTC - 5:00)
System Uptime: 0 days 1:45:33.447
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  MsMpEng.exe
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`0001801d 00000000`00000002 00000000`00049272
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Nov 13 12:46:10.187 2010 (UTC - 5:00)
System Uptime: 0 days 0:01:52.640
BugCheck F4, {3, fffffa8005e2db30, fffffa8005e2de10, fffff80002de35d0}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_C0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`05e2db30 fffffa80`05e2de10 fffff800`02de35d0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Help with BSoD issues

Getting worse