GPU-Z says the following...
Release Date: August 12, 2008
BIOS Version VER011.007.000.000.030318
How do I find out what the latest BIOS version is and obtain a copy of it?
Printable View
GPU-Z says the following...
Release Date: August 12, 2008
BIOS Version VER011.007.000.000.030318
How do I find out what the latest BIOS version is and obtain a copy of it?
ah i thought you ment mb bios. anyway techpowerup has a vga bios collection. http://www.techpowerup.com/vgabios/ although for a saphire 4870x2 i couldn't find one newer than yours. you might wanna do a google search to see if there are any more updated ones or if someone made one.Quote:
Originally Posted by kompulsive
Yeah, all those are older than mine. What's with the lack of BIOSs? People just don't flash them much or what?
I just did a fresh install of Catalyst 9.1 and I'm getting this crap now...
http://members.cox.net/kompulsive/fail.jpg
Any suggestions? Also, does this mean that only "half" of my card is working?
So I followed normal procedure to try to get the driver installed correctly. I right-clicked the "ATI Radeon 4870X2" with the yellow exclamation mark, went to uninstall, got rid of it, then scanned for new hardware and the display adapter popped up. I navigated to where the 9.1 drivers were on my computer, it began installing them, the screen started flicker like the install was going fine, then this message popped up in the status bar...
http://members.cox.net/kompulsive/fail2.jpg
What the hell is going on?
well does it work even tho only one core is working? also have you checked your bios settings to make sure there aren't any problems there?
Do you have an LCD TV, I would try that at 1080P before you blame the card....I have an issue with a samsung monitor and blurays plus bluray software, If I update the software it says my monitor is not HDCP compliant and refuses to work.........My Tv however is problem free.
No LCD TV here. I have a BenQ E2400HD.
Yes, I can play games and everything still. Which BIOS settings should I check in particular?Quote:
Originally Posted by roofsniper
well if the problems are all gone when that one core is disabled it might say something. see if it will let you disable the other core and turn the one that is disabled right now back on. if disabling a core is making everything work then its most likely not your monitor. as for the bios settings im not really sure what to look for but i would check them out especially the graphics related ones. did a google search of "asus p6t 4870x2" and found this: http://forums.guru3d.com/showthread.php?t=282912. someone else had problems with both cores working at the same time. try using 8.10? http://www.techpowerup.com/downloads...XP_32-bit.htmlQuote:
Originally Posted by kompulsive
Uh...no. My monitor problems are not all gone. In fact, they are worse. I have the Out of Range issue AND the drivers not being properly installed.
Process of elimination done right would at least imply a clean OS install to start with as mentioned previously dude.Quote:
Originally Posted by kompulsive
I just did a fresh install on a different hard-drive. The previously mentioned issues with the driver installs are gone, but the good ole' "Out of Range" error remains.
you have done enough troubleshooting i would just rma the card to see if it changes anything. it has made it to the point where its probably a hardware issue.Quote:
Originally Posted by kompulsive
The out of range error is the refresh rate and some games intro are @ 640 but main menu starts @ 800 try to wait for the main menu to come on,if you get a picture set res and refresh rate and restart app.If menu is also @ 640 then you need to change cfg or create auto cfg.:up:
Guys the "Code 43" problem is widely spread over users of multi-gpu configurations. For quite a number of people (including me) no catalyst driver except 8.10 (sometimes 8.11) are working.
I think that also relates to refresh rates and multimonitor support.
I also have Code 43 error with every catalyst drivers bar 8.10.
Also started getting black screen during boot up although no out of range error. Tried every possible combination of what's listed and many more....
Also I know for a FACT that there is nothing wrong with the card....crossfire and everything works perfect in 8.10 - only weird sh&&t start from Cat 8.11 onwards - no need to RMA.
It is a driver problem which hasn't been resolved yet....and it also is related to Ati External Event service which installs automatically with drivers.
Go to command/services.msc disable the service completely and REBOOT - that solves the Code 43 problem (and possibly the refresh rates)....but there is other issue......if you disable this service all 3D acceleration stops working - apps can't initialize 3d device and/or D3D.
What's even more strange that disabling this service in Catalyst 8.10 has no effect on working 3d - you can run everything with it as well as without. With Cat 8.11+ if you disable it....code 43 is gone....but no 3D :shrug:
Issue persists....hope this clarifies a situation a little bit....I think ATI has a lot of work to do.:down:
i would go with the last post, i have been watching tyhis thread, and all this reminds me of the hasle we nvidia guys had with SLI when Visat was released.
nvidia just coudnt get the drivers correct, and i was getting 'out of range' errors, and second GPU disabled crap, one set of drivers seemed to work correctly and that was some early XP drivers
try the 8.10 drivers, i bet its fine :up:
EDIT: Reading through the thread, it sounds like during your work you also screwed up your driver install -- so before doing what I suggest below (admittedly it is a long shot), either a clean install or try booting safe mode and running the 'AIT remove all software' wizard from control panel, then reinstall drivers from scratch.Quote:
Originally Posted by kompulsive
I can think of a couple of ways to test this, in order --
1) Run Bioshock from a command line order -DX9 (or if you are on Steam use properties launch with command line options under advanced enter -DX9), does it run? If yes proceed to step 2.
2) Open windows task manager, click on services, find the two services with the word "Tablet" in them, by I cannot remember the full name, but they are the only two services with tablet.
Right-click the select 'Stop'.... Now try running Bioshock but without the -DX9 commandline.
There is a nasty, nasty bug in DX10 and I believe it is in the Xinput API, I have not tracked that down just yet.... anyway, DX10 games tend to hang, not set resolution correctly, or not even go into full screen just stay windowed run a bit then hang -- all this if the Tablet service is running.
I have seen this problem on both nVidia and ATI cards. nVidia cards allow some games to get through the cinematics, but the ATI cards I randomly get the blank screen as you report -- my monitor simply says resolution not supported :)
jack
well im guessing he already used 8.10. i googled it and people said 9.1, 8.12 and 8.11 don't work but they say they got the error gone with 8.10.Quote:
Originally Posted by roofsniper
Bioshock is the one game that worked, for me, @ 1080p and 60hz. As long as you have the 1.2 patch.
You'll need to try a game like Crysis or FC2 to verify that the problem is gone :up:
I quit installing monitor drivers a long time ago, I never found a scenario where they were needed. FYI, the maximum refresh rate reported is usually a refresh rate supported at a lower resolution than what is native or on a different connection, like VGA.
It seems obvious to me that the refresh rate and/or resolution of your monitor is the major hurdle in all of this. The driver issues that have cropped up are most likely because of the repeated installs/uninstalls etc.
Connect that old monitor you have and get your driver issues resolved so both GPUs are working and everything is stable without trying to run any games. Then try running some games to verify everything is still working and stable on that old monitor. If you're buddies with the PC shop guy, ask if you can borrow a standard monitor that runs 1920x1200 instead of 1920x1080 (without the HDMI and all that other crap).
If everything works, you've found your problem. Return/sell the Benq and get something else.
I'm reporting live from a Dell S2409W 24" monitor. I finally went to Best Buy and got another monitor so I could further troubleshoot my issue. I am having the same exact problem with this monitor. This was kind of expected, as I did not think that my monitor was to blame. I just wanted to make sure of it. Aside from the "Out of Range" error, I'm also having the same issues with odd login screen resolutions and dim brightness after logging in (until I run a game, at which point the brightness switches to the correct/normal level but goes dim when I reboot again.) Also, the yellow (!) in the Device Manager has returned since I hooked up the Dell monitor. All of these issues, except the "Out of Range" error which is constant, seem to arise when a DVI connection is changed. The drivers throw a fit and the yellow (!) pops up in the Device Manager.
Anyhow, back to the original problem; the "Out of Range" error that occurs anytime I try to game full screen at 1920x1080 in DX10. I've eliminated a couple of possibilities...
1) My BenQ E2400HD monitor is not to blame.
2) My current install of Vista is not to blame.
The next thing I'm going to do is install an instance of Windows 7 (I've been beta testing it for quite some time now) and see if the issue comes up. Do you folks have any other suggestions?
This is a long shot but you may try this. the repair for vista files is a joke on the startup disk but I had a bunch of troubles with installing ccc after I changed my mobo and this worked. uninstall all your drivers for ati. Use cccleaner as well. physically remove all folders too. reboot and and try the system file checker thru cmd heres the link http://support.microsoft.com/kb/936212 a lot of people dont know about this. make sure all your mobo driveers are upto date or try reinstalling them to be sure. now reinstall catilyst drivers. sometimes vista files are corrupted and startup repair wont fix them. Its worth a try. this nifty little tool has solved a lot of prolems in vista for me.
if you have tried 8.10 already then idk i would just rma the card.
Guess what? Problem didn't happen on Windows 7 32bit. Next thing I'm going to try is Windows Vista 32bit.