2209WA monitor won't come out of Power Save with Precision 5510

This could be because the 7 year old 2209WA was never tested in Windows 10. The lack of a dedicated Windows 10 INF driver for the 2209WA could be the culprit in the HDMI to DVI/VGA communciation breakdown =

I take it that you did not have this issue when using a computer with DVI out or VGA out ports?
Did you try to install the 2209WA driver in Windows 10 compatibility mode?

The monitor has worked fine on machines running Vista and Windows 7 through VGA with Power Save performing correctly.

The current Windows 10 machine was upgraded from Windows 7 which presumably had the driver installed correctly.

I haven't reinstalled the driver and haven't installed it in compatibility mode.

The driver currently installed (as per device manager) is "Dell 2209WA(Analog)" with a driver from Dell from 21/04/2009 version 1.0.0.0. The only files shown are monitor.sys and 2209WA.ICM - no .inf file here.

In the Microsoft-Windows-Kernel-PnP/Device Configuration log are the following:

Device DISPLAY\DELF010\4&b23856c&0&UID198195 could not be migrated.

Last Device Instance Id: DISPLAY\ITE40D6\4&B23856C&0&UID198195

Class Guid: {4d36e96e-e325-11ce-bfc1-08002be10318}

Location Path:

Migration Rank: 0xF000FFFF0000F102

Present: false

Status: 0xC0000719

Device DISPLAY\DELF010\4&b23856c&0&UID198195 was configured.

Driver Name: oem60.inf

Class Guid: {4d36e96e-e325-11ce-bfc1-08002be10318}

Driver Date: 04/21/2009

Driver Version: 1.0.0.0

Driver Provider: Dell Inc.

Driver Section: 2209WA_Analog.Install

Driver Rank: 0xFF0000

Matching Device Id: MONITOR\DELF010

Outranked Drivers: monitor.inf:*PNP09FF:00FF2000

Device Updated: false

Parent Device: PCI\VEN_8086&DEV_191B&SUBSYS_06E51028&REV_06\3&11583659&0&10

Device DISPLAY\DELF010\4&b23856c&0&UID198195 was started.

Driver Name: oem60.inf

Class Guid: {4d36e96e-e325-11ce-bfc1-08002be10318}

Service: monitor

Lower Filters:

Upper Filters:

Any suggestions for things to try first?

The driver I listed does have an INF. Unzip the file and force the Device Manager to accept the INF. Unknown how non-validated Windows 10 will react.

Windows 10 may not accept it.

* Download the monitor driver to your desktop
* Unzip the file to its own folder on your desktop
* Open the Device Manager
* Click the icon left of Monitors
* Double click the monitor listed
* Click the Driver tab
* Click the Update Driver button
* Click No, not at this time
* Click Next
* Dot Install from a list or specific location
* Click Next
* Click Don't search. I will choose the driver to install
* Click Next
* Click Have Disk
* Click Browse and navigate to where the three files (ICM/INF/CAT) are located
* Click the monitor inf file
* Click Open
* Click OK
* Click Next
* Click Finish

I just checked the 2209WA.inf against the oem60.inf. They are exactly the same, character for character. So that's probably why it wouldn't update the driver.

This makes me then wonder what DPMS control the Intel 530 HD is exercising (H-sync and V-sync?) and whether this is what is incompatible with the monitor.

Chris - it doesn't quote work out as you suggest in Windows 10. The driver selection when updating is a little different and you can only select the folder not the .inf file. When I try to update the driver with the folder with the 2209WA driver in it, it says that it is already up to date (and I assume doesn't actually update the driver). When I look through the properties/details for the monitor is references both oem60.inf for "inf name" and "configuration id". It's worth noting that the oem60.inf file on my machine is actually written by Dell for the 2209WA:

;-------------------------------------------
; Copyright (c) 2007 Dell Corporation
; Issue date -- 04/21/09
; revision 1
;This is a setupfile for 2209WA
;-------------------------------------------
[version]
signature="$CHICAGO$"
Class=Monitor
ClassGuid={4D36E96E-E325-11CE-BFC1-08002BE10318}
Provider=%Dell%
CatalogFile=2209WA.cat
DriverVer=04/21/2009,1.0.0.0

...

...

[2209WA_Analog.Install]
DelReg=DEL_CURRENT_REG
AddReg=2209WA_Analog.AddReg, 1680, DPMS
CopyFiles=2209WA_Analog.CopyFiles

So it's got DPMS turned on.

The "power data" for the driver in the driver properties is this (not sure if this is relevant):

Current power state:
D0

Power capabilities:
00000009
PDCAP_D0_SUPPORTED
PDCAP_D3_SUPPORTED

Power state mappings:
S0 -> D0
S1 -> D0
S2 -> D3
S3 -> D3
S4 -> D3
S5 -> D3

So I'm not sure what the way forward on this is. Is there an alternative way to get the driver recognised? Would it work anyway if it was recognised? Is there something in the BIOS that needs changing? Is there a registry hack to force the setup to deal correctly with Power Save? Is there a mini-program that could be triggered from a function key or similar that forces the re-recognition of the monitor to force it out of power save without having to disconnect the cable?

Sorry for so many questions, but as you can tell this is really hacking me off.

Thanks

Andrew

There is nothing in the laptop bios to address the monitor and Windows 10. You should ask the guys on the Windows 10 board the questions about possible registry hacking. It may just be time to get a current monitor that is supported by Windows 10.

Chris - thanks for all your input. I'll try the Windows 10 guys as you suggest. It seems a shame to ditch a perfectly good monitor.