Two XP installs (c: and d:) and d: boots but c: BSODs

Toggle sidebar Toggle sidebar
P

peterh337

Honorable
May 5, 2016
155
0
10,690
This should be really simple to solve i.e. compare the \windows\system32\driver directories.

Does anyone else have any ideas on where to look?

I can run a utility to compare the two \windows directories but I don't want to break it so that the c: drive gets corrupted, etc.

Should I start by copying d:\windows\system32\driver to c:\windows\system32\driver ?

I don't want to copy over the registry (\windows\system32\config) because that stuff is bound to contain drive letters etc.

AIUI, winXP loads hardware drivers dynamically during boot.

I should add that the booting installation dodn't need any special drivers. It just installed straight off a slipstreamed SP3 DVD. No F6 business, etc.

Many thanks for any tips.
 
Solution
SkyNetRising
As it was noted in that other topic - you have to reinstall OS after changing motherboard to different chipset.
You changed from P35 chipset to X58.

You can get full BSOD picture, if you disable automatic restart. Just press F8 before windows starts booting and choose appropriate menu option.

Also you can try booting into safe mode, delete drivers one by one and force windows to re-detect them.
If safe mode doesn't work, you can try repair option when booting from windows install media.

Note - it is really bad idea to put multiple OS-es on the same partition. Try to avoid doing that.
Sort by date Sort by votes
P

peterh337

Honorable
May 5, 2016
155
0
10,690
The two partitions have very different data however.

The c: one has loads of apps installed (maybe 100) and some of them are old and highly valuable ones, which is why I would like to get that one to boot.

The d: one is a throw-away one, with minimal apps etc. (It will be replaced with a win7-64 installation)

Drive letters are all over the registry...

Cloning d:\windows to c:\windows will probably trash my c: app config.
Cloning d:\docs and settings to c:\docs and settings will definitely trash everything on c:
 
Upvote 0 Downvote
P

peterh337

Honorable
May 5, 2016
155
0
10,690
The BSOD happens too fast - a frame out of a 50fps video is here
http://www.tomshardware.co.uk/answers/id-3076506/asus-p5k-gigabyte-ex58-ud5-cloned-boot.html

I suspect it is a HD driver issue but maybe not.

What is interesting is that the working XP installation boots fine after installing from a stock XP DVD (SP3 + all updates). AND the non-booting installation was also installed from the exact same DVD, in 2014, but on a different motherboard (P5K-E).

So, whatever the difference is, is taken care of by XP+SP3+updates. No F6 business to install special SATA drivers etc.

In another context, I did change some drive letters in MountedDevices but just got a looping reboot so had to reinstall the whole OS.
 
Upvote 0 Downvote
P

peterh337

Honorable
May 5, 2016
155
0
10,690
I have compared system32\drivers of the booting and non-booting installations.

The booting one has the following four *extra* files:

usbccid.sys
imagedrv.sys
imagesrv.sys
wmiacpi.sys

and sure enough the last one is all over google, for this sort of thing!
 
Upvote 0 Downvote
SkyNetRising

SkyNetRising

Titan
Jan 4, 2016
29,823
3,846
111,640
As it was noted in that other topic - you have to reinstall OS after changing motherboard to different chipset.
You changed from P35 chipset to X58.

You can get full BSOD picture, if you disable automatic restart. Just press F8 before windows starts booting and choose appropriate menu option.

Also you can try booting into safe mode, delete drivers one by one and force windows to re-detect them.
If safe mode doesn't work, you can try repair option when booting from windows install media.

Note - it is really bad idea to put multiple OS-es on the same partition. Try to avoid doing that.
 
Upvote 0 Downvote
Solution
P

peterh337

Honorable
May 5, 2016
155
0
10,690
"you have to reinstall OS after changing motherboard to different chipset."

Not true - I have done that dozens of times. So long as the new MB boots up (usually it does) then you can load the new MB drivers.

However it has to be said that most of the time in the past I moved across a HD controller (RAID etc) so that was one less variable. This time, I am not using a separate HD controller. I just configured the MB SATA in the BIOS for the lowest possible level. (ASUS and Gigabyte call them different things).

"You can get full BSOD picture, if you disable automatic restart. Just press F8 before windows starts booting and choose appropriate menu option."

Can one reconfig the BSOD auto-reboot from there? I haven't seen that option.

"you can try repair option when booting from windows install media."

I tried that but there were 2 problems:

1) The only XP install CD I have which has the Repair option is only SP2. That is the widely sold one. I am not sure if a fully updated (SP3+updates) was ever sold, though obviously they exist. So if that worked, you still need to find a way to install SP3 and all the subsequent MS updates.

2) The SP2 install CD doesn't produce an XP installation which boots up on the EX58 MB, anyway. I don't know why; it crashes and hangs right away, with some video corruption. I guess XP+SP2 doesn't support the EX58 MB and I don't know how one could introduce new drivers. The F6 option is for HD drivers, AFAIK. OTOH it could be the GTX750 video card which is crashing it...

" it is really bad idea to put multiple OS-es on the same partition"

I am not doing that. I have one on c: (that's the non-booting one) and one on d: (the newly installed booting one). I have built dozens of machines like that. The idea is that if c: gets corrupted or becomes non-bootable you can still usually boot into the d: one and get at the data. In fact a lot of people use win2k for this "second boot" purpose because it doesn't require validation ;)
 
Upvote 0 Downvote
SkyNetRising

SkyNetRising

Titan
Jan 4, 2016
29,823
3,846
111,640
Check your boot.ini file. There are 2 OS-es on same partition:

  • \WINDOWS
    \WINDOWS.0
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS.0
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS.0="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP drive c: (default)" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows XP drive d: (bare - VGA output?)" /noexecute=optin /fastdetect
 
Upvote 0 Downvote
P

peterh337

Honorable
May 5, 2016
155
0
10,690
Ah, apologies!

partition(1)\WINDOWS was the original d: installation and, like the c: one, it doesn't boot.

partition(1)\WINDOWS.0 is the fresh d: installation which does boot.

This .0 .1 etc is what happens if you install winXP (maybe later versions too?) onto a partition which has already got windows installed on it. The previous installation becomes probably useless (because it's stuff in Documents and Settings got overwritten by the next one, etc).

The "neat" solution to this would be to first clean up

d:\documents and settings
d:\program files
d:\windows

all 3 of which contain just the bare minimum which came with that "emergency purpose" installation.

The problem is that 2 or 3 of the above cannot be deleted, due to locked files ***even if the deletion is done from an OS which is nothing to do with d: (e.g. one which booted from c: )***

So I use an Ubuntu boot CD which supports NTFS and doesn't care and is great for cleaning stuff up.

Eventually d: will have win7-64 on it so all the
\windows
\windows.0
\program files
\documents and settings
will be cleaned up before I put that on.


 
Upvote 0 Downvote
P

peterh337

Honorable
May 5, 2016
155
0
10,690
Unfortunately copying over the drivers directory from the booting to the non-booting didn't do it...

The c: installation still BSODs.

In safe mode, it runs through all the drivers up to mup.sys and then it BSODs when loading sptd.sys. So I deleted that driver ( a Daemon Tools item ) from system32\drivers.

Still BSODs...

In safe mode, the BSOD takes place while it is displaying the previous driver, mup.sys.

This issue is all over the internet but no obvious solutions. I believe it is not mup.sys because that one has already been loaded if it is displayed...?

Unfortunately sptd.sys keeps coming back. There is a backup copy stored somewhere... I found a utility for removing it and now it is gone.

But there is still a BSOD - a few seconds after mup.sys.

I need to find out which driver is getting loaded after mup.sys... it turns out this is all over the internet too e.g.
http://www.aitechsolutions.net/mupdotsysXPhang.html

And this issue looks really complicated.

Except that I have a *booting* installation on d: so there should be an easier way.

I am out of ideas...
 
Upvote 0 Downvote
P

peterh337

Honorable
May 5, 2016
155
0
10,690
Just an update in case anyone finds this thread:

I abandoned this problem and installed a fresh win7-64 on c: and a fresh winXP-32 on d:

I did that because (a) I wanted win7 on c: (and recovering the cloned drive would have placed XP on c: ) and (b) I judged the mup.sys bsod issue to be probably intractable.

I ended up with two apps which simply would not run in win7 and especially not 64-bit win7 (Orcad SDT/386 and Protel PCB 2.8 - both very high value apps from the 1990s) and tried two different winXP VMs for them: Microsoft Virtual PC and VMware. Protel worked great in both. Orcad worked fully only in VMware (cursor / mouse driver issues).
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom