Liefr
asked on
Get around BSOD after xp sp3 install
A friends computer;
It's an HP Dual AMD 2.4 ghz, XP media center, sp2 with all patches, approx 300gb free space, lots of additional hard drives, two TV tuners and several printers and other assorted hardware.
So, we thought let's put sp3 on. The explanation said it was for media center... oops.
Install appeared to go fine but on reboot got blue screen with Stop: 0x0000007E (etc) but no english explanation.
I tried to get into safe mode but got the same bsod.
I have the Ultimate Boot Disk for Windows and ran recovery console and rebuilt the boot.ini to no effect.
I researched MSDN and found article 888372 which mentions this error code in relation to dual AMD machines built from a 'Sysprep' prepared on an Intel machine. Geez ...
It is a fairly simple fix... just change one key in the registry but I do not know how to get to the registry using UBD for windows. I cannot get into safe mode either.
Can someone give me a hint, please? I know it can be done because I can get to the C: drive.
If this registry change is not the right fix any help in another direction would be gratefully received.
TIA
Lief
It's an HP Dual AMD 2.4 ghz, XP media center, sp2 with all patches, approx 300gb free space, lots of additional hard drives, two TV tuners and several printers and other assorted hardware.
So, we thought let's put sp3 on. The explanation said it was for media center... oops.
Install appeared to go fine but on reboot got blue screen with Stop: 0x0000007E (etc) but no english explanation.
I tried to get into safe mode but got the same bsod.
I have the Ultimate Boot Disk for Windows and ran recovery console and rebuilt the boot.ini to no effect.
I researched MSDN and found article 888372 which mentions this error code in relation to dual AMD machines built from a 'Sysprep' prepared on an Intel machine. Geez ...
It is a fairly simple fix... just change one key in the registry but I do not know how to get to the registry using UBD for windows. I cannot get into safe mode either.
Can someone give me a hint, please? I know it can be done because I can get to the C: drive.
If this registry change is not the right fix any help in another direction would be gratefully received.
TIA
Lief
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Well, no results yet.
It is an HP computer so there is no media center CD.
I used the recovery console in UBCD4Win but the SC command is not available in c:\Windows so that did not work out.
Will a XP Pro windows disk work as well, or perhaps enter the recovery console from the boot menu?
I used the regedit tool in UBCD to look at the HKLM\system\controlset001\
I can make the key but do not know the format for the data value... does anyone know that?
I created the error again and the first parenthetical value in the stop message is the 0xC000005 value so there is a strong indication that this is the problem. We still do not get the english problem description.
I will make a CD from the .iso but I think that may not have helped in this case because the SP2 (from Microsoft Update) must have been created on an Intel machine using sysprep, so this problem would have happened anyway.
It is hard to imagine that Microsoft would have created this situation and there have not been loud noises about it. AMD is a popular choice.
In any case, thanks for your continued interest.
Lief
It is an HP computer so there is no media center CD.
I used the recovery console in UBCD4Win but the SC command is not available in c:\Windows so that did not work out.
Will a XP Pro windows disk work as well, or perhaps enter the recovery console from the boot menu?
I used the regedit tool in UBCD to look at the HKLM\system\controlset001\
I can make the key but do not know the format for the data value... does anyone know that?
I created the error again and the first parenthetical value in the stop message is the 0xC000005 value so there is a strong indication that this is the problem. We still do not get the english problem description.
I will make a CD from the .iso but I think that may not have helped in this case because the SP2 (from Microsoft Update) must have been created on an Intel machine using sysprep, so this problem would have happened anyway.
It is hard to imagine that Microsoft would have created this situation and there have not been loud noises about it. AMD is a popular choice.
In any case, thanks for your continued interest.
Lief
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
HP caused the problem by putting both files in their image . . somewhat understandable since they use both Intel and AMD processors . . but it's silly to blame Microsoft for something HP did . . .
ASKER
OK, the problem seems to be solved.
The answer was in the article r-k supplied. In that article was a link to a Microsoft MVP who has been dealing with this problem for himself and others.
Simpswr; the command you supplied is the correct command for use in safe mode. It will solve the problem if you can get to safe mode (which I could not).
The correct command for use in recovery console is 'disable intelppm' with out the quotes of course.
This command worked even though I got into recovery console through the UBCD vs a Windows install disk.
There is apparently danger of DRM issues but so far they have not surfaced for my friend. His machine is recording the scheduled show as if nothing had happened.
As far as who caused the problem, a little intelligence in the service pack update process, since this is a known problem since 2004 (or so), probably would have saved many people a lot of time and sweat.
I'm just sayin'...
Anyway, thanks and I will be sharing points to those who contributed.
The answer was in the article r-k supplied. In that article was a link to a Microsoft MVP who has been dealing with this problem for himself and others.
Simpswr; the command you supplied is the correct command for use in safe mode. It will solve the problem if you can get to safe mode (which I could not).
The correct command for use in recovery console is 'disable intelppm' with out the quotes of course.
This command worked even though I got into recovery console through the UBCD vs a Windows install disk.
There is apparently danger of DRM issues but so far they have not surfaced for my friend. His machine is recording the scheduled show as if nothing had happened.
As far as who caused the problem, a little intelligence in the service pack update process, since this is a known problem since 2004 (or so), probably would have saved many people a lot of time and sweat.
I'm just sayin'...
Anyway, thanks and I will be sharing points to those who contributed.
ASKER
It seems that this is a newish problem as my google search did not find much on it. Thanks again for the help.
"The correct command for use in recovery console is 'disable intelppm' "
Thanks for that usefull tidbit . .
Thanks for that usefull tidbit . .
ASKER
I will try this tomorrow and report back