I apologize if this is the wrong place for this topic. I shut down my
computer during a windows update and now every time I restart I get a
blue screen message that lasts for about a second and then my computer
restarts itself again. It does this every time. I'm operating in safe
mode right now. I'm sorry if this sounds vague, I'm not very good with
computer terms and stuff, but I'll give more details if I need to. Thank
you in advance.


--
Tfile

While in safe mode, try a system restore to an date prior to the update.


"Tfile" wrote in message
...

I apologize if this is the wrong place for this topic. I shut down my
computer during a windows update and now every time I restart I get a
blue screen message that lasts for about a second and then my computer
restarts itself again. It does this every time. I'm operating in safe
mode right now. I'm sorry if this sounds vague, I'm not very good with
computer terms and stuff, but I'll give more details if I need to. Thank
you in advance.


--
Tfile

Blue screens are usually driver related. As you can't get into normal mode I
suggest you first try safe mode and disable the auto restart to read the
blue screen. See this link from my website:
http://www.winuser.co.uk/windows_vis... essages.html

Alternatively, as you think it may have been the Windows Update, you could
try a system restore back to a time prior to when the update was installed
to see if everything goes back to normal. Can you recall what the update was
for?

--

--
John Barnett MVP
Windows XP Associate Expert
Windows Desktop Experience

Web: http://www.winuser.co.uk
Web: http://xphelpandsupport.mvps.org
Web: http://vistasupport.mvps.org
Web: http://www.silversurfer-guide.com

The information in this mail/post is supplied "as is". No warranty of any
kind, either expressed or implied, is made in relation to the accuracy,
reliability or content of this mail/post. The Author shall not be liable for
any direct, indirect, incidental or consequential damages arising out of the
use of, or inability to use, information or opinions expressed in this
mail/post..


"Tfile" wrote in message
...

I apologize if this is the wrong place for this topic. I shut down my
computer during a windows update and now every time I restart I get a
blue screen message that lasts for about a second and then my computer
restarts itself again. It does this every time. I'm operating in safe
mode right now. I'm sorry if this sounds vague, I'm not very good with
computer terms and stuff, but I'll give more details if I need to. Thank
you in advance.


--
Tfile

Thank you so much for the replies, Robert and John. I did system restore
through startup recovery and now I am able to log back on windows. I
still don't know what the cause was, but after I logged on, windows
solution gave me a message telling me my antivirus or firewall program
is what caused the Blue screen error.

Anyways, thank you so much for your help!


--
Tfile

I'm glad you got things sorted. However, now you are up and running again it
would be beneficial to follow my instructions and disable the automatic
restart to read blue screen messages. At least if you have a similar problem
you will be able to see the blue screen details and give the relevant
information if it is asked for.

--

--
John Barnett MVP
Windows XP Associate Expert
Windows Desktop Experience

Web: http://www.winuser.co.uk
Web: http://xphelpandsupport.mvps.org
Web: http://vistasupport.mvps.org
Web: http://www.silversurfer-guide.com

The information in this mail/post is supplied "as is". No warranty of any
kind, either expressed or implied, is made in relation to the accuracy,
reliability or content of this mail/post. The Author shall not be liable for
any direct, indirect, incidental or consequential damages arising out of the
use of, or inability to use, information or opinions expressed in this
mail/post..


"Tfile" wrote in message
...

Thank you so much for the replies, Robert and John. I did system restore
through startup recovery and now I am able to log back on windows. I
still don't know what the cause was, but after I logged on, windows
solution gave me a message telling me my antivirus or firewall program
is what caused the Blue screen error.

Anyways, thank you so much for your help!


--
Tfile

I did actually follow your advice and disabled the automatic restart and
copied the blue screen message before I got it working again. I'll go
ahead and post what it said just in case it might reveal something:
--------

A problem has been detected and Windows has been shut down to prevent
damage to your computer.

If this is the first time you've seen this Stop error screen, restart
your computer. If this screen appears again follow these steps:

Check to be sure you have adequate disk space. If a driver is
identified in the Stop message, disable the driver or check with the
manufacturer for driver updates. Try changing video adapters.

Check with your hardware vendor for any BIOS updates. Disable BIOS
memory options such as caching or shadowing. If you need to use Safe
Mode to remove or disable components, restart your computer, press F8 to
Advanced Startup Options, and then select Safe Mode.

Technical information:
*** STOP: 0X0000008 (0XC0000005, 0X8D385E67, 0X9B6A2018, 0X00000000)

Collecting data for crash dump . . .
Initializing disk for crash dump . . .
Beginning dump of physical memory,
Dumping physical memory to disk: 100
Physical memory dump complete.
Contact your system admin or technical support group for further
assistance.
---------

Again, thanks for the help.


--
Tfile

On Apr 18, 11:42*am, Tfile wrote:
Technical information:
*** STOP: 0X0000008 (0XC0000005, 0X8D385E67, 0X9B6A2018, 0X00000000)

Code did not execute properly when an exception should have been
processed. Why? We don't know yet. For example, do the same four
parameters appear inside parentheses? Then it is the same software
operating in the same hardware memory location. Which one is
defective? Hardware or software? Welcome to a fundamental concept of
diagnostics. Break the problem down into parts. Locate which half
has the problem.

One common solution is to run Memtst86 on memory both at room
temperature and also when memory is heated to its preferred
temperature - heated with a hairdryer on highest heat setting. That
would immediately identify a specific problem.

Or swap memory sticks so that a repeatable problem executes inside a
different memory chip. This means the problem must first be made
repeatable and does not identify which memory stick is defective.

Of course, if the problem is software, well, which driver? Which
software? Something too subjective to respond to suggested the anti-
virus software. What did the system (event) logs report - especially
the numbers and software file names?