Win7 Ultimate x64, BSOD when waking up from automatic monitor shut-off

Page 1 of 4 123 ... LastLast

  1. Posts : 18
    Windows 7 Ultimate x64
       #1

    Win7 Ultimate x64, BSOD when waking up from automatic monitor shut-off


    I built this system last week and passed all my preliminary stability testing (20 passes of LinX, 2 hours of Furmark, etc)

    Everythings grand, except i've had two hard crashes so far, both related to recovering from the automatic powersaver "monitor turns off after 10 minutes." The first time was two days ago, when it was idle for maybe 20 minutes, and when I walked over to my desk and went to grab my phone I lightly nudged the mouse enough for it to kick back up. Except it didnt, my monitor power light switched from orange (on, no signal) to blue (on, working), and my video card fan immediately pushed itself to 100% for about a minute, then stopped for a few seconds and whirred back up to full blast, with nothing but a black screen despite the power light turning blue. In order to stop it I had to hold the power button for 5 seconds to do a hard shutdown.

    I wrote it off as a one-off typical system hiccup as everything settles in until just a few minutes ago, waking it up from the powersaver state multiple times since then. Again, I walked away from my PC for a while and the monitor turned itself off as normal. When I came back and moved the mouse to wake it up, nothing. So I hit keys on the keyboard, nothing. Unplugged/replugged the DVI, nothing. Walked over to my laptop and accessed shared network files on the PC with absolutely no problem, opened and closed the DVD drive and it even made the "reading" motions as if it was trying to autorun a disk. Then I noticed that none of the hotkeys on my Sidewinder X4 keyboard were working (changing macro sets, toggle numlock, etc). The backlights were off but the status LEDs were fine as was the red mouse laser. Plugged in an extra mouse, and it got power just fine, but didnt make a difference.

    So I figured it was the keyboard drivers possibly locking up the system and went to disconnect the keyboard and mouse. Instant BSOD, all I caught before the autoreboot was DRIVER POWER STATE FAILURE before it restarted itself. Of course, there isnt much useful in the error logs either. Really hoping this is something stupid like "update your SSD firmware" and not "RMA your motherboard," this build was already a total nightmare Any help you guys can give is appreciated, the minidump/log zip is attached below.

    For the record, sleep and hibernate are both completely turned off.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Welcome aboard.

    First of all, uninstall Daemon tools and Catalyst Control Center.

    Next, change the VGA/DVI/HDMI cable that you use to connect the monitor with the computer.

    Let us know the situation.
    Code:
    0: kd> !irp fffffa800cbcb010
    Irp is active with 3 stacks 1 is current (= 0xfffffa800cbcb0e0)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
         cmd  flg cl Device   File     Completion-Context
    >[ 16, 2]   0 e0 fffffa800af87ab0 00000000 fffff80002a79ce0-fffffa800d205840 Success Error Cancel 
               \Driver\amdkmdap    nt!IopUnloadSafeCompletion
                Args: 00000000 00000001 00000001 00000000
     [ 16, 2]   0 e1 fffffa800af92c70 00000000 fffff80002a79ce0-fffffa800c42da40 Success Error Cancel pending
               \Driver\monitor    nt!IopUnloadSafeCompletion
                Args: 00000000 00000001 00000001 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-fffffa800a63b550    
    
                Args: 00000000 00000000 00000000 00000000
    0: kd> !devobj fffffa800af87ab0
    Device object (fffffa800af87ab0) is for:
     Cannot read info offset from nt!ObpInfoMaskToOffset
     \Driver\amdkmdap DriverObject fffffa800a5478a0
    Current Irp 00000000 RefCount 0 Type 0000001c Flags 00003044
    DevExt fffffa800af87c00 DevObjExt fffffa800af87f88 DevNode fffffa800a7aa5b0 
    ExtensionFlags (0000000000)  
    AttachedDevice (Upper) fffffa800af92c70 \Driver\monitor
    Device queue is not busy.
    0: kd> !drvobj fffffa800af87ab0 7
    fffff80002c35fb0: Unable to get value of ObpRootDirectoryObject
    fffff80002c35fb0: Unable to get value of ObpRootDirectoryObject
    Driver object (fffffa800af87ab0) is for:
    fffffa800af87ab0: is not a driver object
      My Computer


  3. Posts : 18
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Ill do those and we'll see how it goes, thanks.

    Is there a particular reason Daemon Tools might cause that instability? I've been using it for years and never had an issue.
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    DS1971 said:
    Ill do those and we'll see how it goes, thanks.

    Is there a particular reason Daemon Tools might cause that instability? I've been using it for years and never had an issue.
    Demon tool (and Alcohol 120%) mount virtual ODDs, and for doing that, they use a driver called stpd.sys.

    stpd.sys, most often than not, specifies a hardware information to be exist, which is not there actually. So they cause a power state failure off and on.

    There is a free version of MagicIso. That does the same thing that Daemon does, but does not use stpd.sys.
      My Computer


  5. Posts : 18
    Windows 7 Ultimate x64
    Thread Starter
       #5

    I uninstalled them and ran chkdsk just in case (which found nothing).

    I've let it go idle and turn the monitor off numerous times over the past day anywhere from a minute or two to a few hours, and it's bounced back properly every time so far. I'll reinstall CCC tomorrow and see if it stays stable.

    Thanks!
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    Inform us the situation, in time.
      My Computer


  7. Posts : 18
    Windows 7 Ultimate x64
    Thread Starter
       #7

    No luck, got another bluescreen. This time it locked up while idle and just sat there locked up until I turned the monitor off and then back on.

    Removed Gigabyte EasyTune 6, Gigabyte Autogreen, and catalyst control center, we'll see how it holds up.

    Edit: also removed Gigabyte ON/OFF charge utility.

    Attached is the logs.
      My Computer


  8. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #8

    Both the dumps say the same thing:
    Code:
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, fffffa800af87ab0, fffff800045143d8, fffffa800cbcb010}
    
    *** 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
    
    Followup: MachineOwner
    ---------
    You may try to sweep all ATI driver entries using |MG| Driver Fusion (Driver Sweeper) 1.2.0 Download, and reinstall those, othe rthan Catalyst.

    Install the drivers in device manager.
      My Computer


  9. Posts : 18
    Windows 7 Ultimate x64
    Thread Starter
       #9

    I haven't had time to fully reinstall the drivers, but it hasn't bluescreened last night or any time today. I did however just catch it making an odd noise while idle. It sounded like the video card whirred up the fan for only a few spins, then let it spin down for a few seconds and did it all over again. As soon as touched the mouse and the monitor came back on it immediately stopped. Seems like it might be related considering what happened with the very first freeze, i'll completely reinstall the drivers tonight and see how it goes, but could it just be a defective card?
      My Computer


  10. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #10

    Test the video card then, to be sure.
    Video Card - Stress Test with Furmark
      My Computer


 
Page 1 of 4 123 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 03:08.
Find Us