HP NetServer LP 1000r HP Netserver Ultra3 SCSI HBA Guide - Page 38

Error Messages

Get HP NetServer LP 1000r PDF manuals and user guides View all HP NetServer LP 1000r manuals
Add to My Manuals
Save this manual to your list of manuals

Page 38 highlights

Press spacebar NOW to invoke the Last Known Good menu 3. Once your computer is operational again, check all of the hardware and soft- ware configuration changes you want to make. Look specifically for conflicts with parts of the existing system configuration that are not being changed. Error Messages Error messages generated by the adpu160m.sys driver can be viewed by opening the Windows NT Event Viewer error logs. To view events generated by the driver, follow these steps: 1. Double-click the Event Viewer icon in the Administrative Tools program group. Error messages generated by the driver show up as Event ID 11. Error messages generated by the SCSI port show up as Event ID 9. 2. To view event details, select System from the Log menu. Double-click the adpu160m.sys driver event that has an Event ID of 11. (There may be none or multiple driver events.) The top portion of the Event Detail dialog box displays information such as the time that the event was generated, the computer on which the event occurred (in case of remote monitoring) and the description of the event. The Data section of the Event Details dialog box displays the error messages generated. 3. Click the Words radio button. In the Data section of the dialog box, the entry in the second row and second column (to the right of the 0010: entry) lists the error message generated by the driver. The common error messages for the driver are described below. NOTE The entry in the third row of the last column identifies the SCSI ID of the device originating the error. 32

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
32
Press spacebar NOW to invoke the Last Known Good menu
3. Once your computer is operational again, check all of the hardware and soft-
ware configuration changes you want to make. Look specifically for con-
flicts with parts of the existing system configuration that are not being
changed.
Error Messages
Error messages generated by the
adpu160m.sys
driver can be viewed by
opening the Windows NT Event Viewer error logs.
To view events generated by the driver, follow these steps:
1. Double-click the
Event Viewer
icon in the Administrative Tools program
group.
Error messages generated by the driver show up as Event ID 11. Error messages
generated by the SCSI port show up as Event ID 9.
2. To view event details, select
System
from the Log menu. Double-click the
adpu160m.sys
driver event that has an Event ID of 11. (There may be none
or multiple driver events.)
The top portion of the Event Detail dialog box displays information such as the
time that the event was generated, the computer on which the event occurred (in
case of remote monitoring) and the description of the event. The Data section of
the Event Details dialog box displays the error messages generated.
3. Click the
Words
radio button.
In the Data section of the dialog box, the entry in the second row and second
column (to the right of the 0010: entry) lists the error message generated by the
driver. The common error messages for the driver are described below.
NOTE
The entry in the third row of the last column identifies the SCSI ID of
the device originating the error.