[IAmMoen]

So I come home to my computer sitting on the login screen. Interesting I thought. Check the event log and at 9:55 this morning I got a System error category (102) event 1003.
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: 30 30 30 30 30 30 31 30 00000010
0028: 39 20 20 50 61 72 61 6d 9 Param
0030: 65 74 65 72 73 20 61 33 eters a3
0038: 61 30 33 61 33 38 36 31 a03a3861
0040: 31 35 37 38 31 61 2c 20 15781a,
0048: 62 33 62 37 34 36 62 65 b3b746be
0050: 62 33 39 32 34 65 36 61 b3924e6a
0058: 2c 20 66 66 66 66 66 38 , fffff8
0060: 30 30 30 31 33 34 66 36 000134f6
0068: 34 64 2c 20 30 30 30 30 4d, 0000
0070: 30 30 30 30 30 30 30 30 00000000
0078: 30 30 30 31 0001

Anyone have any idea what happened?

[redduc900]

That's very little information to go on, especially without knowing which OS you're running. Copy and paste (use the "Copy to Clipboard" button under the arrow buttons in the "Event Properties" window of Event Viewer) the latest critical error message (related to Event ID: 1003) as it appears under the "Description" field, and post it in this thread.

After you hit the "Copy to Clipboard" button in the "Event Properties" dialog, the contents in the Description field will be copied to the ClipBook Viewer (ClipBoard). You can then just paste the contents into your post, as there is no Edit-->Select All-->Copy function in ClipBook. In addition you could type clipbrd in the Run box, which will open the ClipBook Viewer containing the copied text from the Event Properties dialog... then perform a File-->Save As, and save the file with a *.txt extension. You could then perform a Edit-->Select All, then do a copy/paste of the text in your new post... so you have a couple different options.

[CGR]

Thats usually gets logged from a BSOD, however your system apparently rebooted to get back to the login screen. Systems usually do not do that when they get a BSOD from what I know.

I havent gotten one in a long time though..

[Skeith]

Originally Posted by CGR

Thats usually gets logged from a BSOD, however your system apparently rebooted to get back to the login screen. Systems usually do not do that when they get a BSOD from what I know.

I havent gotten one in a long time though..

Yes windows xp and win2k will reboot on a BSOD unless you have the option enabled to prevent it from doing so. Sometimes the reboot is so quick you dont even see the BSOD

[IAmMoen]

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 5/8/2007
Time: 9:55:25 AM
User: N/A
Computer: CMSTACKER
Description:
Error code 0000000000000109, parameter1 a3a03a386115781a, parameter2 b3b746beb3924e6a, parameter3 fffff8000134f64d, parameter4 0000000000000001.

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 30 0000000
0020: 30 30 30 30 30 30 31 30 00000010
0028: 39 20 20 50 61 72 61 6d 9 Param
0030: 65 74 65 72 73 20 61 33 eters a3
0038: 61 30 33 61 33 38 36 31 a03a3861
0040: 31 35 37 38 31 61 2c 20 15781a,
0048: 62 33 62 37 34 36 62 65 b3b746be
0050: 62 33 39 32 34 65 36 61 b3924e6a
0058: 2c 20 66 66 66 66 66 38 , fffff8
0060: 30 30 30 31 33 34 66 36 000134f6
0068: 34 64 2c 20 30 30 30 30 4d, 0000
0070: 30 30 30 30 30 30 30 30 00000000
0078: 30 30 30 31 0001

[thideras]

Ok, there are two possible problems with the error code "109":



Or