win 7 BSOD ZIP attached

Post #9 - 131full.zip (87.1 KB, 0 views)
Post #11 - 131full.zip (87.1 KB, 0 views)

Were these 2 uploads supposed to be identical?

You have 4 memory dumps, 3 of which are Verifier Enabled Memory Dumps - and they have 3 different errors and causes.

Most likely this is a hardware problem with your system, less likely is that there are 3 separate problems that we've gotta fix.

Please turn Driver Verifier off (Delete existing settings).

Then, let's start with these hardware diagnostics:

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)

Also, please run this test:

CHKDSK /R /F:
Run CHKDSK /R /F 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.

Please post back with the results and we'll move on to further troubleshooting.

Summary of the BSOD's:

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jan 31 04:58:28.207 2010 (GMT-5)
System Uptime: 0 days 0:15:08.003
BugCheck 1A, {41790, fffffa80007c8420, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jan 31 11:51:32.966 2010 (GMT-5)
System Uptime: 0 days 0:02:28.075
BugCheck C4, {f6, 134, fffffa8008350b30, fffff88002c186f6}
*** WARNING: Unable to verify timestamp for AsIO.sys
*** ERROR: Module load completed but symbols could not be loaded for AsIO.sys
Probably caused by : AsIO.sys ( AsIO+16f6 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  UpdateChecker.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jan 31 12:54:00.466 2010 (GMT-5)
System Uptime: 0 days 0:00:12.402
BugCheck 24, {1904fb, fffff880033759a8, fffff88003375200, fffff80002aefa83}
Probably caused by : Ntfs.sys ( Ntfs!NtfsNonCachedIo+23f )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jan 31 12:55:57.165 2010 (GMT-5)
System Uptime: 0 days 0:00:25.211
BugCheck A, {0, 2, 0, fffff80002ad90b6}
*** WARNING: Unable to verify timestamp for MCfilt64.sys
*** ERROR: Module load completed but symbols could not be loaded for MCfilt64.sys
Probably caused by : MCfilt64.sys ( MCfilt64+1817 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System

There's no use in running Driver Verifier at this point. It's not designed as a general troubleshooting tool, and it may actually cause BSOD's when there's nothing wrong.

It's good to hear that you're not having problems tho' - thanks for letting us know!