Why does my HD4850 suck!?

Hahaha, retardude48, didn't Camaro build your PC? That worked right out of the box, compared to what he's going through.

At first I thought it was the CPU holding you back. And to this day, I still think its the CPU holding you back. :)

Be glad you don't have any Shuttle problems.

D
 
Hahaha, retardude48, didn't Camaro build your PC? That worked right out of the box, compared to what he's going through.

At first I thought it was the CPU holding you back. And to this day, I still think its the CPU holding you back. :)

Be glad you don't have any Shuttle problems.

D

Yea, I would recommend that too. Use family/friend computer to see if the video card is at fault otherwise go to Frys and get yourself a Diamond 4850(70) and maybe a case fan. Also check out the car audio section, lcd monitors, and 32" lcd tv's if you're there too. This way you can eliminate if it is the graphics card. Maybe get yourself an Nvidia chipset too, they seem to get better FPS than those damn P45 boards. Asus is a must. Maybe consider overclocking your cpu and determine if you need to get a aftermarket HSF. Noctua are nice but pricey. Looks like the Artic Cooler Freezer 7 Pro seems like the best bang for you buck. Other than that, I would pour water all over my system.

This helps... Thanks guys! :p

Yes... we all go to the same school, they are losers though.
 
lol@ Camaro's last reply, sorry man, isn't it painful, forums and all. Here's a couple quick questions for you, and if I missed this while reading through, well I know what to expect in reply.

On your original install, with the G33 board, which netted you a slightly better result. Did you have a fresh install of .64 on there, did you have x.64 XP or VIsta on there? Another question on the old install, did you do a fresh, straight-to 8.6hotfix install, or did you roll through a few as they were released since you bought the card, lets say 8.2,8.5,8.6, etc?

On another note, in CPU-Z do your memory settings/timinigs look good?

Let me know, I've recently swapped a bad HD, it was starting to do clicks of death and a loud whine metal on metal noise. Dropped in a brand new HD, installed XP-Pro, went straight to 8.6s' and by doing the seat of the pants, eyeball test on COD4, the framerate seemed off. So I keyed in _drawfps tag as I did before, well it's dropping often below my vsynced' 60FPS. Beforehand, it'd take an airstrike or something major to drop it below 60FPS. So I don't know what gives, I know one thing, using the 8.6 or 8.5 drivers cannot install the HDMI Oudio Out, even with microsoft hotfix for that installed beforehand. The 8.2? drivers or whatever came on the CD took care of that originally. This is more of a hunch, nothing official, but I can and will soon reinstall the old HD to confirm this, just lazy right now and I'm addicted to the dem COD4.
 
It's the 64-bit HL2 binary that is the issue.

I have a Q6600 running at default 2.4ghz and a stock 4850 on Vista x64. Running the 64-bit binary, I get 95fps at 1680x1050 with everything maxed out at 4xAA; running the 32-bit binary, I get 140fps at the same settings.

Try adding -32bit to your Lost Coast shortcut (see below) in Steam and see what you get.

steambl1.jpg
 
I wish you luck, and definitely hope you figure this thing out. However, think about people who game with crappy vid cards... like me.

FX5200 /seppuku
 
It's the 64-bit HL2 binary that is the issue.

I have a Q6600 running at default 2.4ghz and a stock 4850 on Vista x64. Running the 64-bit binary, I get 95fps at 1680x1050 with everything maxed out at 4xAA; running the 32-bit binary, I get 140fps at the same settings.

Try adding -32bit to your Lost Coast shortcut (see below) in Steam and see what you get.

steambl1.jpg

I'll have to try this out when I get home, however, when I ran it on my friends computer (E6600 on 650i chipset) it was running in 64bit mode and it got like 135 or something. I'll have to check when I get home.
 
lol@ Camaro's last reply, sorry man, isn't it painful, forums and all. Here's a couple quick questions for you, and if I missed this while reading through, well I know what to expect in reply.

On your original install, with the G33 board, which netted you a slightly better result. Did you have a fresh install of .64 on there, did you have x.64 XP or VIsta on there? Another question on the old install, did you do a fresh, straight-to 8.6hotfix install, or did you roll through a few as they were released since you bought the card, lets say 8.2,8.5,8.6, etc?

On another note, in CPU-Z do your memory settings/timinigs look good?

Let me know, I've recently swapped a bad HD, it was starting to do clicks of death and a loud whine metal on metal noise. Dropped in a brand new HD, installed XP-Pro, went straight to 8.6s' and by doing the seat of the pants, eyeball test on COD4, the framerate seemed off. So I keyed in _drawfps tag as I did before, well it's dropping often below my vsynced' 60FPS. Beforehand, it'd take an airstrike or something major to drop it below 60FPS. So I don't know what gives, I know one thing, using the 8.6 or 8.5 drivers cannot install the HDMI Oudio Out, even with microsoft hotfix for that installed beforehand. The 8.2? drivers or whatever came on the CD took care of that originally. This is more of a hunch, nothing official, but I can and will soon reinstall the old HD to confirm this, just lazy right now and I'm addicted to the dem COD4.

First off to clearify... I've fresh installed windows like 30 times in the past week. Also I've always installed 8.6 hotfix drivers except now I have 8.7 with the same results.

Memory timings are correct as well.
 
running in 32 bit mode (still vista 64) improved the fps to 120 from 30-60 on the lost coast benchmark.. still less than expected but i'll run some other tests as this seems to be at least partially a hl2 64bit problem for me
 
Not familiar with the Bios on the Asus board you are using but go into your bios and set the PCI-E vid card bus to 100mhz manually.
 
Not familiar with the Bios on the Asus board you are using but go into your bios and set the PCI-E vid card bus to 100mhz manually.

Thanks, I have also set this to 100mhz manually, also I believe this is the lowest setting it allows so anything higher should only mean better performance I assume.
 
I'll have to try this out when I get home, however, when I ran it on my friends computer (E6600 on 650i chipset) it was running in 64bit mode and it got like 135 or something. I'll have to check when I get home.

Any update?

On a side note, it seems to be limited to Vista x64 on my system. I booted into XP-64 to test this and, while the 64-bit binary still ran at a lower framerate than 32-bit, the difference was only about 5-10%. Not only that but (in a cruel twist of fate) I had to reinstall Vista today because an unrelated issue caused it to BSOD on boot up. The problem persists after reinstalling and I'm still getting ~40% lower framerate with the 64-bit binary. Also, I have my Steam folder on a separate, third partition, so XP-64 and Vista are using the exact same Lost Coast installation. Literally, the only difference between these test runs are the operating system while the drivers and config files are the same.

Long story short, I'm all but convinced that the issue lies with how Vista x64 handles the 64-bit binary. Lost Coast hasn't been updated (to my knowledge) since long before Vista was released so it's definitely plausible.

Edit:

Regarding your friend, is he running XP-64 or Vista x64? If you're certain that he's running Vista x64 then it might be an issue with Intel chipsets and Vista x64 (I'm running on a P965 board). The 95fps you were getting on your previous Foxconn board were already far too low, so this might just be a different manifestation of the same problem. From my digging around I've found that everyone having this issue is running Vista x64, and most of them seem to have Intel chipsets (many don't state it so I don't know for sure).

In any case, it seems limited to HL2 so it's really a non-issue. Especially if the 32-bit codepath fixes it.

Edit 2:

I looked around a bit more and it's a universal issue; Lost Coast runs vastly slower in 64-bit mode than 32-bit under Vista. Crysis does the same.
 
Not familiar with the Bios on the Asus board you are using but go into your bios and set the PCI-E vid card bus to 100mhz manually.

Thanks, I have also set this to 100mhz manually, also I believe this is the lowest setting it allows so anything higher should only mean better performance I assume.

100mhz is the default frequency for PCIe, anything over that is overclocking the PCIe bus and can result in instability so I'd recommend having it on 100mhz at least until you have solved the problem.

Looking at your power supply, reading an article where they tested just about every PSU that have come out the last 5 years the recommendation for XION is that it is a PSU to avoid.
Looking at the list for ATI certified PSU's XION is nowhere to find.
I'm not saying the XION is crap but maybe it's not completly up to the task and it's probably a good idea to test with an ATI certified PSU.
http://ati.amd.com/products/certified/powersupplies.html
 
According to the Guru3D PSU 12V page, it shows that your PSU has a combined total of 30A. I know that's fine for the setup, but I thought I'd just let you know it's not 35A. ;)
 
I'm convinced his processor is bottlenecking. He has a good OC, but I'm not too sure how good his processor is. When I get my 4850 I'll run the lost coast test or whatever and post a screenshot of my results. I should get it by Friday afternoon or so.
 
Any update?

On a side note, it seems to be limited to Vista x64 on my system. I booted into XP-64 to test this and, while the 64-bit binary still ran at a lower framerate than 32-bit, the difference was only about 5-10%. Not only that but (in a cruel twist of fate) I had to reinstall Vista today because an unrelated issue caused it to BSOD on boot up. The problem persists after reinstalling and I'm still getting ~40% lower framerate with the 64-bit binary. Also, I have my Steam folder on a separate, third partition, so XP-64 and Vista are using the exact same Lost Coast installation. Literally, the only difference between these test runs are the operating system while the drivers and config files are the same.

Long story short, I'm all but convinced that the issue lies with how Vista x64 handles the 64-bit binary. Lost Coast hasn't been updated (to my knowledge) since long before Vista was released so it's definitely plausible.

Edit:

Regarding your friend, is he running XP-64 or Vista x64? If you're certain that he's running Vista x64 then it might be an issue with Intel chipsets and Vista x64 (I'm running on a P965 board). The 95fps you were getting on your previous Foxconn board were already far too low, so this might just be a different manifestation of the same problem. From my digging around I've found that everyone having this issue is running Vista x64, and most of them seem to have Intel chipsets (many don't state it so I don't know for sure).

In any case, it seems limited to HL2 so it's really a non-issue. Especially if the 32-bit codepath fixes it.

Edit 2:

I looked around a bit more and it's a universal issue; Lost Coast runs vastly slower in 64-bit mode than 32-bit under Vista. Crysis does the same.

Sorry to take so long to get back as I have been busy with school, but this is GREAT news. I really want to thank you a lot for your research in the subject as it makes complete sense for every issue I have experienced.
I am testing now as we speak to see if I get improved FPS running 32bit binary.

Also since you said the problem occurs in Crysis 64bit, could explain a way to run Crysis in 32bit on a 64bit system to improve performance.

Thanks again, great work my friend!
 
According to the Guru3D PSU 12V page, it shows that your PSU has a combined total of 30A. I know that's fine for the setup, but I thought I'd just let you know it's not 35A. ;)

I appreciate your research in the matter, however on the side of my PSU it specifically states 17A for 12v1 and 18A for 12v2... if I'm not mistaken that equals 35A total.

Please explain to me if there is something I'm missing here...
 
It's maximum power draw over each line. They don't sum up (exactly). For example one of my PSUs has 2x 20A and 2x 18A on it's four 12V lines. But in all it's only 550W PSU. On the other hand my Corsair TX750W has only one line @ 60A. And that seems sensible.
 
It's maximum power draw over each line. They don't sum up (exactly). For example one of my PSUs has 2x 20A and 2x 18A on it's four 12V lines. But in all it's only 550W PSU. On the other hand my Corsair TX750W has only one line @ 60A. And that seems sensible.

I see, thanks for the info.

UPDATE: Everything that hordaktheman posted is 100% correct as I have tested so far. I got about 40FPS higher when running under the 64bit binary in HL2. I have yet to test in crysis yet as I am not aware of a way to run it as 32bit on a 64bit system.

I am now strongly considering re-installing with 32bit Vista just because I only have 2Gb's and 64bit isn't 100% necessary right now.
 
What about right-clicking the short cut to the game, go to properties, and check the "run this program in compatibility mode for"

and select windows xp (service pack 2)...maybe that will help. :(
 
What about right-clicking the short cut to the game, go to properties, and check the "run this program in compatibility mode for"

and select windows xp (service pack 2)...maybe that will help. :(

Thanks, that's a good recommendation, I'll be sure to test that out.
 
I see, thanks for the info.

UPDATE: Everything that hordaktheman posted is 100% correct as I have tested so far. I got about 40FPS higher when running under the 64bit binary in HL2. I have yet to test in crysis yet as I am not aware of a way to run it as 32bit on a 64bit system.

I am now strongly considering re-installing with 32bit Vista just because I only have 2Gb's and 64bit isn't 100% necessary right now.
Go to the Crysis folder, there is a Bin64 and Bin32 folder. The rest is pretty self explanatory.
 
I'm actually running vista 64 as well, I'm going to see if I can reproduce your problem when my card comes in.
 
Back
Top