Stop errors during encoding--Gordian Knot, Xvid, WinXP

[sector9]

OK. Windows XP SP1, Gordian Knot, Xvid. If it matters, an Athlon XP 2100+, 768 Mb DDR ram.
While encoding, I've gotten a bunch of stop errors. It's happened at least 10,11 times over the last month, maybe more--not sure, really. I haven't always been able to record the error, but I think they have all been the same one. The event viewer on winXP has these two events:
Error code 00000050, parameter1 b6dc5194, parameter2 00000000, parameter3 bf872a0f, parameter4 00000000. This one has an error code 1003. The link given shoots me to a page saying that this means, roughly, "Windows had an error. Look for the error code 1001 in the log."
Right before it...such an error.
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xb6dc5194, 0x00000000, 0xbf872a0f, 0x00000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP.

This only happens while encoding video. It's both annoying--if I set up 8 hours of encoding in the queue, and the computer reboots after 3, it wastes a lot of time--but also worrying--I hope they aren't damaging my computer.

Has anyone seen this? Can anyone help me?

[jggimi]

Most errors you are describing occur due to heat stress; video encoding produces more CPU heat than the vast majority of workstation applications. This can happen with "off the shelf" computers as well as custom or home built ones.

If you are overclocking .... go back to factory defaults.

For more on managing PC stability, and for links to stress testing tools and temperature monitoring software, see this thread:

Hardware problems / How to test system stability (http://forum.doom9.org/showthread.php?s=&threadid=54130)

[sector9]

Not overclocking. My CPU temperatures are (unloaded) under 40 degrees C. Any other possibilities?

[jggimi]

Memory testing, stress testing, per the link I provided? Other than that, you could debug the dump. With the SP1 symbol table it might point to a driver or other module that may be in error. Though running Windows debugging tools from the SDK is a little outside the bounds for the newbie forum.

[sector9]

Well, I ran prime95 and memtest, for 6-8 hours each, no problems whatsoever. Any other ideas?

[sector9]

OK, so that's odd. I was doing some more encoding, and it happened again. However, since for once I was at the computer paying attention, I caught something--on the BSOD was noted the file causing problems--navex15.sys. A quick google seems to say that this is part of Norton Antivirus! (Which I do indeed run.) I'm still googling, but does anyone know of crashes caused by this file?

[niamh]

I found this (http://support.microsoft.com/kb/q255928/). It seems relevant. Basically Norton flunked an update on navex15. What's new? :rolleyes: