 | |
| |
| 12 Dec 2011 | #1 |
| | BSOD only at restart/shutdown Windows 7: x64 home Original installed OS is on the system OEM installed Hardware is about year and half old (new video card about 1 month old) OS installation is year and half old, I have not reinstalled OS I only get BSOD when I click restart or shutdown. It happens rather immediately after I click them (the "shutting down" screen doesn't even pop up, crashes straight from desktop). I have noticed this only tends to happen after I have played a computer game (oddly enough, it doesn't crash at all while I am playing and even when I close the game program, my computer functions normally with all other programs, browsing, etc). I have also noticed that when I have not played any games, the machine will shut down normally. I have tried to install updated graphics drivers, but this has not corrected the issue, not sure what else to do at this point, any help would be greatly appreciated! Thanks! |
My System Specs | |
| 12 Dec 2011 | #2 |
| | 
Quote: Originally Posted by capobello  Windows 7: x64 home Original installed OS is on the system OEM installed Hardware is about year and half old (new video card about 1 month old) OS installation is year and half old, I have not reinstalled OS I only get BSOD when I click restart or shutdown. It happens rather immediately after I click them (the "shutting down" screen doesn't even pop up, crashes straight from desktop). I have noticed this only tends to happen after I have played a computer game (oddly enough, it doesn't crash at all while I am playing and even when I close the game program, my computer functions normally with all other programs, browsing, etc). I have also noticed that when I have not played any games, the machine will shut down normally. I have tried to install updated graphics drivers, but this has not corrected the issue, not sure what else to do at this point, any help would be greatly appreciated! Thanks! These crashes were caused by memory corruption (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!!! 1-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 or 6 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. 2-Driver verifier Quote: I'd suggest that you first backup your data 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). In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu . 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). 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. Further Reading Using Driver Verifier to identify issues with Windows drivers for advanced users |
| My System Specs |
| 12 Dec 2011 | #3 |
| | thanks for the prompt reply. okay, to start off, I ran driver verifier off the bat, after the reboot, I experienced frequent BSODs until I had to use system restore to get back to an operational level. How do I examine the results of the damage verifier to determine which drivers are causing the problem? |
| My System Specs |
| . |
| |
| 12 Dec 2011 | #4 |
| |
Quote: Originally Posted by capobello thanks for the prompt reply. okay, to start off, I ran driver verifier off the bat, after the reboot, I experienced frequent BSODs until I had to use system restore to get back to an operational level. How do I examine the results of the damage verifier to determine which drivers are causing the problem? |
| My System Specs |
| 12 Dec 2011 | #5 |
| | okay, here is the latest DMP file I pulled...I also have several from yesterday, dated 12/11 that I added as well... |
| My System Specs |
| 12 Dec 2011 | #6 |
| |
Quote: Originally Posted by capobello okay, here is the latest DMP file I pulled...I also have several from yesterday, dated 12/11 that I added as well... I do notice Symantec which is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST http://us.norton.com/support/kb/web_...080710133834EN http://www.microsoft.com/security_essentials/ Old drivers needing updating Code: bcm4sbxp.sys 11/21/2006 7:25:43 AM 0x90cbe000 0x90ccf000 0x00011000 0x4562f047 stwrt.sys 5/10/2007 11:01:29 AM 0x8f76c000 0x8f7bf000 0x00053000 0x464341d9 rimsptsk.sys 7/29/2007 8:42:56 PM 0x90d2e000 0x90d42000 0x00014000 0x46ad4220 rixdptsk.sys 7/29/2007 9:54:01 PM 0x90d42000 0x90d94000 0x00052000 0x46ad52c9 rimmptsk.sys 2/15/2008 4:01:16 AM 0x90d1d000 0x90d2e000 0x00011000 0x47b554dc VSTCNXT3.SYS 10/15/2008 7:29:13 PM 0x93316000 0x933cb000 0x000b5000 0x48f68ad9 VSTAZL3.SYS 10/15/2008 7:30:03 PM 0x8f600000 0x8f63d000 0x0003d000 0x48f68b0b VSTDPV3.SYS 10/15/2008 7:32:04 PM 0x93214000 0x93316000 0x00102000 0x48f68b84 igdkmd32.sys 9/23/2009 2:18:09 PM 0x8fe3a000 0x90343000 0x00509000 0x4aba7471 bcmwl6.sys 10/12/2010 12:22:42 PM 0x90828000 0x90c38000 0x00410000 0x4cb49962 SynTP.sys 3/31/2011 8:28:27 PM 0x91e31000 0x91f75680 0x00144680 0x4d952a3b epfwwfp.sys 6/28/2011 2:28:47 AM 0x81fd6000 0x81fe7000 0x00011000 0x4e0982af epfw.sys 6/28/2011 2:28:52 AM 0xa7ce2000 0xa7d0a000 0x00028000 0x4e0982b4 ehdrv.sys 6/28/2011 2:34:32 AM 0x8b3df000 0x8b3ff000 0x00020000 0x4e098408 tdrpman.sys 7/6/2011 2:14:20 AM 0x82023000 0x820dc6a0 0x000b96a0 0x4e140b4c EpfwLWF.sys 7/11/2011 11:18:29 AM 0x8eed9000 0x8eee5000 0x0000c000 0x4e1b2255 timntr.sys 7/12/2011 12:45:32 PM 0x81b48000 0x81bdb380 0x00093380 0x4e1c883c Quote: - search Google for the name of the driver - compare the Google results with what's installed on your system to figure out which device/program it belongs to - visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager). - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program. - - Driver manufacturer links are on this page: Drivers and Downloads |
| My System Specs |
| 12 Dec 2011 | #7 |
| | okay, to review, I will uninstall symantec and test to see if this has corrected the problem. Also, go through each of the drivers listed above and check to see if there are updates, is there anything else I need to do? Thanks again for all your help! |
| My System Specs |
| 13 Dec 2011 | #8 |
| |
Quote: Originally Posted by capobello okay, to review, I will uninstall symantec and test to see if this has corrected the problem. Also, go through each of the drivers listed above and check to see if there are updates, is there anything else I need to do? Thanks again for all your help! |
| My System Specs |
| 13 Dec 2011 | #9 |
| | okay, I utilized the link provided to remove all of the symantec software from machine, however, after reboot, I launched a game for 5 mins and then attempted to shutdown afterwards, and got the same BSOD error... here is the latest DMP any ideas what would still be triggering the crash at shutdown? |
| My System Specs |
| 13 Dec 2011 | #10 |
| |
Quote: Originally Posted by capobello okay, I utilized the link provided to remove all of the symantec software from machine, however, after reboot, I launched a game for 5 mins and then attempted to shutdown afterwards, and got the same BSOD error... here is the latest DMP any ideas what would still be triggering the crash at shutdown? |
| My System Specs |
 |
BSOD only at restart/shutdown problems?
« BSOD while playing certain games, (skyrim, eve online, LoL)
|
BSOD while playing Dirt 2, Is becoming more occurnet in games ? »
| Thread Tools | |
| Similar help and support threads for: BSOD only at restart/shutdown | ||||
| Thread | Forum | |||
| BSOD shutdown then restart | BSOD Help and Support | |||
| BSOD at shutdown/restart of pc | BSOD Help and Support | |||
 BSOD on shutdown/restart | BSOD Help and Support | |||
| BSOD when shutdown/restart | BSOD Help and Support | |||
| Shutdown / Restart = BSOD | BSOD Help and Support | |||
All times are GMT -5. The time now is 04:06 PM.
