RE: Windows 2003 server restart with system error
- From: Osvaldo Casagrande <Osvaldo Casagrande@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 4 Sep 2006 05:34:02 -0700
Hi, I have the same problem. With a HP Proliant ML350. And looks like a bad
driver, because, I think that is impossible that 3 servers from same
manufacturer and another from different have the same Hardware problems.
Another thing is that all of us are using the same SO with different
languages (I´m using spanish).
I Will checking for drivers and let you know the results.
Bye
"handelsmann" wrote:
Hi Massimo,.
seems like we are experiencing exactly the same problem (apart from the
language, obviously): note the system error's parameters!
eventlog says:
Ereignistyp: Fehler
Ereignisquelle: System Error
Ereigniskategorie: (102)
Ereigniskennung: 1003
Datum: 11.08.2006
Zeit: 13:23:27
Benutzer: Nicht zutreffend
Computer: SERVER
Beschreibung:
Fehlercode 0000000a, 1. Parameter 00000016, 2. Parameter 0000001b, 3.
Parameter 00000000, 4. Parameter 80847491.
Weitere Informationen über die Hilfe- und Supportdienste erhalten Sie unter
http://go.microsoft.com/fwlink/events.asp.
Daten:
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 30 0000000
0020: 61 20 20 50 61 72 61 6d a Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 31 36 2c 20 000016,
0038: 30 30 30 30 30 30 31 62 0000001b
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 38 30 38 34 00, 8084
0050: 37 34 39 31 7491
this happens randomly (almost every day).
we are running Windows 2003 Server R2 (incl TerminalServer) on a
built-to-order machine with
intel pentium D dual core (2x3.00 Ghz) processor
4x1024 Mb DDR2 RAM
Mainboard: ASUS P5LD2
NIC: Yukon Marvell (onboard)
according to different forums where at least similar problems are being
discussed our little problem seems to be related to:
a) bad drivers (but which??) and /or
b) bad memory (maybe memory leaks caused by bad drivers)
c) a bug with servicepack1
RemoteAccess may be an issue too: No Remote Accesses, no System Errors...
Since we got exactly the same sytem error code I do hope we both can shed a
bit more light in this mystery by exchanging some more information for
instance:
a) Does your event viewer show any other suspicious events?
I can offer this one, but I'm not really sure if there is a connection to
the main problem:
Ereignistyp: Fehler
Ereignisquelle: EventLog
Ereigniskategorie: Keine
Ereigniskennung: 6004
Datum: 11.08.2006
Zeit: 10:35:15
Benutzer: Nicht zutreffend
Computer: SERVER
Beschreibung:
Ein Treiberpaket, das vom E/A-Subsystem empfangen wurde, war ungültig. Die
Daten sind das Paket.
Weitere Informationen über die Hilfe- und Supportdienste erhalten Sie unter
http://go.microsoft.com/fwlink/events.asp.
Daten:
0000: 0c 00 e0 00 0e 00 00 00 ..à.....
0008: 7c 22 e5 11 21 bd c6 01 |"å.!½Æ.
0010: 40 00 00 00 00 00 00 00 @.......
0018: 00 00 00 00 04 00 4e 00 ......N.
0020: 00 00 00 00 cb 0b 00 80 ....Ë..€
0028: 00 00 00 00 10 00 00 c0 .......À
0030: 00 00 00 00 00 00 00 00 ........
0038: 00 00 00 00 00 00 00 00 ........
0040: 4d 00 52 00 78 00 53 00 M.R.x.S.
0048: 6d 00 62 00 00 00 5c 00 m.b...\.
0050: 44 00 65 00 76 00 69 00 D.e.v.i.
0058: 63 00 65 00 5c 00 4c 00 c.e.\.L.
0060: 61 00 6e 00 6d 00 61 00 a.n.m.a.
0068: 6e 00 52 00 65 00 64 00 n.R.e.d.
0070: 69 00 72 00 65 00 63 00 i.r.e.c.
0078: 74 00 6f 00 72 00 00 00 t.o.r...
0080: 4b 00 50 00 4b 00 00 00 K.P.K...
0088: 4e 00 65 00 74 00 42 00 N.e.t.B.
0090: 54 00 5f 00 54 00 63 00 T._.T.c.
0098: 70 00 69 00 70 00 5f 00 p.i.p._.
00a0: 7b 00 34 00 36 00 38 00 {.4.6.8.
00a8: 37 00 42 00 42 00 32 00 7.B.B.2.
00b0: 33 00 2d 00 41 00 35 00 3.-.A.5.
00b8: 34 00 42 00 2d 00 34 00 4.B.-.4.
00c0: 33 00 30 00 36 00 2d 00 3.0.6.-.
00c8: 42 00 43 00 31 00 43 00 B.C.1.C.
00d0: 2d 00 32 00 44 00 46 00 -.2.D.F.
00d8: 43 00 43 00 36 00 00 00 C.C.6...
b) Any strange devices or services (like iomega REV; special hardlocks) on
your machine?
I'm looking forward to hear (read) from you
"Massimo" wrote:
Hello! I need help
I have 2 Servers HP PROLIANT ML350 G4P with
Windows 2003 server R2 sp1 Installed.
The two servers are update with all patch (SO and Hardware bios and drivers)
but
all two server restart with this system error:
Tipo evento: Errore
Origine evento: System Error
Categoria evento: (102)
ID evento: 1003
Data: 18/07/2006
Ora: 7.57.00
Utente: N/D
Computer: server
Descrizione:
Codice errore 0000000a, parametro1 00000016, parametro2 0000001b, parametro3
00000000, parametro4 80847491.
Per ulteriori informazioni, consultare la Guida in linea e supporto tecnico
all'indirizzo http://go.microsoft.com/fwlink/events.asp.
Dati:
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 30 0000000
0020: 61 20 20 50 61 72 61 6d a Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 31 36 2c 20 000016,
0038: 30 30 30 30 30 30 31 62 0000001b
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 38 30 38 34 00, 8084
0050: 37 34 39 31 7491
Can someone help me?
Thank You
--
Massimo
- Prev by Date: Re: net use - and descriptive name...
- Next by Date: Re: Software RAID5 slow write speeds
- Previous by thread: Rejoin cluster node to NT4 domain
- Next by thread: Re: date and time of last boot
- Index(es):
Relevant Pages
|
