Monitor quits

NascarFool · Post by **NascarFool** » Mon Feb 16, 2004 12:05 am

I recently switched from an nForce board to a VIA600 board. While playing UT2K3, the monitor quits and it displays "Out of Range" on the screen. The green power light turns amber too. I went back to the Cat 4.1 drivers and it still happens. Any clues ?

*Edit*
It only happens when gaming.

Specs:
ViewSonic A90 monitor set at 1024x768 @ 85Hz refresh
XP3000+ (no O/C, 30C on the temp)
2x512megPC3200
MSI KT6 Delta LSR (Latest bios and Via drivers installed)
ATI Radeon AIW 9700 Pro with Zalman HP cooler and 80mm fan (Cat 4.1 now)
2x36GB Raptors in RAID0
Fresh XP Pro with SP1 installed
DX9 installed

VidmanII · Post by **VidmanII** » Mon Feb 16, 2004 1:14 am

Could it have anythng to do with the refresh rate override in the "display" tab of the CAT drivers? Check to make sure it's not set too high or low ( I have it disabled on both my monitors ) and make sure your refresh rate in the "adapter" tab is set to where it should be.

nexus_7 · Post by **nexus_7** » Mon Feb 16, 2004 1:20 am

Would you listen to a Junkie? LOL

Greg

wvjohn · Post by **wvjohn** » Mon Feb 16, 2004 8:05 am

sounds like some kind of refresh rate/resolution in compatibility - might have to bring it up in safe and and start at 800x600x16x60 and take it from there - i had that problem when i would try and hook up oe of my main rigs to a bench monitor which could only do low settings

nice pice vid!

NascarFool · Post by **NascarFool** » Mon Feb 16, 2004 8:23 am

Refresh rate in the Displays tab is disabled. Will try again later today.

Post by **FlyingPenguin** » Mon Feb 16, 2004 10:20 am

Are you using Refresh Force or some other app that forces the refresh to stay at a certain setting when gaming? Could be set wrong.

Alternately if you're not already using it, it could fix your problem.

By NVidia and ATI are supposed to default to 60Hz in games unless you use Refresh Force or (in D3D) use the refresh override in the ATI display settings.

Might also be the CAT drivers. Go back to old reliable 3.7 and see what happens.

NascarFool · Post by **NascarFool** » Mon Feb 16, 2004 6:26 pm

No sir, I don't use any refresh programs. Just a fresh install of WinXP with the latest updates and all hardware drivers are current. No "hacked" drivers either.

*Edit*
Found that one 512megPC3200 was bad. Now I'm wondering if I could have a flakey install of WinXP. Damn, 255 errors on Memtest #2. Sure am glad I bought ram with a lifetime warranty.

Post by **FlyingPenguin** » Mon Feb 16, 2004 10:54 pm

Better swap that out for a known good stick of ram and test it again.

The problem with memory tests is that things other than bad ram can also give you errors (overheating CPU, bad CPU, flaky mobo)

VidmanII · Post by **VidmanII** » Mon Feb 16, 2004 11:04 pm

Originally posted by FlyingPenguin
Better swap that out for a known good stick of ram and test it again.

The problem with memory tests is that things other than bad ram can also give you errors (overheating CPU, bad CPU, flaky mobo)

Don't forget flaky user . :laugh

NascarFool · Post by **NascarFool** » Mon Feb 16, 2004 11:09 pm

Originally posted by FlyingPenguin
Better swap that out for a known good stick of ram and test it again.

The problem with memory tests is that things other than bad ram can also give you errors (overheating CPU, bad CPU, flaky mobo)

Ok, I maxed at 518 errors on one stick. I ran the other 512PC3200 and no errors. UT2K3 runs fine with that stick too. Looks like I have One stick of Buffalo with Infineon chips that is bad and one stick of Buffalo with Winbond CH-5 chips that is bad.