The system has recovered from a serious error --with no error numb

[Guest]

I frequently see this message in the morning, after the system has been
running all night long doing nothing but making an incremental backup at two
minutes after midnight.

The window says that a log of the error has been created and asks me to send
an error report.

If I do, I get a Windows Error Reporting Page
(wer.microsoft.com/responses/Response.aspx etc.) that tells me the problem is
caused by a device driver. It says that the problem is a Windows stop error
and tells me "a message appears on a blue screen with error code information."

But I've never seen the famous "blue screen," much less the message.

However, I've updated every driver I can find in a vain effort to solve the
problem. Where do I go from here?

 

[Rock]

I frequently see this message in the morning, after the system has been
running all night long doing nothing but making an incremental backup at
two
minutes after midnight.

The window says that a log of the error has been created and asks me to
send
an error report.

If I do, I get a Windows Error Reporting Page
(wer.microsoft.com/responses/Response.aspx etc.) that tells me the problem
is
caused by a device driver. It says that the problem is a Windows stop
error
and tells me "a message appears on a blue screen with error code
information."

But I've never seen the famous "blue screen," much less the message.

However, I've updated every driver I can find in a vain effort to solve
the
problem. Where do I go from here?

Look in the Event Viewer for the error message.

 

[Guest]

Rock, thanks for your response. I checked the Event Viewer, and the latest
of the errors lists the source as System Error and the Category as (102).
The Event Properties window lists the Event ID as 1003.

There's a link to the Help and Support Center, which says, "A matching event
with Event ID 1001 might also appear in the event log. This matching event
displays information about the specific error that occurred." But I can find
no such matching event.

If it helps any, the event properties window also contains the following
information:

Error code 1000000a, parameter1 80000011, parameter2 0000001c,
parameter3 00000000, parameter4 804e5cfa.

And under Data (Bytes):

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 31 30 30 30 30 30 30 1000000
0020: 61 20 20 50 61 72 61 6d a Param
0028: 65 74 65 72 73 20 38 30 eters 80
0030: 30 30 30 30 31 31 2c 20 000011,
0038: 30 30 30 30 30 30 31 63 0000001c
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 38 30 34 65 00, 804e
0050: 35 63 66 61 5cfa

I really appreciate your help with this!

Barney

 

[Rock]

Rock, thanks for your response. I checked the Event Viewer, and the
latest
of the errors lists the source as System Error and the Category as (102).
The Event Properties window lists the Event ID as 1003.

There's a link to the Help and Support Center, which says, "A matching
event
with Event ID 1001 might also appear in the event log. This matching event
displays information about the specific error that occurred." But I can
find
no such matching event.

If it helps any, the event properties window also contains the following
information:

Error code 1000000a, parameter1 80000011, parameter2 0000001c,
parameter3 00000000, parameter4 804e5cfa.

And under Data (Bytes):

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 31 30 30 30 30 30 30 1000000
0020: 61 20 20 50 61 72 61 6d a Param
0028: 65 74 65 72 73 20 38 30 eters 80
0030: 30 30 30 30 31 31 2c 20 000011,
0038: 30 30 30 30 30 30 31 63 0000001c
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 38 30 34 65 00, 804e
0050: 35 63 66 61 5cfa

I really appreciate your help with this!

Barney

Start with some reading here.
http://aumha.org/a/stop.htm
0x0000000A: IRQL_NOT_LESS_OR_EQUAL

 

[Guest]

Rock,

Again, thanks for your response. I went to the URL you suggested, but found
it difficult to understand --and as far as I could tell it didn't answer my
question.

So I called the manufacturer of my computer (I should have done that in the
first place). The technician suggested that I replace the driver of my video
card. He said the messages didn't give any information worth having, but
that video drivers were the most likely answer.

I have now installed (or reinstalled) the latest video driver, and I'm
keeping my finger crossed.

Barney

 

[Rock]

Ok, good luck. Yes, BSOD is often times associated with a driver.