XP crashes and re-starts

[trevormidgley]

Hi - I don't know if anyone can help me.

Over the past few weeks, my computer has occasionally shut down, then
re-started, warning me that it has just recovered from a serious fault.

It's just done it again this morning, and I've taken the following
from the Error Properties in the System Event viewer.

So far as I can establish, I have no virus or spyware on the machine,
and the Device Manager is giving me a clean bill of health.

Any advice appreciated!!

Many thanks -

TM

Source: System Error
Category: (102)
Event ID: 1003

Description:

Error code 00000077, parameter1 00000001, parameter2 13237303,
parameter3 00000000, parameter4 f3900c4c.

Data ("Words")

0000: 74737953 45206d65 726f7272 72452020
0010: 20726f72 65646f63 30303020 37303030
0020: 50202037 6d617261 72657465 30302073
0030: 30303030 202c3130 33323331 33303337
0040: 3030202c 30303030 202c3030 30393366
0050: 63346330

 

[Detlev Dreyer]

Over the past few weeks, my computer has occasionally shut down, then
re-started, warning me that it has just recovered from a serious fault.

It's just done it again this morning, and I've taken the following
from the Error Properties in the System Event viewer.

Why don't you disable the automatic restart on system failures in order
to obtain an error message. I've seen cases of unexpected reboots (hard-
ware problems) where the system did not have enough time to create an
entry in the System Event viewer. Therefore, you cannot always be sure
that the latest entry will be related to your problem in particular.

"Windows XP restarts unexpectedly or restarts when you shut down the
computer" http://support.microsoft.com/?kbid=320299

 

[trevormidgley]

Done that - thanks!

Let's see what comes.

Do I assume that the Error Details above aren't connected to the
crash/re-start problem?


TM

 

[Detlev Dreyer]

Done that - thanks!

Let's see what comes.

Do I assume that the Error Details above aren't connected to the
crash/re-start problem?

Maybe yes, maybe no. Anyway, the expected error message will be more
detailled in most cases - if the restart was caused by a specific
device, you'd find the driver's name in that message for instance.
In the worst case, you'll get a similar message as the event viewer
has already listed. Good luck!

 

[trevormidgley]

I posted this an hour or so back, but it hasn't appeared!! Once more
into the breach...

An interesting little pattern; Event ID 5036 (The Remote Access
Connection Manager service entered the running state) appears 20
seconds before each crash/re-start cycle.

Significant?

 

[Detlev Dreyer]

An interesting little pattern; Event ID 5036 (The Remote Access
Connection Manager service entered the running state) appears 20
seconds before each crash/re-start cycle.

Significant?

Nope. That Event ID *may* be related to the "Microsoft Application
Center" if installed. See also

"INFO: Event ID: 5036 Replication Session General StartFailed"
http://support.microsoft.com/kb/288596/en-us

"Application Center 2000"
http://www.microsoft.com/technet/prodtechnol/acs/default.mspx

If this does not apply, make sure that SP2 has been installed. This
article may also help via Start > Run: services.msc
http://support.microsoft.com/kb/329441/en-us (excerpt)

| If the problem is not resolved, make sure the Telephony, Remote Access
| Connection Manager, and Remote Access Auto Connection Manager services
| are running.

 

[trevormidgley]

Hmm... interesting. Remote Access AUTO Connection Manager wasn't
running. Others were. (I've started it now!)

Will monitor progress.

Thanks again -


TM

 

[Detlev Dreyer]

Hmm... interesting. Remote Access AUTO Connection Manager wasn't
running. Others were. (I've started it now!)

Will monitor progress.

Thanks again -

You're welcome.

 

[Ron Martell]

Description:

Error code 00000077, parameter1 00000001, parameter2 13237303,
parameter3 00000000, parameter4 f3900c4c.

0x00000077: KERNEL_STACK_INPAGE_ERROR
This indicates that the requested page of kernel data from the paging
file could not be read into memory.

Cause
If the first parameter is 0 or 1, the stack signature in the kernel
stack was not found. This error is probably caused by defective
hardware, such as a RAM error.

Two things to try:
1. Download one of the following free memory test utilities and run
it for an extended period, such as overnight, to check out the RAM in
your computer:
DocMemory http://www.simmtester.com
Windows Memory Diagnostic http://oca.microsoft.com/en/windiag.asp
Memtest86: http://www.memtest.org

2. Go to the hard drive manufacturer's web site, download their free
diagnostic test utility and run it to check out your hard drive for
possible hardware problems.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."

 

[trevormidgley]

Thanks Ron - I'll check that out.

Another crash occurred this morning. The folowing is the Error Report
that was generated. Strangely, again it came straight after the Remote
Access Connection Manager ran. I've included that event as well, just
for interest.

TM


Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 14/01/2007
Time: 11:41:03
User: N/A
Computer: BACK-COMPUTER
Description:
Error code 000000c2, parameter1 00000007, parameter2 00000cd4,
parameter3 00000000, parameter4 85d61710.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 63 000000c
0020: 32 20 20 50 61 72 61 6d 2 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 37 2c 20 000007,
0038: 30 30 30 30 30 63 64 34 00000cd4
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 38 35 64 36 00, 85d6
0050: 31 37 31 30 1710




Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7036
Date: 14/01/2007
Time: 11:40:43
User: N/A
Computer: BACK-COMPUTER
Description:
The Remote Access Connection Manager service entered the running state.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

 

[Ron Martell]

Thanks Ron - I'll check that out.

Another crash occurred this morning. The folowing is the Error Report
that was generated. Strangely, again it came straight after the Remote
Access Connection Manager ran. I've included that event as well, just
for interest.

TM


Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 14/01/2007
Time: 11:41:03
User: N/A
Computer: BACK-COMPUTER
Description:
Error code 000000c2, parameter1 00000007, parameter2 00000cd4,
parameter3 00000000, parameter4 85d61710.

0x000000C2: BAD_POOL_CALLER
(from http://www.aumha.org/win5/kbestop.htm): "A kernel-mode process
or driver incorrectly attempted to perform memory operations.
Typically, a faulty driver or buggy software causes this."

See
http://msdn.microsoft.com/library/d..._e76af1ab-e90d-4afa-9a22-d74ed3f78672.xml.asp
for information on using Verifier to check out device drivers.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."

 

[trevormidgley]

Cheers, Ron.

Hmm - the old Chinese curse - "May you live in interesting times...!"

I tried the Verifier, but rather think I did something wrong! Anyway,
something went pear-shaped and I lost the ability to boot up - the
Windows\System32\Config\System file became either corrupted or went
missing.

Luckily, I have Acronis True Image on board, so I've managed to get
myself recovered to last night's backup.

Thought about trying Verifier again, but now I've noticed that XP Help
recommends you don't ask Verifier to check "all" the drivers.

A few questions if I may, before I move further:

What's the problem with asking verifier to check "all"?
What can I expect to see when I re-boot after giving the "check-all"
instruction?
How long is the check likely to take?
How will results be reported?
Lastly -
Will Verifier re-load at next boot-up, or will it be cancelled?

Sorry about this litany, but none of these questions are addressed in
Help, and I'm just a leetle bit nervous after this afternoon's episode.

Many thanks -


TM

 

[trevormidgley]

Ron - one more point of interest.

The following Error keeps getting reported in the System Event Viewer:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 15/01/2007
Time: 16:21:41
User: N/A
Computer: BACK-COMPUTER
Description:
The Intel AnyPoint APINFO Protocol Driver service failed to start due
to the following error:
The system cannot find the file specified.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


I used to have an Intel AnyPoint II network adaptor connected to this
computer via USB, but I took it off - now use a router for my network.
I've fully uninstalled the Intel AnyPoint program - have also run
Intel's ClnDrv utility to remove any driver fragments that might have
hung on - but this error still shows several times a day.

Could this be connected to my crashing problem? In fairness, the Intel
error never seem to show up around crash-time...

Thanks for your patience -


TM

 

[Ron Martell]

Cheers, Ron.

Hmm - the old Chinese curse - "May you live in interesting times...!"

I tried the Verifier, but rather think I did something wrong! Anyway,
something went pear-shaped and I lost the ability to boot up - the
Windows\System32\Config\System file became either corrupted or went
missing.

Luckily, I have Acronis True Image on board, so I've managed to get
myself recovered to last night's backup.

Thought about trying Verifier again, but now I've noticed that XP Help
recommends you don't ask Verifier to check "all" the drivers.

A few questions if I may, before I move further:

What's the problem with asking verifier to check "all"?
What can I expect to see when I re-boot after giving the "check-all"
instruction?
How long is the check likely to take?
How will results be reported?
Lastly -
Will Verifier re-load at next boot-up, or will it be cancelled?

Sorry about this litany, but none of these questions are addressed in
Help, and I'm just a leetle bit nervous after this afternoon's episode.

Many thanks -

My instructions for using Verifier say that you should choose the
"Automatically select unsigned drivers" option and then reboot.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."

 

[trevormidgley]

Thanks Ron.

I'm holding fire on this, because the good news is, since having to
fully restore my hard drive from the Acronis backup, the problem hasn't
re-occurred!

Weird, but there we are.

So for now, to paraphrase the old adage, "As it ain't broke, I won't
fix it...!"