Solved Repeated shutdowns with Kernal Power Event ID 41

[dbvogt]

I’ve got a repeated shutdown problem with an HP dc7900 running Windows 7. My system started shutting down when the PC went into sleep mode. It continued until the original Nvidia video card failed. It was replaced by a local firm that said the system would shut down if hardware was failing. The new card is an ATI Radeon but the PC is still shutting down, 13 times this month. I disabled screen saver but the PC has just shut down while I was working. The Event Viewer tells me there is a Kernal Power event ID 41. Someone mentioned this may happen due to overheating but the fans are clean and no dust. There is a MEMORY.DMP file (dated 1/30/12, 10.04AM EDT) file but I cannot open it. It says it needs the administrator (me!). Windows asked me if I wanted to send a log to Microsoft and I said yes. The blue screen has a lot of data on it but it flashes by so quickly I can’t read it or capture it. The PC reboots immediately after the screen disappears.
Any way to open the file assuming it is readable in a text editor? Any suggestions as to fixing this problem? I really can't go on with the PC in this condition. Attached the JCGriff file, sorry about the RAR extension - it wipes out Zip usage.

Windows 7 32 bit. Original OS was Vista but a repair shop installed new Windows 7 after an HD crash in 2009. PC purchased 10/2008.

A Health Report html file was created but the instructions do not specify a filename, just extension. The Manage Attachments window says my title of SystemHealthReport.html is an "Invalid file."

 

[writhziden]

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


Loading Dump File [K:\BSODDmpFiles\dbvogt\013012-26473-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x82e52000 PsLoadedModuleList = 0x82f9b4d0
Debug session time: Mon Jan 30 08:03:29.668 2012 (GMT-7)
System Uptime: 0 days 4:04:33.058
Loading Kernel Symbols
...............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
............
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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

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

*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys

FAULTING_IP: 
atikmdag+105bc
938445bc 8bff            mov     edi,edi

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
948b3b74 93d1507b 00000116 87a00510 938445bc nt!KeBugCheckEx+0x1e
948b3b98 93d09937 938445bc 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d
948b3bbc 93d4592c 00000000 00000102 87811788 dxgkrnl!TdrIsRecoveryRequired+0xb8
948b3c34 93d6f944 fffffcfb 000e5985 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
948b3c5c 93d70065 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68
948b3c98 93d4c8f0 948b3c90 879bb810 872485f0 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1
948b3d28 93d713c9 87811788 82e89509 87811788 dxgmms1!VidSchiScheduleCommandToRun+0xaa
948b3d3c 93d71485 87811788 00000000 87856a48 dxgmms1!VidSchiRun_PriorityTable+0xf
948b3d50 8305afda 87811788 a5369bd8 00000000 dxgmms1!VidSchiWorkerThread+0x7f
948b3d90 82f031f9 93d71406 87811788 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmdag+105bc
938445bc 8bff            mov     edi,edi

SYMBOL_NAME:  atikmdag+105bc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49f1996c

FAILURE_BUCKET_ID:  0x116_IMAGE_atikmdag.sys

BUCKET_ID:  0x116_IMAGE_atikmdag.sys

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

Your display card or display card driver was unresponsive to the system signal telling it to respond. See http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html for steps to resolve this crash. Proceed carefully through the steps usasma lays out for you in the first three posts of that thread.

 

[dbvogt]

Thank you for the reply. Unfortunately, Furmark will not run - it says it reqires an Open GL2 compliant controller. I opened the case up and don't believe heat is the problem. My CPU is enclosed in a box with its own fan (total of 2 in the PC) and fins resembling those on an AC unit. No indication of excess heat at all. OTOH, it's odd that the replacement (presumed to be new) video card has a problem. I don't think it's a very good one - the Experience Index went down from 3.2 (Graphics) with the Nvidia to 2.0 with the ATI Radeon. HP currently recommends the original Nvidia Quadro NVS 290 PCie x 16 (256 MB for dual monitors) but doesn't sell it - it's an old model but still available. I emailed both Nvidia sales and HP asking for a replacement/upgrade model but neither replied. I would assume that a Quadro 300 with 512 MB would be faster but really don't know whether to go beyond that. Then that doesn't fix the Video error. Could be power supply problem which a card with more memory would likely exacerbate.

 

[writhziden]

You can check your temperatures just to be sure by downloading and installing HWiNFO64 Download and using the sensor-only mode of that program.

You can also test the PSU with http://www.sevenforums.com/hardware-devices/201055-psu-testing.html#post1688197 by Britton30. Do so carefully; we do not want any fried users on the forum.

 

[dbvogt]

OK, thanks. I tried to download HWINFO32 but got an error: "HW32_292.exe unsafe to download and was blocked by Smartscreen Filter. Next...

I'll try the PSU testing. Any suggestions as to a better video card assuming I find the problem?

What would CPU temperature have to do with the video card failing to respond?

 

[writhziden]

The video card may also be overheating. That is why HWINFO was recommended to check the GPU temperatures. Trust me, it is a trusted piece of software used by many of the gurus on these forums. Do not know why Microsoft complained.

 

[dbvogt]

Got it from CNET and no complaints from Smartscreen - its version 3.92-1500, not the latest. Sensor status:
Core Temp - current(F)
0 96.8
1 93.2
2 86.0
4 86.0
ThermMon is OK for each core. HWINFO is very nice software and I appreciate your help. I felt the fins on the ATI card and they're hot. Do you think this is a bad card or is there something in the system causing good cards to fail?

 

[writhziden]

CPU temperatures look good for idle. What do they get up to when you game? Also, did HWINFO give any GPU data? It will on most systems, but it depends on whether there is a sensor built in. Can you start logging in sensor-only mode and re-create the crash? That will save all sensor info in a CSV file that you can zip and upload here.

As to whether it is the card that is failing or an underlying problem, we will have to go through some steps to determine that. It could be that your video card driver is corrupted and needs to be re-installed or updated. Do the following steps whether you currently have the latest driver installed or not.

1. Download the latest drivers for your display card(s)
2. Click Start Menu
3. Right Click My Computer/Computer
4. Click Manage
5. Click Device Manager from the list on the left
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
8. Restart your computer after uninstalling drivers for all display cards
9. Install the latest driver for the display cards once Windows starts

Alternatively:

1. Login as an adminstrative user
2. Download the latest drivers for your display card(s)
3. Click Start Menu
4. Click Control Panel
5. Click Hardware and Sound
6. Click Device Manager (the last link under Devices and Printers)
7. Expand Display adapters
8. 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
9. Restart your computer after uninstalling drivers for all display cards
10. Install the latest driver for the display cards once Windows starts

 

[dbvogt]

For ATI GPU, HWINFO has 371.3 MHz for Clock and 195.8 MHz for Memory Clock. I never had much time for gaming so cannot tell what impact that has on the graphics card. Reinstalled driver. The PC would generally crash when the screensaver was running so I went back to the same screen saver settings as before. No crash but I ran Google Earth and the system crashed after a minute or so. Only a slight increase in Core 0 of the CPU – up to about 103F. ATI card fins still almost too hot to touch. No CSV file was found with today’s date, just a Memory.dmp which I cannot upload as the system says I need the administrator - me - to open. I have a second 500 gig. SATA drive installed so that may stress the power supply some. Thinking back, the Nvidia card failed years after the second drive was installed. The only thing left is a possible failure in the power supply. The image in the PSU test message is so small that the numbers are hard to read.

 

[writhziden]

For ATI GPU, HWINFO has 371.3 MHz for Clock and 195.8 MHz for Memory Clock. I never had much time for gaming so cannot tell what impact that has on the graphics card. Reinstalled driver. The PC would generally crash when the screensaver was running so I went back to the same screen saver settings as before. No crash but I ran Google Earth and the system crashed after a minute or so. Only a slight increase in Core 0 of the CPU – up to about 103F. ATI card fins still almost too hot to touch. No CSV file was found with today’s date, just a Memory.dmp which I cannot upload as the system says I need the administrator - me - to open. I have a second 500 gig. SATA drive installed so that may stress the power supply some. Thinking back, the Nvidia card failed years after the second drive was installed. The only thing left is a possible failure in the power supply. The image in the PSU test message is so small that the numbers are hard to read.

If you click on an image on the forums, it gets bigger. You can also save it to your computer and open it and zoom in.

HWINFO32 has a logging feature in its sensor-only mode. Start that logging and save the CSV file in your Documents folder, not the Windows folder. The Windows folder requires special permissions to access, so it will not save the log there without running in an elevated mode. Much better and safer is saving in the Documents folder.

 

[dbvogt]

Got the image, thanks. This system can be crashed at will just by rapidly zooming out from a Google Earth image. That never happened before. The 1:35 PM crash a few minutes ago added to a HWINFO created CSV file. The only thing I can think of is the power supply is failing and that causes the video card to overheat. If that's the case, I wonder if replacements are available.

How do people capture the blue screen with text on it, it flashes so quickly on screen then the system reboots?

 

[writhziden]

Nothing obvious in the values. See if you can get the GPU temperatures using the GPU-Z Video card GPU Information Utility.

 

[dbvogt]

Nothing about temperatures. The ATI is probably pretty old technology. I really need to get a better card – at least as good, preferably better than the Nvidia Quadro 290.
Temperature from a mercury laboratory thermometer shows the base plate of the fins to be 140 degrees (F). The RAR file has a log and two screen captures from the program.

 

[writhziden]

Sorry you are having to go through all these steps. I am just hesitant to tell you to go out and replace the PSU when the graphics card may be at fault or an underlying driver may be causing conflicts.. 60 Celsius is a reasonable temperature for a graphics card, if that is the temperature of the card itself (which it probably is, +/- 5 Celsius). I would say temperature is not the culprit in this instance. Still not sure if it is the card or PSU or an underlying driver causing the crashes. Let's test for underlying drivers.

An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:

a. Backup your system and user files
b. Create a system restore point
c. If you do not have a Windows 7 DVD, Create a system repair disc
d. Run Driver Verifier

If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.

Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.​

 

[dbvogt]

Sorry you have to go through all these steps too! I'm logged in on a laptop as the PC is cycling through BSODs. It probably should be shut down and smaller sets of MS drivers selected. This will take several days to sort out as it has yet to boot with all MS drivers selected. Again, thank you for your help.

 

[writhziden]

Sorry you have to go through all these steps too! I'm logged in on a laptop as the PC is cycling through BSODs. It probably should be shut down and smaller sets of MS drivers selected. This will take several days to sort out as it has yet to boot with all MS drivers selected. Again, thank you for your help.

The instructions for Verifier are to select all non-Microsoft drivers. Did you select Microsoft drivers, too?

 

[dbvogt]

Yes, missed that little word "not" - too much going on. I selected non-MS drivers and got the BSOD anyway. Startup Repair started but is unable to repair the system. When I get the BSOD, how do I know which driver has the problem? Seems like it has to be done one at a time.

 

[writhziden]

The .dmp file will tell which driver it is if it was able to be written. If you repost your crash logs, we'll take a look and let you know if anything is new.

 

[dbvogt]

Update:
The ATI Radeon driver atikmdag.sys is listed by Bluescreenview as the cause of every crash. It's the latest driver according to ATI but ATI does not provide support for the ATI Radeon X300/550 card under Windows 7. The latest driver is for Vista.

I'm going to go out on a limb and say the Nvidia card failed for some unknown reason and the local repair shop that replaced it with an ATI one used an obsolete card. I'm also marking this as solved. I'm impressed with the feedback I got and thank you very much.

 

[writhziden]

There are methods to Install Vista Drivers on Windows 7 that may work. Have you tried doing so using the steps in that tutorial?