x264 Error

[StHapns247]

I searched the forums and couldn't find anything quite like what I am experiencing. I know it is a beta program, but I thought I'd post anyway in hopes of maybe finding a solution.

I have tried several versions of BD Rebuilder to see if it was a version error, but its not. When Rebuilder goes to re-encode the video a Windows error pops up telling me x264.exe has stopped working. The problem details from Windows are as follows:

Problem Event Name: APPCRASH
Application Name: x264.exe
Application Version: 0.0.0.0
Application Timestamp: 4b1593c5
Fault Module Name: msvcrt.dll
Fault Module Version: 7.0.6002.18005
Fault Module Timestamp: 49e0379e
Exception Code: c0000005
Exception Offset: 0000a1a3
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033
Additional Information 1: fd00
Additional Information 2: ea6f5fe8924aaa756324d57f87834160
Additional Information 3: fd00
Additional Information 4: ea6f5fe8924aaa756324d57f87834160

And this is the log for BD Rebuilder:

[18:37:29] BD Rebuilder v0.31.04 (beta)
- Source: HURT_LOCKER
- Input BD size: 34.01 GB
- Approximate total content: [02:10:39.832]
- Target BD size: 7.72 GB
- Windows Version: 6.0 [6002]
- Audio Settings: AC3=1 DTS=1 HD=0 Kbs=640
[18:37:29] PHASE ONE, Encoding
- [18:37:29] Extracting A/V streams [VID_00001]
- [19:10:37] Reencoding: VID_00001 (1 of 1)
- Encode failed. Retrying.

Note that I am using 0.31.04 for this example, but I have tried it with the most current version and it still fails.

Is this a known error? Is there a way to fix it? Any help would be great.

Windows Vista 32bit SP2

And all the other apps (avisynth, etc...) are all installed correctly.

[jdobbs]

Looks like its crashing in msvcrt.dll... I believe that's a C runtime support module. I'd suggest you download and replace that module (from Microsoft). It's possible some other program has replaced for some reason.

If that doesn't do it -- I'd suspect memory or, if you're overclocked, your processor.

[setarip_old]

@StHapns247

Hi!

1) I successfully used BDRB to create a movie-only version of "The Hurt Locker" (U.S. version)

2) Have you previously successfully used BDRB with any BluRay discs?

3) As has been posted here several times, this thread is for tracking down new bugs. Therefore, you should not be using older versions of the program. Use ONLY the most recent version of BDRB, together with the supporting tools versions ONLY from Post #1 of this thread.

[StHapns247]

@StHapns247

Hi!

1) I successfully used BDRB to create a movie-only version of "The Hurt Locker" (U.S. version)

2) Have you previously successfully used BDRB with any BluRay discs?

3) As has been posted here several times, this thread is for tracking down new bugs. Therefore, you should not be using older versions of the program. Use ONLY the most recent version of BDRB, together with the supporting tools versions ONLY from Post #1 of this thread.

I get this error no matter what version I use... And this would be the first time I used BD Rebuilder.. Ever.

And jdobbs suggestion didn't seem to work... Reinstalling Visual C+++ didn't replace the msvcrt.dll file.

[jdobbs]

I get this error no matter what version I use... And this would be the first time I used BD Rebuilder.. Ever.

And jdobbs suggestion didn't seem to work... Reinstalling Visual C+++ didn't replace the msvcrt.dll file.How old is your C++ package? It's possible that the one it is installing is older than the one that comes with Windows 7. The DLL in the system32 directory of my Windows 7 x64 install is dated 7/13/2009 and is 634,880 bytes in size. The one on my Windows 7 32 bit system is dated 7/13/2009 and is 690,688 bytes in size.

Also, is your system overclocked?

[StHapns247]

The msvcrt.dll was created on October 22, 2009 and is 679,936 bytes. The file version is 7.0.6002.18005 and the product version is 6.1.8638.18005.

I cannot delete the file manually and replace it either. Every time I try it says I do not have permission and I have tried literally everything to give myself total rights to it... There is not deleting the .dll.

[jlm86]

regarding the x264.exe stopped working....I DID installl a Core AVC program a few weeks ago for PS3 Media Server codecs....i will test uninstall and report results

[jlm86]

still issues:
-----------------------
[05:10:23] BD Rebuilder v0.39.01 (beta)
- Source: REVENGE_OF_THE_SITH
- Input BD size: 40.37 GB
- Approximate total content: [02:20:05.855]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- MOVIE-ONLY mode enabled
- Auto Quality: Good (Very Fast), ABR
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[05:10:23] PHASE ONE, Encoding
- [05:10:23] Processing: VID_00300 (1 of 2)
- [05:10:23] Extracting A/V streams [VID_00300]
- [05:21:44] Reencoding video [VID_00300]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 2,964 frames
- Bitrate: 19,229 Kbs
- [05:21:44] Reencoding: VID_00300, Pass 1 of 1
- [05:26:52] Video Encode complete
- [05:26:52] Reencoding audio tracks (if req'd)
- [05:26:52] Multiplexing M2TS
- [05:27:01] Processing: VID_00301 (2 of 2)
- [05:27:01] Extracting A/V streams [VID_00301]
- [05:51:18] Reencoding video [VID_00301]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 198,575 frames
- Bitrate: 19,850 Kbs
- [05:51:18] Reencoding: VID_00301, Pass 1 of 1
- Encode failed. Retrying.
- Encode failed. Retrying.
- Reached retry limit. Aborting.
- BD-Rebuilder v0.39.01 (beta)
- Windows Version: 6.1 [7601]
- AVISYNTH Version: 2.5.8.0, Ok
- HAALI Splitter: 1.11.96.14, Ok
- FFDSHOW: 3882, Ok
- WIN7 preferred AVC CODEC: Ok
- WIN7 preferred VC-1 CODEC: Ok
- WIN7 preferred MPEG2 CODEC: Ok
- FFDSHOW VC-1 set to "wmv9", Ok
- FFDSHOW MPEG2 set to "libavcodec": Ok
- FFDSHOW AVC set to "ffmpeg-mt": Ok
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
[05:51:22] - Failed video encode, aborte

[jdobbs]

@jim86

Is your system overclocked? After you removed CoreAVC, did you reinstall FFDSHOW? Sometimes external CODECs can disengage FFDSHOW, and when they are removed there is nothing to take their place.

[jlm86]

Yep, this did solve the x264.exe stopped working error i was getting....

Although, yes my cpu is overclocked, and took it down a notch also....

I run PS3 Media Server wihich allows the codecs from AVC Core to be implemented thru the PMS application..Might try to re-install...

Is the known issue of overclocking due to over-heating issue? Have used this overclocked cpu config. for long time with BD Rebuilder....

thanks for assistance....

[RobertM]

Is the known issue of overclocking due to over-heating issue? Have used this overclocked cpu config. for long time with BD Rebuilder....

I would imagine that your issue was a codec problem, not an overclock problem. Overclocking can cause stability issues if it is pushed too far, and video encoding is demanding on the system. But is sounds like your system wasn't exhibiting any previous stability issues, so it is much more likely that the codec fix was what did the trick.

Should be a pretty simple test, though. Return to your default OC profile and see if the x264 error returns.

[jdobbs]

Yep, this did solve the x264.exe stopped working error i was getting....

Although, yes my cpu is overclocked, and took it down a notch also....

I run PS3 Media Server wihich allows the codecs from AVC Core to be implemented thru the PMS application..Might try to re-install...

Is the known issue of overclocking due to over-heating issue? Have used this overclocked cpu config. for long time with BD Rebuilder....

thanks for assistance.... Usually overheating -- not always, though. X264 really pushes the CPU to its limits -- in fact I've found it is a better test of stability than Prime95 or any of those other tests. In your case I think CoreAVC was more likely the issue.

If you do install CoreAVC, make sure you uninstall/reinstall FFDSHOW after... that might fix it, but not sure.

[samuelfi13]

I also installed CoreAVC on a Windows 7 (64-bit) system and had probems similar to the ones you describe. When I ran the "Inspect.exe" program that comes with BDRB, I noticed that it reported that FFDSHOW VC-1 was set to something other than "wmv9". (I think CoreAVC was listed there instead, but I'm not sure now.) What worked for me, believe it not, was to simply run BDRB "as administrator". When I ran Inspect.exe again it read FFDSHOW VC-1 set to "wmv9", Ok and everything has worked fine ever since.

Samuel