BSOD 0X0000009f unable to resolve

Page 2 of 2 FirstFirst 12

  1. Posts : 17
    Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #11

    i'll update my specs later tonight when i am back home. i'm not sure if this is relevant or not but the BSOD i had yesterday was after logging on. everything was loaded and i had left my computer idle. after about 10 minutes of idel the BSOD showed up.

    ill update my information and go into NVIDIA and set my othe card as the default for everything. i'll attempt to re-disable the intel 3000 card (last time gave me a black screen, computer still working but no vision. it re-enabled itself after a forced restart) and hope it works. thanks for the help. will keep updated if i get another BSOD after all the changes.
      My Computer


  2. Posts : 26,863
    Windows 11 Pro
       #12

    May I make a suggestion. Just make your discrete card the default for everything but do not disable the HD3000. I'm afraid what happened last time may very well happen again if you disable it. I would suggest, just select your discrete card to be the default for everything and don't disable the HD3000. It seems to me that if you select to use the discrete card for everything, you have effectively disabled the HD3000 without actually doing so. You have basically told the computer not to use it. You may have to go program by program to do that, but once it's done you have effectively disabled the HG3000. I have a reason for this, but it is just a WAG, not based on anything I can prove.
      My Computer


  3. Posts : 17
    Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #13

    edit, googled and found out how to set nvidia as default. will keep up to date on how it goes. thanks for the help
      My Computer


  4. Posts : 26,863
    Windows 11 Pro
       #14

    Be sure and let us know how it goes.
      My Computer


  5. Posts : 17
    Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #15

    everything went well yesterday, but when i logged on today another BSOD. latest log.
      My Computer


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

    The same BSOD continues here.
    Code:
    BugCheck 9F, {3, fffffa8009c2fa10, fffff80000b9c3d8, fffffa800cbc8530}
    
    Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : pci.sys
    
    Followup: MachineOwner
    ---------
    The pci.sys is the NT Plug and Play PCI Enumerator. Which controls the PCI/PCIe devices. In the current case, the device that is having the driver failure is the GPU, because of the display driver error reported.
    Code:
    Irp is active with 4 stacks 2 is current (= 0xfffffa800cbc8648)
     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 fffffa8009c20940 00000000 fffff8800f9a5f38-fffffa800be31450 Success Error Cancel pending
               \Driver\ACPI    nvlddmkm
                Args: 00000000 00000001 00000001 00000000
     [ 16, 2]   0 e1 fffffa800a42e040 00000000 00000000-00000000    pending
               \Driver\nvlddmkm
                Args: 00000000 00000001 00000001 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-fffffa800cf05b20    
    
                Args: 00000000 00000000 00000000 00000000
    And the thing behind the failure is ACPI.
    Code:
    Device object (fffffa800a42e040) is for:
     InfoMask field not found for _OBJECT_HEADER at fffffa800a42e010
     \Driver\nvlddmkm DriverObject fffffa800a42b440
    Current Irp 00000000 RefCount 0 Type 00000023 Flags 00002004
    DevExt fffffa800a42e190 DevObjExt fffffa800a42eb48 
    ExtensionFlags (0x00000800)  DOE_DEFAULT_SD_PRESENT
    Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
    AttachedTo (Lower) fffffa8009c20940 \Driver\ACPI
    Device queue is not busy.
    The failure is happening when the primery GPU (Intel HD 3000) becomes inactive and the dedicated GPU takes the charge.

    Yes, as per the DXDIAG.txt supplied with the zip, the GPU is intel. It reads the primary GPU data.
    Code:
    ---------------
    Display Devices
    ---------------
              Card name: Intel(R) HD Graphics 3000
           Manufacturer: Intel Corporation
              Chip type: Intel(R) HD Graphics Family
               DAC type: Internal
             Device Key: Enum\PCI\VEN_8086&DEV_0116&SUBSYS_04BA1028&REV_09
         Display Memory: 4048 MB
       Dedicated Memory: 1488 MB
          Shared Memory: 2559 MB
           Current Mode: 1600 x 900 (32 bit) (60Hz)
    I am not sure how you set the nvidia GPU as primary, but it did not take effect. Follow it:



    If still the same BSOD continues to occur, you have two ways left. Either disable either GPU in BIOS and perform a clean install; or contract your vendor.

    Because I have nothing more to say here.
      My Computer


 
Page 2 of 2 FirstFirst 12

  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 05:36.
Find Us