Is Intel trying to Kill Overclocking with the i815 Chip?

jzodda

Senior member
Apr 12, 2000
824
0
0
Well if this is true then I will have to take back my CUSL2 while I still can.

First off here is a link to the thread:

http://www.cusl2.com/UltraBoard/UltraBoard.cgi?action=Read&BID=5&TID=295&SID=7

It appears that the "Cold Boot Bug" in the ASUS CUSL2 has been uncovered. According to the poster the CUSL2 will cold boot at cpu default Vcore regardless what you specified in the BIOS, and would however adjust the Vcore while booting into the OS. The poster also said "I have tried 6 cusl2 and they all exhibit the same behavior. For all of you who can't attain 700@933 or 566@850, you will need to boot your system at default speed, higher Vcore then reboot at 933 or 850. I suspect this is a *feature* built-in into the 815E chipset rather than an Asus BIOS bug."

Lastly he said "I suspect (just a guess actually) this is more of a chipset *error* is because it looks like a overclocking restriction planted by Intel rather than Asus."

Now if that is true its really bad news. Can anyone shed some light on this. Is it a bios issue or not?



 

Midnight Rambler

Diamond Member
Oct 9, 1999
4,200
0
0
Utter hogwash ...

Try another i815E board if you doubt the Asus board - the MSI 6337 is nice (got a good review here at A'Tech) or the Aopen AX3S Pro (didn't get a great review here, but I suspect it was an early production board as Aopen makes great motherboards in general).
 

Raincity

Diamond Member
Feb 17, 2000
4,477
12
81
Ya its a bunch of crap. My Msi 6337 doesnt have any cold boot problem issue and I have not heard of this issue from any current Msi 6337 owners personally, or from the Alt.comp.mainboards.msi usnet group that I check on every day for 6337 issues. I have been running a p3700 cbo @1015 @1.70 vcore for a month with no stability issues of any kind. This 6337 has been the best mainboard I have ever purchased.

Rain
 

jzodda

Senior member
Apr 12, 2000
824
0
0
Thanks guys, glad to hear that. It gives me hope that ASUS will fix the problem eventually :)