New
#21
Random BSOD's on Windows 7 x64
-
-
New #22
Thank you zigzag, ive deleted the midi driver and there was no BSoD when i came home from work.
Although i got one not long after and the only thing i had done was plug-in an external HDD. Thank you for your time so far.
-
New #23
Im thinking your VMWare but the only way to be sure is to run driver verifier
Driver verifier
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 "Special Pool", "Force Pending I/O Requests" and "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.
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.Last edited by zigzag3143; 24 Feb 2012 at 23:25.
-
New #24
ok it looks like i will be uninstalling vmware as i got another BSoD.
Ive never have this many before. ill post the dmp file wile i take your advice from your last post. (although i don't have a second computer handy) :/
-
New #25
OK. i did as you said, i got a BSoD as soon as my home screen loaded. i did this twice and got the same error
-
New #26
Driver verified and Related to snapman.sys Snapshot API from Acronis. I would remove it at least to test.
-
New #27
Uninstalled Acronis and repeated my steps and no BSoD after left to run for an hour (ish)
then clicked vmware (knowing i will get a BSoD) and i did. so that will be next to uninstall.
Next i opened sony veges and i got a BSoD when trying to load my audio card (M-Audio) which i know the drivers can give BSoD but i set mine to "legacy" and has prevented it so far.
Also i recall when i installed Win7 (this time) i got random BSoD having only installing Chipset and GFX drivers (both up to date via there site). Although i do not have the minidmp of this i remeber is saying "0x00000001" i know its a stab in the dark but any ideas?
The dmps files are from after i deleted Acronis
-
-
New #29
ok. uninstalled vmware and m-audio drivers and repeted steps as before and got a BSoD wile idle. (wonder what now)
-
New #30
Three pages later...
Just a thought.
It might be quicker to get your computer up & running again normally by doing a Clean Install.
FYI.
Clean Install Windows 7
Quote
Related Discussions