• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Baffling Windows XP Professional installation

F

finalgt

Supreme [H]ardness
Joined
Aug 3, 2002
Messages
5,506
I decided to try upgrading to XP awhile ago; I basically failed miserably. At first I thought it was just some problem with hardware that was beyond my control, so I gave up the upgrade for awhile. After getting no errors with my memory in Memtest86 after 3 passes, and considering my motherboard, processor and video card all work fine in Windows 2000, I thought it might be the fact that the Master Boot Record was held by a Grub loader, rather than Windows. So I restored Windows to the Master Boot Record, and I still get the same error message.

The message, by the way, is "PNP_DETECTED_FATAL_ERROR", supposedly caused by a faulty device driver or PnP adapter. But...they're all working flawlessly in Windows 2000, and every component has the most recent drivers available from Windows Update. I don't even really care about the upgrade any more, it was just on a whim to begin with; I'm just wondering if anybody knows how to fix this problem.
 
My guess would be to try to install from scratch, there may be a screwy device driver issuse with some 2k driver that won't work in XP. But if you're content w/ 2k, that's obviously something that can't be tested.
 
A BIOS update/setting somewhere maybe? Try resetting the BIOS to defaults then make no adjustments. Install and see what happens. What part of setup did this happen at anyway?
 
Duplicate PDO: A specific instance of a driver has enumerated multiple PDOs with identical device ID and unique IDs.

That link is actually pretty helpful, despite the fact that I don't know what a PDO is. I'm assuming it's claiming that Windows will crash if I have two devices with the same device ID, but different specific IDs? I know the address of both the new PDO (0x8228D800) and the old PDO (0x8228DBA0) but I have no idea how to convert those into English to find out what device Windows is claiming is causing the problem. I have a hunch it's the hard drives (I have 2 120 WDs, a 160 WD and a 200 WD...although they've never caused problems in Windows setup before) but I recall attempting to start the setup with only one hard drive hooked up, and having it still not work. I'll try again tonight and see if that's the cause.
 
finalgt said:
Duplicate PDO: A specific instance of a driver has enumerated multiple PDOs with identical device ID and unique IDs.

That link is actually pretty helpful, despite the fact that I don't know what a PDO is. I'm assuming it's claiming that Windows will crash if I have two devices with the same device ID, but different specific IDs? I know the address of both the new PDO (0x8228D800) and the old PDO (0x8228DBA0) but I have no idea how to convert those into English to find out what device Windows is claiming is causing the problem. I have a hunch it's the hard drives (I have 2 120 WDs, a 160 WD and a 200 WD...although they've never caused problems in Windows setup before) but I recall attempting to start the setup with only one hard drive hooked up, and having it still not work. I'll try again tonight and see if that's the cause.
Click to expand...

You also might try to take all non-essential hardware out of the machine before you do the install (i.e. just use one HDD). If everything works, you can then add items back one at a time to see what caused the issue.

Just a thought as I haven't run into that one before.
 
Can you post the other numbers with that bugcheck? Better yet, can you get the memory dump off of the machine?
 
OK, Installing Windows with just one drive hooked up actually worked, but the system still instantly restarts when I try booting into XP from the dualboot screen, whether in safe mode or regular; 2K still works fine.

I think there's something I should explain about my system that might be causing this, though I don't know how to fix it; my Windows 2000 installation is on the first partition of my first drive [multi(0)disk(0)rdisk(0)partition(1)] though inside Windows it's recognized as the F:\ drive, due to some setting I changed when originally installing the operating system. Windows XP is on the first partition of the second drive [multi(0)disk(0)rdisk(1)partition(1)] though inside windows it's recognized as C:\. I'm fairly sure this is what's causing the problem, and why the system is instantly restarting...but how do I go about fixing this? Unplugging the first drive results in my being unable to start the computer up, due to the fact that the boot.ini file is on that drive...any help would be appreciated.

Sorry if I left out any details, I just got home from working 11 hours starting at 5 am.
 
You must log in or register to reply here.
Back
Top