"x264 stopped working" (Windows 2008)

[asarian]

In Windows Server 2008, I'm getting this error after a few hours when when transcoding with RipBot264, which uses x264: "x264 stopped working" (see further below). I'm trying to update the x264 version bundled with RipBot264, but when I do that, RipBot264 immediately exits.

Apart from the obvious question whether someone has encountered this error too, is there a special 'bundled' version of x264 or something that I'm unaware of? I'd like tp update the version, hoping maybe that will make the error go away.

Thanks.


--------------
Product
x264.exe

Problem
Stopped working

Date
8/16/2008 3:08 PM

Status
Report Sent

Problem signature
Problem Event Name: APPCRASH
Application Name: x264.exe
Application Version: 0.0.0.0
Application Timestamp: 48338a8c
Fault Module Name: x264.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 48338a8c
Exception Code: c000001d
Exception Offset: 0002f5d9
OS Version: 6.0.6001.2.1.0.400.8
Locale ID: 1033
Additional Information 1: fd00
Additional Information 2: ea6f5fe8924aaa756324d57f87834160
Additional Information 3: fd00
Additional Information 4: ea6f5fe8924aaa756324d57f87834160

Extra information about the problem
Bucket ID: 887741298

[Ranguvar]

Vanilla, unpatched builds can be found at http://x264.nl/, and patched ones can be found in the Patches thread in this subforum, among other places. I highly recommend patched builds if you have half a clue what you're doing with them; it seems there are always excellent features like Psy RDO, the new b-frame decision, etc. Or you could compile your own ;)

[Sharktooth]

hardware problems?

[kemuri-_9]

Exception Code: c000001d

seems to correspond to STATUS_ILLEGAL_INSTRUCTION
so maybe server 2008 (similar base as vista) has some compatibility issues from the build...
would need to compile your own version and test this

[LoRd_MuldeR]

so maybe server 2008 (similar base as vista) has some compatibility issues from the build...

"Illegal Instruction" sounds more like a CPU compatibility problem. But "getting this error after a few hours" definitely sounds like a hardware (overheat) problem...

[Shinigami-Sama]

maybe some of the ASM is is changed to be privilaged(sounds like an MS thing to do)

[LoRd_MuldeR]

maybe some of the ASM is is changed to be privilaged(sounds like an MS thing to do)

Whether a specific instruction is privileged or not is defined by the CPU Architecture, not by the OS. So M$ cannot change that, only Intel can ;)
The OS kernel only handles the interrupt that will be triggered by the CPU when an unprivileged process tries to call a privileged instruction.

Also it would be unlikely that the "problematic" ASM code is never executed for several hours and then suddenly it is...

[foxyshadis]

Most common cause of crashes is system instability caused by overheating or bad memory/power supply, avisynth using too much memory, or bad avisynth plugins. Check the ripbot264 threads for specific details on updating x264, in case it uses some customized variation.

To check a hardware problem, leave wprime running all day, and install tempurature monitors if you can. For the second, watch task manager every so often to see if memory use in x264.exe keeps climbing. For the last, you have to debug it to find out exactly where it's crashing out, which .dll or .exe it's in.