Windows xp event id 51

I'm not sure how repairing windows will fix this problem. Forum Member since I'm not a Dell employee. Browse Community. Windows General. Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.

Showing results for. Search instead for. Did you mean:. Last reply by RoHe Unsolved. My Dimension keeps periodically freezing for about 10 seconds when trying to read the Hard Drive and I noticed errors logged in my Event Viewer. I get 2 each time:. All forum topics Previous Topic Next Topic. Replies RoHe 8 Krypton. This list of ASCQ for each sense code is too large to include in this article. View SCSI. H in the DDK for more information. 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. The CDB data section isn't in the little-endian format. So the bytes shouldn't be flipped.

Be careful when you decode this section, because the format is different from earlier sections. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? Note The device in the description and the specific hexadecimal data may vary. Note When you interpret the hexadecimal data in the Event ID to the status code, remember that the values are represented in the little endian format.

Note The destination disk information is how it appears to the operating system. Note The CDB data section isn't in the little-endian format. 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. BAW Posted April 24, Posted April 24, Im lost? Link to comment Share on other sites More sharing options Here's some information about the error ID This should be helpful to a resolution. Information about Event ID 51 View products that this article applies to.

Data: 04 00 22 00 01 00 72 00 00 00 00 00 33 00 04 80 2d 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 52 ea 04 15 00 00 00 01 00 00 00 04 00 00 00 03 00 00 00 2a 00 00 00 02 84 00 00 00 29 06 00 2a 60 0a 82 75 29 00 00 80 00 Note The device in the description and the specific hexadecimal data may vary.

Back to the top How to decode the data section of an Event ID 51 event message When you decode the data section in 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 failed because the bus was reset but the request will be retried.

The following tables describe what each offset represents.