Odd, but 61.77 and PoV has some weird OC problems

[CrimsonLoneWolf]

I've just done some more testing with overclocking on my PoV 6800 Ultra.

Using the LeadTek bios, that clocks it at 400/1100 both in 2d and 3d mode.
Using the 61.76 and also tested with 61.77 drivers from Nvidia.
Tests used: 3DMark2003

Results:
400/1100 2d, 425/1100 3d -> 3DMark2003 stops responding 20-30 seconds into Game test 2.

400/1100 2d, 415/1100 3d -> 3DMark2003 stops responding 20-30 seconds into Game test 2.

400/1100 2d, 410/1100 3d -> 3DMark2003 stops responding 20-30 seconds into Game test 2.

400/1100 2d, 401/1100 3d -> 3DMark2003 stops responding 20-30 seconds into Game test 2.

Now, it runs PERFECTLY stable at 400/1100 both 3d and 2d, but even 1 mhz oc on the gpu makes 3DMark2003 stop responding?

I'm gonna test with other benchmarks tomorrow, and will post the resulsts here. But for now i'm just really confused about what the heck is going on. I thought my system wasnt getting enough cooling since i couldnt run with the PoV stock settings of 425/1100, but there's NO way that 1 mhz should have such a big impact. Maybe i should also test with having both 2d and 3d settings the same, and maybe, just maybe, there's a problem with the ForceWare drivers and the PoV card.. I just wish i could figure out what the heck is wrong :/


-----
Intel P4 2.8 ghz, 800 FSB
Asus P4C800 Deluxe (using latest bios from asus)
Sound Blaster Audigy 2 (using latest drivers from Creative)
2 * Western Digital Raptors (36,7g)
2*512 400 mhz ddr in dual setup
Point of View GF 6800 Ultra (Using forceware 61.77 atm, and the LeadTek Bios)
DirectX 9.0c

[CrimsonLoneWolf]

Just did some really quick testing with synchronising the 3d and 3d clock speeds. Seems i dont get a freeze in 3DMark 2003 now with 410/1100 in BOTH 2d and 3d. Will test more tomorrow, and see if this will fix it.

[Lfctony]

I've been having problems as well, the 61.77s and DX9c completely screwed up my PC. The system would restart itself half a minute after exiting a 3d app. When I unistalled the drivers and went back to the 61.21s, windows was horribly messed up and the system crashed. Hopefully, no damage to the card was done.

I'm currently on a clean windows installation. Halo works fine @ 1600x1200 w/16AF. Will test some more. I'm currently staying away from the 61.77s.

[CrimsonLoneWolf]

Well, i can confirm that i CAN clock my card and run it stable at 425/1100 IF i use both the vga and the 3d clocks at the same speed.

Even a 1 mhz difference between the two makes my 3DMark2003 pause. Same clock speeds, and it runs perfect.

ForceWare related? Bios/card related? 3DMark2003 related? Unsure, tbh.. but i'm not reverting back to 61.21 and DirectX9.0b again, since this is running pretty much stable for me atm.

[Lfctony]

What ticked me off was that the system would restart AFTER exiting a game, while I was browsing windows. I am really disappointed with my card so far.

[XZiBiT]

I'm running a POV 6800 ultra @ 425/1100 3d and 400/1100 2d without any lockups, can also clock it to 450/1800 stable too.

Directx 9c
61.77

FX53
Asus A8V mobo
1gb Ram


Well tight you guys have problems, if there are any tests i can do for you let me know.

[jcossin]

I installed the 61.77 drivers. I had my BFG 6800 Ultra clocked to 450/1200 which I've been using on the 61.76 drivers with no problem.

With the 61.77 drivers, 3dmark03 blue screened at the third scene with the girl and the Ogres. Then I tried going into the overclock setting and let it determine optimal frequencies and it took FOREVER for it to test and finally it blue screened again.

I finally set the clock speeds back to default, and got through 3dmark03 with no issue. However my 3dmark went down to 12600 with the 425/1100 clocks.

I'll try setting 2D and 3D to the same settings tonight to see if that makes a difference. In my tests last night, I had 3D overclocked and 2D set to default.