Blue Screen of Death!

hahatheman · 29 Apr 2012

I get a blue screen of death. It seems to happen when multi-tasking, but no specific program seem to cause it. When I first played MW3, I had a blue screen problem that was remedied by a BIOS update. My system is installed on the SSD, I know this is new tecnology, would this cause my blue screen? I will post the details when it happens next time.

zigzag3143 · 29 Apr 2012

"It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash.

As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.

If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating.

Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.

Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.

If so, it might be as simple as dust buildup and subsequently inadequate cooling.

I would download cpu-z and gpu-z (both free) and keep an eye on the video temps

STOP 0x116: VIDEO_TDR_ERROR troubleshooting

hahatheman · 29 Apr 2012

I will keep an eye on the heat. I updated my video card driver. I will see if I have any more problems and get send a validating reply.

hahatheman · 11 Jul 2012

Blues screen strikes again! No clue what needs to be done. Here is some screen shots of the GPU-Z and CPU-Z. My guess is that I need to put my fan speed more like 50%.

Sorry for the late reply, I just got my computer back up and running. I had 2x power supply go bad, and 1x motherboard.

usasma · 12 Jul 2012

Please provide a new copy of the jcgriff2 reports: https://www.sevenforums.com/crashes-d...tructions.html

hahatheman · 13 Jul 2012

This Operating system was bought with the computer on 4/16/2012 along with the rest of the computer. My guess on this problem is the graphics card, (HIS H777F1G2M Radeon HD 7770 GHz Edition 1GB 128-bit GDDR5 PCI Express 3.0 x16 HDCP Ready Video Card) I put the invoice so the details are inside.

This is a custom computer, it's original OS is windows 7

I hope I provided enough information.

Thank you for you time.

usasma · 13 Jul 2012

Interestingly your system has 16 gB of RAM, and all but 806 mB is being used!!!
That's not good!
From what I can tell, the system is thrashing your hard drive with pagefile reads - indicating that something in virtual memory is using the heck out of your RAM

Please use this procedure to let us know what's using the most in each column on your system:

Task Manager:
Also, you can monitor the system for excessive resource consumption. To do this, open up Task Manager by right clicking on the Task Bar.
Then select the Processes tab.
Then select the "Show processes from all users" button (in the lower left)
Then select the View menu item, then select "Select columns"
In the Select columns window, place checkmarks next to I/O Reads and I/O Other.
Click OK to accept the changes.
Resize the Task Manager window so you can see the most of the columns.
Wait for the system to freeze/take up the resources.
Look at all of the columns to see if there's anything that looks excessively high - if so, let us know the Image name of the process (clicking on the column header will sort by that column).
NOTE: If the image name is svchost.exe - right click on it and select "Go to Service(s)" and let us know the Services that it highlights
FWIW - System Idle Process is supposed to have high CPU readings - anything else with high CPU readings is an issue.

In the past I've seen issues with the AsRock XFast LAN and XFast USB - please uninstall them.
FNETURPX.SYS dates from 2008 and must be removed. It belongs to the AsRock XFast USB program.

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
Please uninstall the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): DuplexSecure - FAQ

You have at least 2 security apps installed (PC Tools Security and Avast). Please uninstall all but the Avast while we're testing. Then make sure that the Windows Firewall is running.
When done (and the system is stabilized again), feel free to choose one (and only one) security program. Multiple antivirus programs can cause issues like this - as can multiple 3rd party firewall programs.

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Win7 systems.

Please uninstall all AMD/ATI video stuff from Control Panel...Programs...Uninstall a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Uninstall". Reboot for changes to take affect.

Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

Both memory dumps (I only ran the last 2 since you just got it back) point at video with STOP 0x116 errors. After doing the stuff above, try this series of troubleshooting steps: STOP 0x116: VIDEO_TDR_ERROR troubleshooting

Just FYI - with the video errors and the RAM/pagefile consumption - there may be several problems here. We'll continue to work on this until it's solved.

If the above steps don't stop the BSOD's, please zip up and upload any new memory dumps with your next post - and we'll see what we can figure out from there.

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:


AODDriver2.sys     Mon Dec 19 02:30:03 2011 (4EEEE7FB)
AsrAppCharger.sys  Fri Jun 11 02:37:12 2010 (4C11D998)
AsrHidFilter.sys   Thu Feb 17 04:50:28 2011 (4D5CEF64)
AtihdW76.sys       Tue Dec 06 04:14:25 2011 (4EDDDCF1)
EtronHub3.sys      Fri Jan 28 16:46:45 2011 (4D433945)
EtronXHCI.sys      Fri Jan 28 16:46:43 2011 (4D433943)
FNETURPX.SYS       Fri Oct 03 22:27:02 2008 (48E6D476)
GEARAspiWDM.sys    Mon May 18 08:17:04 2009 (4A1151C0)
PCTBD64.sys        Mon Mar 19 21:17:51 2012 (4F67DABF)
PCTCore64.sys      Thu Mar 15 21:11:21 2012 (4F629339)
PCTSD64.sys        Mon Mar 19 20:25:37 2012 (4F67CE81)
PCTSDInj64.sys     Mon Jan 23 00:47:07 2012 (4F1CF45B)
PctWfpFilter64.sys Mon Mar 19 21:02:30 2012 (4F67D726)
TfFsMon.sys        Wed Nov 09 14:59:01 2011 (4EBADB85)
TfNetMon.sys       Wed Nov 09 14:59:04 2011 (4EBADB88)
TfSysMon.sys       Wed Nov 09 14:59:05 2011 (4EBADB89)
amdiox64.sys       Thu Feb 18 10:17:53 2010 (4B7D5A21)
amdxata.sys        Fri Mar 19 12:18:18 2010 (4BA3A3CA)
aswFsBlk.SYS       Tue Mar 06 19:01:31 2012 (4F56A55B)
aswMonFlt.sys      Tue Mar 06 19:01:51 2012 (4F56A56F)
aswSP.SYS          Tue Mar 06 19:04:03 2012 (4F56A5F3)
aswSnx.SYS         Tue Mar 06 19:04:05 2012 (4F56A5F5)
aswTdi.SYS         Tue Mar 06 19:01:56 2012 (4F56A574)
aswrdr2.sys        Tue Mar 06 19:02:19 2012 (4F56A58B)
atikmdag.sys       Thu Mar 08 23:04:49 2012 (4F598161)
atikmpag.sys       Thu Mar 08 22:58:02 2012 (4F597FCA)
cfosspeed6.sys     Mon Jul 04 09:18:51 2011 (4E11BDBB)
cpuz135_x64.sys    Fri Mar 09 03:56:55 2012 (4F59C5D7)
dtsoftbus01.sys    Mon Oct 17 08:12:30 2011 (4E9C1BAE)
k57nd60a.sys       Tue May 10 00:42:30 2011 (4DC8C236)
pctDS64.sys        Mon Feb 27 19:40:33 2012 (4F4C2281)
pctEFA64.sys       Mon Feb 27 19:42:31 2012 (4F4C22F7)
pctgntdi64.sys     Mon Mar 19 20:56:43 2012 (4F67D5CB)
pctplsg64.sys      Mon Mar 19 20:42:28 2012 (4F67D274)
rikvm_38F51D56.sys Fri Oct 29 06:52:09 2010 (4CCAA759)
rtl8192se.sys      Fri Apr 30 04:04:26 2010 (4BDA8F0A)
usbaapl64.sys      Tue Jan 10 19:56:04 2012 (4F0CDE24)
usbfilter.sys      Wed Oct 07 03:44:08 2009 (4ACC46C8)

Code:


Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\063012-14040-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sat Jun 30 14:25:33.749 2012 (UTC - 4:00)
System Uptime: 0 days 14:45:19.857
BugCheck 116, {fffffa8016786010, fffff88007716ae4, 0, d}
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : atikmpag.sys ( atikmpag+7ae4 )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
Bugcheck code 00000116
Arguments fffffa80`16786010 fffff880`07716ae4 00000000`00000000 00000000`0000000d
BiosVersion = P1.70
BiosReleaseDate = 05/29/2012
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\063012-18330-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sat Jun 30 21:45:44.104 2012 (UTC - 4:00)
System Uptime: 0 days 2:11:09.212
BugCheck 116, {fffffa8026edf010, fffff88004324ae4, 0, d}
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : atikmpag.sys ( atikmpag+7ae4 )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
Bugcheck code 00000116
Arguments fffffa80`26edf010 fffff880`04324ae4 00000000`00000000 00000000`0000000d
BiosVersion = P1.70
BiosReleaseDate = 05/29/2012
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Blue Screen of Death!

Blue Screen of Death!

Thank You

Problem unsolved

Back to you