Comments on: Blue Screen of Death after Virgin XP ReInstall

Question: Blue Screen of Death after Virgin XP ReInstall

BigBrownBear — Thu, 02 Mar 2006 09:00:31 -0800

I'm getting the blue screen of death right after reinstalling windows XP and the drivers

...and I'm not sure why. It's an HP laptop, less than a year old. I am reinstalling from the CD (not from within Windows), deleting partition and creating a new one. I have the HP drivers disk. I download some of the windows updates, virus protection, firewall, etc., then I get the blue screen STOP error that says I might have a device driver problem. The computer won't even give me the option to start in Safe Mode - I get a black screen (although I can get into the diagnostics).

This has happened twice already. First time I updated bios right away and second time I didn't. Any ideas what's going on? The weird thing is that the computer was actually running for a while before it died the second time -I'd already installed a bunch of programs and rebooted a dozen times.

By: jackofsaxons

jackofsaxons — Thu, 02 Mar 2006 10:02:32 -0800

I've seen XP do some wierd stuff from driver problems with ACPI, and since this is a laptop, that might be a good lead...

By: BigBrownBear

BigBrownBear — Thu, 02 Mar 2006 10:30:54 -0800

ok, that's a good lead. i'll see if there are updates for those drivers

By: Hexidecimal

Hexidecimal — Thu, 02 Mar 2006 11:30:56 -0800

Definitely Sounds like a driver issue, the best thing to do is to install a clean xp, grab either the Service Pack 2 CD, or the IT Pro exe, unless your XP has SP2 integrated.

Install that, then grab the latest drivers for all your hardware from HP's website or their various vendors. If the problem persists, check your RAM, I've had similar problems with my desktop system after the ram started dying, replacing the RAM stopped all my issues.

By: muddgirl

muddgirl — Sat, 04 Mar 2006 14:46:16 -0800

I might have a device driver problem

For what it's worth, this is pretty much a general error message Windows spits out when it doesn't really know what the problem is (the status quo). Check your drivers first, but keep in mind the problem probably lies somewhere else.