Graphics
Intel® graphics drivers and software, compatibility, troubleshooting, performance, and optimization
20598 Discussions

Black Screen after upgrading to G45/G43 Chipset driver 8.15.10.2182

idata
Employee
9,738 Views

Hi,

I searched for this problem but only came up w/ an issue against the 8.15.10.2086 driver that has supposedly been resolved in 2182. I am having the same symptoms described in the 2086 thread but with the 2182 version.

My current driver version is 8.15.10.1749. I am running Windows 7 Home Premium on a Dell Studio desktop. Microsoft update pushed the latest display adapter driver to my PC and from that point on, I would get a black screen when the logon screen displays. I logged into safe mode to roll back the driver. I then went to Intel's driver detector site and downloaded 2182 directly. The screen snapped to a huge resolution then to black. I rebooted and got the same black screen problem.

I am trying to upgrade the driver b/c I am attempting to play Diablo II Lord of Destruction (admittedly an old game) and it starts fine and plays for a while, then crashes out. Oftentimes, the graphics get corrupted and window posts an error saying the driver stopped working but recovered.

Here is my information from the Graphics and Media Control Panel:

Intel® Graphics Media Accelerator Driver Report

 

Report Date: 9/18/2010

 

Report Time[hr:mm:ss]: 11:38:11

 

Driver Version: 8.15.10.1749

 

Operating System: Windows 7 (6.1.7600)

 

Default Language: English (United States)

 

DirectX* Version: 10.0

 

Physical Memory: 6109 MB

 

Minimum Graphics Memory: 32 MB

 

Maximum Graphics Memory: 1695 MB

 

Graphics Memory in Use: 61 MB

 

Processor: Intel64 Family 6 Model 23 Stepping 10

 

Processor Speed: 2499 MHz

 

Vendor ID: 8086

 

Device ID: 2E22

 

Device Revision: 03

 

* Accelerator Information *

 

Accelerator in Use: Intel(R) G45/G43 Express Chipset (Microsoft Corporation - WDDM 1.1)

 

Video BIOS: 1666.0

 

Current Graphics Mode: 1440 by 900

 

* Devices Connected to the Graphics Accelerator *

 

Active Digital Displays: 1

 

* Digital Display *

 

Monitor Name: Generic PnP Monitor

 

Display Type: Digital

 

Gamma Value: 2.35

 

DDC2 Protocol: Supported

 

Maximum Image Size:

 

Horizontal: 16.14 inches

 

Vertical: 10.24 inches

 

Monitor Supported Modes:

 

640 by 480 (67 Hz)

 

640 by 480 (72 Hz)

 

640 by 480 (75 Hz)

 

640 by 480 (60 Hz)

 

720 by 400 (70 Hz)

 

800 by 600 (72 Hz)

 

800 by 600 (75 Hz)

 

800 by 600 (56 Hz)

 

800 by 600 (60 Hz)

 

832 by 624 (75 Hz)

 

1024 by 768 (75 Hz)

 

1024 by 768 (70 Hz)

 

1024 by 768 (60 Hz)

 

1152 by 864 (75 Hz)

 

1152 by 870 (75 Hz)

 

1280 by 1024 (75 Hz)

 

1280 by 960 (60 Hz)

 

1280 by 1024 (60 Hz)

 

1440 by 900 (60 Hz)

 

1440 by 900 (75 Hz)

Display Power Management Support:

 

Standby Mode: Not Supported

 

Suspend Mode: Not Supported

 

Active Off Mode: Supported

 

Raw EDID:

 

00 FF FF FF FF FF FF 00 4C 2D 74 02 39 31 45 4D

 

08 11 01 03 80 29 1A 87 2A DE 95 A3 54 4C 99 26

 

0F 50 54 BF EF 80 95 00 95 0F 81 80 81 40 71 4F

 

01 01 01 01 01 01 9A 29 A0 D0 51 84 22 30 50 98

 

36 00 9A 01 11 00 00 1C 00 00 00 FD 00 38 4B 1E

 

51 0E 00 0A 20 20 20 20 20 20 00 00 00 FC 00 53

 

79 6E 63 4D 61 73 74 65 72 0A 20 20 00 00 00 FF

 

00 48 4D 45 50 32 31 36 32 30 38 0A 20 20 00 77

 

* Other names and brands are the property of their respective owners. *

Thanks in advance for any help you can provide.

0 Kudos
46 Replies
idata
Employee
1,945 Views

I forgot to mention that I have 64-bit Windows. That driver is for 32-bit versions. Do you have a 64-bit version?

0 Kudos
idata
Employee
1,945 Views

No joy with 2104 either. Same symptoms. When upgrading, display loses signal and goes to sleep, never comes back. Restarting the machine results in loss of signal and going to sleep at the logon screen.

0 Kudos
ROBERT_U_Intel
Employee
1,945 Views

In you diag report above it show "Generic PnP Monitor",, can you go into display properties and enumerate it for the correct display? Once the correct display is shown, try updating the driver to the 15.17.11.2202 at http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=19336 http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=19336

0 Kudos
idata
Employee
1,945 Views

Almost...

In the Intel Graphics Properties window, it appropriately showed my monitor as SynchMaster, but not in the Device Manager in the Control Panel. I updated the monitor drivers and now they show the appropriate monitor.

I then downloaded and installed version 2202 of the driver. It ran a test for a little while before dropping my screen resolution to the lowest setting, then ran a little while longer then the monitor lost signal. I let it sit for several minutes before the computer eventually restarted.

I was able to log in, but the Aero feature of Windows 7 was diabled. I then attempted to run Diablo 2 Lord of Destruction (which I had been running previously) and the monitor lost signal again and never came back on. I restarted the computer and the monitor would again lose signal at the login screen. I rebooted multiple times with the same result.

I once again had to start up in safe mode and roll the driver back.

0 Kudos
ROBERT_U_Intel
Employee
1,945 Views

What is the model number of your display? How is it connected (DVI, HDMI, DP, VGA) ?

By any chance do you have access to another display you can try with the 2202 driver?

0 Kudos
idata
Employee
1,945 Views

It is a Samsung SyncMaster 906BW. It is connected to the PC using a DVI-D Dual Link cable through a DVI-D-to-HDMI adapter (the port on the PC is HDMI which the monitor does not support). I do have access to another display, but it is only a VGA display. When I get a chance to grab it and try it out, I will post my results here.

0 Kudos
idata
Employee
1,945 Views

I just tried the 2202 driver using a Lenovo VGA monitor and it seems to be working better. The install went more smoothly. There was still the jump to low res, but then back to hi res, never losing signal. I have restarted the machine 4 times without reproducing the issue. I started Diablo II LoD without issue. I did not play the game long enough to determine if the intermittent display-related crashes still occurred.

Looks like the problem is tied to either the output signal from the display adapter or the monitor itself.

By the way: I appreciate all of your help.

0 Kudos
ROBERT_U_Intel
Employee
1,945 Views

Good news!! Thanks for posting back your results.

0 Kudos
idata
Employee
1,945 Views

Is that good news b/c that helps you figure out a fix for the problem, or good news b/c you figure it's not your problem anymore?

It's not good news for me b/c I still can't upgrade my drivers and am still stuck with old versions that crash my game randomly. The VGA monitor I tested on had to go back to its original owner.

0 Kudos
ROBERT_U_Intel
Employee
1,945 Views

As I read your last post it appeared the 2202 driver, the latest, resolved your issue. Therefore the "good news" was your issue resolved. My problems with the drivers will never go away, there will always be new issues to address as software and hardware evolve.

0 Kudos
idata
Employee
1,945 Views

Sorry, no, there must be a misunderstanding. The problem w/ the 2202 driver went away when I switched to an analog VGA monitor I borrowed for debugging purposes and had to return to the owner. The problem still exists with the digital HDMI/DVI monitor that actually belongs to my system.

All we know now is that the driver is buggy either with my specific monitor or with the digital output. Hopefully you can still track down the problem so I can one day upgrade on my system.

Thanks.

0 Kudos
ROBERT_U_Intel
Employee
1,945 Views

I will see if I can find that display and see if I can replicate the issue. None of the panels I have reproduce it.

0 Kudos
idata
Employee
1,945 Views

I got this problem with both the 8.15.10.2182 and the 8.15.10.2202 driver chipset. As long as they are disabled my computer works fine. When I enable them I get the black screen when the Login Screen should be present.

0 Kudos
idata
Employee
1,945 Views

Is there any update on this issue? It's been silent for 3 months.

Thanks!

ROBERT_U_Intel
Employee
1,945 Views

We have not been able to reproduce this issue as detailed in this thread. However, similar issues have been resolved with the following drivers. If possible, please test the following drivers to see if it will resolve the issue you are seeing and provide feedback.

64 bit driver http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=18402 http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=18402

32 bit driver http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=18400 http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=18400

0 Kudos
idata
Employee
1,945 Views

The driver you just linked to has the exact same version number as the driver we already tried 3 months ago (as you'll see by reading page 1 of this thread). Oddly, though, the two links point to files that have different dates and slightly different file sizes, but I suppose this could be attributed to being packaged slightly differently.

Anyway, with the same failed driver version as last time, I get the same failed result as last time. Do you have anything different to try?

0 Kudos
idata
Employee
1,945 Views

Well, now Windows Update has started pushing 2202 to my desktop which is again resulting in the black screens. I had to log in to Safe Mode and roll back the driver and then disable the update in Windows Update to continue to use my machine.

I imagine the continued silence means Intel has given up on this issue and I just need to suffer through intermittent pushes of drivers that disable my machine going forward.

0 Kudos
idata
Employee
1,708 Views

I also received the update on Windows updates. I wondered about installing the file, and when I looked into it, I found all this trouble like what you say. I also disabled the update to my G45 express chipset. I just see I will keep the version 8.15.10.1749 and not update the graphics unless I ever see the trouble is resolved. Sorry you have had so much trouble.

0 Kudos
Reply