Windows 7 crashing in sleep mode

https://www.sevenforums.com/crashes-d...tructions.html

Thanks for the guide....I'm working through the steps. I've attached the latest .dmp file to my original post....and will add another reply later tonight, once I've completed all the steps in your guide.

I've also taken several photos of my screen while these errors are occurring.

I tried uninstalling my ATI Catalyst drivers, to see if they might be causing the problems. This resulted in another BSOD. I rebooted, and reinstalled the newest ATI Catalyst drivers, and got another BSOD. Then it went ahead and booted windows. In Windows, the new drivers didn't seem to be working. Computer monitor resolution was restricted to low levels, dual monitor support disabled, etc. So I uninstalled the drivers again, then rebooted.

Windows booted ok, I reinstalled the ATI Catalyst drivers, and again, everything seemed to work fine. Rebooted, and had no problems.

Tried going to sleep mode, and when I tried to wake the PC, monitors wouldn't come back on, though PC fan and CPU were running. So, did hard reboot, and got past the BIOS screen, and it went to a black screen and Windows never loaded.

Did hard reboot again, and it went to a system screen where it informed me the attempt to resume the system from previous location failed. Gave me a choice to continue with system resume or delete restoration data and proceed to system boot menu. I chose the second option and got a screen saying one of my disks needs to be checked for consistency. It then deleted a bunch of corrupt records, but doesn't find any bad files or bad sectors.

I also ran a checkdisk but found no errors.

I can tell that the system *is* on, because I used my second computer to connect wirelessly to the desktop (the one having the problems) and access the shared drive (on the desktop) and download a file....it got halfway through a 1 GB file transfer before the desktop apparently rebooted itself due to a crash. All this happened while I supposedly couldn't "wake" it....ie. no output to the monitors, no control.

Pleb5919

Here are the files I got from following your BSOD reporting procedure.

I notice one thing...it comments that I don't have an anti-virus product installed...but I do....I've got Microsoft Security Essentials. In my taskbar, it says my computer status is protected.

I don't know what "dirty bit" means.

I have two hard drives..my C drive is a 1 TB WD SATA HD and contains my Windows installation. My E drive is an older 500 GB WD SATA HD that I ripped out of my old PC and stuck in this one for extra storage space.

Pleb5919

Read this STOP 0x116 error: STOP 0x116: VIDEO_TDR_ERROR troubleshooting

Regards...

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800476c4e0, fffff880089b23bc, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** 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+73bc )

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

Quick update.

I was working through the first set of suggestions that DeanP posted....starting with the overheating suggestion.

My wife and I are expecting our first child, and in January, we were setting up the baby's room, which is the room next to the office......lots of sanding, cutting with power saws, etc. I had done this with the door to the office closed, to try and reduce the amount of dust getting into the office, and vacuumed off the exterior of the computer before using it again.

It was around this time that the problems started occurring though. When I opened up the computer yesterday, the innards were coated with a thin layer of gyprock dust and sawdust.....the video card was the most coated out of any of the components. So I blew out the fans, removed the video card and sound card, and vacuumed everything off, and blew out every nook and cranny I could find, including all the cooling elements for the video card....they were coated heavily in dust.

I hooked everything up again today after letting it sit for a night, and it *seems* on initial testing that it's running ok. I've put it into sleep mode several times now, ranging from 10 seconds to 5 minutes, and it's come back on with no problems each time.

I'll keep testing......if it's not generating any more error codes, then it'll be difficult to test anything else...but it could be an indicator the dust was the problem.

The big test will be leaving it in sleep mode overnight. Failing from being in sleep mode overnight is when I first realized there was a problem...then it started happening even when going into sleep mode for 5 seconds. So I'll try this tonight, and see what happens.

Thanks for the help so far. I'm *hoping* that this was the cause of the problem, and that there's no permanent damage to the system.

Pleb5919

Sounds good. Update us within 2 or 3 days about the BSOD news.

Hmm.....things worked perfectly until Friday, and then it started happening again.

I went off to a meeting, put the machine in sleep as I was in the middle of working on a document, and came back 3 hours later. Took it out of sleep, video card refused to come back on.

Pressed power button to reboot, got a "resuming windows" screen, and it went to the black screen and just sat there. Pressed power again, Windows booted, said it was recovering from an unexpected shutdown, and then went through a screen where it did a hard drive scan, deleted corrupt recordds....similar to in the screenshots I posted earlier in the week.

I tried sleeping for 5 minutes this morning, and it did the exact same thing.

The only thing that has changed (that I'm aware of) is that late Thursday, I was patching a program, and the patch damaged the software, so I ran Windows System Restore, going to a restore point from the previous day. That fixed the problem with the program, but now this other error is happening again.

It's not giving me BSOD errors though.....it's just the whole "won't turn on, then takes two attempts, and a bunch of time sitting there restoring corrupted records before it'll load Windows" thing.

Under scan disk and check disk, the hard drive doesn't appear to have any errors.

I looked in Event Viewer, and came up with these lists of records this morning:

"Session "WUDFTrace" stopped due to the following error: 0xC0000102

The driver detected a controller error on \Device\Harddisk7\DR7.

The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolume2.

Task Scheduling Error: m->NextScheduledSPRetry 15600

The previous system shutdown at 10:29:58 AM on ‎05/‎03/‎2011 was unexpected.

The search service has detected corrupted data files in the index {id=4400}. The service will attempt to automatically correct this problem by rebuilding the index.
Details:
The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)

The Windows Search Service is being stopped because there is a problem with the indexer: The catalog is corrupt.
Details:
The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)"

The hard drive controller drivers are the only ones I haven't updated....I've got the latest versions downloaded, but there must be fragments of Windows Installer files from another program, because whenever I try to update them, the installer for ATI Catalyst Control Centre gets started.

I tried looking for Windows Install Cleanup Utility, but it doesn't appear to be available for download anymore, and I've read that it can damage the system, so I've been hesitant to download it from third party websites.

Definitely feels like something odd is going on. Is it just chance that System Restore was done, and then I started coming out of sleep mode and having these errors again? Or are they actually related? If they're related, wouldn't it mean that the dust was not part of the problem?

Or, was the dust related to the BSOD's I was getting.....but isn't related to the other issues with the system failing to come out of sleep properly?

Pleb5919