How to troubleshoot Event ID: 50 & 51 Windows Paging errors

Document Details

Article ID
T4303-1230

Last Review
July 23, 2007

Products
Warp Drive 3.5"
Warp Drive 2.5"

Firmware Versions
NA

Related Articles

Related How-To Videos

 

You receive the errors:

Event ID: 50 (Lost Delayed-Write Data), Or

Event ID: 51 (An error was detected on device \Device\Harddisk1\DR2 during a paging operation)

 

 

Event ID 50 and 51 are generic errors that may occur anytime paging information is requested from a drive. Similar Event IDs are 9, 11 and 15. A paging operation is defined as anytime the operating system writes or reads data from memory to drive, or reads from the hard drive and writes to memory. These errors are not caused by the external storage device. The error may be related to problems in either the USB / ATA / SCSI / 1394 controller sub system or another storage device.

 

 

Here are some troubleshooting tips to help you diagnose and pinpoint the problem.

• The TRITTON Warp Drives are not recommended for backup of entire drive volumes or large volume transfer over a computer network. Slow command responses due to network traffic can cause these errors.
• File size limits. A single file cannot exceed 4 GB in the FAT 32 file system. Reformatting the drive in the NTFS File System allows a maximum file as large as the entire drive. Windows 98 and Millennium Edition do not support NTFS. Windows 2000 prior to Service Pack 3 does not support the NTFS version used by Windows XP.
• Close all applications not immediately needed. Close all email applications and disable Power Management schemes, all pre-scheduled diagnostics, CD auto-insert notification, Window Update polling, and virus control programs. Shut down all applications that actively poll the I/O subsystem or use CPU cycles.
• Simplify the device chain. Disconnect all other devices from the controller. Allow only the Warp Drive on the USB controller. If you have a USB mouse, keyboard, or printer, substitute the equivalents serial or parallel port device to isolate the issue.
• Note the time. Find out if errors occur under certain operations (such as backups), after the system has been on for a long period of time or during heavy disk drive processing.
NOTE: Hard drives show these errors under heavy stress, often due to a slow CPU speed. In a multitasking environment like Windows, the processor may not be fast enough to process all the I/O commands that come in nearly simultaneously.
• Try replacing the interface cable or moving the drive in question to another controller. If the problem follows the drive, consider replacing it.