Originally posted by: yrrab436
I'm using on board sound, and I know that uses the CPU right? Could that cause the lower scores?
It's only been one day, but so far so good. No loop crashes.
I just wish nVidia and/or the manufacturers would release an OFFICIAL updated BIOS to fix the issue.
Originally posted by: RampantAndroid
However, the onboard audio will only hurt things...onboard audio has also been know to cause lockups...
EDIT: Oops, looks like the 3500 is 2.2...the 3800 is 2.4....sorry people
Originally posted by: RampantAndroid
Well,, lets see, you say you got a BFG 6800 Ultra OC.....wait, doesnt that mean it'll be overclocked by BFG, above the 400/1100 425/1100?????????? What did you think you'd get?
Sure, drop the speeds to 425 core (2d and 3d) and 1100 mem...........but next time, try to figure out what you are buying?
)
Originally posted by: yrrab436
It's so nice to see I'm not alone. I play EverQuest lots and the only other person in my guild with a 6800 has this problem. He has an ASUS, and I have a PNY. 6800 Ultra 256MB
The card is at 58C, the CPU at 38 and motherboard at 33 currently. the CPU does go up when I do more intensive things, but I've never seen the graphics card say it's very high. However, I doubt it's a heat issue since it only occurs while zoning or tabbing out. By going into windowed mode in Everquest so I could see the driver's temperature gauge, and spinning around with the mouse as fast as I could, I was able to raise the temperature quickly to 65C, and then is very very slowly rose up to 67, I could get it to 68 but it would quickly drop back down again. I'm not sure if that's normal temperature, but I still do not think the crashes are temperature related, especially since tabbing causes it just as often as zoning does.
It sounds like the same issue. When I zone (change areas in the game) the loading screen shows and then a breif moment after my character appears in zone the screen will lock up... after a few seconds it will either:
A) Totally go blank. (very very rare)
B) Continue normally. (sort of rare)
C) Continue with severe graphics corruption. (Naked characters, polygons stretched all over, general corruption "grate" effect)
D) Get caught in a loop. I'll hear the EQ music then it will stop for a few seconds, and then continue, and then stop, until finally I get a BSOD with graphics card loop or a drop into 16 color mode and a popup saying the graphics driver stopped working right.
I should have contacted PNY, but looking at this thread it looks like that wouldn't do much good. I will do that though since it's obvious that should have been the first thing to do. I was just terrified I was responsible for static damage or some such.
I don't know the slightest thing about looking for an updated bios, or modifying it myself. I'll have to read this entire thread eventually but I don't have time now.
It also happens to me in the Doom 3 demo, and when I scroll really fast on a web page with many graphics, such as a screenshot thread and such. This is extremely frustrating indeed. Everything runs so quickly and then BAM it stops and it's time to pray "pleeeeease don't get stuck in a loop."
hehe
Edit:
Okay I found RivaTuner. There's a bunch of mumbo jumbo I don't understand but I clicked on Customize, then System Settings, and told the overclock tab to detect the card's settings.
It shows:
standard 2D: 400
low power 2D: 425
performance 3d: 425
Do I understand correctly, that many people fix this issue by changing standard 2d to 425?
Originally posted by: ph03n1x
Well I just realized that if I use Single Channel DDR configuation my problem goes away. I bought this RAM because I actually thought it would work as Dual Channel but maybe I misunderstood. I thought it just had to be a matched pair of DDR400. Is there something more special about it? It was working, just not reliably I guess. Or should it be working fine?
This is my RAM
Originally posted by: RampantAndroid
OK people, I don't wanna sound like a dickhead, but I think that if you would go through this forum, you'd find all of this has been said already. This is becoming redundant...you may have to get into the advanced Bios settings (alt+F1 sometimes while in Bios)...
How many times have I said that, 2 or 3 at least. I'm sure if you skim this thread, you'll find multiple possible solutions.