Cannot install OS

[DDY]

This is one of the most confusing problems I've come across and I really need help.

This is what happened:
I installed the Stalker: SoC 1.0005 patch which freezes the system 5 mins after starting a new game, I then re-installed the game which ran perfectly without the patch but after applying the 1.005 patch again the same thing happened, but this time I had to restart the PC using the reset button... This is where the problem began...

Once the system finished POST'ing and when Windows XP would usually boot I get the message "Windows could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM"

The natural thing to do is return everything to stock, this did not work. Then attempt a windows repair, I did the F6 thing (since I'm running RAID0), install the ICH9R drivers, get to the menu and hit R for repair then a BSOD will take over "BAD_POOL_CALLER". Then attempted a BIOS reset, nothing.

Faulty RAM? Nope, memtest loop 10 times, tried another set of RAM too.

I then tried to boot the Ubuntu 7.10 live CD so I can recover some files, I got on to the main menu and selected to boot the live CD, after doing this the monitor will enter power saving mode and stay that way until I hit the reset button.

So I tried DSL-N, another Linux live CD. This gets stuck while booting and gives me the "DSL cant find knoppix file system" error, I know this CD is a good one (i.e. not a coaster), it works on other systems perfectly.

Uggh, forget recovering the files. Time for a fresh windows install. So I booted the windows XP CD, fast forward to the EULA bit and hit F8, guess what? BSOD again but this time "PAGE_FILE_FAULT_IN_NON_PAGED_AREA".

Maybe the RAID is causing problems? I tried a single SATA disk on IDE mode and still get the same problem. Graphics card? Tested it on another machine, worked fine. CPU? Not sure, never ever had a faulty CPU before.

Machine in question is the one to the left <-- .

What's left to do except test the motherboard?

[tom18230]

This happened to me and I had to do a clean install with ubuntu.

I don't know how to solve your problem, but I think you get this error when you don't defragment your disk, and the hive becomes too large to boot.

[carbon8ed]

Sounds like RAM, something installing has loaded into RAM which it didn't like, run memtest from CD to check the RAM - I've had this with older RAM

HTH

[-iceblade^]

That sucks..

Don't know what you can do to sort it, but don't install that STALKER patch next time...

[speardane]

peculiar indeed...

Any Post beeps? (presumably not)
I think you're right to check out individual components.
Might be worth resetting the system the CMOS (take battery out).
I would also try & check out the PSU & HD.

I have had odd problems (including with Ubuntu) with a PSU that later failed completely.

whilst it might sound odd to suggest a different HD - as you want recover the data - it would avoid any possibility of a virus affecting the system. (if it worked you could always mount the disk you want to recover the data from as a second or USB HD)

[DDY]

This happened to me and I had to do a clean install with ubuntu.

I don't know how to solve your problem, but I think you get this error when you don't defragment your disk, and the hive becomes too large to boot.

I don't think that caused it, I defrag my disks most weeks.

Sounds like RAM, something installing has loaded into RAM which it didn't like, run memtest from CD to check the RAM - I've had this with older RAM

Yep, tried that. Memtest looped 10 times and found no problems. I even tried with a different set of RAM from another working system and got the same BSOD.

That sucks..

Don't know what you can do to sort it, but don't install that STALKER patch next time...

, Of course I won't.

peculiar indeed...

Any Post beeps? (presumably not)
I think you're right to check out individual components.
Might be worth resetting the system the CMOS (take battery out).
I would also try & check out the PSU & HD.

I have had odd problems (including with Ubuntu) with a PSU that later failed completely.

whilst it might sound odd to suggest a different HD - as you want recover the data - it would avoid any possibility of a virus affecting the system. (if it worked you could always mount the disk you want to recover the data from as a second or USB HD)

Beeps - none, speaker not installed , the POST completes successfully, I can boot into the windows XP CD etc but it BSODs when I attempt to install it.

I reset the CMOS many times, doesn't help.

PSU is fine, HDDs are good; I formatted each one on a different system, fdisk'ed them (no errors reported) and put them back in, same problem. I also used an old 20GB IDE drive but again same problem.

A virus could have corrupted the system file, but I'm still getting a BSOD even with a completly empty HDD which rules that out.

[Lucio]

When you cleared your overclock settings, did you put the RAM voltage back up to manufacturer's recomended settings? I know you said you've done memtest but it's worth checking.

Also, might be worth clearing down your CMOS, just in case something in the Stalker patch, caused a low level issue in communicating via the Southbridge (since all your errors are related to communicating with things via that)

[DDY]

Default DRAM voltage is 1.8v and I have cleared the CMOS.

One thing I haven't tried is updating the BIOS, might as well give it a try.