Messages are too fast

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am trying to get recoverd from a bad SP1 upgrade by doing a repair frm my
Windows XP home Cd. I get to a certain place and there is a flash of a blue
screen and some writing on it but it is so fast I can't see what the message
is! Is there a way to get the computer to stop there so that I can read the
message?

I think that if I can get an error messge I might be able to have a place to
start looking for help.
Thanks
 
Frustrated said:
I am trying to get recoverd from a bad SP1 upgrade by doing a repair
frm my Windows XP home Cd. I get to a certain place and there is a
flash of a blue screen and some writing on it but it is so fast I
can't see what the message is! Is there a way to get the computer to
stop there so that I can read the message?

I think that if I can get an error messge I might be able to have a
place to start looking for help.
Thanks
Click to expand...


To get started troubleshooting the cause of your problems, we'll
need to learn what specific errors are occurring and being recorded.

To get the error message from the blue screen (a.k.a. the BSOD --
Blue Screen of Death), you'll need to turn off WinXP's automatic
reboot "feature:" Right-click My Computer > Properties > Advanced >
Startup and Recovery > Uncheck "Automatically restart." The next time
your PC crashes, you'll be left with a blue screen full of memory
addresses and other seeming gibberish. The top 2 or 3 lines of this
screen will contain information that can help solve your problem.
Carefully write down these lines and post the exact text back here.
Hopefully, one of us will be able to provide some insight.

Additionally, you should check your Event Logs to see if they can
shed any light on the matter, To do so, Right-click My Computer >
Manage > Event Viewer > System and Application. Record the specifics
of any red-flagged error messages and post the exact text back here.
Again, hopefully, one of us will be able to provide some insight.

--

Bruce Chambers

Help us help you:



You can have peace. Or you can have freedom. Don't ever count on
having
both at once. - RAH
 
Bruce Chambers said:
To get started troubleshooting the cause of your problems, we'll
need to learn what specific errors are occurring and being recorded.

To get the error message from the blue screen (a.k.a. the BSOD --
Blue Screen of Death), you'll need to turn off WinXP's automatic
reboot "feature:" Right-click My Computer > Properties > Advanced >
Startup and Recovery > Uncheck "Automatically restart." The next time
your PC crashes, you'll be left with a blue screen full of memory
addresses and other seeming gibberish. The top 2 or 3 lines of this
screen will contain information that can help solve your problem.
Carefully write down these lines and post the exact text back here.
Hopefully, one of us will be able to provide some insight.

Additionally, you should check your Event Logs to see if they can
shed any light on the matter, To do so, Right-click My Computer >
Manage > Event Viewer > System and Application. Record the specifics
of any red-flagged error messages and post the exact text back here.
Again, hopefully, one of us will be able to provide some insight.

--

Bruce Chambers

Help us help you:



You can have peace. Or you can have freedom. Don't ever count on
having
both at once. - RAH
Click to expand...
 
Bruce Chambers said:
To get started troubleshooting the cause of your problems, we'll
need to learn what specific errors are occurring and being recorded.

To get the error message from the blue screen (a.k.a. the BSOD --
Blue Screen of Death), you'll need to turn off WinXP's automatic
reboot "feature:" Right-click My Computer > Properties > Advanced >
Startup and Recovery > Uncheck "Automatically restart." The next time
your PC crashes, you'll be left with a blue screen full of memory
addresses and other seeming gibberish. The top 2 or 3 lines of this
screen will contain information that can help solve your problem.
Carefully write down these lines and post the exact text back here.
Hopefully, one of us will be able to provide some insight.

Additionally, you should check your Event Logs to see if they can
shed any light on the matter, To do so, Right-click My Computer >
Manage > Event Viewer > System and Application. Record the specifics
of any red-flagged error messages and post the exact text back here.
Again, hopefully, one of us will be able to provide some insight.

--

Bruce Chambers

Help us help you:



You can have peace. Or you can have freedom. Don't ever count on
having
both at once. - RAH



The problem is that I can't get into Windows at all. The windows start up svreen comes up then then after about 30 seconds a Blue screen flashes then the computer rebotes. If I leave it alone the patern repeats itself endlessly. I've tried to take the SP out manually and am not able too. I'm trying to reinstall Windows XP home but it will simply reboot when it gets to whatever is blocking the setup.
Click to expand...
 
Can you not boot into Safe Mode?

--

Bruce Chambers

Help us help you:



You can have peace. Or you can have freedom. Don't ever count on
having
both at once. - RAH
 
No, can't get into safe mode, the last line that I can see ends with MUP.sys
also I'e tried "Last know configuration" and Safe mode with command prompt.
All woth the same effect. Flash a blue screen (split second) then reboot.

Thank you for your help
 
Hi!

Have now been facing the same type problem. So far not resolving it, but
will
go on checking ...

The problem is not on mup.sys, even being the last loaded one, but on some
driver loaded in a second or two after that ... Hard to say how to
find/recognize the real problem point, maybe backing with some update, or
detaching some components and rebooting, or checking possible Stop Error
details, or doing some other troubleshooting etc., and as a last hope action
try to Repair install the Windows with a full licence Retail CD.


Best regards,

Pete V.
 
Hi!

Sorry, forgot to mention, add to boot.ini WinXP line the parameter
/crashdebug, it will let you to check the error message for a few seconds.


Best regards,

Pete V.
 
Back
Top