BSOD 0X0000009f unable to resolve

Can you please re-upload the above file in zip format as it is easier to read plus i do not have a .rar file reader. Thanks

To read a .rar file, free 7-Zip may be used.

Supported formats:

• Packing / unpacking: 7z, XZ, BZIP2, GZIP, TAR, ZIP and WIM
• Unpacking only: ARJ, CAB, CHM, CPIO, CramFS, DEB, DMG, FAT, HFS, ISO, LZH, LZMA, MBR, MSI, NSIS, NTFS, RAR, RPM, SquashFS, UDF, VHD, WIM, XAR and Z.

Does the BSOD occur in a chrome session, or when the computer comes out of sleep?

If it happens during chrome, disable Hardware Acceleration. Open a video in YouTube. When it is started, right click on the screen and choose "settings"



In the resulting window, uncheck the option for hardware acceleration, and then close the window.


Also, see these tutorials:

• Chrome GPU Hardware Acceleration - Turn On or Off
• Firefox GPU Hardware Acceleration - Turn On or Off
• Internet Explorer GPU Hardware Acceleration - Turn On or Off

If it happens during waking up from sleep, disable either the Intel(R) HD Graphics 3000 or the NVIDIA GeForce GTX 460M.

The option to disable either of them will be in the BIOS and in the NVIDIA control panel.
________________________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8009c4ea10, fffff80000ba2748, fffffa80076c7760}

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
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffffa8009c4ea10, Physical Device Object of the stack
Arg3: fffff80000ba2748, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa80076c7760, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f

MODULE_NAME: pci

FAULTING_MODULE: fffff88000e00000 pci

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

DPC_STACK_BASE:  FFFFF80000BA2FB0

STACK_TEXT:  
fffff800`00ba26f8 fffff800`0353d8d2 : 00000000`0000009f 00000000`00000003 fffffa80`09c4ea10 fffff800`00ba2748 : nt!KeBugCheckEx
fffff800`00ba2700 fffff800`034d885c : fffff800`00ba2848 fffff800`00ba2848 00000000`0000fff7 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`00ba27a0 fffff800`034d86f6 : fffff880`00fa32b0 00000000`0000d4c4 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00ba2810 fffff800`034d85de : 00000001`fa79111e fffff800`00ba2e88 00000000`0000d4c4 fffff800`0364cb08 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00ba2e60 fffff800`034d83c7 : fffff800`03648ec3 fffffa80`0000d4c4 fffffa80`0a83b000 00000000`000000c4 : nt!KiTimerExpiration+0x1be
fffff800`00ba2f00 fffff800`034d0d15 : 00000000`00000000 fffffa80`0b2f9b50 00000000`00000000 fffff880`05087588 : nt!KiRetireDpcList+0x277
fffff800`00ba2fb0 fffff800`034d0b2c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`0b7c3560 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


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
---------

The same BSOD continues, and you have to disable either graphics.

Code:

BugCheck 9F, {3, fffffa800804ba10, fffff80000b9c3d8, fffffa80071e4880}

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
---------

I am requesting essenbe to guide you how to disable it.

Could I get you to fill out your system specs please (System Info - See Your System Specs) It will help us to know how to help you. Much of the problems I have seen with switchable graphics is different manufacturers Implement it differently. I've found that drivers work better downloaded from the manufacturers web site, just because of that fact. If you disable your on chip graphics and only use the discrete card, it will affect your battery life. How much will depend on which discrete card you have. I have a laptop with an Nvidia card which uses their Optimus technology, which is simply Nvidia's implementation of switchable graphics. If you have an Nvidia card you should be able to go into the NVidia control panel and select which is the primary graphics adapter and also go by program to program and select which to use. On my laptop, I chose to use the discrete graphics card for everything. In that way, you are not disabling on board graphics, you are just not using it. Technically, if you really care to know, all the graphics go through the CPU and the CPU decides which graphics to use. The problem is the CPU choosing the wrong one and the delay during the switch over. You, from what I've read, are having problems updating your on chip graphics. If that is the case, I would try going into the global settings and making the discrete card primary graphics adapter and the going into the local settings and choosing those programs that make you crash and choosing to use the discrete card as primary. That avoids the problem of the CPU having to decide to switch over. Try doing that and see if it helps. But, be aware that your battery life will be shorter. That usually does not cause a problem once you learn how long the battery life is depending on which programs you use. You just make allowances for that.