Quote:
Originally Posted by Clunk
Welcome to the forums Stanley
Sounds like you may have a corrupt CMOS - if that is the case, just flip the battery out for an hour or so, PSU unplugged...more than an hour is sometimes needed.
Another thing that can cause this kind of weirdness is using settings from CMOS reloaded that were saved using a previous BIOS - this was especially bad on the T3RS.
Another thing to check is that you don't have any bad memory. The behaviour you describe can also happen if you have a dead or dying stick - memtest86+ test 5 for an hour on each stick, make sure you cool the sticks while testing.
|
Thanks for the reply man~~
Yes I suspected that was a corrupt
CMOS as well, No I haven't tried removing the battery even once.
For DRAM Cooling, I am currently using Thermaltake V1R and heating shouldn't be a problem as I only clocked the DRAM at CL6-6-5-18 1666Mhz @1.936v
BIOS and proved memtest 86+ ver 2.01 stable at all times.
Settings as follows:
Clock Driving Strength: 6
Data Driving Strength: 8
Ch.1 DLL Skew model: 1
Ch.2 DLL Skew model: 1
I wonder if the
FSB Strap to
NB setting will really hinder the
FSB overclocking ability as I saw other overclockers using Rampage Extreme can use 2:3 divider which is 266/800 Strap and go for 600FSB benching I believe...
For the setting above I've tried setting the DLL Skew model to 3 but no
POST if do so. Actually I'm here not just to ask for help but to discuss together and figure out a way to break the blockade. Maybe a suggestion to DFI
BIOS Engineer will do a trick?
EDIT: Just a google search and found that X48 400/1333 Strap was actually 400/1200 which is 2:3 Divider?! It started to confuse me as I found memtest 86+ was showing a different mem. frequency from Target mem. frequency shown in
BIOS?!