Windows 7: Laptop Crashes w/ FSX, LOUD FANS, HOT TO TOUCH. Error Code 3221225485

mrcitadel2008 · 26 Apr 2012

I am having more problems recently with my laptop crashing completely (no power to anything) while playing Flight Simulator X. This mostly occurs only when playing FSX but tonight i have noticed my machine getting super hot and shutting down unexpectantly. The Fans also begin to speed up prior to shutdown. I have set the computer to maximize performance, disable start up items, etc. After researching this It seems this may be more of a hardware issue than software. Please help. I have attached the requested info. Any help would be most appreciated.

*I apologize for the lack of complete explanation. I am battling a kidney infection and it has truly taken a toll on me along while having to troubleshoot a Pesky Laptop

writhziden · 28 Apr 2012

Problem Devices:

Code:

Microsoft Virtual WiFi Miniport Adapter	{5D624F94-8850-40C3-A3FA-A4FD2080BAF3}\VWIFIMP\5&3E0E20C&0&01	This device is disabled.

Was the above intentional? If so, can you explain the reasoning for disabling it?

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\mrcitadel2008\Windows_NT6_BSOD_jcgriff2\042612-102196-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`03404000 PsLoadedModuleList = 0xfffff800`03648650
Debug session time: Thu Apr 26 17:14:52.996 2012 (UTC - 6:00)
System Uptime: 0 days 0:10:39.541
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80042fc170, fffff8800417802c, 0, 2}

*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+602c )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80042fc170, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800417802c, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP: 
atikmpag+602c
fffff880`0417802c 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`021bd9c8 fffff880`04321000 : 00000000`00000116 fffffa80`042fc170 fffff880`0417802c 00000000`00000000 : nt!KeBugCheckEx
fffff880`021bd9d0 fffff880`04320d0a : fffff880`0417802c fffffa80`042fc170 fffffa80`06130950 fffffa80`03cf1410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`021bda10 fffff880`043c7f07 : fffffa80`042fc170 00000000`00000000 fffffa80`06130950 fffffa80`03cf1410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`021bda40 fffff880`043f1b75 : 00000000`ffffffff 00000000`00009f6b 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`021bdb20 fffff880`043f02bb : 00000000`00000102 00000000`00000001 00000000`00009f6b 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`021bdb50 fffff880`043c32c6 : ffffffff`ff676980 fffffa80`03cf1410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`021bdbf0 fffff880`043efe7a : 00000000`00000000 fffffa80`06130950 00000000`00000080 fffffa80`03cf1410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`021bdd00 fffff800`0371afda : 00000000`fffffc32 fffffa80`04f6f8d0 fffffa80`03cea890 fffffa80`04f6f8d0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`021bdd40 fffff800`034719c6 : fffff800`035f5e80 fffffa80`04f6f8d0 fffffa80`04f5f440 fffffa80`04c53270 : nt!PspSystemThreadStartup+0x5a
fffff880`021bdd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+602c
fffff880`0417802c 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+602c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b9e3d99

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

Followup: MachineOwner
---------

The above crash was a 0x116 TDR crash.

Quote: Originally Posted by H2SO4

These are all stop 0x116 VIDEO_TDR_FAILURE conditions.

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.

The above quote was taken from http://www.sevenforums.com/crashes-d...tml#post280172, which is linked to in usasma's thread about this error. Closely follow the first three posts of usasma's thread outlining STOP 0x116: VIDEO_TDR_ERROR troubleshooting and proceed through each step. Let us know if you need further help.

I do note that your graphics card/display card driver is from 2010. There may be a driver update for the ATI graphics. For re-installing your graphics:

Download the drivers you want for your display card(s)
Click Start Menu
Click Control Panel
Click Uninstall a program
For AMD:
- Uninstall AMD Catalyst Install Manager if it is listed (this should remove all AMD graphics software and drivers)
- If AMD Catalyst Install Manager is not listed, use the following method to uninstall the graphics drivers:
  1. Click Start Menu
  2. Right Click My Computer/Computer
  3. Click Manage
  4. Click Device Manager from the list on the left
  5. Expand Display adapters
  6. Do the following for each adapter (in case you have multiple display cards)
    - Right click the adapter
    - Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
    - Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
    Alternatively:
    1. Login as an adminstrative user
    2. Click Start Menu
    3. Click Control Panel
    4. Click Hardware and Sound
    5. Click Device Manager (the last link under Devices and Printers)
    6. Expand Display adapters
    7. Do the following for each adapter (in case you have multiple display cards)
      - Right click the adapter
      - Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
      - Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
- Restart your computer after uninstalling drivers for all display cards
- Install the driver you selected for the display cards once Windows starts

Windows 7: Laptop Crashes w/ FSX, LOUD FANS, HOT TO TOUCH. Error Code 3221225485

Laptop Crashes w/ FSX, LOUD FANS, HOT TO TOUCH. Error Code 3221225485 problems?