Home All Groups Group Topic Archive Search About

Windows 2003 Stop 0x000000c2 Error

Author
21 Jul 2005 4:32 PM
03error
Hi,

We have a new HP Proliant ML570 running 2003 enterprise configured as a file
server.  Without any warning, the server locked up, closed all the shares,
and produced the following error report.  After a reboot, the server was back
online.  This is the first time the following error came up.  Any thoughts? 
Thanks!

Event Type:    Warning
Event Source:    USER32
Event Category:    None
Event ID:    1076
Date:        7/19/2005
Time:        3:05:46 PM
User:                    xxx\xxx
Computer:    CA3
Description:
The reason supplied by user xxx\xxx for the last unexpected shutdown of this
computer is: System Failure: Stop error
Reason Code: 0x805000f
Bug ID:
Bugcheck String: 0x000000c2 (0x00000007, 0x00001153, 0x04200401, 0xe1a91b30)
Comment: 0x000000c2 (0x00000007, 0x00001153, 0x04200401, 0xe1a91b30)

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0f 00 05 08               ....   


Event Type:    Error
Event Source:    System Error
Event Category:    (102)
Event ID:    1003
Date:        7/19/2005
Time:        3:05:52 PM
User:        N/A
Computer:    xxx
Description:
Error code 000000c2, parameter1 00000007, parameter2 00001153, parameter3
04200401, parameter4 e1a91b30.

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 31 31 35 33   00001153
0040: 2c 20 30 34 32 30 30 34   , 042004
0048: 30 31 2c 20 65 31 61 39   01, e1a9
0050: 31 62 33 30               1b30

Author
21 Jul 2005 9:59 PM
Giuseppe Nacci
03error wrote:
> Hi,
>
> We have a new HP Proliant ML570 running 2003 enterprise configured as
> a file server.  Without any warning, the server locked up, closed all
> the shares, and produced the following error report.  After a reboot,
> the server was back online.  This is the first time the following
> error came up.  Any thoughts? Thanks!
>
> Event Type: Warning
> Event Source: USER32
> Event Category: None
> Event ID: 1076
> Date: 7/19/2005

      This event refers to the failure indicated by the previous EventLog
6008 event. The User32 1076 event is written when the first user with
shutdown privileges logs on to the computer after an unexpected restart or
shutdown and supplies a reason for the occurrence. An unexpected restart or
shutdown is one that the system cannot anticipate, such as when the user
pushes the computer's reset button or unplugs the power cord.

      A member of the Administrators security group can also log the reason
for a remote computer's unexpected restart or shutdown using the
Shutdown.exe tool. If many remote computers are unexpectedly shut down, as
in the case of a power outage, Shutdown.exe provides a way for the
administrator to remotely log the same shutdown reason on all the affected
computers.

      The User32 1076 event is written to the system log only when the
Shutdown Event Tracker group policy setting is enabled or not configured on
a computer running a Windows Server 2003 operating system. For more
information about Shutdown Event Tracker group policy settings, see Help and
Support.






> Event Type: Error
> Event Source: System Error
> Event Category: (102)
> Event ID: 1003
> Date: 7/19/2005

A blue screen (Stop error) was reported. The message contains details about
the error. 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


For both errors no user action are required
Regards
--
----
Giuseppe Nacci
Microsoft Certified System Engineer
Microsoft Certified Trainer
Security Manager
Are all your drivers up to date? click for free checkup

Author
23 Jul 2005 3:39 PM
lukesh
Hi,
Stop c2 is caused due to an incompatible driver. Please update all your
drivers in case the blue screen did not display a specific driver.

Lukesh

Show quoteHide quote
"03error" wrote:

> Hi,
>
> We have a new HP Proliant ML570 running 2003 enterprise configured as a file
> server.  Without any warning, the server locked up, closed all the shares,
> and produced the following error report.  After a reboot, the server was back
> online.  This is the first time the following error came up.  Any thoughts? 
> Thanks!
>
> Event Type:    Warning
> Event Source:    USER32
> Event Category:    None
> Event ID:    1076
> Date:        7/19/2005
> Time:        3:05:46 PM
> User:                    xxx\xxx
> Computer:    CA3
> Description:
> The reason supplied by user xxx\xxx for the last unexpected shutdown of this
> computer is: System Failure: Stop error
>  Reason Code: 0x805000f
>  Bug ID:
>  Bugcheck String: 0x000000c2 (0x00000007, 0x00001153, 0x04200401, 0xe1a91b30)
>  Comment: 0x000000c2 (0x00000007, 0x00001153, 0x04200401, 0xe1a91b30)
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 0f 00 05 08               ....   
>
>
> Event Type:    Error
> Event Source:    System Error
> Event Category:    (102)
> Event ID:    1003
> Date:        7/19/2005
> Time:        3:05:52 PM
> User:        N/A
> Computer:    xxx
> Description:
> Error code 000000c2, parameter1 00000007, parameter2 00001153, parameter3
> 04200401, parameter4 e1a91b30.
>
> 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 31 31 35 33   00001153
> 0040: 2c 20 30 34 32 30 30 34   , 042004
> 0048: 30 31 2c 20 65 31 61 39   01, e1a9
> 0050: 31 62 33 30               1b30   
>
Author
23 Jul 2005 8:46 PM
TechUK
Hi. I chased a couple of these around a similiar HP box. Two BSOD stop errors for two different reasons. Had me caught up for days. The resolutions were;

1. Stop error caused by installation of Symantec Corp Edition V9 and Symantec PC Anywhere on the same box. Following installation of PCAW I saw numerous stop errors following moderate server load. Solution was to unload PCAW.

2. Stop error caused by pagefile error. Solution was to increase physical memory from .5 to 1gb.

I also Googled for help and was directed to faulty USB drivers etc. This wasn't true in either of my cases but it does seem to be the prescribed MS diagnosis. Your mileage may vary of course.



lukesh wrote:
Show quoteHide quote
> *Hi,
> Stop c2 is caused due to an incompatible driver. Please update all > your
> drivers in case the blue screen did not display a specific driver.
>
> Lukesh
>
> "03error" wrote:
>
> > Hi,
> >
> > We have a new HP Proliant ML570 running 2003 enterprise configured > as a file
> > server.  Without any warning, the server locked up, closed all the > shares,
> > and produced the following error report.  After a reboot, the > server was back
> > online.  This is the first time the following error came up.  Any > thoughts?
> > Thanks!
> >
> > Event Type:    Warning
> > Event Source:    USER32
> > Event Category:    None
> > Event ID:    1076
> > Date:        7/19/2005
> > Time:        3:05:46 PM
> > User:                    xxx\xxx
> > Computer:    CA3
> > Description:
> > The reason supplied by user xxx\xxx for the last unexpected > shutdown of this
> > computer is: System Failure: Stop error
> >  Reason Code: 0x805000f
> >  Bug ID:
> >  Bugcheck String: 0x000000c2 (0x00000007, 0x00001153, 0x04200401, > 0xe1a91b30)
> >  Comment: 0x000000c2 (0x00000007, 0x00001153, 0x04200401, > 0xe1a91b30)
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> > Data:
> > 0000: 0f 00 05 08               ....
> >
> >
> > Event Type:    Error
> > Event Source:    System Error
> > Event Category:    (102)
> > Event ID:    1003
> > Date:        7/19/2005
> > Time:        3:05:52 PM
> > User:        N/A
> > Computer:    xxx
> > Description:
> > Error code 000000c2, parameter1 00000007, parameter2 00001153, > parameter3
> > 04200401, parameter4 e1a91b30.
> >
> > 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 31 31 35 33   00001153
> > 0040: 2c 20 30 34 32 30 30 34   , 042004
> > 0048: 30 31 2c 20 65 31 61 39   01, e1a9
> > 0050: 31 62 33 30               1b30
> > * -- TechUK ------------------------------------------------------------------------ Posted via http://www.mcse.ms ------------------------------------------------------------------------ View this thread: http://www.mcse.ms/message1747311.html

Bookmark and Share