Log in

View Full Version : x264 crashes... screenshot inside

graysky
18th September 2007, 20:09
Every version of x264.exe gives the error and it seems to be independent of commandline options/video encoding profile in meGUI.

Thoughts from anyone?

http://img233.imageshack.us/img233/4213/errordq0.gif
Sagekilla
18th September 2007, 20:17
I probably can't help you, but I can help save some (other people's) time by asking what settings you used, as well as how your source avisynth script was set up. I have a curious feeling it may have something to do with the source, but I could be wrong.
graysky
18th September 2007, 21:05
It's independent of settings and scripts; I've tried using the default "HQ Slower" profile as well as others. I have tried numerous scripts and mpg sources. The identical scripts/d2v/mpg files can get encoded on other machines just fine... it's really odd.
fields_g
18th September 2007, 21:21
Overclock?
graysky
18th September 2007, 21:24
fields_g: no, stock settings... it's an older machine so it might be that, but I have done x264 encodes on it in the past with no issues.
HowlerX
18th September 2007, 21:31
Try re-downloading and overwriting your current executable.
jeffy
18th September 2007, 21:37
Try MemTest on that PC, the memory might be bad.
graysky
18th September 2007, 21:45
@HowlerX - tried it, same results
@jeffy - I can try that, but I'm guess it's fine since other apps are happy
bob0r
18th September 2007, 23:13
try with x264.exe + avs file only (no megui)
then try to limit your avs script lines one by one if it happenswith different sources
graysky
18th September 2007, 23:55
bob: I did that actually. It doesn't seem to matter... oh well, it's not a big deal really
jeffy
19th September 2007, 23:40
@HowlerX - tried it, same results
@jeffy - I can try that, but I'm guess it's fine since other apps are happy

Well, I had bad memory at the beginning of this year, everything seemed so okay, just the x264.exe was crashing (!) and some other programs followed it soon; suddenly, some of the downloaded files became corrupt and then even part of the NTFS filesystem became corrupt and then MemTest found out the memory gone bad (both 1066 MHz DDR2 sticks) :(
bob0r
20th September 2007, 00:36
bob: I did that actually. It doesn't seem to matter... oh well, it's not a big deal really

Hell yeah its a big deal!
If you have a problem, WE have a problem! :D

But the more info comes available, the more it seems there is some hardware issue on your side. :(
le_canz
23rd September 2007, 16:43
Hello to the Doom9 community :)

I've got the same kind of problem here (the only I had with x264 so far).

x264 (any revision) works fine with all of my computers, except with my old K6-III (yeah I know I'm crazy, I was just curious about how slow an encode would be)

I tried to find wich parameter was causing the bug, and I found that using --no-asm solves the crash.

--no-asm is the only way to make x264 work, with it encoding goes on until the end flawlessly.

All my others CPUs got SSE, only the K6 lacks it. So maybe... ?

Here is a screenshot :

http://img230.imageshack.us/img230/7325/bug01ye9.png

Anyway, I'd like to thank developpers, testers etc. You do great things, and doom9 is a pleasant forum to read :thanks:

PS : sorry for my english... :p