Multiple BSOD help, please?

[cstoddart]

Hi. I've never posted in one of these forums before because so far I've been able to figure out stuff on my own, but I'm way over my head with this one. I read the instructions and did the stuff before I posted, so I'll be attaching the zip file on here to see if somebody out there can help me, but first I'm going to answer the questions that I'm supposed to answer and tell the story a little.

The computer that's acting funky is an Acer Aspire 5251-1513, operating with windows 7 x64. The OS came pre-installed and has never been re-installed since its purchase last November -so as you can see, it's not nearly old enough to be acting this way.

What I did do was restore it to factory settings last week because of some Microsoft update; it installed automatically and after that it just kicked and I couldn't restore it to an earlier point, either, because Windows refused to start up. These files I'm attaching are from after that crash; I've received three BSOD's thus far. I realize that some stuff might not work okay until all the backed-up updates from six months are done, but the thing really is crashing left and right. So, if somebody could help me figure out what really is going on I would really, really be grateful. Thank you!

 

[usasma]

There are only 32 hotfixes installed on your system. Win7 has at least 60-70 hotfixes before Service Pack 1
Please visit Windows Update and get all the updates available for your system.

Then, please run Driver Verifier according to these directions:

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]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\053111-49904-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue May 31 16:29:43.829 2011 (UTC - 4:00)
System Uptime: 0 days 2:05:09.250
BugCheck E4, {1, fffff88002f62c40, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1056e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xE4
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xE4_nt!_??_::FNODOBFM::_string_+1056e
Bugcheck code 000000E4
Arguments 00000000`00000001 fffff880`02f62c40 00000000`00000000 00000000`00000000
BiosVersion = V1.04
BiosReleaseDate = 04/23/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\053111-42588-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue May 31 14:24:08.645 2011 (UTC - 4:00)
System Uptime: 0 days 0:11:02.066
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteFcb+3f6 )
BUGCHECK_STR:  0xc2_7_NtfF
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc2_7_NtfF_Ntfs!NtfsDeleteFcb+3f6
Bugcheck code 000000C2
Arguments 00000000`00000007 00000000`00001097 00000000`0158030c fffff8a0`0d1775c0
BiosVersion = V1.04
BiosReleaseDate = 04/23/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052911-23836-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun May 29 07:36:14.654 2011 (UTC - 4:00)
System Uptime: 0 days 0:37:58.074
Probably caused by : ntkrnlmp.exe ( nt!RtlImageNtHeaderEx+3f )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  rundll32.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!RtlImageNtHeaderEx+3f
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02e62047 00000000`00000000 000007ff`fffa0000
BiosVersion = V1.04
BiosReleaseDate = 04/23/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052311-49920-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon May 23 21:57:51.804 2011 (UTC - 4:00)
System Uptime: 0 days 0:28:29.240
BugCheck E4, {1, fffff88002f4dc40, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1056e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xE4
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xE4_nt!_??_::FNODOBFM::_string_+1056e
Bugcheck code 000000E4
Arguments 00000000`00000001 fffff880`02f4dc40 00000000`00000000 00000000`00000000
BiosVersion = V1.04
BiosReleaseDate = 04/23/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[cstoddart]

Thank you. You are very kind. Like I said, I had to restore the thing to factory settings last week and I've been slowly downloading the stuff, but it crashes often so I can't really ever finish or really figure out exactly what to do. I will try your suggestion tomorrow -not much to back up, really, it's totally clean right now so I can skip that bit- and cross my fingers that it works out. Thanks again very much for your suggestion.