32Press spacebar NOW to invoke the Last Known Good menu3. 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 beingchanged.Error MessagesError messages generated by the adpu160m.sys driver can be viewed byopening 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 programgroup.Error messages generated by the driver show up as Event ID 11. Error messagesgenerated by the SCSI port show up as Event ID 9.2. To view event details, select System from the Log menu. Double-click theadpu160m.sys driver event that has an Event ID of 11. (There may be noneor multiple driver events.)The top portion of the Event Detail dialog box displays information such as thetime that the event was generated, the computer on which the event occurred (incase of remote monitoring) and the description of the event. The Data section ofthe 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 secondcolumn (to the right of the 0010: entry) lists the error message generated by thedriver. 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 ofthe device originating the error.
