BSOD after startup, error 0x0000009f


  1. Posts : 5
    Windows 7 Ultimate 64 bit
       #1

    BSOD after startup, error 0x0000009f


    Hi,

    My laptop has recently been giving a BSOD approx 5 minutes after I start it for the first time during the day. After it reboots it functions fine without any further errors.
    I've attached the two zip files.
    Any help would be greatly appreciated. Thank you
      My Computer


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

    EndaC said:
    Hi,

    My laptop has recently been giving a BSOD .......
    Not very recently.

    The issue is caused by the switchable graphics, and it is occurring irrespective of the display driver version installed.

    The primary graphics is the integrated one .... Intel(R) HD Graphics. The issue occurs during switching between this one and the dedicated one, NVIDIA GeForce GTX 580M.

    You use Alienware. So it appears that you need the nvidia graphics. Make it the primary. Follow the video.



    Now, let us know how the computer works.
    _________________________________________
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa800d7d2a10, Physical Device Object of the stack
    Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: fffffa800fbdb5d0, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    IMAGE_NAME:  pci.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f
    
    MODULE_NAME: pci
    
    FAULTING_MODULE: fffff88000d6a000 pci
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    
    DPC_STACK_BASE:  FFFFF80000BA2FB0
    
    STACK_TEXT:  
    fffff800`00b9c388 fffff800`02d488d2 : 00000000`0000009f 00000000`00000003 fffffa80`0d7d2a10 fffff800`00b9c3d8 : nt!KeBugCheckEx
    fffff800`00b9c390 fffff800`02ce385c : fffff800`00b9c4c0 fffff800`00b9c4c0 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x33af0
    fffff800`00b9c430 fffff800`02ce36f6 : fffff880`00fcf2b0 00000000`0000ea6f 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`00b9c4a0 fffff800`02ce35de : 00000002`2e0b3393 fffff800`00b9cb18 00000000`0000ea6f fffff800`02e57068 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00b9caf0 fffff800`02ce33c7 : 00000000`87eca5c2 00000000`0000ea6f 00000000`87eca5fd 00000000`0000006f : nt!KiTimerExpiration+0x1be
    fffff800`00b9cb90 fffff800`02cd08ca : fffff800`02e53e80 fffff800`02e61cc0 00000000`00000002 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
    
    IMAGE_VERSION:  6.1.7601.17514
    
    FAILURE_BUCKET_ID:  X64_0x9F_3_ACPI_IMAGE_pci.sys
    
    BUCKET_ID:  X64_0x9F_3_ACPI_IMAGE_pci.sys
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x9f_3_acpi_image_pci.sys
    
    FAILURE_ID_HASH:  {f949ba98-ee69-8040-f9fe-7209de5e5499}
    
    Followup: MachineOwner
    ---------
    
    0: kd> !thread
    GetPointerFromAddress: unable to read from fffff80002f10000
    THREAD fffff80002e61cc0  Cid 0000.0000  Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 0
    Not impersonating
    GetUlongFromAddress: unable to read from fffff80002e4fba8
    Owning Process            fffff80002e62180       Image:         <Unknown>
    Attached Process          fffffa800d07e040       Image:         System
    fffff78000000000: Unable to get shared data
    Wait Start TickCount      60015        
    Context Switch Count      415391         IdealProcessor: 0             
    ReadMemory error: Cannot get nt!KeMaximumIncrement value.
    UserTime                  00:00:00.000
    KernelTime                00:00:00.000
    Win32 Start Address nt!KiIdleLoop (0xfffff80002cd0870)
    Stack Init fffff80000b9cc70 Current fffff80000b9cc00
    Base fffff80000b9d000 Limit fffff80000b97000 Call 0
    Priority 16 BasePriority 0 UnusualBoost 0 ForegroundBoost 0 IoPriority 0 PagePriority 0
    Child-SP          RetAddr           : Args to Child                                                           : Call Site
    fffff800`00b9c388 fffff800`02d488d2 : 00000000`0000009f 00000000`00000003 fffffa80`0d7d2a10 fffff800`00b9c3d8 : nt!KeBugCheckEx
    fffff800`00b9c390 fffff800`02ce385c : fffff800`00b9c4c0 fffff800`00b9c4c0 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x33af0
    fffff800`00b9c430 fffff800`02ce36f6 : fffff880`00fcf2b0 00000000`0000ea6f 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`00b9c4a0 fffff800`02ce35de : 00000002`2e0b3393 fffff800`00b9cb18 00000000`0000ea6f fffff800`02e57068 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00b9caf0 fffff800`02ce33c7 : 00000000`87eca5c2 00000000`0000ea6f 00000000`87eca5fd 00000000`0000006f : nt!KiTimerExpiration+0x1be
    fffff800`00b9cb90 fffff800`02cd08ca : fffff800`02e53e80 fffff800`02e61cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
    fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    0: kd> dps !irp fffffa800fbdb5d0
    Couldn't resolve error at '!irp fffffa800fbdb5d0'
    0: kd> !irp fffffa800fbdb5d0
    Irp is active with 4 stacks 2 is current (= 0xfffffa800fbdb6e8)
     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
    >[ 16, 2]   0 e1 fffffa800d7cec50 00000000 fffff8800f23ac0c-fffffa800f8e56a0 Success Error Cancel pending
               \Driver\ACPI    nvlddmkm
                Args: 00000000 00000001 00000001 00000000
     [ 16, 2]   0 e1 fffffa800e18c040 00000000 00000000-00000000    pending
               \Driver\nvlddmkm
                Args: 00000000 00000001 00000001 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-fffffa800dd3a390    
    
                Args: 00000000 00000000 00000000 00000000
    0: kd> !devobj fffffa800e18c040
    Device object (fffffa800e18c040) is for:
     InfoMask field not found for _OBJECT_HEADER at fffffa800e18c010
     \Driver\nvlddmkm DriverObject fffffa800e2db060
    Current Irp 00000000 RefCount 0 Type 00000023 Flags 00002004
    DevExt fffffa800e18c190 DevObjExt fffffa800e18cb48 
    ExtensionFlags (0x00000800)  DOE_DEFAULT_SD_PRESENT
    Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
    AttachedTo (Lower) fffffa800d7cec50 \Driver\ACPI
    Device queue is not busy.
    0: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`0f0eb000 fffff880`0fdbf000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Sun Sep 14 01:29:50 2014 (5414A236)
        CheckSum:         00C8E3A6
        ImageSize:        00CD4000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 5
    Windows 7 Ultimate 64 bit
    Thread Starter
       #3

    Thanks for your reply. I followed the video but the Nvidia processor was already selected in the Nvidia control panel.
    Is there anything else I can try?
      My Computer


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

    Plan to use the computer as a desktop only, where only one GPU is always active.

    Disable the integrated graphics in the device manager. It will nullify any remaining chance of graphics switching. Though it will consume more battery charge.

    Let us know the situation after doing it.
      My Computer


  5. Posts : 5
    Windows 7 Ultimate 64 bit
    Thread Starter
       #5

    I disabled the integrated graphics in the device managed. Immediately I lost all visuals. I restarted and windows was in very low resolution and I am not able to access the Nvidia control panel now
      My Computer


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

    EndaC said:
    I disabled the integrated graphics in the device managed. Immediately I lost all visuals. I restarted and windows was in very low resolution and I am not able to access the Nvidia control panel now
    Nvidia Optimus Technology. You cannot disable the integrated graphics even selecting the nvidia card as preferred one. The nvidia one is a part of the integrated GPU only, as optimus rules.

    Enable integrated graphics in device manager, and restart.
    Go to nvidia control panel. Select integrated graphics as preferred.
    Disable nvidia graphics in device manager.
    Restart.

    It will stop the BSODs for the time being. But games will not run. I will search for ways to disable Optimus technology, if possible.
      My Computer


  7. Posts : 5
    Windows 7 Ultimate 64 bit
    Thread Starter
       #7

    I've just done this. Thanks for your help so far
      My Computer


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

    Hi EndaC.

    Can you please have a look at this one?

    Disabling nVidia Optimus & Perform Clean Install - Autodesk Community


    I would request you to read it, and try the procedure, if possible.
      My Computer


  9. Posts : 5
    Windows 7 Ultimate 64 bit
    Thread Starter
       #9

    I tried this but was unable to disable optimus in bios. So I updated to the latest version of bios and was then able to disable switchable graphics. I then installed the latest Nvidia driver using a clean install.
    So far i've not had any blue screen errors.
    Thanks greatly for you help in solving this issue
      My Computer


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

    EndaC said:
    I tried this but was unable to disable optimus in bios. So I updated to the latest version of bios and was then able to disable switchable graphics. I then installed the latest Nvidia driver using a clean install.
    So far i've not had any blue screen errors.
    Thanks greatly for you help in solving this issue
    That is a great info which will help a lot of other people in future. Thanks a great lot for posting it back.

      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 18:34.
Find Us