Need help with BFG 6800 GT and coolbits

[wiggedout]

Okay here it goes:

I have a MSI Neo2 Platinum MB with a 939 AMD 3800+, Running a BFG 6800GT AGP with the 66.81 guru3d drivers/winxp sp2.

I enabled coolbits via nvHardpage 2.1 and did a detect optimal values run in the nvidia driver control panel. It detected 395/1.07 for my card. I figured that was pretty conservative so I did a 3dmark03 run. During the run it froze and my machine rebooted. NO big deal right?. Well now when ever I try to tell the card to revert to defaults or no overclocking it still thinks it should be running 395/1.07 instead of 370/1.00. I remove coolbits it still runs at 395/1.07, I tell it no overclocking it runs at 395/1.07.

So then I got riva tuner. same thing. except riva tuner also states that the low voltage 3d is also 395/1.07.

Now I've taken the card out put it in another machine/with 66.81 and it works as expected default 370/1.00.

I've even pulled a copy of the bios off the card with nvflash to ensure it didn't get fried and it still says 370/1000, and this was in the machine that forces it to run at 395/1.07 when in Windows.

I can force riva tuner to make the card run at 370/1000 in 2D/3D/Low voltage 3d and it works fine.

But if I take it out and turn off all overclocking the card reverts back to 395/1.07 while in this system and booted into windows xp.

The only think I can think of is that nvcpldaemon (which initializes the clockspeed of the card at windows startup so I've read) is reading 395/1.07 as the defaults for that card now from somwhere on my system and forcing the card to run at that speed. I've tried removing nvcpldaemon out of HKLM/Software/Microsoft/Windows/Run but the drivers keep adding it back.

I've also tried different driver revisions, removing and re-adding. removing ALL Nvidia software (including the MB drivers), running Nvidia R.I.P. and then re-installing. and ripping all nvida keys referenced in the registry out.

Can anyone tell me where the startup values for gpu/memory speeds are stored? Where it reads the defaults from and where it stores the clock speeds when you tell it to apply at startup? I suspect it's somwhere in the user hive but I'm not sure.

This is a serious pain because the card isn't stable at thoes speeds and works fine in another system. I don't want to have to use a overclocking tool to force my card to clock normal. . lol kinda counter productive and I really don't want to rebuild my box.

Any help would be greatly appreciated. I've been banging my head on this for 3 days now and google isn't helping me find where those values are stored.

Any ideas?

Thanks,
WiggedOut

[Rukee]

try and press and hold the 'ctrl' key as it`s booting.

[wiggedout]

Tried that too. . . that still makes the card revert back to 395/1.07 =(

I see what you are saying though holding down CTRL should bypass the nvcpldaemon at the startup. But it still reverts back to 395/1.07 just like when I select no overclocking. . . where in the world is the driver getting these clock speeds from?

[wiggedout]

bumpage in hopes that some uber driver/coolbits software guru will help me or can tell me where:

1) the driver gets it's default clock speeds from
2) where coolbits and/or nvcpldaemon stores those values at when apply at startup is selected.

This is driving meh crazy. . .

Thanks !
-wigged

[wiggedout]

Well it's fixed now. . .

For those interested in what I did if you ever have the same problem. .

I snagged an old hard drive I had. .just a 13 gig to re-intsall the OS on, left my old one in the machine but not plugged into any IDE channel.

I reinstalled the OS and SP2. rebooted, then installed 5.10 nforce for my MB then 66.81 forceware for 6800GT and rebooted again. Enabled coolbits via reghack to show clock speeds, and it was at 370/1.00 by default as it should be. Then I removed coolbits and shutdown cleanly.

Unplugged that hard drive, plugged my original one back in, and viola. . its defaulting to it's normal clock speeds again. Just to be sure I un-installed and re-installed 66.81 and it's still 370/1.00 as it should be.

Freaky Freaky Freaky. . . I guess some registers somewhere got messed up and a fresh install corrected them. :confused: :confused:

Anywho. . . I'm posting JIC someone needs a similar fix.

Wiggedout (no more) :toast: :banana: :banana: :banana4: :D