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.
A conflict has been detected betwwen two drivers which claimed two ovelapping memory regions. Driver s3virge with device <device\video1.translated>, claimes a memory range with starting address in data address 0x28 and 0x2c, and length in data address 0x30.
|English: Request a translation of the event description in plain English.|
As per Microsoft: Two drivers are requesting exclusive use of the same input/output (I/O) ports. The second driver cannot be loaded, and functionality dependent on this driver will not be available. Change the set of I/O ports for the specified driver. Or, if you know which driver is competing with the specified driver for these ports, change ports for the competing driver. For information on how to change I/O ports, see your hardware documentation.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated