Random BSOD in Windows 7. Help!

[NinjaTurtleSoup]

ok, i just recently built a new pc a couple weeks ago and my components are listed below. Iv been getting random BSOD while surfing the web with firefox and sometimes when the pc is idle. I even got a BSOD while installing windows 7 upgrade on top of a fresh install of windows 7. I have scanned my memory with memtestx86+ for 7 passes with no errors. Iv scanned both hard drives and i get no errors. my video card, and CPU were from my previous build and i did not have a single issue with them. I am including my memory dumps below so maybe someone here can shed some light on why this happening. Thanks

 

[usasma]

Not much info given by the BSOD's.

What did you scan your hard drive with? I suggest both of the following:

1 - HD Diagnostic

2 -

CHKDSK /R:
Run CHKDSK /R from an elevated (Run as adminstrator) Command Prompt.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.

You can also try these tests:

Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
Try this free stress test: http://www.mersenne.org/freesoft/

Beyond that, try 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"
- 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.

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

Here's a summary of the BSOD's:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Jan 26 02:13:36.753 2010 (GMT-5)
System Uptime: 0 days 0:15:41.470
BugCheck 50, {fffffa80029a8420, 0, fffff80002cbe2d0, 2}
Probably caused by : memory_corruption ( nt!MiRemoveNode+170 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  windeploy.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Jan 26 19:24:22.484 2010 (GMT-5)
System Uptime: 0 days 0:10:17.201
BugCheck 3B, {c0000005, fffff80003187ffd, fffff88002313070, 0}
Probably caused by : ntkrnlmp.exe ( nt!EtwpRundownNotifications+69 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  audiodg.exe