Inspect your RAM sockets and/or run memtest86

I assume you are using a slipstreamed XP-SP2 CD?

majestyk wrote on 2023-07-28, 19:01:

I assume you are using a slipstreamed XP-SP2 CD?

Not sure what slipstreamed is supposed to mean but the cds i have are official Microsoft Windows xp cds. One with service pack 1 and the other with service pack 2.

Set everything to default speed. IIRC you said you have a K6-2+ 500 MHz, so be sure to set it to 5x100 and set the CMOS settings to the defaults. I find it easiest to run Memtest from a floppy when using machines that have a floppy drive, so hopefully that machines has one, and you have a floppy disk on hand.

Repo Man11 wrote on 2023-07-28, 19:51:

Set everything to default speed. IIRC you said you have a K6-2+ 500 MHz, so be sure to set it to 5x100 and set the CMOS settings to the defaults. I find it easiest to run Memtest from a floppy when using machines that have a floppy drive, so hopefully that machines has one, and you have a floppy disk on hand.

Yeah I have a k6-2+ overclocked to 600 mhz. I'll try running the installation with the cpu set at its rated speed. Yes the pc has a floppy drive and i have a few spare floppys i can use so I'll try running Memtest as well.

Could be not completely stable at 600mhz, and nothing like XP install has ever stressed it enough to throw errors.

A page fault in a none paged area basically means it looked into a memory address and that address was empty when it shouldnt have been.

Test you RAM with Memtest86.

Florian J wrote on 2023-07-28, 20:11:

Repo Man11 wrote on 2023-07-28, 19:51:

Set everything to default speed. IIRC you said you have a K6-2+ 500 MHz, so be sure to set it to 5x100 and set the CMOS settings to the defaults. I find it easiest to run Memtest from a floppy when using machines that have a floppy drive, so hopefully that machines has one, and you have a floppy disk on hand.

Yeah I have a k6-2+ overclocked to 600 mhz. I'll try running the installation with the cpu set at its rated speed. Yes the pc has a floppy drive and i have a few spare floppys i can use so I'll try running Memtest as well.

Set it to a base clock and try the install again, if you call no joy do the above.

Warlord wrote on 2023-07-28, 20:49:

Could be not completely stable at 600mhz, and nothing like XP install has ever stressed it enough to throw errors.

Yeah but the CPU and RAM are linked, so the CPU could be stable while the RAM cant keep up so errors in the way it is and causes page faults in the system RAM.

ElectroSoldier wrote on 2023-07-28, 23:54:

A page fault in a none paged area basically means it looked into a memory address and that address was empty when it shouldnt have been.

Test you RAM with Memtest86.

That´s the common explanation, but don´t hold your breath, I have seen countless cases when this error was not RAM related at all.

Florian J wrote on 2023-07-28, 18:46:

I've been trying to install windows xp on my amd k6-2+ but everytime it gets to copying the files i get a blue screen "page_faul […]
Show full quote

I've been trying to install windows xp on my amd k6-2+ but everytime it gets to copying the files i get a blue screen "page_fault_in_nonpaged_area". I have tried 2 different cds but both have the same issue. I've also tried a windows vista cd and that gave me a different blue screen, "pfn_list_corrupt blue". Also I'm pretty sure that both the dvd rom and the installation cds work fine as I've used them before without any issues.

Troubleshooting steps I've already done:

Trying different ram, trying different hard drives, different IDE cables, resetting bios.

Any help would be appreciated as I've been trying to figure this out for hours.

Does it blue screen at the same spot (like progress indicator shows 5%) while copying files?

majestyk wrote on 2023-07-29, 04:56:

ElectroSoldier wrote on 2023-07-28, 23:54:

A page fault in a none paged area basically means it looked into a memory address and that address was empty when it shouldnt have been.

Test you RAM with Memtest86.

That´s the common explanation, but don´t hold your breath, I have seen countless cases when this error was not RAM related at all.

I agree, but its the common one because it often works and Ive found over the past 30 odd years its easiest to go with the common ones first then work your way up through the less common after that.

Theres no point searching for a difficult fix if a simple one will do.

sangokushi wrote on 2023-07-29, 05:33:

Florian J wrote on 2023-07-28, 18:46:

I've been trying to install windows xp on my amd k6-2+ but everytime it gets to copying the files i get a blue screen "page_faul […]
Show full quote

I've been trying to install windows xp on my amd k6-2+ but everytime it gets to copying the files i get a blue screen "page_fault_in_nonpaged_area". I have tried 2 different cds but both have the same issue. I've also tried a windows vista cd and that gave me a different blue screen, "pfn_list_corrupt blue". Also I'm pretty sure that both the dvd rom and the installation cds work fine as I've used them before without any issues.

Troubleshooting steps I've already done:

Trying different ram, trying different hard drives, different IDE cables, resetting bios.

Any help would be appreciated as I've been trying to figure this out for hours.

Does it blue screen at the same spot (like progress indicator shows 5%) while copying files?

It mostly blue screens when the installation starts copying files or while formatting.

Also I sadly can't run memtest as i don't have a hard drive with anything on it.

Also it can never copy the modem.sys file. And when i press enter to try again it always blue screens.

Underclock the cpu, and put slowest ram settings. If cache has options, put slowest.
Not a solution, just a layman's trick. Unless it doesn't work.
If you can, try another cd/dvd drive.

Nexxen wrote on 2023-07-29, 11:02:

Underclock the cpu, and put slowest ram settings. If cache has options, put slowest.
Not a solution, just a layman's trick. Unless it doesn't work.
If you can, try another cd/dvd drive.

I've already tried a different cd rom and that didn't make a difference.

Alright so the installation works fine if i run the cpu at its rated speed. Thanks for the help 👍

Florian J wrote on 2023-07-29, 10:36:

Also I sadly can't run memtest as i don't have a hard drive with anything on it.

Memtest86 runs from a CD or any other bootable media.
If you can install XP then you can run memtest86

Florian J wrote on 2023-07-29, 11:54:

Alright so the installation works fine if i run the cpu at its rated speed. Thanks for the help 👍

I discovered this in 2002 when I got my first copy of WinXP and tried to install it on my KT7A. I had my cheepo TigerDirect RAM set to tight timings, and it seemed okay with Windows 98, but when I tried to install XP it would halt with some code. I set the RAM timings to default (after trying many other things), and it worked fine. Sure, there had been signs, but I was able to blame them on Windows 98 and Via; but the preinstallation tests that Windows XP does revealed the real culprit was me. Very similarly but much more recently, my PCChips P4 system seemed fine with Win98 and the tightest timings on the RAM (DDR400 running at DDR266 speeds) but when I installed Windows XP to test a video card not supported by Win98 it revealed a fault that I had (again) blamed on Win98. I suppose that's one of the many reasons that NT kernel operating systems are more stable than 9x - they designed better preinstallation tests to reveal hardware faults that would cause the system to crash.

Repo Man11 wrote on 2023-07-29, 23:44:

Florian J wrote on 2023-07-29, 11:54:

Alright so the installation works fine if i run the cpu at its rated speed. Thanks for the help 👍

I discovered this in 2002 when I got my first copy of WinXP and tried to install it on my KT7A. I had my cheepo TigerDirect RAM set to tight timings, and it seemed okay with Windows 98, but when I tried to install XP it would halt with some code. I set the RAM timings to default (after trying many other things), and it worked fine. Sure, there had been signs, but I was able to blame them on Windows 98 and Via; but the preinstallation tests that Windows XP does revealed the real culprit was me. Very similarly but much more recently, my PCChips P4 system seemed fine with Win98 and the tightest timings on the RAM (DDR400 running at DDR266 speeds) but when I installed Windows XP to test a video card not supported by Win98 it revealed a fault that I had (again) blamed on Win98. I suppose that's one of the many reasons that NT kernel operating systems are more stable than 9x - they designed better preinstallation tests to reveal hardware faults that would cause the system to crash.

I discovered that in pretty much the same way as you did.
I over clocked a dual P3 system that was working under WinNT, then nicely under Win2k but XP Pro (Devils0wn of course because I was a very early adopter) didnt want to install at all.
It took a lot of trial and error to discover it was the overclock that was causing the problem, even though it had never caused a problem up until that point.

I also discovered many of the niggles that I had put down to the OS were to do with over clocking.
Dual CPU systems prevent the locking up that you get on single CPU systems, so the apps crash due to the OC but the OS carries on on the second CPU.

I drifted away from pin mods and over clocking in favour of stock n stable systems.