XP Installation Problem: Getting a Blue Screen After Accepting EULA

By pyrofalkon ·
I built a computer for a customer in late 2005, and its hard drive finally failed to work. I bought a new hard drive and installed it properly. I installed Windows XP, just as I had the last time. No new software was being introduced.

After XP installed (and it DID install properly) and fully updated, I returned the computer to the customer, as she elected to do the rest of her installations (printer, modem, etc.) by herself. When attempting to use her install disc for her printer, she says the progress bar hit 75%, then the entire computer froze: no blue screen, no anything.

From then on, any time she's restarted the comp, it gets to the "loading XP" screen before restarting itself. This when she decided to call me about the problem.

I've tried running XP in safe mode, with the same result. I've tried running XP in "Last Known Good Config" mode, same result. I figured I'd just reinstall Windows then. After restarting yet again, I get to the XP setup, then hit F8 to accept the license agreement...

And THEN I get a blue screen of death, with IRQL NOT LESS OR EQUAL. I've done some searching and have seen this error reported a lot, but can't find a solution to it happening at THIS spot (i.e., directly after accepting Microsoft's EULA).

I'm not sure if any of the following is relevant, but I know for things like this, there is never "too much information"...

The four parameters of the error message are 0x0a33001f, 0x00000002, 0x00000000, and 0x8081c63c.

The printer that started this whole mess is a HP1310.

The copy of XP is legal, but I'm not sure if she activated Windows before trying to install anything. (Lesson learned: Activate Windows before the computer leaves my possession from now on.)

Not sure where to go from here, so any help would be greatly appreciated.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

Drivers should be installed BEFORE you update XP.

by OldER Mycroft In reply to XP Installation Problem: ...

If you have updated XP before the drivers were installed, you will constantly hit a barrier because the updates are newer than the original drivers.

All the chipset and system drivers should have been installed before any updates were invoked.

Collapse -


by pyrofalkon In reply to Drivers should be install ...

Didn't realize that... that includes hardware basics like the printer?

This still doesn't help my core problem: I can't reinstall Windows at the moment thanks to that IRQL blue screen. Any way of clearing that out?

Collapse -

What is the service pack

by Jacky Howe In reply to XP Installation Problem: ...

that is on the XP CD that you are installing from. If it is not SP2 you may have to slipsteam the XP CD.
If it is SP2 try a Repair/Install and if that works. Try this.
Disconnect the printer from the PC
Go to the Control Panel and click on Add/Remove Programs. Highlight any Printer Software that is listed here. Select Remove.
From the Control Panel, click on Printers & Faxes. Right click the printer in question and select Delete
Look at the Toolbar. Select File, then Server Properties. Look in the Drivers tab. Highlight the printers drivers listed here and click on Remove for each one.
Reboot the PC. Do NOT reconnect the printer!
Go to the website of your printer manufacturer. Look for new XP drivers for your model. Download the correct software.
Run the exe file you just downloaded. It should auto-start the installation program
The software will tell you when to connect the printer.
Once the software is installed and the printer connected, Set the printer as the Default, try a test page. and check your notifications.

Collapse -

SP2 on disc, SP3 at time of problem

by pyrofalkon In reply to What is the service pack

The disc has Service Pack 2, but I had upgraded XP all the way (including Service Pack 3) before the customer installed the printer drivers. I just advised her not to hook up hardware before installing drivers, and that it was my fault I didn't warn her about that before. I guess it's one of those things that I take for granted and just forget to tell people usually...

Anyway. At the moment, we can't get far enough into Windows to remove anything. The computer always restarts itself at the loading screen for XP (the black screen with the XP logo, not the all-blue screen with the word "loading"). I figured I'd just reinstall Windows clean and be done with it, but this IRQL thing is stopping me.

I've tried doing a repair, but it gives me the same error (albeit with different parameters) once the recovery console tries to start.

Collapse -

See if this helps

by Jacky Howe In reply to SP2 on disc, SP3 at time ...

Faulty Fans, Dust and Grime build up on the Heatsink restricting air flow. I would give the inside of the case a blowout with compressed air. When blowing air through the fans make sure that you physically stop them from spinning, as they may generate power and **** something up. Remembering to ground yourself by placing the back of your hand on the Power Supply Unit and not moving your feet. By not taking this precaution it is possible that you could inadvertantly cause damage to the PC from an electrostatic discharge. Then remove the Heatsink, giving it a thorough clean and reseat the CPU applying new CPU grease. If the Fans spin freely when you give them a spin they are probably OK. If there is resistance replace them.

Clean the golden edge of each memory stick with a soft rubber, remembering not to touch the golden edge of the memory stick. Check with one stick at a time, remembering to disconnect the power from the PC.
Also check Capacitors around the CPU for swelling or bulging.

Check the memory.
You can test the memory by running Windows Memory Diagnostic that can be downloaded from http://oca.microsoft.com/en/windiag.asp. If memory problems are found, try re-seating the RAM. If it doesn't work, replace the defective RAM.

Note: A damaged or insufficiently charged internal battery can corrupt CMOS or BIOS settings. It can also cause all sorts of wierd things to happen.

Collapse -

More info

by Jacky Howe In reply to See if this helps

Troubleshooting a Stop 0x0000000A error in Windows XP


Download and create this CD. If it boots up OK and runs smoothly it will rule out hardware.


Collapse -

RAM Checks Out Okay

by pyrofalkon In reply to More info


I ran that Microsoft Memory Tester you sent me the link for, and the RAM passed with flying colors.

I'm a little too exhausted to deal with this any more tonight (it's 11:00pm as I write this, and I've been dealing with it since about 4:00pm), so I'll run the other thing tomorrow when I get a chance.

You don't happen to know of an ISO that gives me a bootable CD with the ability to just format a hard drive, do you?

Collapse -

You can try this

by Jacky Howe In reply to RAM Checks Out Okay

The Windows Vista Recovery CD can be used to Boot your PC.

<b>Creating a Windows Vista Recovery CD</b>


<b>Download from here:</b>


Boot from the CD and Delete the Partition. Use your XP CD to recreate it.
< Format >
Reset your BIOS by clearing CMOS, refer to your Motherboard Manual. If that doesn't work Flash your BIOS.


Collapse -

OK, this is (should) be an easy one to sort out..

The IRQ that you stated is some how related to the memory chips, since you can see something on screen means it can not be the graphic card.
But one step at a time here.
1). Take out the ram chips and replace with a good make. More the better here but just place one in the slot at the moment.

2). Reboot and see if that makes any difference. You might need to make some changes in the bios for the new memory, so go in there and see if the memory shows up ok.

3). Is the computer running off the on-board graphics?. If so you might want to add on a card since the on-board graphics pull off the memory to work good, just in case.
See how you go.

Please post back if you have any more problems or questions.

Collapse -

RAM Experiment

by pyrofalkon In reply to OK, this is (should) be a ...

Okay, after shooting darn near the entire computer with compressed air, I removed one (of the two) RAM stick to see if anything would change. Still the same IRQL issue. So I took out that stick and put in the other one. Again: same IRQL issue. However, both times when the comp was only running on a single stick, it was producing different parameters on the IRQL blue screen. If it's only the RAM, then I can only assume it's both sticks. If it's not the RAM, then I'm pretty much out of options for my own expertise, unless one of you guys can offer some insight. This is driving me nuts.

I don't have any spare RAM sticks on me, and I hesitate to get more just to experiment. But if that's what I've got to do, I can find a way to procure some.

Yes, the customer operates off on-board graphics. She's not a gamer, and typically only uses the comp for office-like applications and the occasional Flash Movie.

Related Discussions

Related Forums