FAIL - 4870x2@1920x1080 60Hz w/ DX10

[kompulsive]

Has anyone got this to work yet? I'll definitely be back on the phone with ATI tomorrow as they tried to tell me today that it was a problem with the individual games that were working and now I know it is a problem on their end. This is absolutely ridiculous that this card is not working to do the one thing I bought it for. This is highway robbery.

MY BLOOD IS BOILING.

[G0ldBr1ck]

How is it not working? black screen, artifacts, crash, etc.........

[soundood]

you allready have a core i7, just go the nvidia route, and RMA it

[SNiiPE_DoGG]

of course the 4870x2 work at the spec you listed in the OP, you probably have a bad driver installation or a bad card....

[kompulsive]

I just built this system and I am using a 24" BenQ E24000HD monitor. My desktop resolution is 1920x1080 at 60Hz and it is working fine. I have the latest drivers installed for both my 4870X2 graphics card and monitor. In some games, when I try to select 1920x1080 resolution, my monitor goes completely blank and an "Out of Range" message is displayed by my monitor. In many cases I am forced to hard reset my machine, but sometimes I can CTRL+ALT+DEL out of it. This happens in BioShock, S.T.A.L.K.E.R. Clear Sky and World in Conflict so far. This is so frustrating. I've called BenQ and they told me that my monitor driver is installed just fine and that it has to be an issue with the graphics card, which I believe. ATI told me to contact the game manufacturer because my graphics drivers are all installed fine. To make sure that it wasn't just the games, I installed the Unigine benchmarking program and I experienced the same crashes when using DX10. I feel like a sucker and an idiot. I absolutely cannot figure out what the problem is. I'm going insane here.

I'm about to take a baseball bat and destroy my entire rig, strip down naked, light myself on fire, and run down the street screaming.

[soundood]

this is not just an issue for that res, have you tried a custom autoexec.cfg file with the 'r_width=1920' and 'r_height=1080' for games?

you know like crysis?

[BeepBeep2]

Thats because the games are changing from 60hz to XXhz.

The monitor says out of range because the video card is outputing too many hz for the monitor. It's a safety mechanism.

[BeepBeep2]

Okay, first...open up Catalyst 9.1 and do to the Digital Panel (DVI) page. Take a screenshot and show it to me. Trust me, I can fix this for you if you show me that page.

[cadaveca]

only 3D gives you crashes? For Stalker, it's definately the app...there are so many bugs as in the original stalker, that it's hard to complete the game...

I think that most DX10 apps have a classic memory leak...it could be a simple problem like you DirectX has a bad file...


DX10 support and 1920x1080 not working is a software issue...Crysis had the same problem, but a patch fixed it(pissed me off..2560x1600 monitor, best I could select was 1680x1050)...

I feel your pain, having gone through it myself, but I do feel that these OEMs are NOT giving you the run around...they are probably just as confused as you are.

[kompulsive]

Okay, first...open up Catalyst 9.1 and do to the Digital Panel (DVI) page. Take a screenshot and show it to me. Trust me, I can fix this for you if you show me that page.

Here it is...

[Sparky]

I'm about to take a baseball bat and destroy my entire rig, strip down naked, light myself on fire, and run down the street screaming.

I think your username fits you quite well

[kompulsive]

this is not just an issue for that res, have you tried a custom autoexec.cfg file with the 'r_width=1920' and 'r_height=1080' for games?

you know like crysis?

I don't have Crysis. I'm epic broke right now but I will buy it soon. I did have a version of it, but 1920x1080 was not an option.

[BeepBeep2]

Check reduce DVI frequency on high-res displays. Then start up any game that didnt work...

See, the games were trying to run 1080p @ 85hz. Checking that should fix it.

[msimax]

theres also this
or try regedit to set the resolution it works for a number of my games

[BeepBeep2]

Yes, try what I said first then try what msimax shown if it doesnt work.

[kompulsive]

As soon as I click that check box, the dreaded "Out of Range" message pops up and I have to do a hard restart.

[kompulsive]

/facepalm

[Raiderman]

Use the windows/properties/advanced tab and make sure the 60hz is used. That way if you get the "out of range" screen again, windows will revert back to the original setting.

[kompulsive]

Use the windows/properties/advanced tab and make sure the 60hz is used. That way if you get the "out of range" screen again, windows will revert back to the original setting.

I'm using Vista x64 so I'm not sure which setting you're talking about, but under "Advanced" Display settings I already have it set to 60Hz. It still does not reset back to 60Hz when this problem happens.

[kompulsive]

I tried connecting my monitor to my 4870X2 via HDMI and 1920x1080 worked. No more "Out of Range." The thing is, I find the quality of the connection unacceptable. There is a weird color/contrast distortion for some reason. Also, the games ran with four bars around the picture. The benchmark utility, however, did not have the bars. I guess this means that my monitor is not the problem. So what else does this all mean?

[Miwo]

HDMI is the same quality as DVI, the only difference is that the cable can transfer Audio also. I doubt the card is at fault here tbh

The four bars around the picture sounds like you are underscanning.... go to Scaling Options and make sure its set to 0%. I use the DVI->HDMI connection to go to my Samsung 37" and i had to do this for the picture to be the correct size

As far as the weird contrast, its possible your display has different video settings on the HDMI input to gear towards other video devices (such as bluray or PS3). Check your settings on the TV/Monitor

[kompulsive]

Damnit. I unplugged everything but the HDMI connection to the monitor and the picture looked good when I started up. I checked the settings and it said it was set to 1920x1080 at 59Hz instead of the normal 60Hz it says when I'm connected via DVI. So being the idiot I am, I messed with it and changed it back to 60Hz. Now the picture is messed up looking and the color is messed up again. I switch back to 59Hz but this doesn't fix it. Keep in mind, this entire time when I check my monitor buy using the buttons on the side of it and selecting "Information" it says 60Hz.

...it seems like the issues just keep multiplying.

[kompulsive]

I uninstalled the drivers for my monitor and here is what CCC says now.

[charged3800z24]

Damnit. I unplugged everything but the HDMI connection to the monitor and the picture looked good when I started up. I checked the settings and it said it was set to 1920x1080 at 59Hz instead of the normal 60Hz it says when I'm connected via DVI. So being the idiot I am, I messed with it and changed it back to 60Hz. Now the picture is messed up looking and the color is messed up again. I switch back to 59Hz but this doesn't fix it. Keep in mind, this entire time when I check my monitor buy using the buttons on the side of it and selecting "Information" it says 60Hz.

...it seems like the issues just keep multiplying.

Does your monitor have an auto adjust button or option in the menu?

[ownage]

Out of range?????

Most times that means that a game starts on its default resolution (if the game is just installed and starts for the first time), and that big ass screen doesn't support small resolution. That happens sometimes. Maybe you should also install the monitor driver.

And have you tried what that guy on the AMD forum replied to you?

With the ‘Out of Range’ error I got, I sent a few emails and received some phone calls from BenQ and I must say their willingness to go above and beyond to figure out the issue was absolutely excellent! At this time I believe the actual problem was a windows driver issue. I installed the BenQ Plug & Play Monitor driver (supplied on the included CD) and upgraded to the latest (went from 8.8 Catalyst to the 8.10 Catalyst package) drivers and so far have not seen the problem return. And if it did, a reboot so far always has fixed it (again, pointing more toward windows and/or driver issue and not the monitor itself).