Hyundai ImageQuest Q17 problem

Soldato
Joined
6 Nov 2002
Posts
9,921
Location
London UK
Evening all, I’ve had my Hyundai ImageQuest Q17 since late 2003 and it’s been a fine monitor, currently serving as my second display for odd bits but mainly video. Anyway I turned it on last night and the desktop flashed up for a second and then the screen went blank. I powered it off and on and still the same issue.

Now I’ve been testing today, different resolutions, both inputs VGA/DVI, and even from different PCs but I keep getting the same problem. Following a signal or res change the screen will display an image for a split second and then turn off.

Any ideas what this could be, If possible I’d like to fix it rather than going for a new screen as other than this fault the screen is in perfect condition. But obviously due to the age of the screen and how cheap replacements are it’s not viable to send it off for repair.

So any help appreciated before I have to post a ‘What LCD do I buy?’ thread :-)
 
Don't know if this is the same problem I get every so often. The monitor keeps defaulting to analogue VGA instead of DVI.

If you press the button right one of the power button (D-Sub/DVI) you might get it to flick back to working before quickly returning to the black screen. If that works then carry on reading.

I had to keep the button pressed in and then go to Device Manager while screen keeps flicking between inputs. Remove the ImageQuest Q17 Digital monitor driver.

Can't remember if needed to reboot or simply Scan for Hardware Changes.
 
Bane, I owe you a beer! :)

I tried the input select and indeed the screen was flashing up. Held down the button whilst removing the driver although no joy, but proceeded to press all buttons at once (using my 10 years worth of professional technical knowledge :p ) and the screen has sprung back into life.

Major result as I really couldn't be bothered with the hassle of deciding on a new monitor.

EDIT: There does appear to be some sort of banding issue on the screen now, although hopefully a reboot and driver update may resolve.
 
Last edited:
Back
Top Bottom