Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Everytime I download this windows update my monitor turns black

04 Nov 2017   #1
bobxxx

Windows 7 Home Premium 64 bit
 
 
Everytime I download this windows update my monitor turns black

As the title says, everytime I try to use the windows update on my computer for these couple graphics changes, my computer screen turns black and kinda goes into sleep mode. I end up having to restart the computer and system restoring it back to before the update.

Here are the pics of the windows update changes that Windows wants. I just ended up not doing them, but I am puzzled as to why this is happening and if whether it could be my graphics card, although I recently replaced my graphics card because I took it to the shop recently and they gave me a new one and did a diagnostics to fix issues.

Should I be worried and what can I do to fix it so I can update and not have this problem?




Attached Thumbnails
Everytime I download this windows update my monitor turns black-update-issue.jpg  
My System SpecsSystem Spec
.
04 Nov 2017   #2
AddRAM

Windows 7 Pro x64 Windows 10 Pro x64
 
 

Which update is causing the problem ? The nvidia update or the Intel update ?

If you need an nvidia driver get it from nvidia, not through windows update.

If you are using an nvidia graphics card, don`t even worry about the CPU graphics, just hide the update.
My System SpecsSystem Spec
04 Nov 2017   #3
RoasterMen

Windows 10 Pro 64-bit
 
 

We need a complete specification of your system as I am not sure if this is a laptop or a desktop you're having problem with.
My System SpecsSystem Spec
.

05 Nov 2017   #4
torchwood

W7 home premium 32bit/W7HP 64bit/w10 tp insider ring
 
 

purely my point of view

Dissable MS driver updates, allways go to the manufacturer especially for graphics cards
NEVER install the PREVIEW updates.

And your comp will allways black screen when installing graphics drivers, unless there done on a reboot
(remove old drivers >> black screen >> install new drivers >> up and running)

Roy
My System SpecsSystem Spec
05 Nov 2017   #5
bobxxx

Windows 7 Home Premium 64 bit
 
 

Quote   Quote: Originally Posted by AddRAM View Post
Which update is causing the problem ? The nvidia update or the Intel update ?

If you need an nvidia driver get it from nvidia, not through windows update.

If you are using an nvidia graphics card, don`t even worry about the CPU graphics, just hide the update.
It's the Intel update I believe. Because I tried doing just the intel update alone and it was going me the issue.

Also my computer is a desktop, Windows 7 64-bit with a GeForce Nvidia GTX 1060 graphics card. i5 processor, with DDR3 8 GB ram

Ok so the consensus is to just not do any windows updates on graphics card?


Quote   Quote: Originally Posted by torchwood View Post
purely my point of view

Dissable MS driver updates, allways go to the manufacturer especially for graphics cards
NEVER install the PREVIEW updates.

And your comp will allways black screen when installing graphics drivers, unless there done on a reboot
(remove old drivers >> black screen >> install new drivers >> up and running)

Roy
Ok I will update from Manufacturer.

Ya I know computers black screens for a couple seconds when you install graphics drivers but this is different. When I update, it just stays black and never comes back until I unplug the computer and restart it and then windows automatically states something wrong happened and asks if I want to do a system restore. If I don't do the system restore and go straight yo start up then it goes back to the black screen. I am practically forced to system restore.
My System SpecsSystem Spec
05 Nov 2017   #6
helpfulHwMan

Windows 7 Home Premium 64-bit
 
 
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
---------


Attached Thumbnails
Everytime I download this windows update my monitor turns black-currrent_device_manager_settings_for_nvidia.png  
Attached Files
File Type: zip KATEWIN7-PC-Sun_11_05_2017__82225_66.zip (2.50 MB, 0 views)
File Type: txt 103017-33524-01_windbg_analysis.txt (4.8 KB, 0 views)
My System SpecsSystem Spec
3 Weeks Ago   #7
helpfulHwMan

Windows 7 Home Premium 64-bit
 
 
I may have been too quick to blame Nvidia for my pci.sys crashes

I was stable for 15 days, then started crashing the Nvidia driver in pci.sys again. The screen blanked out four or five times before the BSOD. Capturing the dm bundle and examining the crash dump revealed I was crashing in the HCI Fresco Logic USB3.0 driver with a "power down" fault, even though the system wasn't going to sleep or shutting down. I was running a 7/30/2015 HCI USB 3.0 driver version 3.6.8.0.

On the Fresco Logic website I found a 3.8.33709.0 driver. It was hard to install the Fresco installer package with the crashing Nvidia display driver, so I temporarily disabled the Nvidia driver in device manager, allowing me to boot into a VGA session and run the Fresco driver install package (you can't run this in Safe mode).

I've been up and stable for a few hours now, so hopefully this problem is behind me. I'm leery of updating the Nvidia driver, as it was the recommended version for Windows 7 on their website. Stable is good place to be.

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: fffffa80072cfa10, Physical Device Object of the stack
Arg3: fffff80004c513d8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa800ecee0e0, The blocked IRP

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


DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7928f

MODULE_NAME: pci

FAULTING_MODULE: fffff88000f9b000 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: FFFFF80004C57FB0

STACK_TEXT:
fffff800`04c51388 fffff800`03301810 : 00000000`0000009f 00000000`00000003 fffffa80`072cfa10 fffff800`04c513d8 : nt!KeBugCheckEx
fffff800`04c51390 fffff800`0329bc3c : fffff800`04c514c0 fffff800`04c514c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x2e5f0
fffff800`04c51430 fffff800`0329bad6 : fffffa80`0d947168 fffffa80`0d947168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`04c514a0 fffff800`0329b9be : 0000008d`762f458e fffff800`04c51b18 00000000`003b6d93 fffff800`034114e8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`04c51af0 fffff800`0329b7a7 : 0000001b`91387dc3 0000001b`003b6d93 0000001b`91387d71 00000000`00000093 : nt!KiTimerExpiration+0x1be
fffff800`04c51b90 fffff800`03287b0a : fffff800`0340de80 fffff800`0341bcc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`04c51c40 00000000`00000000 : fffff800`04c52000 fffff800`04c4c000 fffff800`04c51c00 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
---------

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: fffffa80072cfa10, Physical Device Object of the stack
Arg3: fffff80004c513d8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa800ecee0e0, The blocked IRP

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


DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7928f

MODULE_NAME: pci

FAULTING_MODULE: fffff88000f9b000 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: FFFFF80004C57FB0

STACK_TEXT:
fffff800`04c51388 fffff800`03301810 : 00000000`0000009f 00000000`00000003 fffffa80`072cfa10 fffff800`04c513d8 : nt!KeBugCheckEx
fffff800`04c51390 fffff800`0329bc3c : fffff800`04c514c0 fffff800`04c514c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x2e5f0
fffff800`04c51430 fffff800`0329bad6 : fffffa80`0d947168 fffffa80`0d947168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`04c514a0 fffff800`0329b9be : 0000008d`762f458e fffff800`04c51b18 00000000`003b6d93 fffff800`034114e8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`04c51af0 fffff800`0329b7a7 : 0000001b`91387dc3 0000001b`003b6d93 0000001b`91387d71 00000000`00000093 : nt!KiTimerExpiration+0x1be
fffff800`04c51b90 fffff800`03287b0a : fffff800`0340de80 fffff800`0341bcc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`04c51c40 00000000`00000000 : fffff800`04c52000 fffff800`04c4c000 fffff800`04c51c00 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
---------


Attached Files
File Type: zip KATEWIN7-PC-Mon_11_20_2017_121851_52.zip (2.51 MB, 0 views)
File Type: txt windbg_analysis_fresco_logic_bsod.txt (7.4 KB, 1 views)
My System SpecsSystem Spec
Reply

 Everytime I download this windows update my monitor turns black




Thread Tools




Similar help and support threads
Thread Forum
monitor turns black after start up 2 blue boxes scrolling on screen
Help please - on switching on screen shows "Dell logo and Windows is starting" then screen goes black, two small blue boxes as big as downloading progress bars with the words "input not support" between them start to scroll round the screen. Mouse does not work and I am unable to do anything to...
General Discussion
HDTV as second monitor turns black during the movie
Hello everyone,while I'm waiting for answer/s on my previous thread about errors in my energy report :huh: I decided to ask a question about another issue that bothers me for some time.In fact, I using Toshiba HDTV model L2433 as a second monitor connected via an HDMI cable with my pc, and each...
Media Center
My second monitor works on boot up but then turns black!
Hi there I recently upgraded to have two monitors for my pc. My graphics card is the AMD radeon hd 7770 and I have a Benq GL2250 and a Samsung S22B150. On first setup everything was fine with my first monitor (Benq) plugged in via vga from the monitor into a vga to which I think is a dvi-i...
Graphic Cards
Problem: monitor spontaneously turns black
Windows 7 Ultimate OS Service Pack Service Pack 1 CPU Type - Intel Core 2 Duo E7400, 1600 MHz (6 x 267) Motherboard - Shuttle FG33M (1 PCI, 1 PCI-E x16, 2 DDR2 DIMM, Audio, Video, Gigabit LAN, IEEE-1394) Motherboard Chipset - Intel Bearlake G33 System Memory - 4096 MB (DDR2-800 DDR2 SDRAM)...
Hardware & Devices
Monitor automatically turns black, and computer freezes after. HELP!
Hey guys. I'm new to this site and I am seeking help. See, my monitor turns to black like its going to sleep and then when i check my computer, its still working but freezes after the blackout. I've tried going to control panel and change the power options but it still crashes. It happens when i am...
BSOD Help and Support


Our Sites

Site Links

About Us

Find 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 01:27.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App