beautypg.com

Bug check/blue screen event records, Table 94: bug check/blue screen, Os stop event record typical characteristics – Kontron S5500 SEL Troubleshooting User Manual

Page 111: 3 bug check/blue screen event records

background image

Microsoft Windows* Records

System Event Log Troubleshooting Guide for Intel® S5500/S3420 series Server Boards

102

Intel order number G74211-001

Revision 1.0

16.3 Bug Check/Blue Screen Event Records

When the system experiences a bug check (blue screen) there will be multiple records written to the event log. The first is a Bug Check/Blue
Screen OS Stop/Shutdown Event Record; this can be followed by multiple Bug Check/Blue Screen code OEM records that will contain the Bug
Check/Blue Screen codes. This information can be used to determine what caused the failure.

Table 94: Bug Check/Blue Screen

– OS Stop Event Record Typical Characteristics

Byte

Field

Description

8

9

Generator ID

0041h

– System Software with an ID = 20h

11

Sensor Type

20h = OS Stop/Shutdown

12

Sensor Number

00h

13

Event Direction and
Event Type

[7] Event direction

0b = Assertion Event

1b = Deassertion Event

[6:0] Event Type = 6Fh (Sensor Specific)

14

Event Data 1

[7:6]

– 00b = Unspecified Event Data 2

[5:4]

– 00b = Unspecified Event Data 3

[3:0]

– Event Trigger Offset = 1h =

Run-time Critical Stop (that is,

‘core dump’, ‘blue screen’)

15

Event Data 2

Not used.

16

Event Data 3

Not used.

Table 95: Bug Check/Blue Screen code OEM Event Record Typical Characteristics

Byte

Field

Description

1

2

Record ID

ID used for SEL Record access.

3

Record Type

[7:0] - DEh = OEM timestamped, bytes 8-16 OEM defined