sdk

Ok guys maybe you are able to help me out.

When I first got the board there were some obvious issues. Any mhz above the 800mhz for memory caused freezes etc. However this was solved by manually putting in 2.2 volt as noted on my memory (1066 mhz)

I did a 3dmark on 3.0 Ghz (1500 fsb) and 3.8 Ghz (1900 FSB highest I ever went). After that I used 3.0 ghz and 3.2 for normal use since that causes all values to be green in pc probe.

Latest months I did not game a lot and just got new harddrives. So I tried nvidia control panel and for the first time I could set fsb in windows without my system freezing (caused by the undervolting of the memory). I decided to stick with 2800 Mhz instead of 3000.

However I just got a new 22inch display andI need the higher cpu Ghz once again. So I changed fsb back to 1500/1600.
All looked fine untill I started to play.
Racedriver Grid shows slowdowns @ 3 ghz, like 10 seconds it runs fine then a 2 second slowdown (fps the same) then it runs again and warps @ 3.2 ghz.
Unreal 3 shows 103 FPS @ 2.8 Ghz and 87 fps @ 3.2 Ghz (changed fsb with nvidia)

Looks like something is wrong.

A few things have changed:
I updated bios 1103 to 1205 to get a better "q-fan"
I recently found out about the sli ready EXPERT setting so that I get the nice timings. It really helps to get the ideal timings.
Change in FSB to Memory ratio (1400 fsb with around 1000 memory instead of the lower ratio).
I changed memory from slot 1,3 to 2,4 since I was not sure the dual data rate was enabled. I somewhere read that slot 1,3 is 1 T and slot 2,4 is 2T. So i looked it up and changed memory to slot 2,4.

I already put memory to synced mode to make sure the memory is not getting into trouble (so it's at 750-850 mhz isntead of 1066)


Specs
Asus p5n32-e sli
E6750 1333mhz
2x 1024mb Kingston hyperx KHX8500 2GN (nvidia ready)
750W powersupply
8800GTS 640mb.


Bios:
voltages all auto (used to work fine!) exept memory-->2.200
fsb 1400 ATM goal back to 1600
memory atm linked with synced ratio, normal 3:2 or 5:4 linked.
cpu temp <30 degrees with 2.8 ghz

A lot of stuff is disabled but spreadspectrum control isnt. I think I saw virtualization also on but that didnt change at all.

Also NB core is now at 1.52 under AUTO isnt that high for 1400 fsb???

Again: I got to 3.8 Ghz (1900 FSB) without problems 4 months ago!

ps nvidia seems to reset the FSB when I change it in the bios how do I disable that...

johnny9794

Might be RMA'ing my board or just throwing it out, went into bios, set bios to bios defaults, rebooted, I Gotzz no screen, ablinking greenlight on my monitor, all the fans, hdd, even the green power LED on the board turns on, I turned main power off, unplugged psu, pulled the mobo battery out and set clrtc to 2 and 3 for an hour, tried one stick of my ram in all 4 different slots vice versa with the other stick of ram. put battery back in, set clrtc back to 1 and 2, plugged psu power cord back in start the pc up and the same,no screen,no blinking of hdd led on the case. the whole reason of setting bios to defaults was to update to 1205 to use my razor copperhead mouse... right after setting to defaults, pc booted up to the AI lifestyle boot wallpaper and then graphics went all nuts, it restarted back up with no screen.

I just cannot get it to post.

mica3speedy

if you are using your razor mouse, use another mouse until you update the bios to 1205 or later.

johnny9794

I have a buddy coming by today with 2 sticks of his ddr2, ima slap them in and see if it boots so i can set the correct voltage for my ballistix ect. so i have read that might fix my problem and hopefully it will work.

it will not post period, right after setting bios defaults I my fault forgot to go directly back into bios to set ram voltage ekkk...

itzsteven

I need help with my SupremeFX card. I have a 5.1 speakers system, I plug it in and ran the test on the sound config, everything is working fine. When I try to play the music, only the front speakers are playing, none of the other one will work. I already downloaded and upgraded the newest patch for the sound card already. Any idea what's going on??

mica3speedy

unplug the razor, razor usb devices are known to cause posting problems with the 1203 bios. If you are still unable to post, then reset the cmos

shnoops

I believe its a problem with windows 64 bit. I have teh exact same problem, ive tried every program to get it to use 5.1 Only thing that seems capable of using it is the damn control panel :P. Really its just not a good card and should look to get a cheap turtle beach sound card. Dont go with a cheap creative one, even more problems with 64 bit vista their.

Agnostik888

Picking up my second Spirit II for SB and then once I have those gonna hit the OC. Been trying to gather any notes and knowledge I can from this thread but it has gotten rather large. I am assuming the first post is still the basic overall idea?

If anyone has any tips for my setup for OC, let me know! =) I am aiming for 3.4GHz but once i get there if temps look good might try to push 3.6 if possible.

Thanks.

burtethead

Hey everyone, i probably should post first in the introductions or whatever, but since this is really the only thread I have read extensively, i wanted my first post here. First off, robilar is the man, etc, ive learned more on this thread than in any class. thanks to everyone. So basically, I was going just fine until I decided to upgrade to an e8400 (from an e6600) before really starting to OC. I put in the chip and started up, and it notified me that my cpu had been changed so i went into bios. After making no changes whatsoever, I save and exit... only to be greeted by the ol' 'bios checksum error', and that it couldnt detect a keyboard. So i clear the CMOS, and it starts up again, gets into bios again, and upon save and exit, the same thing happens. So i am currently running off defaults, which is certainly stable, but changing any bios settings is out of the question. Is my CMOS battery weak or something? I tested 3.1v which should be good enough. Is it a product of BIOS 1404? Before this i was running 602 since i built the thing last december. On a side note, if i run nTune (or even just nvidia control panel) i instantly get a BSOD naming nvoclk64.sys as the culprit. any clues?

mica3speedy

so you are using bios 1404? I would double check all of your voltages, ram, ect. As for the nvoclk64.sys problem, I suggest uninstalling ntune for the time being. Find a newer version if possible, and install that.