Can't install any Windows OS --> see inside

[Sentry24]

I've just built myself a new system that contains the following components:

AMD Athlon XP 1900+
512mb cas2.5 pc2100 ram
Shuttle AK31 v3.1
LG 16x CDRW
Western Digital 100gb 7200rpm HDD
Leadtek Geforce 4 ti 4400
Creative Labs SB Audigy OEM
SMC NIC
Aopen 56k v92 modem

That's my setup.. the whole system posts fine, I can use a bootdisk to get into DOS and all, access cds and fdisk and format the hard drive.

The problem comes when installing any Windows OS:

With Windows 95 it goes smoothly until it gets to actually loading windows: prints some error regarding IOS.

With Windows 2000 I can start to copy files over for the installation but when it goes to "start windows" to continu the installation process, it gives me a Stop error regarding ntoskrnl.exe.

With Windows XP Pro it's pretty much the same as Win2k, it copies over all the files from the setup boot disks/i386 folder and then when I press Enter to install on, it prints a Stop error: 0x00000050 ntfs.sys with mention of PAGE_FAULT_IN_NONPAGED_AREA.

What does this all mean and how can I resolve it? Stop errors usually refer to software, drivers, or hardware incompatibilities..

Is my HDD faulty? did I not partition it right and format it okay? Any ideas?

 

[AndyHui]

Have you tried Windows 98?

Windows 95 will not work with any AMD processor faster than 333MHz without being patched. It will give you the IOS error that you are seeing.

 

[Sentry24]

Ah, I didn't know that about W95.. well, I learnt something

I haven't tried with Windows 98, I'll give it a spin but I don't know if it'll work as Win2k and WinXP didn't.

Could it be a problem with my ram?

 

[Electrode]

Yes, it does sound like a RAM problem. I remember getting those pagefault in nonpaged area stops, and I fixed it by replacing the RAM.

 

[owensdj]

Sentry24, are you overclocking? That could cause those kernel STOPs you're getting with Win2K and WinXP. If not, you may want to run the hard drive diagnotics included in Western Digital's Data Lifeguard Tools to see if you have a problem with your drive. Also, you should be partitioning and formating during the Win2K or WinXP install, not in DOS FDISK.

 

[Sentry24]

Well, I took out the modem sound card and NIC, and actually had the installation going through, at one point it locked up though and I figured I'd try it from scratch.

Now it comes up with a Stop error 0x00000024 with ntfs.sys (versus a 0x00000050 error before)

I looked the error code up and it points to a File System error.. urgh, what to do now?

I also ran diagnostics on my HDD and all seems okay.

 

[Sentry24]

I just tried booting the setup from the cdrom, it starts up and loads all the files that the boot disks do, then when i press ENTER to continu with the setup it displays a (gasp) new error.. 0x000000BE with ntfs.sys.

I looked the error code up and it is ATTEMPTED_WRITE_TO_READONLY_MEMORY, which means that a driver attempted to write to read-only memory. Commonly occurs after installing a faulty device driver, system service, or firmware.

This just ain't getting any better..

 

[Nothinman]

Have you even tested the memory yet?

 

[Sentry24]

<< Have you even tested the memory yet? >>



*slaps forehead* running it right now..

 

[Sentry24]

First of all, I'd like to say thanks to everyone that offered any kind of support at all, it was greatly appreciated.

After having run memtest86 (thanks Nothinman), which brought up 2500 errors (throughout test 3, 4 and 5), I called up the shop and arranged to replace the stick on Tuesday (they didn't have any stock)

Anyways I went out to buy a new 256mb stick to get me through till Tuesday, and in the memory tests I ran there was no problem and installation is going on well and smoothly.

Again, thanks for all your help everyone!

 

[GonzoDaGr8]

which brought up 2500 errors

:Q Holy Cow!!