B
Bryan Hunter
P4C800-E Deluxe, Bios 1014, P4(c) 3.0G, Corsair TwinXMS 2x512 DDR400 /
3200C2PT, 465W p/s, XP SP1 plus.
Short version: If I turn OFF HT in the BIOS, from a cold start the
machine typically fails to boot with "windows could not start because
the following file is missing or corrupt:
\windows\system32\config\system", but boot succeeds on a 2nd (or 3rd)
try, no need to use safe mode. This error occurs without software or
hardware changes.
If I turn ON HT in the BIOS, the machine BSODs on startup
(repeatedly), and randomly BSODs when running. Details below.
My best guess is that either the CPU or the MB should be replaced ...
but which one first?
Details:
The problem is not changed by replacing hard disks (both IDE and SATA,
including single IDE with all SATA off), RAM, video card (Nvidia MX400
versus FX5600), CDRom. All BIOS performance enhancements are off,
except that DDR voltage is bumped to 2.75 (a suggestion frequently
posted by Corsair's "Ram Guy" at their site). I have not switched the
p/s, but don't think that's the problem. Memtest runs fine, SI Sandra
mostly okay (the burn wiz has made it through a complete cycle, and
then hung on later runs). Part replacement as been easy so far, but
CPU / MB are going to be more complicated. All temps are nominal.
All drivers are latest.
With hyper-threading enabled, it typically takes 6 or more tries
before this machine boots successfully. Generally it BSODs and
immediately POSTs as soon as the first XP graphic starts to display.
Once started, it BSODs at random intervals, typically within about
30-60 minutes. Once running, it generally is able to do a warm reboot
successfully. The stops that don't immediately POST are typically
driver_irql_not_less_or_equal or page_fault_in_non_paged_area, stop
codes are variously 0x8e, 0xd1, 0x24, generally involving reads,
variously in win32k.sys, ntfs.sys or one of the video drivers. The
general situation sounds an awful lot like one described by Darth
Elvis here recently (10/12).
Noting that Mr. Elvis' thread ends with his report that dropping in a
non-HT P4 fixed the problem, and that turning off HT in the BIOS on my
machine ends the BSODs, I figure that the problem is neither RAM nor
drivers. Which pretty much leaves me replacing either the MB or CPU
.... but which? Thoughts? Suggestions?
Thanks for your help!
Bryan
3200C2PT, 465W p/s, XP SP1 plus.
Short version: If I turn OFF HT in the BIOS, from a cold start the
machine typically fails to boot with "windows could not start because
the following file is missing or corrupt:
\windows\system32\config\system", but boot succeeds on a 2nd (or 3rd)
try, no need to use safe mode. This error occurs without software or
hardware changes.
If I turn ON HT in the BIOS, the machine BSODs on startup
(repeatedly), and randomly BSODs when running. Details below.
My best guess is that either the CPU or the MB should be replaced ...
but which one first?
Details:
The problem is not changed by replacing hard disks (both IDE and SATA,
including single IDE with all SATA off), RAM, video card (Nvidia MX400
versus FX5600), CDRom. All BIOS performance enhancements are off,
except that DDR voltage is bumped to 2.75 (a suggestion frequently
posted by Corsair's "Ram Guy" at their site). I have not switched the
p/s, but don't think that's the problem. Memtest runs fine, SI Sandra
mostly okay (the burn wiz has made it through a complete cycle, and
then hung on later runs). Part replacement as been easy so far, but
CPU / MB are going to be more complicated. All temps are nominal.
All drivers are latest.
With hyper-threading enabled, it typically takes 6 or more tries
before this machine boots successfully. Generally it BSODs and
immediately POSTs as soon as the first XP graphic starts to display.
Once started, it BSODs at random intervals, typically within about
30-60 minutes. Once running, it generally is able to do a warm reboot
successfully. The stops that don't immediately POST are typically
driver_irql_not_less_or_equal or page_fault_in_non_paged_area, stop
codes are variously 0x8e, 0xd1, 0x24, generally involving reads,
variously in win32k.sys, ntfs.sys or one of the video drivers. The
general situation sounds an awful lot like one described by Darth
Elvis here recently (10/12).
Noting that Mr. Elvis' thread ends with his report that dropping in a
non-HT P4 fixed the problem, and that turning off HT in the BIOS on my
machine ends the BSODs, I figure that the problem is neither RAM nor
drivers. Which pretty much leaves me replacing either the MB or CPU
.... but which? Thoughts? Suggestions?
Thanks for your help!
Bryan