Solved BSOD only at restart/shutdown

[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!

 

[zigzag3143]

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.

*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.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

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/Win7 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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[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?

 

[zigzag3143]

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?

Unless you can read DMP files upload them here.

 

[capobello]

okay, here is the latest DMP file I pulled...I also have several from yesterday, dated 12/11 that I added as well...

 

[zigzag3143]

okay, here is the latest DMP file I pulled...I also have several from yesterday, dated 12/11 that I added as well...

Probably caused by Symantec. I would remove and replace it with Microsoft Security Essentials

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_view.jsp?wv_type=public_web&docurl=20080710133834EN

http://www.microsoft.com/security_essentials/



Old drivers needing updating

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

How To Find Drivers:

- 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.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

 

[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!

 

[zigzag3143]

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!

I would just do symantec first. It is probably the cause.

 

[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?

 

[zigzag3143]

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?

This oe is inconclusive. You have removed symantec. I do notice that Agent.exe has been running in each of the crashes. Might want to remove it.

 

[capobello]

hmm, I am having trouble locating the directory for agent.exe

 

[capobello]

just wanted to provide an update and get your thoughts:

I think I have isolated the cause to my networking card. I ran a third party DMP software reader, and all of the errors were the same:


Bugcheck code: 0x76(0x0, 0xfffffa800e0e5b30, 0x2, 0x0)
Error: Process has locked pages
Description: NT kernel & system
Bug check description: This bug check indicates that a driver failed to release locked pages after an I/O operation, or that it attempted to unlock pages that were already unlocked. The crash took place in the windows kernel.


I checked online to see if people had similar errors, found many, in particular, found one user who linked it to his networking card, same make and model as mine: Killer Xeno Pro

As a test, I removed the drivers for the network card, then launched a pc game for 10 mins, then proceeded to shut down the machine, upon which there was NO BSOD.

However, during the reboot, I received a BSOD shortly after windows started, which was something that has not occurred before.

Every reboot afterwards also resulted in BSOD, with me not even being able to get into Windows. Luckily, I had a back up disc, so I was able to boot from that, and when back at desktop, I was able to run system restore and restored system to before driver was deleted, so now system is operating with out BSOD at startup.

Unfortunately, I do not have any spare NICs available, but I will invest in a cheaper Intel card as I believe this should eliminate the BSODs.

Based on the situations above,does this sound like it could be the problematic driver?

Thanks

 

[zigzag3143]

just wanted to provide an update and get your thoughts:

I think I have isolated the cause to my networking card. I ran a third party DMP software reader, and all of the errors were the same:


Bugcheck code: 0x76(0x0, 0xfffffa800e0e5b30, 0x2, 0x0)
Error: Process has locked pages
Description: NT kernel & system
Bug check description: This bug check indicates that a driver failed to release locked pages after an I/O operation, or that it attempted to unlock pages that were already unlocked. The crash took place in the windows kernel.


I checked online to see if people had similar errors, found many, in particular, found one user who linked it to his networking card, same make and model as mine: Killer Xeno Pro

As a test, I removed the drivers for the network card, then launched a pc game for 10 mins, then proceeded to shut down the machine, upon which there was NO BSOD.

However, during the reboot, I received a BSOD shortly after windows started, which was something that has not occurred before.

Every reboot afterwards also resulted in BSOD, with me not even being able to get into Windows. Luckily, I had a back up disc, so I was able to boot from that, and when back at desktop, I was able to run system restore and restored system to before driver was deleted, so now system is operating with out BSOD at startup.

Unfortunately, I do not have any spare NICs available, but I will invest in a cheaper Intel card as I believe this should eliminate the BSODs.

Based on the situations above,does this sound like it could be the problematic driver?

Thanks

Its possible. Just curious that agent.exe was running in every single crash. You might want to run mawarebytes to ensure agent.exe isnt malware.

 

[capobello]

got it, I will run malwarebytes tonight, I believe I am due for one...

Still having trouble locating agent.exe as well, did searches on the C drive and results came up with nothing

 

[zigzag3143]

got it, I will run malwarebytes tonight, I believe I am due for one...

Still having trouble locating agent.exe as well, did searches on the C drive and results came up with nothing

Had you googled it you would have seen it is game related

agent.exe - Google Search

 

[capobello]

I did google it yesterday, and came across an article discussing as much...

I deleted the beta software, and everything seems to have been corrected, I did a shutdown/restart after a game launch and there was no BSOD...

I will attempt again tonight, but I think the issue has been corrected, once confirmed, I will mark as solved...

Thanks again for all your assistance!

 

[zigzag3143]

I did google it yesterday, and came across an article discussing as much...

I deleted the beta software, and everything seems to have been corrected, I did a shutdown/restart after a game launch and there was no BSOD...

I will attempt again tonight, but I think the issue has been corrected, once confirmed, I will mark as solved...

Thanks again for all your assistance!

Good luck and let us know if you need help

 

[capobello]

problem has been corrected, removal of agent.exe has stopped all BSODs, closing this one out as solved!

Thanks

 

[zigzag3143]

problem has been corrected, removal of agent.exe has stopped all BSODs, closing this one out as solved!

Thanks

Good luck


Ken