W7 x64 BSOD Dumps.. Plz Help

[Snypar]

My issues have been ongoing for over a year, so I will give you the cliffs notes
I fresh installed W7 x64 Retail after formatting C: in January.
My computer had a Gigabyte GA-P35-DQ6 mobo. It ran stable for a little while then started BSOD. Memtest showed a bad DIMM. Crucial replaced all RAM.
Ran stable for a few weeks then BSOD's showed back up.
Memtest ran success.
I replaced the MOBO with an ASUS P5Q on Sept 13th.
Formatted C: and fresh install of W7 x64.
Ran fine for 7 days then started BSODs again.

I am at a loss, it could be other hardware I guess, hopefully your debugging research will help me pinpoint what to do next. It looks like I already replaced a good MOBO and wasted $120 and can't afford to shotgun approach replacing hardware or build a new machine.

The BSODs are random and different event ids. For what it might be worth.. Most of the BSODs happen in the middle of the night around 2:30am-3am.. weird.

I built this computer 3 years ago, however, have replaced a few components.
The HDDs are only about a year old.
The memory was replaced by Crucial in Jan of this year.
The mobo last week.

Thank you for any assistance and direction you can provide.

Snypar

 

[usasma]

IME, the Asus P5 series of boards may have some issues with Memory management and Win7 that may cause BSOD's. I'd suggest visiting both the Asus and the Crucial website for the correct timings/settings/voltages - and then set these timings/settings/voltages manually in the BIOS (in other words, DON'T use the "Auto" setting for memory).

4 memory dumps all from the same day.
3 different BSOD errors cited
4 different causes blamed
Probably a hardware/compatibility error, but too soon to tell for sure.

Although I have no concrete reason to suspect your Norton, please try this to rule it out:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the Norton from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Norton using this free tool: KB Article Not Found
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's

Beyond that, please run Driver Verifier according to these directions to see what it can tell us. Let it generate several BSOD errors so we can have a comparison:

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: Tue Sep 21 03:45:15.002 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:29.688
BugCheck F4, {3, fffffa80079f5950, fffffa80079f5c30, fffff80002d915d0}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xF4_C0000005
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`079f5950 fffffa80`079f5c30 fffff800`02d915d0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 20 14:39:56.778 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:25.838
Probably caused by : ntkrnlmp.exe ( nt!RtlDeleteNoSplay+96 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  chrome.exe
Bugcheck code 00000050
Arguments fffffe80`0944f6a8 00000000`00000001 fffff800`02a5ecc2 00000000`00000007
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 20 14:35:36.179 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:26.864
Probably caused by : cdd.dll ( cdd!memcpy+bd )
BUGCHECK_STR:  0x1a_5002
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
Bugcheck code 0000001A
Arguments 00000000`00005002 fffff700`01080000 00000000`00001271 00001670`fffffffe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 20 13:54:18.896 2010 (UTC - 4:00)
System Uptime: 3 days 0:29:39.561
Probably caused by : memory_corruption ( nt!MiCaptureAndResetWorkingSetAccessBits+97 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
Bugcheck code 00000050
Arguments fffff6fd`5001a498 00000000`00000000 fffff800`02b81ef7 00000000`00000002
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[karlsnooks]

I've never understood why you don't turn off verifier the easy way:
Go to an elevated command prompt and type verifier /reset

If for some reason you can't get to an elevated command prompt from safe mode, then you can always get to an elevated command prompt using a System Repair Disc.

 

[usasma]

That will work too.

My instructions presume that it's the first time the user has seen the Verifier interface and that it'll be easiest for them to go back into it in order to stop Verifier from running.

Also, the user may not be familiar with the use of the Command Prompt or with how to launch it elevated (run as administrator).

 

[karlsnooks]

You also might want to consider referring to the tutorial:
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[usasma]

While I have all the respect in the world for Jonathan King, I'll continue to use my method.

This method was discussed by Mark Russinovich at TechEd 2006. I've added a bit to it, but follow his basic principles (applying all possible tests to all possible 3rd party drivers that are being loaded).