Quote Originally Posted by tekjunkie View Post
I think I just bricked my S2E. I flashed to 0702 using awdflash and hit F1 after the flashing was done and then I did a stupid thing. I hit the "CLR CMOS" button while it was going through the POST process. I always CLR CMOS after a BIOS flash. Now the board is stuck @ "CODE INIT". I took the battery out and will keep the battery out and hope when I pop the battery in tomorrow, it magically comes back to life, like the old strikers did with the dreaded "CPU INIT" bug. If not, I guess I would have to go through Asus for RMA. Anybody here familiar with the RMA process with Asus. Thanks in advance.
It just happened to me. PC froze so I reset it twice and it was stuck at CODE INIT so I pressed the turn on button until I shutted down, then turn it on again and it would let me boot, however I never touched the ClearCMOS button.
Right now my vcore is 1.287xx and its been working good. 1.27500 failed within 10 mins

Quote Originally Posted by BenchZowner View Post
@Slim142:
Looks like system files scan ( sfc ) @ Windows XP isn't really good to tell if we have corruption or not, because it looks like it asks for the windows disc even when there's no corruption ( just tested it on my P5K3 Deluxe ). [ probably checks the files not only from the "backup repository" on the HDD, but from your windows disc as well, that's why it's asking for it every now and then ].

So, unless you're having silly crashes ( like crashing while idling in Crysis main menu ) you shall be fine.

p.s. The white memory slots are clocking higher than the blue ones.
Glad to hear that because I thought I had already messed XP again :P
Will try games probably tomorrow. I want to get to at least 400Mhz FSB estable and then start checking games and stuff.
BTw, around what FSB speed do you guys needed to start upping your NB voltage to more than 1.40v?