If you have system error 51 on your system, this guide should help you.
Approved: Fortect
Event ID 51 is a fundamental failure of any type of failure that definitely occurs when paging I / O information. A paging operation occurs when the disk system swaps a page of space from memory to disk, or fetches some type of page of memory from disk for storage. Event ID 51 is only received during I / O paging.
- 10 minutes to read.
Event code 51 can occur before information is written to the physical disk. This article describes how to decode this section of data from event message fifty-one from event ID.
Applies to: Windows 7 SP1, Windows Server 2012 R2
Original Knowledge Base Number: 244780
Resume
Connect the silent hard drive to another computer (if you have one).If you need a desktop computer, try connecting the hard drive to a different port (ex.
When you record synchronization information for a physical disk, the following event match may be logged in the system log:
Event ID: 51Event type: WarningEvent Source: DiskDescription: An error was detected on device Device Hard Disk3 DR3 during a new swap process.Danny:0000: 2008 00 22 00 01 00 72 500008: 00 00 00 00 thirty three 00 04 800010: 2d 07 00 00 00 00 00 double zero0018: 00 00 00 00 00 double zero 00 000020: 00 52 specialist consultant 04 15 00 00 000028: 04 00 00 00 04 00 double zero 000030: 03 00 00 double zero 2a 00 00 000038: 10 84 00 00 00 29 06 500040: 2a 60 0a 82 seventy five 29 00 000048: ninety 00
Additional Information
If a generic error occurs when your entire computer is communicating with the hard disk or with the hard disk, Event Principles and ID 51 are logged. In a paging operation, each operating system swaps a page of memory from memory to disk or may even fetch a page of memory from disk whenever you need memory. This is part of the Windows Storage Guide.
However, the computer may log the above event message when it downloads and reads images outside of storage, writes to locally mapped files, or any write (assuming it is buffered I / O). Do not log this event message if it is performing unbuffered I / O. Can you troubleshoot the event messageand with event ID 51 the same way you troubleshoot event ID 9, perhaps event messages with event ID 11?
Under certain circumstances, the system logs the following event message with event ID 51:
An error was detected on your device Device DeviceName during the paging process
In this case, no harmful effects were found. For example, Event ID 51 is recorded if a blank medium such as CDR, CDRW, DVDR is inserted into the recordable drive when a USB device is connected. The system records the event even if the CD / DVD is writable. and the USB process can still be used. You can safely ignore these cases. No action required.
In Windows Vista or later, the main event log entry has been increased and the device name has not been truncated.
You can use binary data completely associated with each DISK error (event ID 7, search, 11, 51, and other event IDs) to determineFix the problem by reviewing the data report section.
p>
Event ID 51 contains an optional Descriptor Control Block (CDB) package. When purchasing the information portion of the event message with event ID 51, please note the following information.
Decode The Data Section Of The Event Message With Event ID 51
Event ID 129 means there is a timeout issue on the storage device. And there are tap-ctl errors on Dom0, displayed read requests failed at some point. So this issue was caused by running too much many requests for reading disk I / O and the need to tune the performance of disk I / O.
If your company decrypts the perfect data section in the summary section, you can imagine that this is an attempt to author operation on LUN 3 from market 0x2975820a for sectors 0x0080, because the entire bus has been dropped, but the request can be retry. The rest of this article describes some specific steps to decode this example.
| offset | length | values |
|---|---|---|
| 0x00 | 1 | Operation type: 0x03 = read, 0x04 corresponds to write, 0x0F = IOCTL |
| 0x01 | 1 | Number of attempts remaining |
| 0x02 | 2 | Dump data size 0x0068 |
| 0x04 | 2 | Number of lines 0x0001 |
| 0x06 | 2 | Offset around namesand devices |
| 0x08 | 2 | Not used |
| 0x0a | 2 | Padding Byte |
| 0x0c | 4 | Error code NTSTATUS |
| 0x10 | 4 | Unique error value |
| 0x14 | 4 | NTSTATUS end state 0x00000000 = call will repeat |
| 0x18 | 4 | Ordinal number – not used |
| 0x1c | 4 | Io check code (not applicable to this event) |
| 0x20 | 8 | Byte or bad sector, if applicable |
| 0x28 | 8 | Check the minute the error occurred |
| 0x30 | 4 | Port number – Not used |
| 0x34 | 1 | Error Messages |
| 0x35 | 3 | Not used |
| 0x38 | 88 | Block structure for SCSI requests |
| 0x90 | 18 | Recognize data structure |
Key Decoding Sections
Error Code
In the example that actually appears in the Summary section, the error marketers are listed on the second line. This line starts with 0008: and matchesthe last 4 bytes of the string.
0008: 50 00 00 00 33 00 2004 80
This code is error code fifty-one. This code is the same for all event messages from Event ID 51:
IO_WARNING_PAGING_FAILURE
Latest Location Code
In the example sector Summary , the final status code is above 0x14 (on the third line), which starts at 0010: and includes the last 2 bytes of that line.
0010: 01 2j 50 00 00 00 00 00
It maps positively to STATUS_SUCCESS and implies that the request will be retry.
Destination Disk
The harddisk0 dr0 device has a bad block, which indicates that there may be a bad block on its own hard drive as a whole. If the data block is not properly connected, there is no way to help it recover. Fortunately, you can force your operating system not to treat the block as bad. It is very effective in preventing data loss.
You can use your data to determine which disk the problem is on:
0028: 01 00 00 double zero 04 00 00 00
0030: 03 00 double zero 00 2a 00 00 00
It may be easier to determine the scope using the symbolic link provided in the branding event ID description. For example, Device Harddisk3 DR3 .
SCSI Request Block (SRB) Parameters
Approved: Fortect
Fortect is the world's most popular and effective PC repair tool. It is trusted by millions of people to keep their systems running fast, smooth, and error-free. With its simple user interface and powerful scanning engine, Fortect quickly finds and fixes a broad range of Windows problems - from system instability and security issues to memory management and performance bottlenecks.
In the example sections Summary ScsiStatus 0x02 (first byte of line 0038) and Is srbstatus 0x84 (second b Line 0038) represent the following information:
0038: 02 84 00 00 double zero 29 06 00
0x00 = SCSISTAT_GOOD0x02 = SCSISTAT_CHECK_CONDITION0x04 = SCSISTAT_CONDITION_MET0x08 = SCSISTAT_BUSY0x10 = SCSISTAT_INTERMEDIATE0x14 implies SCSISTAT_INTERMEDIATE_COND_MET0x18 = SCSISTAT_RESERVATION_CONFLICT0x22 = SCSISTAT_COMMAND_TERMINATED0x28 = SCSISTAT_QUEUE_FULL
0x00 = SRB_STATUS_PENDING0x01 = SRB_STATUS_SUCCESS0x02 = SRB_STATUS_ABORTED0x03 corresponds to SRB_STATUS_ABORT_FAILED0x04 = SRB_STATUS_ERROR0x05 = SRB_STATUS_BUSY0x06 = SRB_STATUS_INVALID_REQUEST0x07 = SRB_STATUS_INVALID_PATH_ID0x08 = SRB_STATUS_NO_DEVICE0x09 = SRB_STATUS_TIMEOUT0x0A means SRB_STATUS_SELECTI
Speed up your computer's performance now with this simple download.
