PDA

View Full Version : New PC Build Probs - BSOD installing XP??


csnokia
03-22-2004, 02:15 PM
right well ive just built a new pc, have built many before this one.. and i keep getting BSOD's?!? im really confised as this shouldnt be happening as all the parts are brand spankers..

Can anyone help?
The messages i get are:

BAD_POOL_CALLER
IRQL_NOT_LESS_OR_EQUAL
or.. more commonly..
PFN_LIST_CORRUPT

Any ideas as to what the problems might be, i have tried 2 copies of XP and neither seem to work, both home and pro edition..

Spec is a 2200+, dvd rom, 256corsair ram ...etc

shouldnt be havin a problem, unless its me being stupid.. could anyone help me out? thanks in advance.
Chris

Edit:

I've also had the BSOD saying 'IO1_INITIALISATION_FAILED' as well.. but i seem to only get that one when i attempt to install xp home.

PH/\T B,5TARD
03-22-2004, 02:47 PM
Without a bit more info I would have stab a guess at bad ram as it's one of the few things that have given me grief building XP/W2K machines to date.
That and "Manifest Parse Error" (bad copy of XP).

PhilEnfield
03-22-2004, 02:54 PM
Seem to remember a m8 of mine had this and it was down to faulty or mismatched RAM.

If you have more than one stick, try removing one at a time and retrying or maybe check it's the right type for the mobo.

Littlejack
03-22-2004, 03:48 PM
also, if possible, adjust memory timings. some motherboards do not like the super fast low latency memory, i have found macking adjustments here prevents these kind of errors.

Nuttapper
03-22-2004, 04:53 PM
PFN LIST http://support.microsoft.com/default.aspx?scid=KB;en-us;291806


more or equal http://www.computerhope.com/issues/ch000365.htm

pool attendant http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/Default.asp?url=/resources/documentation/Windows/XP/all/reskit/en-us/prmd_stp_czgw.asp

each time you have tried a reinstall, did you delete the partition and recreate it, just so there aint sumthing on the MBR stored?

QWERTY
03-22-2004, 06:36 PM
It's either bad RAM, like everyone else mentioned, or one or more of the drivers. Have you tried updating all the drivers? (Video, audio, NIC, motherboard chipset)