UberGerbil wrote:I was going to ask you what type of video output you were using but checking the specs it looks like that particular motherboard only has VGA out (it also has COM, Parallel, and two PS/2 ports -- how very retro). So it seems likely there's some issue with the analog video signal -- it's out of spec as far as what the monitor can handle, or the monitor needs to be manually adjusted. It's been a while since I messed with fine-tuning VGA, and I know I've never done it with a Sandy Bridge IGP, so I don't know what options are available in your display settings for the analog output. But if it's trying to drive the monitor at a refresh rate it doesn't like (for example), you could see the symptoms you describe.
(There's a chance it's your no-name PSU -- cheap PSU + analog signals might produce this kind of problem once the video driver is pushing things hard, but I'd look into the display settings first)
Ryhadar wrote:Did you make sure the refresh rate of the monitor wasn't set to something stupid low/high? 60Hz is where it probably should be at.
ludi wrote:When you verified the display refresh rate, did you look for it in the Windows control panel applet, or did you look for it in the Intel graphics utility?
Not sure about the newest stuff, but I know my CULV-based laptop has a separate Intel graphics utility that likes to live down in the system tray. Haven't had any problems with it, but several years ago I did fight several times with an ATi driver that would override the Windows refresh rate preference with a custom driver setting that was buried deep in ATi Submenu 17, just above the earth's core. It was quite maddening to chase that one out, because you could set the Windows refresh rate to whatever you wanted, and it would indicate that the new setting was active, but the display was stuck at 60Hz regardless.
ludi wrote:If you've also tried multiple driver revisions (assuming they exist), there's a very good possibility that you have a defective board. If there is only one driver revision available, then it could be the board or the driver.
Users browsing this forum: Bing [Bot] and 5 guests