I could really use someone's help! 1st - here is my working config:
ASUS P4CD800-E Deluxe
Intel P4 2.6 533BUS NO H/T
2 Sticks CORSAIR TWINX 256MB 3200 MEM DDR
2 80-GIG WD HARD DRIVES W/ 8MB CACHE
ENERMAX EG465P-VP POWER SUPPLY RATED @ 431 WATTS
GEOFORCE FX 5900 ULTRA 256MB VIDEO CARD
SOUNDBLASTER AUDIGY 2 SOUNDCARD
KENWOOD 52X CD-ROM
WINDOWS XP HOME EDITION SP1
Now the problem: The system works fine under this config. I installed a P4 2.8 800-BUS W/ HYPER-THREADING processor. Upon reboot I config'd the BIOS to accept new processor and enabled Hyper-threading. When Windows starts, it sees the new processor and starts to load some files (drivers?) and then asks to reboot. Upon reboot, the system locks up after it posts and tells me this file is missing or corrupted: windows\system32\config\system. I did a clean install of XP with the new processor installed and a quick blue screen comes up stating conflict or non-page fault error. If I reboot again and I am able to re-install Windows, it cannot find random files on the CD-Rom needed to finish the installation. I can install Windows with the old processor in and have no problems. The problems occur when the new processor is put in. Please help!!!!!
It could be a power or RAM problem. My guess is RAM. Try using the "333MHz" RAM setting in BIOS just to see if that clears things up. If so, you can try cranking it back up to "400MHz" and increase RAM voltage or increasing latency to restabilize it.
<font color=blue>Only a place as big as the internet could be home to a hero as big as Crashman!</font color=blue>
<font color=red>Only a place as big as the internet could be home to an ego as large as Crashman's!</font color=red>
<font color=blue>Only a place as big as the internet could be home to a hero as big as Crashman!</font color=blue>
<font color=red>Only a place as big as the internet could be home to an ego as large as Crashman's!</font color=red>
Actually it's not that odd at all from the research that I did when I was buying my system in July.
It's an 875 mobo meaning that it has PAT. If I remember correctly PAT is only enabled at 800MHz FSB. And since low-latency RAM and PAT don't play well togetherm it's only logical that problems suddenly pop up during the switch from 533 to 800 on an 875 mobo. Disable PAT or fudge with the latency timings and the problems will usually all go away. Fudging with the RAM's voltage can also help, but usually not for Asus boards because they overvolt the RAM already despite the settings in BIOS since they already were well aware of PAT memory stability problems.
<pre><A HREF="http://ars.userfriendly.org/cartoons/?id=20030905" target="_new"><font color=black>People don't understand how hard being a dark god can be. - Hastur</font color=black></A></pre><p>
Normally, reducing latency decreases stability, and increasing latency increases stability.
<font color=blue>Only a place as big as the internet could be home to a hero as big as Crashman!</font color=blue>
<font color=red>Only a place as big as the internet could be home to an ego as large as Crashman's!</font color=red>
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.