Solved BSOD - can't get to restore point

[mjm64]

I bought an APC ups and loaded their software. It says it is win7 compatible. It worked for about an hour then started to BSOD.

I can't even run long enough to make a backup copy of my data in in7. Thank heaven for Hirens BootCD.

I got the 5 dumps here. View attachment 72728

I have been through this before when I first installed Win7. If I loaded any of the patches from Windows Update, it Blue Screened.

Is this just a flaky hardware that I have.. or is there something that windows just doesn't like. Everything is supposed to be windows 7 compatible.

I am stuck re-installing my whole machine again as I can't do anything without it BSOD. Like, try and run control pannel, BSOD, try and bring up manange computer, BSOD...

HELP

Matt.

 

[usasma]

5 memory dumps with 2 different STOP errors and 2 different causes blamed.

I'd first suggest this free memory test: Memory Diagnostics (read the details at the link)
If that passes, then I'd suggest running 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 - by using the Windows installation disk to get into Startup Repair).

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

Summary of the BSOD's:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu May 13 12:08:07.283 2010 (GMT-4)
System Uptime: 0 days 0:07:08.783
BugCheck 50, {fffff880085656b8, 1, fffff800022e49ba, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExAcquireFastMutex+1a )
BUGCHECK_STR:  0x50
PROCESS_NAME:  explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu May 13 12:00:19.511 2010 (GMT-4)
System Uptime: 0 days 0:04:10.822
BugCheck A, {fffff6fffffeff80, 0, 0, fffff80002eecc9e}
Probably caused by : memory_corruption ( nt!MiDispatchFault+de )
BUGCHECK_STR:  0xA
PROCESS_NAME:  InputPersonali
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu May 13 11:55:26.277 2010 (GMT-4)
System Uptime: 0 days 0:03:48.962
BugCheck A, {fffff703c5000190, 2, 0, fffff80002e9e0f1}
Probably caused by : memory_corruption ( nt!MiObtainSystemCacheView+125 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu May 13 11:50:59.631 2010 (GMT-4)
System Uptime: 0 days 0:04:49.942
BugCheck 50, {fffff88008f55218, 1, fffff80002e8a9ba, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExAcquireFastMutex+1a )
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu May 13 11:44:07.991 2010 (GMT-4)
System Uptime: 0 days 0:11:58.100
BugCheck 50, {fffff88007745ae8, 1, fffff80002ee69ba, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExAcquireFastMutex+1a )
BUGCHECK_STR:  0x50
PROCESS_NAME:  wininit.exe