Seamus67
asked on
XP Pro logon loop at welcome screen
Here's my scenario in brief:
My wife appears to have installed some sort of worm or malware from an email attachment from one of her cousins. I never had a chance to see what the attachment was, but the following day, the laptop I let her use suddenly went to the blue screen, and attempted to recover. I didn't get to see everything, but what I saw suggested dread.
After the system (sorry: XP Pro w/ SP2) attempted to recover, it went back to the blue screen with:
STOP: c000021a {Fatal System Error}
The Session Manager Initialization system process terminated unexpectedly with a
status of 0xc0000034 (0x00000000 0x00000000).
The system has been shutdown.
I could not reboot into safe mode not could I use could I use safe mode to go back to a point where things were last known to work (got the same error on both occasions).
So, I started researching. I found the following articles and attempted the following things, and based on what I've read hear, I'm back to the first thing I had tried:
http://www.digitalwebcast.com/articles/viewarticle.jsp?id=8658-1
(just a wordy version of: http://support.microsoft.com/?kbid=307545)
Recovery Console :
md tmp
copy C:\windows\system32\config
copy C:\windows\system32\config
copy C:\windows\system32\config
copy C:\windows\system32\config
copy C:\windows\system32\config
delete C:\windows\system32\config
delete C:\windows\system32\config
delete C:\windows\system32\config
delete C:\windows\system32\config
delete C:\windows\system32\config
copy C:\windows\repair\system C:\windows\system32\config
copy C:\windows\repair\software
copy C:\windows\repair\sam C:\windows\system32\config
copy C:\windows\repair\security
copy C:\windows\repair\default C:\windows\system32\config
-- No result from this.
http://www.michaelstevenstech.com/XPrepairinstall.htm#Warning1
Windows XP Recovery -- got to registration, but couldn't connect to the
Internet. Then entered logon/logoff loop.
http://www.winxptutor.com/wsaremove.htm
In Recovery Console, tried:
CD SYSTEM32
COPY USERINIT.EXE WSAUPDATER.EXE
-- File not found.
https://www.experts-exchange.com/questions/21241365/XP-Pro-logon-loop-at-welcome-screen.html
Tried booting to safe mode -- Logon loop again.
Tried copying userinit.exe from a working XP Pro system to the laptop.
Couldn't access CD drive.
So, at the end of all of this, I seem to at least be able to boot, but logon goes into this loop, and nothing I've found so far seems to be able to get me out of that so that I can log back on to see if all of my applications and data are still there. Not a huge loss if they aren't (set's me back maybe a week), but not being able to log on at all is an opstacle I'd rather over come over having to reinstall XP Pro from scratch and wipe everthing out.
My wife appears to have installed some sort of worm or malware from an email attachment from one of her cousins. I never had a chance to see what the attachment was, but the following day, the laptop I let her use suddenly went to the blue screen, and attempted to recover. I didn't get to see everything, but what I saw suggested dread.
After the system (sorry: XP Pro w/ SP2) attempted to recover, it went back to the blue screen with:
STOP: c000021a {Fatal System Error}
The Session Manager Initialization system process terminated unexpectedly with a
status of 0xc0000034 (0x00000000 0x00000000).
The system has been shutdown.
I could not reboot into safe mode not could I use could I use safe mode to go back to a point where things were last known to work (got the same error on both occasions).
So, I started researching. I found the following articles and attempted the following things, and based on what I've read hear, I'm back to the first thing I had tried:
http://www.digitalwebcast.com/articles/viewarticle.jsp?id=8658-1
(just a wordy version of: http://support.microsoft.com/?kbid=307545)
Recovery Console :
md tmp
copy C:\windows\system32\config
copy C:\windows\system32\config
copy C:\windows\system32\config
copy C:\windows\system32\config
copy C:\windows\system32\config
delete C:\windows\system32\config
delete C:\windows\system32\config
delete C:\windows\system32\config
delete C:\windows\system32\config
delete C:\windows\system32\config
copy C:\windows\repair\system C:\windows\system32\config
copy C:\windows\repair\software
copy C:\windows\repair\sam C:\windows\system32\config
copy C:\windows\repair\security
copy C:\windows\repair\default C:\windows\system32\config
-- No result from this.
http://www.michaelstevenstech.com/XPrepairinstall.htm#Warning1
Windows XP Recovery -- got to registration, but couldn't connect to the
Internet. Then entered logon/logoff loop.
http://www.winxptutor.com/wsaremove.htm
In Recovery Console, tried:
CD SYSTEM32
COPY USERINIT.EXE WSAUPDATER.EXE
-- File not found.
https://www.experts-exchange.com/questions/21241365/XP-Pro-logon-loop-at-welcome-screen.html
Tried booting to safe mode -- Logon loop again.
Tried copying userinit.exe from a working XP Pro system to the laptop.
Couldn't access CD drive.
So, at the end of all of this, I seem to at least be able to boot, but logon goes into this loop, and nothing I've found so far seems to be able to get me out of that so that I can log back on to see if all of my applications and data are still there. Not a huge loss if they aren't (set's me back maybe a week), but not being able to log on at all is an opstacle I'd rather over come over having to reinstall XP Pro from scratch and wipe everthing out.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
NT Status code 0xc0000034 means OBJECT_NAME_NOT_FOUND
According to microsoft webpage http://support.microsoft.com/kb/q156669
Attach the following files at any webspace. I will study your log and dumps.
C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\drwtsn32.log
C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dmp
According to microsoft webpage http://support.microsoft.com/kb/q156669
Attach the following files at any webspace. I will study your log and dumps.
C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\drwtsn32.log
C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dmp
ASKER
Regarding Status code 0xc0000034, I had already resolved that in my description above. That was the initial issue. The issue now is the logon/logoff loop.
I don't have time to try slaving the laptop's hdd, so I finally broke down and took it in to a repair shop.
Thanks anyways.
I don't have time to try slaving the laptop's hdd, so I finally broke down and took it in to a repair shop.
Thanks anyways.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi Merete,
I have to say you've had the only helpful input here.
Had I more time, I'd have loved to get "geeky" on making the hdd in my laptop a slave to another computer as you suggested. I just didn't have the time to try as this is "Cyber Monday" and our clients are slamming us with requests & questions -- that is, I need to be spending my time running my business rather than learning cool new tricks.
I expect your recommended solution would have worked for me if I had had the time to try it.
I did try accessing last known goof congfig via recovery mode -- not safe mode -- but that didn't work. I tried that before posting here.
Anyway, I'm going to award you points as at least you were helpful. Not your fault I didn't have time to try it.
Thanks!
I have to say you've had the only helpful input here.
Had I more time, I'd have loved to get "geeky" on making the hdd in my laptop a slave to another computer as you suggested. I just didn't have the time to try as this is "Cyber Monday" and our clients are slamming us with requests & questions -- that is, I need to be spending my time running my business rather than learning cool new tricks.
I expect your recommended solution would have worked for me if I had had the time to try it.
I did try accessing last known goof congfig via recovery mode -- not safe mode -- but that didn't work. I tried that before posting here.
Anyway, I'm going to award you points as at least you were helpful. Not your fault I didn't have time to try it.
Thanks!
awe thank you Seamus67 at least you have one of the best resources on the web to get geeky lol.
Laptops are very time consuming to repair and often times repair shops love to format instead. Quick fixes.
You could even consider getting an external enclosure snap a good hdd into it plug it into the Laptop firewire or usb slot and back up your contents to it often or simply use it as a slave perminently.
Best wishes to you hope they fix it good and get the Laptop back on track asap.
Merete
Laptops are very time consuming to repair and often times repair shops love to format instead. Quick fixes.
You could even consider getting an external enclosure snap a good hdd into it plug it into the Laptop firewire or usb slot and back up your contents to it often or simply use it as a slave perminently.
Best wishes to you hope they fix it good and get the Laptop back on track asap.
Merete
ASKER
Just for the record, and in case it helps anyone else: It turns out that it was not a worm after all. It was bad sectors on the hdd. So, I'm looking at a new hdd & OS installation.
And hdd always go just when you least expect it.
Seamus67 did you notice the performance of the hdd was getting irratic just a point of reference so that if it happens again you can associate this experience.
Oh well bad luck but hopefully they can save off your stuff.
Best Wishes to you and glad to be of assistance.
Merete
Seamus67 did you notice the performance of the hdd was getting irratic just a point of reference so that if it happens again you can associate this experience.
Oh well bad luck but hopefully they can save off your stuff.
Best Wishes to you and glad to be of assistance.
Merete
ASKER
Hi Merete,
Thanks, you have been helpful.
This happened with absolutely no warning, nothing erratic at all. Everything was running perfectly until the sudden Blue Screen of Death appeared.
I had assumed it was a worm because my wife attempted to open an attachement that did something odd (I wasn't there, so I wasn't able to get any decent data on that). The BSOD did occur the day following, so it was obviously my mistake to have comflated the two incedences.
The only other thing I can think of that might be relevant is that I did have the laptop set to hybernate when I close it. I have noticed that hybernation can create some odd behavior when opening again from hybernation.
Warm regards,
-- Seamus67
Thanks, you have been helpful.
This happened with absolutely no warning, nothing erratic at all. Everything was running perfectly until the sudden Blue Screen of Death appeared.
I had assumed it was a worm because my wife attempted to open an attachement that did something odd (I wasn't there, so I wasn't able to get any decent data on that). The BSOD did occur the day following, so it was obviously my mistake to have comflated the two incedences.
The only other thing I can think of that might be relevant is that I did have the laptop set to hybernate when I close it. I have noticed that hybernation can create some odd behavior when opening again from hybernation.
Warm regards,
-- Seamus67
http://support.microsoft.com/kb/q156669/