Troubleshooting 4-3
4.Change the data view from Bytes (default) to Words.
5.Examine the entry at offset 0x10: if the low byte = En, match the low byte with the error found in Table
Windows NT Miniport Event Log Codes
The Windows NT Miniport driver can log events/errors in the Windows NT event log. Serious errors will always be logged. Informational events will only be logged if the registry parameter LogError=1 is used.
All Miniport logged events are issued with an Event ID of 11 (INTERNAL ADAPTER ERROR) but do not necessarily indicate an HBA error occurred. Byte offset 0x10 of the event is the driver event code. Byte offsets 0x11 to 0x13 contain event specific information.
0x10 Offset
Table
Windows NT SCSI Port Error Log
Explanation | 0x11 to 0x13 Further Information |
0xD0
0xD1
0xD3
0xD4
0xD5
0xD6
0xD7
0xD8
0xD9
SNS_REQ (XMIT_SEQ failed)
SNS_RSP (RCV_SEQ failed)
RCV_ELS_REQ failed
XMT_ELS_REQ failed
Too many targets found (160+)
SNS request
Mailbox interrupt
TPRLO requested when busy
Link down
0x11 = cmdstat, 12 = parm err
0x11 = cmdstat, 12 = parm err
0x11 = cmdstat, 12 = parm err
0x11 = cmdstat, 12 = parm err
0x11 to 13 = D_DID that didn’t fit
0x11 to 13 no additional information
0x11 = mailbox word 0
0x11 = local req. state, 12 = discstate, 13 = mailbox word 0
0x11 = local req. state, 12 = discstate, 13 = mailbox word 0
continued