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.
The driver ati2dvag for the display device \Device\Video0 got stuck in an infinite loop. This usually indicates a problem with the device itself or with the device driver programming the hardware incorrectly. Please check with your hardware device vendor for any driver updates.
|English: Request a translation of the event description in plain English.|
From a newsgroup post: "For most people, one or more of the following will solve the problem: switching from AGP 8x to AGP 4x, raising AGP voltage, disabling fastwrites, switching to Microsoft's default CPU to AGP controller driver instead of using the VIA Hyperion one".
If you have a ThinkPad system running Microsoft Windows XP, then see the link to “IBM Support - XP Crash: System may hang or restart with previous version of Video Driver” for details on fixing this problem.
From a newsgroup post: "I have seen freezing problems fixed by changing aperture size and turning off AGP fast writes and Write Combining. Find the display controller's Troubleshoot tab and turn down acceleration one notch as a last resort. The only way to fix a problem like this is to keep trying everything until fixed. Start with settings, then drivers, and then replace hardware components".
As per ME293078, this issue can occur when the display driver is caught in an infinite loop, typically waiting for the video hardware to become idle. This usually indicates a problem with the video hardware or with the display driver not being able to program the hardware correctly.
Nick Le Lievre & WaltC
Memory errors or Bad memory causes the stuck in infinite loop error. Memory can POST and still be bad. The infinite loop can happen intermittently whilst playing CPU intensive games but less often when playing pure 3D games - for example my system ran 3D Mark 2001se overnight in a loop with memory that wouldnt get to POST in another board.
Yet this memory would cause system freezes whilst running Prime 95 and intermittently and less frequently during normal use of the system. The error device driver got stuck in an infinite loop suggests a problem with the device itself or the device driver programming would suggest in this case device driver incorrectly programmed due to errors in the memory.
The problem can also happen with good memory that is running out of sync with the CPU under XP but is fine under Windows 98 - but it is always a memory related problem despite the error message pointing to the graphics card see this post for more info at http://tinyurl.com/dky5.
In my case I was running the cpu at 133fsb and the memory at 133fsb the memory was TWINMOS 512MB PC2700 best way to test your system instead of waiting for it to happen again is to download Prime 95. See www.mersenne.org/freesoft.htm.
|Private comment: Subscribers only. See example of private comment|
|Links: ME293078, www.mersenne.org/freesoft.htm, tinyurl.com/dky5, IBM Support - XP Crash: System may hang or restart with previous version of Video Driver|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (1) - More links...|
Send comments or solutions
- Notify me when updated