BSOD as system sleeps


  1. Posts : 2
    Windows 7 Home Premium 64-bit SP1
       #1

    BSOD as system sleeps


    Hi,

    I've had the same issue several times over the last few days. As I open up my laptop's screen, I get the message that the system recovered from an unexpected shutdown. I assume that this is happening when the computer goes to sleep as I shut the screen. The system hasn't crashed while actively using it yet.

    I'm uploading the crash log -- let me know if any additional details would help.

    Thanks!
    Last edited by shlshh; 11 Jul 2013 at 18:50. Reason: Reuploaded attachment
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Start by freeing up the start up:
    Startup Programs - Change
    Your antivirus is the only thing that's really needed there.

    Avast! antivirus is often a cause of BSOD's. I would remove it with the Avast! uninstall tool and replace with Microsoft Security Essentials & the Free version of Malwarebytes, update and make a full scan separately:
    avast! Uninstall Utility | Download aswClear for avast! Removal
    Microsoft Security Essentials - Microsoft Windows
    Malwarebytes Free

    Make scans with the following:

    Kaspersky TDSSKiller - TDSSKiller Rootkit Removal Utility Free Download | Kaspersky Lab US

    ESET online scanner - Online Virus Scanner Eset

    Run a system file check and disk check on your Hard drives:
    SFC /SCANNOW Command - System File Checker
    Disk Check

    Test RAM with memtest86+:
    RAM - Test with Memtest86+
    Pay close attention to part 3 of the tutorial "If you have errors"

    Check for an update on your Synaptics Touchpad Driver:
    Driver Reference Table - SynTP.sys

    Bugcheck
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, fffffa8006cb3060, fffff80000b9c3d8, fffffa801024f7d0}
    
    Probably caused by : ACPI.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa8006cb3060, Physical Device Object of the stack
    Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
    Arg4: fffffa801024f7d0, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    IMAGE_NAME:  ACPI.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79294
    
    MODULE_NAME: ACPI
    
    FAULTING_MODULE: fffff88000ed5000 ACPI
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  X64_0x9F_3_SynTP_IMAGE_ACPI.sys
    
    BUCKET_ID:  X64_0x9F_3_SynTP_IMAGE_ACPI.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd> !irp fffffa801024f7d0
    Irp is active with 9 stacks 8 is current (= 0xfffffa801024fa98)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
         cmd  flg cl Device   File     Completion-Context
    			Args: 00000000 00000000 00000000 00000000
    >[ 16, 2]   0 e1 fffffa800a3d2c70 00000000 00000000-00000000    pending
    	      Unable to load image \SystemRoot\system32\DRIVERS\SynTP.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for SynTP.sys
    *** ERROR: Module load completed but symbols could not be loaded for SynTP.sys
     \Driver\SynTP
    			Args: 00014400 00000001 00000004 00000002
     [  0, 0]   0  0 00000000 00000000 00000000-fffffa800cbc07c0    
    
    			Args: 00000000 00000000 00000000 00000000
      My Computer


  3. Posts : 2
    Windows 7 Home Premium 64-bit SP1
    Thread Starter
       #3

    Thanks, I did most of those steps and cleaned up what I could -- we'll see how it turns out. I was hesitant to update the Synaptics Driver as my Windows software says it's up to date (when I go to 'Update Device Drivers' and click 'Update Driver Software...' after right-clicking the Synaptics pointer).

    Is it common for Windows to say a driver is up-to-date but for it to still need an update?
      My Computer


  4. Posts : 15,026
    Windows 10 Home 64Bit
       #4

    shlshh said:
    Is it common for Windows to say a driver is up-to-date but for it to still need an update?
    Yes sometimes.

    Anyway, let us know if you get more BSOD's.
      My Computer


  5. Posts : 15,026
    Windows 10 Home 64Bit
       #5

    Do you still have bsod problems?
      My Computer


 

  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 01:17.
Find Us