 | |
| |
| 09 Apr 2012 | #1 |
| | BSOD ~ (nt+0x7CD40) Dumps with perfmon report included in rar attached. (Edit - Forgot to add, I am running Windows 7: Home Premium x64) Getting somewhat frequent BSOD's while doing just about anything. Seems to happen mostly when playing games though. From what I can tell it isn't a hardware issue as I have been searching the net for fixes related to these error codes. Haven't had an issue for about a week until today. Crashed with no BSOD but the dump said it was the same issue anyway. Thinking it's a driver issue somewhere but I am unsure of how to figure out which one(s) it would be. Any and all help is appreciated.  |
My System Specs | |
| 09 Apr 2012 | #2 |
| | These crashes were caused by memory corruption/exception (Cx05) probably a driver. Please run these two tests to verify your memory and find which driver is causing the problem. * If you are overclocking anything reset to default before running these tests. In other words STOP!!! * If you have Raid update its Driver. Memtest. Quote: *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool *Boot from the CD, and leave it running for at least 5-7 passes. Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots. Any errors are indicative of a memory problem. If a known good stick fails in a motherboard slot it is probably the slot. Driver verifier Quote: 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/Windows 7 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. |
| My System Specs |
| 09 Apr 2012 | #3 |
| | Please do JMH's suggestions first but in addition you have a file that is known to cause BSOD's. Please remove. Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller DuplexSecure - Downloads DuplexSecure - FAQ when you're done you can use this Freeware: MagicISO Virtual CD/DVD-ROM (MagicDisc) in its place Using MagicISO to create ISO image files |
| My System Specs |
| . |
| |
| 09 Apr 2012 | #4 |
| | Not overclocking and I don't have Raid. I have tried to run verifier previously, system crashed before even getting to Windows boot screen. Went via Safe Mode and disabled it again. Not sure what to do about this... Will run Memtest overnight for a few passes and will see how it goes. Have uninstalled Daemon Tools Lite and will now try MagicIso as suggested. |
| My System Specs |
| 09 Apr 2012 | #5 |
| | Ran Memtest over night for 10 passes, showed no errors. Guess I shall try the driver verifier again. |
| My System Specs |
| 09 Apr 2012 | #6 |
| | 
Quote: Originally Posted by R4ptor  Ran Memtest over night for 10 passes, showed no errors. Guess I shall try the driver verifier again. (oops - Can a mod delete this post?) |
| My System Specs |
| 09 Apr 2012 | #7 |
| | Driver Verifier didn't crash my pc on startup, let's see how long it takes for another BSOD. Maybe it was Daemon Tools causing it after all?  |
| My System Specs |
| 09 Apr 2012 | #8 |
| | Re Verifier.. Quote: 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. Should you get more BSOD's submit the DMPS here for analysis please. |
| My System Specs |
| 10 Apr 2012 | #9 |
| | About 9 hours in, still no BSOD. If I do get one, I will surely post the dump here for review. After the ~36 hours, I should reboot+stop driver verifier, yes? |
| My System Specs |
| 10 Apr 2012 | #10 |
| |
Quote: Originally Posted by R4ptor About 9 hours in, still no BSOD. If I do get one, I will surely post the dump here for review. After the ~36 hours, I should reboot+stop driver verifier, yes? |
| My System Specs |
