• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Windows wont boot after mobo + processor swap

C

Cellwind929

Junior Member
I recently switched motherboards from my msi board with p4 and agp video to a dfi lanparty ultra-d with 165 opteron and pcie video card. The problem is, windows wont boot, this is probably due to the driver signing crap micro$oft has for XP.

I am confused as to what I need to get it running. The xp home I have came with the pc I bought a few years ago, so the cd is labeled as a recovery cd. When I try to repair or reinstall windows, they just crash. When I start the computer I get the "how to you want to load menu" with safemode etc. Any option just causes the computer to restard, so I am at a loss as to what I should do to fix this issue and get windows to boot.
 
It had to do with you not being too bright in thinking that you could change to a completely different chipset and not have any problems.
 
Cubby, thats what I'm probably going to do. My cd fails at repairing, so I'm getting another one from my fathers office to repair but use my key. Thanks for the reply.

@JonnyBlaze
way to be helpful... not
 
Originally posted by: Cellwind929
Cubby, thats what I'm probably going to do. My cd fails at repairing, so I'm getting another one from my fathers office to repair but use my key. Thanks for the reply.

@JonnyBlaze
way to be helpful... not
Click to expand...

Well, when someone spells MS with a $ and then blaims a part of the operating system they obviously know nothing about... A reasonable post gets a reasonable response.
 
First, it's "Microsoft" not "micro$oft".

Second it has nothing to do with the "driver signing crap", it has to do with the fact that you are loading a set of drivers for a chipset that no longer exists.

Third, your retail or corporate copy of XP pro won't work for a repair of XP home with an OEM key.

Fourth, since your OEM copy was truly distrubuted by an OEM that gave you a customized "recovery CD" the fact that you basically "swapped machines" with your hardware changes makes it both illegal and technically impossible to use that CD.

Fifth, I'm betting you didn't backup sh1t.


Get yourself a legitimate copy of XP that you can use and do a repair install with the key that comes with it. If no luck, throw down a parallel and retrieve your data.
 
Hmmm... Sounds a lot like a PICNIC error. 😉

We tried to move the mirror drive of one system to a newer box and never managed to get it booting. It would BSOD with "Inaccessable_Boot_Device" regardless of putting it on the SATA or IDE ports and repair attempts (Fast, and fix boot or MBR - I can't remember) failed as well.
 
Originally posted by: JonnyBlaze
It had to do with you not being too bright in thinking that you could change to a completely different chipset and not have any problems.
Click to expand...

To be fair, you used to be able to pull this trick in windows98 without to much trouble.
 
Here's an idea that probably won't work but might be worth a shot.

Hitch up the old motherboard and processor again to the harddisk. Boot windows (if you still can) and try changing the IDE controller driver the hard disk to the standard PCI IDE controller. Then shut it down, and hitch it back up to your new stuff. If you're lucky it will boot.

Whether its legal or not, or if it'll even activate...
 
Smilin: your whole post was uncalled for. If we all knew everything about everything, this forum would never exist. People come here because they do not know all that is out there. That's why I am here, that's why you are here, that's why he is here.

If he says he has the XP Home disc that came with the computer, why not take his word for it? It's not like he came onto these boards saying "last time I upgraded to SP1 the system became too unstable - is there anything I'm missing by not updating?"

The upgrading of motherboards on an OEM license is a debatable issue. I've switched out boards on Dell, HP, e-Machine computers when they've gone bad, and I've explained the situation in full to the reps on the other end during re-activation, and they've never given me any shread of a hassle. I asked Microsoft honestly for permission, and they said "Yes". Microsoft makes the licensing rules, and all I am doing is following what they tell me.

If you were forced to send the computer back to the manufacturer to repair a motherboard, just out of my own thought, that's probably against some anti-trust laws if Microsoft or the manufacturer enforced it. My own opinion, it's mainly a matter of product support. If I replace a damaged Dell motherboard, well then obviously I can no longer call Dell for support on that machine.
 
If you have a "recovery" CD it's likely an OEM disk. The licensing terms of an OEM OS do not allow you to transfer the OS to another mobo.

If you want to make this work, read me. If you follow the first post with the HDD setup on the old PC first you can probably get this working. There is are two other methods in the thread as well.

Not only can you learn a number of ways to do this, you can learn why it didn't work in the first place.
 
I've switched out boards on Dell, HP, e-Machine computers when they've gone bad
Click to expand...
This is the only time you can replace the mobo on an OEM system with MS' blessing. Otherwise it's quite clear it's not in the OEM license you agreed to.

Ability to activate != legit use.
 
Meh, this whole licensing and activation thing is one of the things that drove me to load Ubuntu on my laptop. Why should a person have to replace their OEM XP license just becaue a part fails? IMO that's BS and no amount of small-print legalese is going to make me change my mind.

Here's a story... I got my IBM T42 with the default IBM load on it. If you have an IBM you know they put a "restore partition" on your drive rather than give you a restore disc. Well, on the first boot - no additional software loaded yet - there was like 50-something running processes and the system was sluggish. Rather than start uninstalling programs and tweaking services I blew it away and loaded it with my legal Retail XP Pro copy (yes, I know that's breaking the rules :roll: ) that's installed on my desktop. It installed and validated without issue. Later on I reloaded my desktop and it failed validation (I've reloaded it several times over motherboard and video card upgrades as well as my T42). I called Microsoft and explained the entire situation and they gave me a validation code without issue.

Did I follow their EULA? No. But in the end I own 2 legal copies (retail on desktop and OEM on IBM) of WinXP Pro and apparently the Microsoft rep I spoke with agreed with me.
 
Originally posted by: cubby1223
Smilin: your whole post was uncalled for. If we all knew everything about everything, this forum would never exist. People come here because they do not know all that is out there. That's why I am here, that's why you are here, that's why he is here.
Click to expand...

Wrong. The OP started with the attitude in his original post.

 
Originally posted by: cubby1223
Smilin: your whole post was uncalled for. If we all knew everything about everything, this forum would never exist. People come here because they do not know all that is out there. That's why I am here, that's why you are here, that's why he is here.
Click to expand...

I provided him with the information he needed. I know all about this forum and why it exists and I'll be the first to step up and help people when I can (others can witness or you can go search yourself). He came in here with attitude about MS causing his problem when he caused his own problem. I called him out on it and I'm not going to retract it.

If he says he has the XP Home disc that came with the computer, why not take his word for it? It's not like he came onto these boards saying "last time I upgraded to SP1 the system became too unstable - is there anything I'm missing by not updating?"
Click to expand...
I did take his word for it. His word was not that he had an XP home disk that came with the computer his word was that he has a RECOVERY disc that came with the computer. The former would be helpful, the latter will simply wipe his data.
The upgrading of motherboards on an OEM license is a debatable issue. I've switched out boards on Dell, HP, e-Machine computers when they've gone bad, and I've explained the situation in full to the reps on the other end during re-activation, and they've never given me any shread of a hassle. I asked Microsoft honestly for permission, and they said "Yes". Microsoft makes the licensing rules, and all I am doing is following what they tell me.
Click to expand...
By swapping mobo and CPU he's basically making a new computer and reusing old components like CDRom and case. His OEM license is done for. My real point here wasn't the legal aspects of it but the more important point that the OEM key isn't going to work with a retail or corporate copy of XP (which will be Pro anyway, not home)
If you were forced to send the computer back to the manufacturer to repair a motherboard, just out of my own thought, that's probably against some anti-trust laws if Microsoft or the manufacturer enforced it. My own opinion, it's mainly a matter of product support. If I replace a damaged Dell motherboard, well then obviously I can no longer call Dell for support on that machine.
Click to expand...

You didn't buy your OEM copy of Windows from Microsoft. You bought it from the OEM. They gave you a killer discount on the OS (nearly free actually) but the catch is you can only use it on that computer for the life of the computer (not a bad deal really). If that machine dies, repair it. If you don't like the catch, buy retail and transfer it from PC to PC all day long.

If following the law is something you have an issue with or want to debate, fine. I won't be participating because frankly it's a black and white issue and I don't give a crap about the debate.

Sorry I got your panties in a bunch but I told him what's up and for technical reasons it's pretty much the gospel in this case...

"Get yourself a legitimate copy of XP that you can use and do a repair install with the key that comes with it. If no luck, throw down a parallel and retrieve your data. "
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top