I also had trouble with the GEforce 388.13 driver, Win7 Home
I created a checkpoint and used DriverEasy to update several out-of-date drivers, including PCIexpress, as I had been seeing BSOD's with pci.sys in the backtrace. I made this mistake of installing the recommended Geforce 388.13 driver. On reboot, my screen would flash, had video drop-outs, and would sometimes generate a 16x16 grid of duplicate screens with low resolution. Along the way two Windows updates were applied.
Rolling back to my oldest checkpoint failed, I must have taken it before the Windows updates but after the new driver had been installed. I soldiered on...
The solution was to go to the Nvidia website to get the recommended driver for my ASUS G73sw laptop with a GEforce GTX 460M graphics card. The driver was bundled into their installer app, and was version 368.68 WHQL, Wed Jul 06, 2016, for Win7 64bit. You must removed all Nvidia bread crumbs left over from a previous failed uninstall, I still had one service installed.
Others may have had better luck, but this was a nightmare until I removed the old driver and loaded the new one in VGA mode (you can't install the driver in Safe Mode).
Along the way I learned how to use this site's dm_log collector (the bundle is attached) then downloaded the Microsoft 8.1A debug sdk, set an environment variable to look for symbols on Microsoft's symbol server, allowing me to run WinDebug and capture the stack trace.
My stack traces just show the pci.sys errors and BSOD; when the screen would flash I would get a warning that the GEforce had timed out on a pci transaction. Eventually this causes the BSOD. I got started on this because the BSOD would happen in the middle of the night (I had turned off sleep and hibernation).
It was well worth joining this forum, so I hope this post helps someone else with a similar problem.
helpfulHwMan
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa80071e9060, fffff80000b9a3d8, fffffa800f2683b0}
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: fffffa80071e9060, Physical Device Object of the stack
Arg3: fffff80000b9a3d8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa800f2683b0, 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: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
DPC_STACK_BASE: FFFFF80000BA0FB0
STACK_TEXT:
fffff800`00b9a388 fffff800`03301810 : 00000000`0000009f 00000000`00000003 fffffa80`071e9060 fffff800`00b9a3d8 : nt!KeBugCheckEx
fffff800`00b9a390 fffff800`0329bc3c : fffff800`00b9a4c0 fffff800`00b9a4c0 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x2e5f0
fffff800`00b9a430 fffff800`0329bad6 : fffffa80`0af86aa8 fffffa80`0af86aa8 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9a4a0 fffff800`0329b9be : 00000048`e7c7c24e fffff800`00b9ab18 00000000`001ea0a6 fffff800`03411748 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9aaf0 fffff800`0329b7a7 : 0000000e`352c98c6 0000000e`001ea0a6 0000000e`352c9897 00000000`000000a6 : nt!KiTimerExpiration+0x1be
fffff800`00b9ab90 fffff800`03287b0a : fffff800`0340de80 fffff800`0341bcc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9ac40 00000000`00000000 : fffff800`00b9b000 fffff800`00b95000 fffff800`00b9ac00 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION: 6.1.7601.17514
FAILURE_BUCKET_ID: X64_0x9F_3_POWER_DOWN_FLxHCIc_IMAGE_pci.sys
BUCKET_ID: X64_0x9F_3_POWER_DOWN_FLxHCIc_IMAGE_pci.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x9f_3_power_down_flxhcic_image_pci.sys
FAILURE_ID_HASH: {10380dcc-bfc7-de71-9c06-2d76c7b39bea}
Followup: MachineOwner
---------
