I had been running an HP w2207 monitor with an AMD setup for about 3 years without any problems using the digital input. Just "upgraded" to an i5 2500k system. Running Win 7 64 bit before and now.

The w2207 works with the 2500k system wonderfully -- until power saving settings turn the monitor off. Then I'm subjected to a constant symphony of "device connect," "device disconnect" sounds. The only way to stop it is to turn those sounds off in the windows sounds screen, or to prevent the power saving system from turning the monitor off at all.

I just added an HP 2311x as a second monitor, and the problem doesn't happen with that monitor, which is a couple of years newer.

Lately, when the computer recovers from S1 standby, the 2311x comes up, but the w2207 is not even detected. I have to reboot my system for my Intel 2500k system to see it again.

I don't have these problems using VGA with the w2207, but I want to use the digital input (the quality difference is quite noticeable). Again, I had no troubles of this sort with the w2207 on my AMD system right up to the day about a month ago that I moved to the Intel 2500k system, and have been having these problems with the Intel system from jumpstreet. So this very much appears to have something to do with the way the w2007 communicates with the HD 3000 graphics in the Intel. I was using the 2509 driver, and just updated to the 2550 driver, with no change.

I hope somebody can help. That "somebody" would probably be Intel with a driver update, but I'd also love to hear if anybody can suggest a temporary workaround.

Thanks, but I mentioned that I had tried the updated driver (I think I referred to it as the 2500 driver, when as you point out it is the 2559 driver). I also made sure that I had the latest monitor driver, and am using the latest BIOS. I tried uninstalling and reinstalling all the drivers a couple of times.

Intel, have you tested this series of monitors and S1 sleep on the i2500k? This series of monitors was hugely popular, and there are doubtless many tens of thousands of them still in service. There is no (good) reason that they should not be fully compatible with Intel GPU/CPUs.

Intel, it has been more than 2 weeks since you last replied to my query, and since then another board member said he has the same issue. Is the best you can tell us that we should go out and buy a separate graphics card so we can use basic computing functions?

On a hunch, I tried a much earlier driver, 2279, from a year ago. Under the ancient driver, my monitor makes only a single "device disconnect" sound going into monitor sleep (no "device connect" sound), and it resumes from S1 sleep. Although I'm glad to have found this temporary workaround, it demonstrates conclusively that this is a driver problem. Accordingly, Intel, I hope you will acknowledge this as a driver issue and promise a fix. Users should not need to run year old drivers, and trade improvements in speed and other attributes that typically come with newer drivers, for basic functionality.

Update: I'm finding that the w2207 sometimes does not come out of sleep with the older driver, but that I can restore it by disabling and then reenabling the display adapter. Again, Intel, this appears to be a driver issue, with the older driver imperfect but better than the newer driver. Can we expect you to address this issue in a driver update?

I am having similar problems with my HDMI connected TV/AVReceiver. The solution (as provided by other Graphics companies) is to have an option on the graphics driver to disable monitor Auto-Detect. It should be a fairly simple option to add, but so far Intel has not agreed to add it. In fact the best I got was that support "may forward this feedback to the appropriate team for a future consideration."

It is possible that there is a registry key to control this behavior already, but support will not discuss it.

I am having the exact same issue. If I forget to turn my primary HP monitor off before the dual monitors go to sleep, the graphics subsystem disconnects and reconnects the device over and over. After hours of this, eventually system usually blue screens. So, it's effectively impossible to have a stable, always-on system without excessive power consumption.

The primary monitor has been used with several other Windows 7 systems, with Nvidia and Radion drivers, with no problem. I'm using Core i5-2500K CPU. Have tried many different versions of HD 3000 Graphics drivers.

How hard would it be for Intel to add a driver option to disable automatic monitor detection? This seems to be the standard practice, and it would not require Intel to test the driver with many different monitor models.

I am extremely discouraged about Intel as a result of the lack of support or any attention to this issue.

I have the same problem, is there a solution for this annoying problem? Every time that I turn of my monitor I hear the connect and disconnect sound, and the worst part is the the resolution flickers when I turn the monitor on which screws up open windows and icons, everything on the desktop becomes mixed up. Who's bright idea was it to implement this feature and how can can it be turned off?

Have same issue. Just built 2 "identical" computers with the following specs - differing in the Monitor only (detailed specs below).

The computer with the HP w2207 monitor connected via DVI (note that this monitor also has a USB hub connection in that it has a USB "in" and allows 2 USB devices connected to the side) will NOT go to sleep IF the monitor has already attempted to go to sleep (in which case it just cycles making USB device connect "bink/bonk" noises). Note that everything works IF you tell the monitor to never go to sleep and the computer attempts to sleep - this issue happens when (the majority case) the monitor attempts to enter sleep mode before the computer. Once the monitor attempts to sleep, it does go dark but then makes connect/disconnect "bink/bonk" noises in an endless loop and prevents the computer from entering sleep mode.

- See if disconnecting the monitor's USB cable (and thus disabling the USB ports on the side of the monitor) work (not acceptable but just want to see if it affects it).

- Check to see if there are any more recent Intel video drives or HP monitor drivers.

Please post here if anyone finds a solution.

NOTE: If you set your monitor to NEVER SLEEP, this seems to work (gets rid of the cycling bink/bonk noises and computer will eventually sleep), but really do not want my monitor to stay on for a couple hours until my computer enters sleep mode.