When my Win7 64-bit machine crashes whenever it wakes up from sleep. Event Viewer has the following: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000116 (0xfffffa800c937320, 0xfffff88002f9845c, 0x0000000000000000, 0x0000000000000002). A dump was saved in: C:\Windows\Minidump\100311-20592-01.dmp. Report Id: 100311-20592-01. The dmp file shows: Dump File Crash Time Bug Check String Bug Check Code Parameter 1 Parameter 2 Parameter 3 Parameter 4 Caused By Driver Caused By Address File Description Product Name Company File Version Processor Crash Address Stack Address 1 Stack Address 2 Stack Address 3 Computer Name Full Path Processors Count Major Version Minor Version Dump File Size 100311-20592-01.dmp 10/3/2011 05:52:42 0x00000116 fffffa80`0c937320 fffff880`02f9845c 00000000`00000000 00000000`00000002 dxgkrnl.sys dxgkrnl.sys+5d000 x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\100311-20592-01.dmp 4 15 7601 337,266 Could anyone offer some clue about this? Hong

dxgkrnl.sys is related to DirectX and your video drivers. Update your video drivers to resolve the issue.If you found this post helpful, please "Vote as Helpful". If it answered your question, remember to "Mark as Answer". Rich Prescott | MCITP, MCTS, MCP [Blog] Engineering Efficiency | [Twitter] @Rich_Prescott | [Powershell GUI] Client System Administration tool | [PowerShell GUI] New AD User Creation tool

Thanks for the tip, Rich. I updated the video driver with the version released last month from AMD's website (for ATI Radeon HD4300/4500 Series), but the problem remains. I guess this is a driver issue, and I cannot do anything about it. Before updating the video driver, I updated DirectX with June 2010 release. The .dmp shows something slightly different as following: Dump File Crash Time Bug Check String Bug Check Code Parameter 1 Parameter 2 Parameter 3 Parameter 4 Caused By Driver Caused By Address File Description Product Name Company File Version Processor Crash Address Stack Address 1 Stack Address 2 Stack Address 3 Computer Name Full Path Processors Count Major Version Minor Version Dump File Size 100311-22744-01.dmp 10/3/2011 08:55:57 0xa0000001 00000000`00000005 00000000`00000000 00000000`00000000 00000000`00000000 atikmdag.sys atikmdag.sys+4cdb1 x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\100311-22744-01.dmp 4 15 7601 288,186 Hong

The atikmdag.sys error confirms that it is an issue with your ATI drivers. Try downgrading your video driver to a previous version since the latest one didn't work.If you found this post helpful, please "Vote as Helpful". If it answered your question, remember to "Mark as Answer". Rich Prescott | MCITP, MCTS, MCP [Blog] Engineering Efficiency | [Twitter] @Rich_Prescott | [Powershell GUI] Client System Administration tool | [PowerShell GUI] New AD User Creation tool

I am sorry for the confusion. Here is the sequence of the events: 1. The crash happened when the video driver was the old one. 2. I posted this question here. 3. I updated DirectX, the crash remains. 4. I updated the video driver to the latest version, the crash remains. In summary, the crash happens with both the old and the new driver. I will turn on hibernation, and use it instead of sleep.Hong

Hi, I notice you updated your video card from AMD site. If your computer is from OEM manufacture, it is recommend downloading the driver there. Also, you can update your display driver from manufacture's site. If the issue persists, please test the issue in Safe Mode without any driver loading. Best Regards, Niki Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi Niki, I put together this computer. I went to the video card vendor's website (VisionTek), and downloaded the driver from it. It appears to be the same, but I installed anyway. The problem remains. As I wrote, I am using hibernation now. I am content with it. However, it would be nice to have sleep working. Hong

I would contact VisionTek also, they may have a glitch in thier video cards and need to address it with ATI. Seems like a minor thing, but ATI will tend to "put more effort" into bug fixes when thier major distributors report issues vs. single folks.:P Advice offered, If you need more help it is advised to seek the council and advice of paid professionals. The answer is always 42, or reboot.

I would contact VisionTek also, they may have a glitch in thier video cards and need to address it with ATI. Seems like a minor thing, but ATI will tend to "put more effort" into bug fixes when thier major distributors report issues vs. single folks.:P Advice offered, If you need more help it is advised to seek the council and advice of paid professionals. The answer is always 42, or reboot.