Occassional BSOD on boot up

[Guest]

I'm occassionally get a BSOD during boot up, it's infrequent but the "Windows
has been stopped to prevent damage" message seems a bit alarming.

The code given is STOP 0X000007E followed by a list of addresses in brackets
beginning 0xC00000005. I quick Google reveals that this is a fairly common
occurance in the Windows XP world but gives numberous possible causes from
virus checker software (I have Kaspersky) to faulty hardware and dodgy
drivers. No drivers or processes are indicated on my BSOD.

Given that it's a rare occurance and to date has only happened during the
boot up process (my XP installation seems sound when up and running) is there
anything to be overly worried about? What sort of 'damage' is Microsoft
trying to prevent?

My Windows XP installation is XP Home SP2 and fully updated via Windows
Update.

 

[Guest]

You may want to enable bootlogging and then wait for it to blue screen again
- this should point out about where it's "glitching" at. The C0000005
usually means an error in accessing the memory.

You can download a free memory tester from here:
http://oca.microsoft.com/en/windiag.asp (Not that I suspect the memory - but
it's a good idea to check)

- John

 

[Guest]

Thank you, I'll get the memory tester a go. I'm not sure it's the memory
either as I've yet to have a BSOD once the machine is up and running (and
only occassionally during boot up) but it would be good to double check.

Thank you again.

Paul

 

[Rock]

I'm occassionally get a BSOD during boot up, it's infrequent but the
"Windows
has been stopped to prevent damage" message seems a bit alarming.

The code given is STOP 0X000007E followed by a list of addresses in
brackets
beginning 0xC00000005. I quick Google reveals that this is a fairly common
occurance in the Windows XP world but gives numberous possible causes from
virus checker software (I have Kaspersky) to faulty hardware and dodgy
drivers. No drivers or processes are indicated on my BSOD.

Given that it's a rare occurance and to date has only happened during the
boot up process (my XP installation seems sound when up and running) is
there
anything to be overly worried about? What sort of 'damage' is Microsoft
trying to prevent?

My Windows XP installation is XP Home SP2 and fully updated via Windows
Update.

Start your troubleshooting here.
http://aumha.org/win5/kbestop.htm
0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED