Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
|
18th August 2008, 23:05 | #1 | Link |
Registered User
Join Date: May 2005
Posts: 1,462
|
"x264 stopped working" (Windows 2008)
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
__________________
Gorgeous, delicious, deculture! |
19th August 2008, 02:16 | #2 | Link |
Registered User
Join Date: Feb 2007
Location: ::1
Posts: 1,236
|
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
|
19th August 2008, 02:46 | #3 | Link |
Mr. Sandman
Join Date: Sep 2003
Location: Haddonfield, IL
Posts: 11,768
|
hardware problems?
__________________
MPEG-4 ASP Custom Matrices: EQM V1(old), EQM AutoGK Sharpmatrix (aka EQM V2), EQM V3HR (updated 01/10/2004), EQM V3LR, EQM V3ULR (updated 04/02/2005), EQM V3UHR (updated 17/12/2004) and EQM V3EHR (updated 05/10/2004) Info about my ASP matrices. MPEG-4 AVC Custom Matrices: EQM AVC-HR Info about my AVC matrices My x264 builds. Mooo!!! |
19th August 2008, 03:12 | #5 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
"Illegal Instruction" sounds more like a CPU compatibility problem. But "getting this error after a few hours" definitely sounds like a hardware (overheat) problem...
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ |
19th August 2008, 03:39 | #7 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Quote:
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...
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 19th August 2008 at 04:00. |
|
19th August 2008, 04:13 | #8 | Link |
ангел смерти
Join Date: Nov 2004
Location: Lost
Posts: 9,558
|
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. |
Thread Tools | Search this Thread |
Display Modes | |
|
|