Operation System Crash, bugcheck 0x0000009f

Page 2 of 5 FirstFirst 1234 ... LastLast

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

    No problem..and I will take a look at the new ones and post my findings :)
      My Computer


  2. Posts : 27
    Window 7 Home Premium 64-Bit SP1
    Thread Starter
       #12

    Did the full scan and the program found nothing wrong
      My Computer


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

    Okay, any new BSOD's or issues after making the rest of the changes? Cause the last dump I see is of 29th May.
      My Computer


  4. Posts : 27
    Window 7 Home Premium 64-Bit SP1
    Thread Starter
       #14

    koolkat77 said:
    Okay, any new BSOD's or issues after making the rest of the changes? Cause the last dump I see is of 29th May.
    No new BSOD since the changes.
    But, I don't know if my BSOD gonna happen again or not. I will just wait and see.
      My Computer


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

    Ral400 said:
    koolkat77 said:
    Okay, any new BSOD's or issues after making the rest of the changes? Cause the last dump I see is of 29th May.
    No new BSOD since the changes.
    But, I don't know if my BSOD gonna happen again or not. I will just wait and see.
    Yes..that's what you have to do. Wait and see if it happens again..and if it does, upload the new reports.

    Take your time, keep us posted. Good luck.
      My Computer


  6. Posts : 27
    Window 7 Home Premium 64-Bit SP1
    Thread Starter
       #16

    The shutdown happen again at 12:52 PM today (CST).
      My Computer


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

    I will take a look at it as soon as I can. Bump the thread if I haven't replied in 48 hours.
      My Computer


  8. Posts : 27
    Window 7 Home Premium 64-Bit SP1
    Thread Starter
       #18

    koolkat77 said:
    I will take a look at it as soon as I can. Bump the thread if I haven't replied in 48 hours.
    Ok. Take all the time you need. You may never know if the laptop will shutdown again after the fix. :)
      My Computer


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

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, fffffa800774e060, fffff80000b9c3d8, fffffa80110ccbd0}
    
    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: fffffa800774e060, Physical Device Object of the stack
    Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
    Arg4: fffffa80110ccbd0, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    IMAGE_NAME:  ACPI.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79294
    
    MODULE_NAME: ACPI
    
    FAULTING_MODULE: fffff88000ee7000 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_TEXT:  
    fffff800`00b9c388 fffff800`0353b8c2 : 00000000`0000009f 00000000`00000003 fffffa80`0774e060 fffff800`00b9c3d8 : nt!KeBugCheckEx
    fffff800`00b9c390 fffff800`034d684c : fffff800`00b9c4c0 fffff800`00b9c4c0 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x33af0
    fffff800`00b9c430 fffff800`034d66e6 : fffffa80`0d0a8c58 fffffa80`0d0a8c58 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`00b9c4a0 fffff800`034d65ce : 000000e5`6f5b1de1 fffff800`00b9cb18 00000000`006062b7 fffff800`0364a968 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00b9caf0 fffff800`034d63b7 : 00000031`2e62c5c3 00000031`006062b7 00000031`2e62c537 00000000`000000b7 : nt!KiTimerExpiration+0x1be
    fffff800`00b9cb90 fffff800`034c390a : fffff800`03646e80 fffff800`03654cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
    fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    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 fffffa80110ccbd0
    Irp is active with 9 stacks 8 is current (= 0xfffffa80110cce98)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
         cmd  flg cl Device   File     Completion-Context
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
    >[ 16, 2]   0 e1 fffffa800a36d730 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-fffffa800f44b160    
    
    			Args: 00000000 00000000 00000000 00000000
    Like earlier, have you tried updating the Synaptic Touch Pad Driver Driver Reference Table - SynTP.sys

    Please uninstall this software " ST MicroElectronics Accelerometer " as well.
      My Computer


  10. Posts : 27
    Window 7 Home Premium 64-Bit SP1
    Thread Starter
       #20

    I did update my pad [on 5/17/2013, version 16.3.15.1] and it was successful. I don't know how to uninstall "ST MicroElectronics Accelerometer". This software is not showing in "Uninstall or Change Program".
      My Computer


 
Page 2 of 5 FirstFirst 1234 ... 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 18:13.
Find Us