Blue screen of death installing WinXP on new comp

[dividedsky319]

Ok, sort of a long story...

Built a new system, and I was putting into it two hard drives I was using in a system I had... a 40 gig and a 120 gig. I backed up what I needed on the 40 gig, then I wanted to format the 120 gig and install WinXP on it in the new system. Well, being dumb, I didn't really know how to format the 120 gig when it was the main disk (I made a DOS boot disk but I couldn't access the hard drive to run fdisk)

So, I went to download.com and found this program: Kill Disk

I started the program and started the process on the hard drive.. Well I decided it was taking too long so I decided to cancel (stupid idea)...

It got far enough that it said there was no OS on the system, so when I booted up with the WinXP disk, the setup thing came up and everything and I tried to install on the 120 gig and format it and everything... well it always gave me a "PAGE_FAULT_IN_NONPAGED_AREA" or a "IRQL_NOT_LESS_OR_EQUAL" error and restarted.

I decided I'd just install the OS on the 40 gig, so I disconnected the 120 gig and installed and everything went fine.. But I still want the OS on the 120 gig drive. It works fine in windows, I ran chkdsk and it's fine, and I can put files on it and everything... but whenever I go to install onto the drive, it always gives me one of those two errors.

I also sometimes randomly get the IRQL error while in windows (usually when I'm installing something or something is being unzipped)

Also, when I try running a game that uses the video card, it usually works for a little while then it just exits back to windows.

I have noticed that my CPU is running sorta hot... 55 degrees or so. Not overclocked.

So many problems... Any ideas?

 

[EeyoreX]

I'm a lazy, lazy man... Check my post here, it may be the same problem with the same solution.

Hope that helps.

\Dan

 

[MaestroQuark]

Had the same problem recently on a clean reinstall of XP (completely wiped Hard Drive).

It's not necessarilly faulty ram. In my case, I had accidentally changed an obscure BIOS setting ('S2k Slew Rate') which caused the system to be massively unstable. I'd recommend going into your BIOS, restoring your default settings, then modifying only what you know works.