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 drivers|
A conflict has been detected between two drivers which claimed equivalent IRQs. Driver <driver name>, with device <device name>, claimed an interrupt with Level in data address 0x28, vector in data address 0x2c and Affinity in data address 0x30.
|English: Request a translation of the event description in plain English.|
See the link to "EventID 24 from source Various" for details on this event.
As per Microsoft: "Two drivers are requesting exclusive use of the same interrupt (IRQ). The second driver cannot be loaded, and functionality dependent on this driver will not be available.
User Action: Change the IRQ value for the specified driver. Or, if you know which driver is competing with the specified driver for this IRQ, change the IRQ value for the competing driver. For information on how to change the IRQ value, see your hardware documentation."
|Private comment: Subscribers only. See example of private comment|
|Links: MSDN, EventID 24 from source Various|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated