Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
|Source: various devices|
A parity error was detected on \<device path>.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is a parity error?
Device: "Atapi" - As per Microsoft: "ATA66 DMA transfer mode is not supported for the onboard IDE controller." See the link below.
One user solved this by disabling DMA in the BIOS and disabling the Write Cache in Windows 2000.
Other reported devices:
- "Sparrow2" - no info
- "aic78xx1" - no info
- "aic78u2" - no info
- "IdeChnDr" - no info
Device: "Atapi" - I am using for a while and strongly recommend "Intel Application Accelerator". This is a fancy marketing name for the best drivers I know for Intel IDE chipsets. It works for most motherboards with Intel chipsets and the results are very good: the system is stable, fast IDE transfer and with reduced CPU usage. This is achieved by automatically selecting the highest possible DMA transfer mode for the particular hardware.
I´ve got lots of event 5 together with warning 51 after changing some hardware-details and then copying from one partition to another (W2K). In the end I realized, that the problem was a special 90 cm long ATA-100 cable for HD-connection to the controller. Changing this to the standard 80-line cable (about 50 cm), the problem disapeared.
|Private comment: Subscribers only. See example of private comment|
|Links: ME262448, Intel Application Accelerator [IAA], Download IAA|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated