• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Odd problem, Windows only boots with higher OC?

M

MikeyB

Limp Gawd
Joined
Apr 20, 2005
Messages
413
Here's the situation

DFI Lanparty NF4 UltraD
3700 San Diego @ 1.50v

I found my highest overclock by upping the fsb a few mhz at a time with clockgen and running SuperPI, then giving a little more volts when it failed. 2805 (255x11) @ 1.50v was the higest I could go so I decided to set these values in bios and then begin the more rigorous testing. I set the values and windows booted up as you would expect. At this speed everything seemed great but the system failed prime95 after about 10 minutes. So I lowered the FSB to 248 and it runs prime95 for over 12 hours. The goofy thing is, I can't boot at 248x11, I have to boot at 255x11 and then lower the FSB using clockgen. At 248mhz windows cuts out right before I hit the login screen. Is there any way to fix this?
 
Honestly bro.....I could have sworn I was running into the same issue with my sig system awhile back...seemed that the system wasn't stable at all (wouldn't get into windows too often) at stock clocks. Turns out that essentially all my random shutdowns/BSOD's/boot issues were tied to an IRQ issue, as I had the only two PCI slots on my DFI Ultra-D used up with my sound and video card...second I yanked out the SB Audigy2 everything was/has been fine.

I'd do some more research before assuming your problem is even directly related to your board and/or CPU.
 
On some motherboards the PCI 33MHz frequency lock only kicks in above a certain FSB frequency
 
This is getting annoying. Now windows won't boot with any oc on the FSB. I have to start at stock FSB of 200, get into windows, and use clockgen to set my oc. This happened after I tried to update my nforce4 drivers. I hate windows.
 
System in sig.

OC: 239 x 11 @ 1.55v

Prime stable in linux for over 8 hours. Runs windows in safe mode just fine. Safe mode w/ vga enable = crash as well as running windows normally. I'm thinking this might be an nforce or video driver problem. Any ideas?
 
Was on a DFI NF3 UT ,what happened was ,I was flashing different bios and never reset
the bios back to default values before the next flash,it was pretty maxed out in bios when
I flashed to next,I finally figured it out ,and just defaulted everything in bios and went right
to the next flash,and everything was baselined again to default.But that was the same deal
as you ,hope it helped.
 
The problem is that windows, for some unknown reason, fails to boot with an OC that is proven to be stable on another OS.

I updated to the 704-1 BIOS, reinstalled the latest nforce4 and catalyst drivers, and I booted into windows without a blue screen. Even though 2600mhz isn't the max for this proc. I may just leave it there for a while and see what happens.
 
You must log in or register to reply here.
Back
Top