Quote:
Originally Posted by sunderstan
(Got some stupid error message like some important files are missing
|
I quite often get a message like that, usually when using 400/1600 strap and >400
FSB. That error appears less often with the more recent BIOSes though.
Quote:
Originally Posted by sunderstan
I have been using a rather high vNB. I've tried 1.555v BIOS but when I try to stress it by extracting files / compression, the system just went off and reboot, while 1.6v won't have such problem.
|
Yeah, for me 1.5-1.6 seems to be what's needed to remain stable. I assume the
NB is a 65nm part, so it shouldn't be
too stressed at that voltage, and the temps always seem fine at around 50c.
Quote:
Originally Posted by sunderstan
The GTL Reference Voltage I'm currently using are:
CPU 1/2: 80
CPU 0/3: 78
NB: 50
VTT 1.21 BIOS
|
I played a lot with
GTL Ref voltages previously, but I've found I don't
really have to to get 3.6/400/1600 stable, though getting them right might mean lower
NB/
VTT voltages, so I'm going to give it a try at some point.
Quote:
Originally Posted by sunderstan
According to your system spec you're using QX9650 which is quad core. AFAIK to get to higher FSB you'll need to tweak CPU GTL carefully so that you can hit 500 FSB easier~
|
I doubt I'll ever get to 500
FSB to be honest. I've settled for 400 for now, I'd be happy with 450 if it ever becomes a possibility.
Quote:
Originally Posted by sunderstan
I know somebody is working hard on other support forums to get DFI to hear from us so that the BIOS can improve in a better way~
|
Which forum is that? I'd like to help any way I could, certainly seeing as quad cores appear to be having a relatively difficult time with this motheboard.
Quote:
Originally Posted by sunderstan
EDIT2: My board have a minor problem. At high FSB it sometimes refuse to POST but when I hit reset it POST fine again. Anyone have this problem so that I can identify it's BIOS related issue please?
|
Yes, I get this a lot. I don't know of any fix for it, it usually freezes just before the memory check in the
POST, and like you say, a quick reset usually resolves it.