Stop error 0x0000007b after motherboard change

[LoneRngr]

I recently had the motherboard in a Win2000 Professional system go bad, and I was unable to find another duplicate motherboard to replace it, so I had to go with a new motherboard and processor. The problem is, now that I have installed the new motherboard, WIN2000 now gives me a stop error 0x0000007b and a blue screen upon loading. According to the Win2000 knowledge base, this is probably caused by the new IDE drivers not being in the Win2000 registry. Their solution is either to use the same hardware(not possible in this situation) or to merge files into the registry before changing the system to the new PC. Of course, neither of these solutions will work in my case.

So, I am left with a nice new MB and processor, and a system that won't boot. Is there any other way to get the system to boot? I have a boot/setup disk set, and it gives me the option to repair Win2000...will this work without wiping out the hard drive? I don't want to reinstall windows unless it can be done while saving all the other info on the HDD as some of it is important.

 

[Eguy]

Hi LoneRngr;

It has been my experience that a new mobo & processor almost always require a new OS install. You can try a repair install, but ???

If you have access to another PC, pull out your hard drive, set the jumpers to make it a slave, and install it there. you should then be able to copy any files that you need.

Ed Please let me know if the suggestion(s) I provide are helpful to you.
Sometimes you're the windshield... Sometimes you're the bug.

 

[LoneRngr]

I'm going to try to install the OS over top of the old one using the ERD. I was reading in another very long thread about this error, and most of the hardware change related IBR stop errors were fixed by installing the OS over the old one. If that doesn't work, I will try to set the drive as a slave and add all the files I need that way. Thanks for the advice.

Lonerngr

 

[LoneRngr]

I was able to hook the hard drive to another motherboard. The new MB and the old were both Slot-1 types, and it turns out they had the same IDE controllers on the MB, so Win2000 booted normally on the second machine. I then followed Microsoft's Knowledge Base article on this, and merged the given file into the registry, and I was then able to boot into Windows on the newly acquired MB. Thanks for the advice!

Lonerngr