Stop Error when replacing Motherboard, how to fix this

[Bill Simard]

I am replacing my motherboard on my XP PRO machine.
The last time I did this I got a Stop 0X000000 error and after much
searching found the cause was the IDE controller being different.

I had to reinstall XP from the CD and that wipes out all my updates and some
of my programs, including my anti-virus, causing me to have to reinstall,
which is a big hassle and takes weeks to get everything back up and running
again.

I have heard a rumor that there are 2 files, that if deleted before the
motherboard is replaced, XP will detect the new IDE controller and rebuild
these 2 files and I will not need to re-do all the windows updates and will
not have to reinstall all my software programs.

Does anyone know what these 2 files are ? Is this true, or is there another
way to make this work ?

Thanks for the help

Bill

 

[R. McCarty]

Not delete, but replace the vendor specific Mass Storage controller
driver with a "Generic" drive. Usually this is "Standard Dual PCI IDE
controller". Once the hardware swap is completed it's necessary to
reapply the correct Vendor driver. This is NOT a universal fix as it
has some less than desirable after effects. Also there can be issues if
the original platform is PATA ( Parallel ATA ) and the destination PC
uses the newer SATA ( Serial ATA ).

 

[Bill Simard]

So in Device Manager I should change the IDE ATA/ATAPI controller which now
says:

Intel(R) 82801DB Ultra ATA Storage Controller - 24CB

to a generic IDE controller ? Is that generic controller in Windows XP ?

Should I use the Update driver to change it ?

What if I delete it and then shut down just before I replace the MB.

Would it find the new hardware on boot up, or would it give me the STOP
error 0X00000 again ?

Thanks

Bill

 

[Bill Simard]

This is a second question I forgot to ask.

I'm just swapping Mother Boards, so the hard drive stays the same.

What are the less than desirable effects ?

Thanks

Bill

 

[R. McCarty]

If you do a repair or In-Place install, one part of that is rebuilding
the device table ( enum ). If you just switch Mass Storage drivers
and swap ( and the machine boots ) it will add all the new devices
but leave the old hardware in the tables, as "Phantom" entries. To
clean up you have to add an environment variable and set it's value
to 1 so that "Plug-&-Play" phantom devices are shown. Normally
even with the DevMgr Show Hidden Devices toggled XP will not
show the Plug-&-Play phantoms.

The effect varies depending on much the two motherboard chipset
components are different. Things like Northbridge/Southbridge sets
require different drivers but Via and Intel Chipset drivers are usually
composite drivers ( meaning they work for a wide range of chips ).
When you go to install chipset drivers they do a check and if they
aren't compatible/designed for your hardware will refuse to load.

 

[Bill Simard]

Where do I add this environment variable ?

My biggest problem has been that it won't boot into XP. It trys, but then
gets the BSOD Stop error because the IDE controllers are different.

If I can get it to not do that and actually get into windows then I should
be able to use safe mode to see those phantoms.

I've seen them before using safe mode in ME and was able to remove them, but
ME did not cause the system crash when swapping motherboards.

I could delete everyhting out of the device manager and then shut down, that
would eliminate most of the old values , wouldn't it ? before replacing the
MB .

Thanks again

Bill

 

[R. McCarty]

Q1 - System, Advanced, Environment Variables (Button) System -
Add ( Variable name DevMgr_Show_NonPresent_Devices )
Set it's value = 1

S2 - Safe Mode doesn't affect the ability to view/see "Phantoms"

Q2 - Not possible, certain deletions automatically trigger a "Reboot
Request", you can remove the PCI Bus driver that removes
everything but I wouldn't approach this in that way.

You might be better off to do a Repair install and SP3 and then the
handful of post-Sp3 updates to get the machine platform change done.

 

[3c273]

I don't mean to sound rude, but according to the timestamps of your posts,
you've been beating your head against the wall trying to bugger up an old
installation of XP for at least 5 hours. In that amount of time, you
could've installed XP and most, if not all, all of your programs. Then you'd
just need to let automatic updates do its thing and you'd be done. Sorry I
don't have a solution to your specific problem, but IMHO, I think you would
be better off with a clean install.
Louis

 

[Bill Simard]

That's what I did last time I needed to replace a MB and it took weeks to get
everything back. Doing a repair erases tons of files and reg data that makes
almost all the programs no longer work.

No to mention that the updates number in the 100's for XP itself, then you
need to put back Java, Macromedia Player, etc..

It is a very, very long task. I have done it before, and if I can find a
way to not have to do it again I would be real happy.

Thanks

Bill

 

[3c273]

If it takes weeks, you are doing it wrong. (Unless, of course, you are on
dialup.) SP1, SP3, plus a couple of updates that have been released since
SP3 are all you need for XP. At 10 minutes per install, you could have
installed 40 or 50 programs by now. I understand that sometimes we just need
to do things the hard way ;-) Good luck!
Louis