It used to overclock to an QDR of 1499, now I can't get above stock without getting a BSOD in windows:
"hardware malfunction
call hardware vendor for support
..."
Is there anything I can do, is it RMA able?
It used to overclock to an QDR of 1499, now I can't get above stock without getting a BSOD in windows:
"hardware malfunction
call hardware vendor for support
..."
Is there anything I can do, is it RMA able?
Last edited by redddraggon; 29-05-2007 at 04:36 PM.
1499.... are you sure??? I don't think so?
Try to make each and every day the best it can be.
QDR of 1499, 1499 is the Rated FSB according to the BIOS.
I know 375 is the other FSB. Don't be so bloody picky.
And it doesn't answer my Question.
http://valid.x86-secret.com/show_oc?id=199821
With this board you enter the QDR.
...
Last edited by redddraggon; 29-05-2007 at 10:36 PM.
I'm also having greif with my new FP-IN9. No matter what I do I can hardly get it to O/C at ALL. I can get it to 2.17GHz (966FSB) with a bit of extra voltaqge on the CPU & northbridge, but even then it locks up occaisionally, at 2.4GHz (1066FSB) it will usually lock up before loading windows. Anything over that and it won't even POST, requiring a CMOS reset. I'm running the memory in sync mode when overclocking (meaning it's way underclocked) so I know it's not a RAM thing. I've been using the beta 13 bios, and tried bios 11 as well (heard 12 was crap for o/c) but it made no difference. Cooling shouldn't be an issue as I'm running a Coolermaster Hyper TX cooler and theres an internal 120mm fan feeding air straight onto the northbridge, my cpu temp hasn't even hit 40 degrees yet in ABitEQ or bios. I've tried a Bsel mod (using about 6 coats of silver conductive varnish as I can't get the defogger repair kits) but that seemed to have no effect (board still posted at 800MHz).
Now I know the newer E4300 won't necessarily provide massive overclocks (though I've seen reports of chips from the sam batch attaining over 3GHz on stock voltagte so it's hardly out of the question) but I was expecting that I'd at least be able to get to around 2.7GHz without too many problems. The only weak point I can think of in my system is possibly my PSU, but as it's a new unit and I haven't exactly pushed it hard I wouldn't expect that to be the cause of my problems yet. Besides it can provide 32A on the 12V rails whereas as far as I can tell my system shouldn't require more than 26A so it should be okay.
I'm probably missing something really obvious but have no idea what it is.. any suggestions would be very much appreciated.
Update: I think I can rule out the PSU as a factor in my current problems. I pulled my video card and remporarily replaced it with an ancient Trident PCI video card which ought to use MUCH less juice than the 8800GTS. I upped to FSB to 1066 and the machine still locked up halfway through booting windows. So I guess it's now down to the CPU or mobo, or me... hopefully the latter.
Last edited by Meatbix; 04-06-2007 at 11:32 AM.
Bump....
Anybody got any suggestions on pinpointing the issues I'm having above? I'm, running the beta 13 bios by the way.
Hi Meatbix,
I've been experiencing the very same problem. At least I'm not the only one.
Just lately I got BIOS 13 beta. Along with this I was also advised to try upping the PCIE bus to 101MHz.
Now, I've managed to O/C to 2.4GHz and it's been stable for 2 days. And I played Company of Heroes for an hour without a crash!!
2.7GHz (FSB 1200) won't post. I'm hoping that the real version of BIOS13 will fix that.
Part of me wishes that I'd stuck with DFI mobo, but i'm determined to get this thing working.
Reddraggon, you posted a piccy of your bios.
It shows your memory synced and running at 533MHz. With you having 800MHz does this affect you performance?
Also, you are running at 2998MHz. So what is this screenie of? Can you post a screenie of your current kickass settings, inc voltage. I'd love to see how you got your high O/C.
There are currently 1 users browsing this thread. (0 members and 1 guests)