Help with BSoD issues

[twa]

Hi

I'm having severe problems with BSoD and Windows 7. I expect it to be a HW issue, but I need help to pinpoint the culprit. I built a new Desktop recently and initially i had issues with the Ram not working properly. Ran Memtest and discovered that it would seem that both motherboard and ram are working fine, except when put in dual channel mode?? I really don't know why, but I decided i could live with 4 Gb in single channel

But now I just booted the comp and had like 5 BSoD in a row, powered down, moved ram to another slot, now comp is working just dandy. PLS HELP!

Followed this guide and attached files accordingly...

Specs:
Windows 7 - Ultimate 64 Bit
CPU: Athlon X4 640 2 mb
MB:ASRock M3A770DE
Graphics: XFX Radeon HD 5670
Mem: OCZ Gold 2 x 2 GB
Disc: Samsung SpinPoint F3 Desktop Class HD103SJ 1 TB
PSU: Corsair VX550W

 

[twa]

Oh btw, the BSoD occurs at random, could be browsing, playing games, listning to music or whatnot, but mainly at startup... Don't know if that helps...

 

[usasma]

14 memory dumps from 26 Sep to 30 Oct 2010 (about 5 weeks)
6 different BSOD errors cited
4 different causes blamed
I would suggest starting with the diagnostics below in the event of a memory problem.

I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Please uninstall Daemon Tools as it has been known to have BSOD issues with some Win7 installations
Please uninstall Catalyst Control Center as it has been known to have BSOD issues with some Win7 installations

If none of the above fixes the issues, please run Driver Verifier according to these instructions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Oct 30 05:32:16.953 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:30.500
Probably caused by : win32k.sys ( win32k!SURFACE::Map+2c8 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  LogonUI.exe
Bugcheck code 00000050
Arguments fffff180`c54251b0 00000000`00000000 fffff960`000b3f78 00000000`00000007
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Oct 30 05:30:06.997 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:12.901
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35e02 )
BUGCHECK_STR:  0x1a_888a
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  smss.exe
Bugcheck code 0000001A
Arguments 00000000`0000888a fffff8a0`032ee0f8 fffff6fc`50009a43 fffffa80`0379dca0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Oct 30 05:24:32.260 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:24.164
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
Bugcheck code 00000050
Arguments fffff900`c9ab8da0 00000000`00000000 fffff960`0019b5f5 00000000`00000002
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Oct 25 16:38:16.604 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:02.009
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`0004ddf8 00000000`00000000 00000000`00000000 fffff800`02b8def7
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Oct 18 14:58:18.018 2010 (UTC - 4:00)
System Uptime: 0 days 1:51:11.423
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`000892db 00000000`00000002 00000000`0004dcf2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Oct  6 17:18:00.578 2010 (UTC - 4:00)
System Uptime: 0 days 0:06:11.000
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+41b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
Bugcheck code 00000050
Arguments fffffa88`7573481b 00000000`00000000 fffff800`02aa153b 00000000`00000005
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Oct  5 11:56:13.187 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:11.656
Probably caused by : ntkrnlmp.exe ( nt!ExpSystemErrorHandler2+5ff )
BUGCHECK_STR:  0xc0000221
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code C0000221
Arguments fffff8a0`00270ec0 00000000`00000000 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Oct  2 13:02:30.436 2010 (UTC - 4:00)
System Uptime: 0 days 0:29:46.905
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  iTunes.exe
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`0010bc40 00000000`00000002 00000000`0004de93
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Oct  2 12:22:49.192 2010 (UTC - 4:00)
System Uptime: 0 days 0:11:32.614
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  TrustedInstall
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`0004b127 00000000`00000002 00000000`00044fef
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Oct  2 09:24:59.859 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:52.328
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35e02 )
BUGCHECK_STR:  0x1a_888a
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CCC.exe
Bugcheck code 0000001A
Arguments 00000000`0000888a fffff8a0`01ddcab8 fffff6fc`8061f951 fffffa80`020f8ce0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Oct  2 09:23:28.578 2010 (UTC - 4:00)
System Uptime: 0 days 0:10:47.000
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+4df )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  AssassinsCreed
Bugcheck code 00000050
Arguments fffffa80`0268b97b 00000000`00000000 fffff800`02a8f5ff 00000000`00000002
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Oct  2 09:12:04.812 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:52.234
Probably caused by : memory_corruption ( nt!MiSwapWslEntries+6a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  spoolsv.exe
Bugcheck code 0000000A
Arguments fffff680`00040300 00000000`00000000 00000000`00000000 fffff800`02ab49fa
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep 28 11:59:12.733 2010 (UTC - 4:00)
System Uptime: 0 days 0:12:46.156
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+31ef2 )
BUGCHECK_STR:  0x1a_403
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
Bugcheck code 0000001A
Arguments 00000000`00000403 fffff680`0000e278 a4d00000`4dac0847 fffff680`00021c0a
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep 25 19:40:08.278 2010 (UTC - 4:00)
System Uptime: 0 days 1:34:06.614
Probably caused by : hardware ( win32k!xxxSendMessageTimeout+2b5 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  CCC.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff960`001aa6e6 fffff880`092e5080 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[twa]

Thank you! I'll look into this and post back if i find anything It'll might take a while thou, I'm not at the comp so often... But thank you very much, it's been driving me mad and i appreciate the assistance

 

[usasma]

Not a problem. The system will send me an email the next time that you post - even if it's a year from now!

 

[twa]

Ok I've looked into it some more...

As I said I already ran memtest86 and found that the ram failed only in dual mode... Still no idea why.

I uninstalled those programs, thou catalyst control center still shows up whwn i right-click the desktop... How to remove that properly? I substituted Daemon Tools with Virtual Clone, seems to work more consistently. Havent had a BSoD for a while.

I couldn't run the HDdiagnostics tool, samsung hasen't provided a utility for F3, I tried running HUTIL, but it wouldn't start...

Then today I experienced some serious problems with windows explorer. It kept crashing on first boot: first i couldn't log in to windows (logon failed, rebooted), then i got in and explorer crashed continuously and i couldn't acces any programs or files. Then BSoD. used safe mode too, still no good, then turned the comp off for a while. Now the problem seems to have disappeared and I'm writing from the comp again...

I've just enabled Drive Verifier and am waiting for the BSoD... Hoping something turns up.

Any Ideas?

 

[usasma]

For the hard drive, either run the Seagate Seatools or the Hitachi Drive Fitness Test.

Please post the BSOD memory dump files after running Driver Verifier.

 

[twa]

Just attached the BSoD from today... (That is, 15 memory dumps in total...)

And downloading hitachis dft now...

And of course, I'm just waiting for the BSoD's now

 

[usasma]

Daemon Tools sptd.sys is still present in the crash dumps. If you haven't uninstalled it, please do so now.
If you have uninstalled it, please also run this free tool to uninstall sptd.sys: DuplexSecure - FAQ

The November 4th memory dump doesn't reveal much. We'l have to wait for the Driver Verifier enabled memory dump....

BSOD BUGCHECK SUMMARY

[font=lucida console]
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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[twa]

w00t finally bsod'ed with driver verifier enabled... 2 times. Hope this memory dump is more revealing

 

[usasma]

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

[FONT=lucida console]
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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/FONT]

 

[twa]

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

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

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

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]

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]

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]

Getting worse

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]

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

[font=lucida console]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]