Fatal stop on boot (occasionally) 0x00000402

[stduc]

I was just about to return this friends system I have been working on (Virus & network problems) When I thought I would just check it boots up this morning, before unplugging it.

I got a BSOD

Stop: c000021a {Fatal System Error} The windows Logon process system process terminated unexpectedly with a status of 0x00000402 (0x00000000 0x00000000)
The system has been shut down.

Rebooted fine when I hit the reset key.

No dump file was created and nothing in the event log though

I powered off & it did the same again.

I googled - but got nowhere.

I'm confused. What's up with this machine now?

Previous threads on this PC

Pathetically slow network

http://www.tek-tips.com/viewthread.cfm?qid=1197410

Hyperthreading/Twin CPU question

http://www.tek-tips.com/viewthread.cfm?qid=1197876

 

[G0AOZ]

Make doubly sure you've not still got an infection lurking in there - maybe do an on-line scan. Panda has a good one here:-

http://www.pandasoftware.com/products/activescan.htm

Have you run a system file and surface scan?

Does the same problem occur in Safe mode?

ROGER - G0AOZ.

 

[stduc]

Not tried safe mode.

Its a fresh install now. Due to trying to figure out what was wrong with the network. I am 100% sure the machine is clean as its behind a firewall and only been on the net for updates.

Apparantly its always done this! I just checked with the owner.

I wish people would tell you all the faults at the beginning!!!!!

It never seems to do it on a reset. Just a cold boot - & I mean cold. So I suspect hardware that needs to warm up. Is that possible?

 

[Zych]

I would use memcheck86 and check the memory. If you can boot and run this for a couple of iterations it is probably software, but since you said it was a fresh install I would suspect the memory.

I have a client who had another tech check their system. He said do to the Windows errors it needed to be re-done. After returning it, minus all of their accounting, it started to display the same problems. I took it and ran memcheck86 and found that the second memory module was bad. Replaced, checked again and everything worked fine. This little program can save you a lot of time debugging windows errors if is the memory.

- Zych

 

[BadBigBen]

Was GoBack ever installed on that system? it may not been totally cleaned from the HD, BOOTSECTOR to be more to the point...

so I would try a FIXMBR on the HD....

if that does not work then perhaps it could also be a problem with the PSU or the MEM as ZYCH pointed out...

Hope this helps...

Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."

 

[BadBigBen]

Ooops almost forgot this one (sorry):

Also see:

http://support.microsoft.com/?kbid=318666&sd=RMVP

Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."