Privacy policy. Event ID 51 may occur when you write information to the physical disk. This article describes how to decode the data section of an Event ID 51 event message. When you write information to the physical disk, the following event message may be logged in the System log:.
If a generic error occurs when your computer pages information to or from the disk, an Event ID 51 event message is logged. In a paging operation, the operating system either swaps a page of memory from memory to disk, or retrieves a page of memory from disk to memory.
It's part of the memory management of Windows. In this case, no harmful effects are experienced. The system logs the event even though the disc is writable, and the USB device is still usable. In these particular cases, you can safely ignore the log entries.
No action is required. As a result, the displayed hard disk number, or the device object name itself may be incorrect. Because a large amount of information is stored in the data section, the space that's available for the DeviceName is reduced. In this case, you can find the appropriate device by looking at the destination disk data that's stored in the data section. For more information, see Decode the data section of an Event ID 51 event message. On Windows Vista and later versions, the event log entry size has been increased, and DeviceName isn't truncated.
Consider the following information when you review the data section of an Event ID 51 event message. When you decode the data section of the example in the Summary section, you can see that an attempt to perform a write operation to LUN 3 starting at sector 0xa for 0x sectors fails because the bus was reset but the request will be retried.
Later, this article lists the specific steps to decode this example. If the SRB status is that the autosense is valid, the sense codes provide additional information. In the example in the "Summary" section, the sense code is 0x06 seventh byte in line "" , and the additional sense code is 0x29 sixth octet in line "".
The additional sense code is located in the sixth byte in line? For the specified sense key, this maps to:. The additional sense code qualifier is located in the fifth byte in line? It is 00 in this example, so it does not apply for the specified ASC. This list of additional sense code qualifiers for each sense code is too large to include in this article.
Please view SCSI. H in the DDK for additional information. Please refer to the hardware vendor. The bytes at offset 0x40 represent the CDB code, the bytes from offset 0x43 to 0x46 represent the starting sector, and offset 0x47 to 0x49 represent the number of sectors involved in the operation.
Note The CDB data section is not in the little-endian format, therefore the bytes should not be flipped. Be careful when you decode this section because the format is different from the earlier ones. Do you have a motherboard with an nforce4 chipset? It could also just mean your drive is failing. Keep your data backed up!
I also heard the problem with NForce4 so i uninstalled the drivers and are now running default MS drivers. Yet i am still having the issues. I suggest reading over this thread for possible tips on how to fix this.
Sometimes the actual driver for the disk can become corrupt and just need re-installing. I deleted the drive from the device manager, rebooted and after Windows re-installed the drivers, no more trouble. Your drive might actually be failing however.
Do you have a spare HDD to install just to rule it out? Search In. Event ID 51? Share More sharing options Followers 0. Recommended Posts. Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services.
Privacy policy. This article provides a solution to system error 51 or 53 that occurs when you access shared resources. When you try to access shared resources on a computer that is running Microsoft Windows or Microsoft Windows Server , you may receive one of the following error messages:.
When you try to view the properties of a Windows client on a domain controller that is running Microsoft Windows NT 4.
0コメント