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 CCVIDEOa 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 vdneor for any driver updates.
|English: Request a translation of the event description in plain English.|
IBM Support Reference #: R1003539 provides information on this event.
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.
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.
|Private comment: Subscribers only. See example of private comment|
|Links: ME293078, www.mersenne.org/freesoft.htm, tinyurl.com/dky5, IBM Support Reference #: R1003539|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated