CheckEmoji Community · the emoji forum
🏠 Home 🆕 What's new ❓ Unanswered 🔥 Popular 📡 RSS Members 👥 0 online log in · register
Home › IT › Software › How to recover Windows XP

How to recover Windows XP

Started by Nicole Bailey82 · · 👁 4 views · 8 replies

📡 Subscribe to replies

Participants Nicole Bailey82Jason Harris5Jack HayesNicholas King
Nicole Bailey82 Nicole Bailey82 NewcomerOP
1 message
joined May 2018
#1 ·
I've run into a massive headache here. My Windows XP machine just won't boot up.
After I get through the boot menu, the monitor just goes completely black. I’m really hesitant to go ahead and format the drive because this is my workstation at the office, and I have this one specific piece of software installed for which I don't have the original installer... and it's absolutely critical for our workflow.
I actually tried running a Windows installation from a CD—using the repair existing installation option so I wouldn't have to wipe everything—but after the system restarts, I'm right back to that same black screen.
Jason Harris5 Jason Harris5 Member
24 messages
joined Jul 2010
#2 ·
Has someone maybe messed with the monitor resolution settings?

When you're booting up, try hitting F8 to pull up the menu where you can select Enable VGA mode.

If that doesn't do the trick, you could try enabling boot logging. That’ll generate a little bootlog.txt file on your hard drive filled with all the messages from the startup process, which should make it a whole lot easier for us to track down what's actually going wrong.
Jack Hayes Jack Hayes Newcomer
7 messages
joined Nov 2008
#3 ·
Have you tried plugging in a different monitor?
Sounds a bit silly, doesn't it?
I actually remember this one guy describing a similar black screen issue once.
He went through the whole routine of testing everything—graphics card, hard drive, motherboard... but nothing worked. He didn't even think to check the monitor because his BIOS loading screen looked perfectly fine. 🤷
Nicole Bailey82 Nicole Bailey82 NewcomerOP
1 message
joined May 2018
#4 ·
The monitor itself isn't the issue here, because I actually set up a separate Windows installation on a different partition (dual boot) and everything works perfectly fine there...
Nicholas King Nicholas King Regular
716 messages
joined Jan 2023
#5 ·
Samuel Sullivan said:The monitor itself can't be the issue—I actually set up a separate Windows installation on a different partition using a dual boot configuration, and that works perfectly fine.

Like I mentioned earlier, it’s possible that this "broken Windows" instance is just trying to boot up with an unsupported resolution.

Just try booting into Safe Mode; honestly, it’s probably the best advice you'll get here.
Nicole Bailey82 Nicole Bailey82 NewcomerOP
1 message
joined May 2018
#6 ·
Nicholas King said:Like I mentioned before, there’s a good chance those glitchy Windows installations are just trying to boot up using the wrong resolution...

Give them a shot by booting up in Safe Mode; honestly, you were given some pretty solid advice there...

I gave that a shot too, but I just can't seem to get past the startup phase... it keeps hanging right there...

It looks like we’ve hit a bit of a snag with that system file... specifically d347bus.sys located deep within the Windows system drivers folder. Based on those directory paths, it seems like the OS is struggling to communicate with the hardware at a fundamental level... possibly a driver conflict or a corrupted boot sector partition... which can be such a headache when you're just trying to get things running smoothly!
Nicholas King Nicholas King Regular
716 messages
joined Jan 2023
#7 ·
Samuel Sullivan said:I gave that a shot, but I'm still hitting a wall during bootup at

multi(0)disk(0)rdisk(0)partition(1)\windows\system 32\drivers\d347bus.sys

A buddy of mine over at Google 😬 mentioned that this might actually be a Daemon Tools module—though, if you ask me, I'm not entirely sure it’s wise to go messing around with Daemon Tools and its various leftovers on a machine running mission-critical software. 🙂

My contact at Google also suggested trying to delete—or maybe just rename, just so we don't run into more headaches later... 🙂—the file at C:\windows\systems32\Drivers\d347bus.sys, and then just seeing if there's any actual progress.
Nicole Bailey82 Nicole Bailey82 NewcomerOP
1 message
joined May 2018
#8 ·
Well, I went ahead and tracked down that file and deleted it, but now I'm stuck staring at the Boot screen again on

\windows\system 32\drivers\isapnp.sys
Nicole Bailey82 Nicole Bailey82 NewcomerOP
1 message
joined May 2018
#9 ·
I finally did it!

I managed to boot straight into my new Windows installation from my dual boot setup
While I was poking around in
C:\WINDOWS\system32\drivers
I stumbled upon two files that were sitting at exactly 0kb, both showing a modification date from the very day the system crashed. I went ahead and deleted them, then gave the computer a quick restart. During the boot sequence, it prompted me to pop in my Windows XP installation disc, and once I did that... everything is running perfectly now!

You must log in or register to reply here.

Log in Register

🔗 Similar threads