New Mobo = BSOD in XP startup

[Antikythira]

(Sorry my english) My old mobo was with VIA 266 chipset and new is with SIS 745. BSOD come when it load old VIA Drivers. I havent installation CD now here, but i have installation files in HD C:/My documents/Install Files.

1. Is it possible in repair console mode go to that directory and start installation from there?

2. If not, what I can do in console mode? Can I modify driver loading list, where is it and what file name?

 

[GonzoDaGr8]

I havent installation CD now here,

You don't have WinXP CD, or don't have driver install CD?

Can you get into safe mode and try un-installing drivers, devices from there?

Good read on this subject in the FAQ's

 

[crisp82]

Can you hook your HD up to another computer and remove the drivers that way?

 

[Antikythira]

I havent WinXP CD, but install files are in HD. Safe mode or nothing else startup option dont work, only console mode works (6 diskettes).

Im now in win98 system (500 MB HD), and i cant got to 80 GB NTFS from here.

 

[crisp82]

Try running Partition Magic to check for errors or bad sectors. Can you hook it up to an NTFS system?

 

[Antikythira]

I try tell again.... main broblem is that windows load in startup old VIA drivers from C:/windows/system 32/Drivers/. How i can disable them in repair console mode?

 

[Antikythira]

I just delete old via-dirvers, but then safe mode loading stucks in mup.sys. I delete it and now blue screen comes after loading vmodem.sys.... i must look now many drivers i must delete...this is very slowly operation.

 

[crisp82]

Try putting new Via drivers in C:\Windows\System folder. then reboot.

 

[toant103]

it's normal that when you install a new MOBO, you have to do a clean install.

Unless you have 9x, then windows will detect it and it should be fine.

Not with NT kernel

 

[Soapm]

Originally posted by: GonzoDaGr8

I havent installation CD now here,

You don't have WinXP CD, or don't have driver install CD?

Can you get into safe mode and try un-installing drivers, devices from there?

Good read on this subject in the FAQ's

Thanks for this information. I am going to change my mother board and plan to give some of this a try...

 

[igiveup]

mup.sys is what XP usually stops on when it goes through the verbose logging mode. Deleting that file was not a good thing to do. Looks like your only option is to borrow a CD and do a repair install. If that doesn't work, sry.

 

[SearchMaster]

I had the same problem (stopping at MUP.sys) the first time I did a mobo swap with Win2K.

From the exact guide above, I used this gem:

- Reportedly, Windows 2000 and XP can be tricked into doing this stuff for you. The procedure is this: Shut down, install your new hardware, power on, and enter your system BIOS. Make sure your First Boot Device is set to CDROM. Insert the Windows 2000/XP setup CD and boot from this disk. (You may have to "press a key to boot from CD" as the prompt says.) Skip the initial prompt asking to repair your existing installation. Then proceed to the screen where you select a partition, and choose your existing Windows partition. Setup will detect your existing installation and ask you to repair. Say yes. When Windows Setup is complete, you should have a fully working installation with all your old user and application profiles. Everything should be intact, except your hardware and driver settings, leaving it fresh for your new motherboard.

It worked beautifully.

Caveat: I have used this trick twice. The ONLY problem I have had since the swaps (and it happened on both swaps) is that Outlook first complains about not being able to connect to the Exchange server. The trick then is to reinstall TCP/IP (all other network connectivity seems fine; it's only Outlook that complains). Then you may get Outlook popups complaining that it couldn't synchronize with the free/busy list. I haven't gotten that one solved, but it hasn't been much of a priority either. SOOOOOO, if you don't use Outlook, the trick above should work fine. Otherwise you may have to do a little more work.