• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

CUSL2 owners look at this!

Xads

Member
I found an interesting quirk about the CUSL2, no matter WHAT BIOS rev you are running.
No matter WHAT you set the CPU voltage to, it doesn't take effect until a complete POST cycle completes, that is, until your OS starts booting.
I've got a dual-boot Windows 2000/ME system, and I had a major problem overclocking my 700E. I decided to check the hardware monitor in BIOS before a full POST, and lo and behold, it was still at 1.65v.

I set it to 1.85v, 700MHz, and went to the Windows 2000 boot menu. I then rebooted, went into hardware monitor, and it was FINALLY at 1.85v. Then I cranked it up to 143MHz, and VOILA, !GHz, ROCK STABLE, completes Sysmark 2000, been running SETI@HOME for 6 hours, no problem.

------------------------------------------------------------------------------------------------------

I saw the following on www.cusl2.com can anyone verify if this is a known issue.
Thanks
 
i put on my 700e, applied (cheap) thermal paste and a (expensive insurance) copper spacer from 3dfxcool and immediately turned on the system and went to the bios.

i changed voltage to 1.8 and FSB to 144, BOOM the system worked perfectly the first time. i knew i needed 1.8 from my previous (p3v4x) board.

 
Nope....I have no problems with running at a higher voltage....it's always on 1.80 volts for me.
 
I do have to agree with Xads. I too was overclocking my CPU and was setting my voltage to 1.8V. I set it, rebooted and immediately went back into bios to see if it stuck. There it was still running at 1.7V but set to 1.8V. I was confused.

So I left it set at 1.8V but set my CPU to 700MHz (stock) and rebooted, went into Windows, rebooted and went back to BIOS. Now it is set to 1.8V and I can overclock just fine. I confirmed this all with MBM to see if it was reading the same thing and it was.

So chalk it up to a strange CUSL2 problem, that like others, only some will see apparantly.
 
This is no quirk affects lots of users. Just check cusl2.com and you will see what I mean. Its an old issue though, the CUSL2 loads the voltage after posting on a COLD boot and so if your CPU cant do 1.65 on a cold boot then you will be effected. On a reboot it does not have this problem and will retain any saved voltage.

I am curious though, for the people that do not have that problem- will you cold boot and then go into the bios and tell us if its 1.65 or what you put it at.

Thanks

Joe
 
Back
Top