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.

 

Go Back   Doom9's Forum > (HD) DVD, Blu-ray & (S)VCD > (HD) DVD & Blu-ray authoring

Reply
 
Thread Tools Search this Thread Display Modes
Old 8th December 2017, 01:19   #1341  |  Link
r0lZ
PgcEdit daemon
 
r0lZ's Avatar
 
Join Date: Jul 2003
Posts: 7,085
I see. Unfortunately, there is nothing I can do, except release a new version of BD3D2MK3D with the last good x264, or wait the next x264 version and hope that it will be fixed. Anyway, the problem doesn't come from my code, as nothing has changed in the x264 command and the way it is launched.

Perhaps you could try to contact the x264 devs ? I can't do it myself, as I don't have the problem. And I will be grateful if you can check the next stable release of x264 before I release it with BD3D2MK3D.
__________________
r0lZ
PgcEdit homepage (hosted by VideoHelp)
BD3D2MK3D A tool to convert 3D blu-rays to SBS, T&B or FS MKV
r0lZ is offline   Reply With Quote
Old 8th December 2017, 10:31   #1342  |  Link
Wildfire
Registered User
 
Join Date: Apr 2003
Location: the Netherlands
Posts: 145
Hmmm.... tried a new encode and while I absolutely swear I had x264 crashes before, now avs2yuv.exe crashes...

From Windows log files (in Dutch, but the relevant parts will be understandable):

Quote:
Naam van toepassing met fout: avs2yuv.exe, versie: 0.0.0.0, tijdstempel: 0x4228f465
Naam van module met fout: ntdll.dll, versie: 10.0.16299.64, tijdstempel: 0xac8afc81
Uitzonderingscode: 0xc0000005
Foutmarge: 0x0003f500
Id van proces met fout: 0x2060
Starttijd van toepassing met fout: 0x01d37006d002b8e3
Pad naar toepassing met fout: C:\Program Files (x86)\BD3D2MK3D\toolset\avs2yuv.exe
Pad naar module met fout: C:\Windows\SYSTEM32\ntdll.dll
Rapport-id: e0af5b8c-0f0a-4cad-8098-85fd22ef646b
Volledige pakketnaam met fout:
Relatieve toepassings-id van pakket met fout:

Quote:
Foutbucket 1460961521198399896, type 1
Naam van gebeurtenis: APPCRASH
Antwoord: Niet beschikbaar
Id van CAB-bestand: 0

Handtekening van probleem:
P1: avs2yuv.exe
P2: 0.0.0.0
P3: 4228f465
P4: ntdll.dll
P5: 10.0.16299.64
P6: ac8afc81
P7: c0000005
P8: 0003f500
P9:
P10:

Toegevoegde bestanden:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4A2B.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4C7F.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4C8A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4CCA.tmp.txt

Deze bestanden zijn mogelijk hier beschikbaar:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_avs2yuv.exe_81c98f127b2e509fff6fa7907dd996155560da26_b83b6774_2f30597b

Analysesymbool:
Opnieuw zoeken naar oplossing: 0
Rapport-id: e0af5b8c-0f0a-4cad-8098-85fd22ef646b
Rapportstatus: 268435456
Opgedeelde bucket: 55069c1852968d10c44660c3558b8198
Wildfire is offline   Reply With Quote
Old 8th December 2017, 12:52   #1343  |  Link
r0lZ
PgcEdit daemon
 
r0lZ's Avatar
 
Join Date: Jul 2003
Posts: 7,085
OK, that seems to confirm that there is something wrong with avisynth or the original BD (or 3D MKV).

If you use the 32-bit version of x264 (not x265), avs2yuv is not necessary and therefore not used. x264 loads the avisynth script directly. It might be a good idea to test that with the same source, as we will know if avs2yuv is the culprit.

Also, you can try to use another version of avs2yuv. There are 4 versions here. Of course, the 64-bit version is not suitable. The version distributed with BD3D2MK3D is 0.24, but its size is 52KB. All komisar builds have a different size, so try the 3 32-bit versions.

I note also that ntdll.dll is involved in the crash. Perhaps it is the real culprit. Could it be caused by a recent M$ update ? What version of Windows do you use ?
__________________
r0lZ
PgcEdit homepage (hosted by VideoHelp)
BD3D2MK3D A tool to convert 3D blu-rays to SBS, T&B or FS MKV
r0lZ is offline   Reply With Quote
Old 8th December 2017, 22:50   #1344  |  Link
Wildfire
Registered User
 
Join Date: Apr 2003
Location: the Netherlands
Posts: 145
I'm on Windows 10 Pro 64-bit, fully up-to-date (Fall Creators Update including all updates up to today).

I managed to get a x264 crash. It crashes when starting the 2nd pass... and that's with the 32-bit x264.

Quote:
Naam van toepassing met fout: x264_8bit_x86.exe, versie: 0.152.2851.0, tijdstempel: 0x59581c4e
Naam van module met fout: x264_8bit_x86.exe, versie: 0.152.2851.0, tijdstempel: 0x59581c4e
Uitzonderingscode: 0xc0000005
Foutmarge: 0x0002199e
Id van proces met fout: 0x1278
Starttijd van toepassing met fout: 0x01d37012a63aefb1
Pad naar toepassing met fout: C:\Program Files (x86)\BD3D2MK3D\toolset\x264_8bit_x86.exe
Pad naar module met fout: C:\Program Files (x86)\BD3D2MK3D\toolset\x264_8bit_x86.exe
Rapport-id: fd94f01d-190b-4506-b020-f73162ef25f7
Volledige pakketnaam met fout:
Relatieve toepassings-id van pakket met fout:
Quote:
Foutbucket 1409739612789152407, type 1
Naam van gebeurtenis: APPCRASH
Antwoord: Niet beschikbaar
Id van CAB-bestand: 0

Handtekening van probleem:
P1: x264_8bit_x86.exe
P2: 0.152.2851.0
P3: 59581c4e
P4: x264_8bit_x86.exe
P5: 0.152.2851.0
P6: 59581c4e
P7: c0000005
P8: 0002199e
P9:
P10:

Toegevoegde bestanden:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8597.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8A3D.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8A49.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8A88.tmp.txt

Deze bestanden zijn mogelijk hier beschikbaar:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_x264_8bit_x86.ex_d7f63a3eaf768c27dd490e86c91523ad361c83_7283c821_12b59025

Analysesymbool:
Opnieuw zoeken naar oplossing: 0
Rapport-id: fd94f01d-190b-4506-b020-f73162ef25f7
Rapportstatus: 268435456
Opgedeelde bucket: 8f75c02b66029f43539066b56e181a97
(and, as stated before, the issue also occurs on another computer, so a software issue seems most likely)

Last edited by Wildfire; 8th December 2017 at 22:52.
Wildfire is offline   Reply With Quote
Old 9th December 2017, 12:02   #1345  |  Link
r0lZ
PgcEdit daemon
 
r0lZ's Avatar
 
Join Date: Jul 2003
Posts: 7,085
Yes, it seems that it's x264 that has a bug, but if x264 crashes sometimes then avs2yuv or even ntdll.dll, it is not easy to know where the bug really is. Is your other machine also running Windows 10 ?

Usually, I encode in CRF, but to check if I can reproduce the problem, I have just finished a 2-pass encoding of a (very small) clip, and it has not crashed. I'm still using Win7 (64-bit) because Win10 is currently still very unstable, and I hate that OS. Maybe there is something specific in Win10 that is not compatible with x264 ? But I suppose that someone else using Win10 and having experienced similar problems would have replied to this thread. It's why I persist to think that there is something wrong with your machine(s). The question is what !

Also, may I know why you encode in 2-pass ? As I've already explained several times (for example here), it is always a bad idea to use 2-pass, unless you need to control exactly the final file size (for example to burn the final MKV on a DVD). So, if it's when starting the second pass that x264 crashes, I strongly suggest to use CRF instead. You will obtain a slightly better quality for the same file size, and no crash any more! ;-)

But of course, it will be better to know why the crash occurs...
__________________
r0lZ
PgcEdit homepage (hosted by VideoHelp)
BD3D2MK3D A tool to convert 3D blu-rays to SBS, T&B or FS MKV
r0lZ is offline   Reply With Quote
Old 9th December 2017, 14:57   #1346  |  Link
Wildfire
Registered User
 
Join Date: Apr 2003
Location: the Netherlands
Posts: 145
Quote:
Originally Posted by r0lZ View Post
Yes, it seems that it's x264 that has a bug, but if x264 crashes sometimes then avs2yuv or even ntdll.dll, it is not easy to know where the bug really is. Is your other machine also running Windows 10 ?

Usually, I encode in CRF, but to check if I can reproduce the problem, I have just finished a 2-pass encoding of a (very small) clip, and it has not crashed. I'm still using Win7 (64-bit) because Win10 is currently still very unstable, and I hate that OS. Maybe there is something specific in Win10 that is not compatible with x264 ? But I suppose that someone else using Win10 and having experienced similar problems would have replied to this thread. It's why I persist to think that there is something wrong with your machine(s). The question is what !

Also, may I know why you encode in 2-pass ? As I've already explained several times (for example here), it is always a bad idea to use 2-pass, unless you need to control exactly the final file size (for example to burn the final MKV on a DVD). So, if it's when starting the second pass that x264 crashes, I strongly suggest to use CRF instead. You will obtain a slightly better quality for the same file size, and no crash any more! ;-)

But of course, it will be better to know why the crash occurs...

Windows 10 unstable? Not in my experience, in fact it's the exact opposite: it's really stable. Both my computers (yes, both Windows 10) run really smooth, I have no problems at all other than some crashes with BD3D2MK3D. And those crashes started occuring recently on both systems (before that, I already did dozens of encodes on both machines without any problem at all), although I cannot pinpoint exactly when that was...

To be sure, recently I performed several hardware tests (storage, memory, CPU) and no problems popped up. Even under extreme stress my system runs fine and no CPU overheating or anything like that.

Why 2-pass? Well, you may explain CRF into the most obscure details if you want, but I still think that 2-pass encoding at best settings just "feels" better to me. Also, I really like having a predictable file size even though the encodes go to my NAS which has ample storage space.
Wildfire is offline   Reply With Quote
Old 9th December 2017, 15:50   #1347  |  Link
r0lZ
PgcEdit daemon
 
r0lZ's Avatar
 
Join Date: Jul 2003
Posts: 7,085
I have not a great experience of Win10 (although I have a partition with Win10 on the Win7 PC but I don't use it often). But I follow the RSS feed of The Windows Club, and although they are real M$ enthusiasts, almost every day they reveal a new problem with Win10. In the other hand, Win7 is old, but without the garbage of the new Windows "universal" apps, and totally stable (although they have made a questionable update recently). Anyway, on my machine, I can't reproduce the x264 problem. I must agree that that doesn't mean that it is more stable because the problem might be caused by other things (the CPU for example), but in the absence of another explanation, I must accuse the OS.

According to the x264 authors themselves, 2-pass is slightly less good because specifying a bitrate constraints the encoding between rigid walls. CRF use exactly the same encoding algorithms, but without any constraint. It is therefore free to use the most appropriate bitrate during the whole movie. 2-pass is of course much better than 1-pass ABR because the first pass is used to evaluate approximately what bitrate to use for the different parts of the movie, but it cannot predict exactly the final bitrate. Hence the slight quality difference with CRF. Unfortunately, there are many web sites that suggest to use 2-pass for the best quality, but it's because they are not well informed or their suggestions apply only to encoders without CRF (like the old encoder of DVDFab that had only 1 or 2-pass). Anyway, I just wanted to suggest to use CRF to avoid the crash during the second pass. You are of course free to use 2-pass if you want.
__________________
r0lZ
PgcEdit homepage (hosted by VideoHelp)
BD3D2MK3D A tool to convert 3D blu-rays to SBS, T&B or FS MKV
r0lZ is offline   Reply With Quote
Old 15th December 2017, 22:10   #1348  |  Link
viperlogic
Registered User
 
Join Date: Dec 2017
Posts: 1
Getting x264 crashes on both win7 (32-bit) and win10 (64-bit) immediately when running __encode_3D.cmd. Windows pop up window of "H.264 (MPEG-4 AVC) encoder has stopped working".

Win7....
Problem signature:
Problem Event Name: BEX
Application Name: x264_8bit_x86.exe
Application Version: 0.152.2851.0
Application Timestamp: 59581c4e
Fault Module Name: FRIMSource.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 596070dd
Exception Offset: 0002ca2c
Exception Code: c0000417
Exception Data: 00000000
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 6153
Additional Information 1: 2d06
Additional Information 2: 2d069ee6c3d46ad12eaf589f86850707
Additional Information 3: 633c
Additional Information 4: 633c17c95b8b015860e3dddcf1a1cd9a


win10...
Log Name: Application
Source: Application Error
Date: 15/12/2017 21:17:07
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: ADMINRG-T59RE8R
Description:
Faulting application name: x264_8bit_x86.exe, version: 0.152.2851.0, time stamp: 0x59581c4e
Faulting module name: FRIMSource.dll, version: 0.0.0.0, time stamp: 0x596070dd
Exception code: 0xc0000409
Fault offset: 0x0002ca1a
Faulting process id: 0xeec
Faulting application start time: 0x01d375ea0f98f4a8
Faulting application path: C:\Users\johndoe\Downloads\BD3D2MK3D\BD3D2MK3D\toolset\x264_8bit_x86.exe
Faulting module path: C:\Users\johndoe\Downloads\BD3D2MK3D\BD3D2MK3D\toolset\FRIMSource.dll
Report Id: 3132e220-e0a2-4fc5-9cf2-256e90da8568
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-12-15T21:17:07.601977900Z" />
<EventRecordID>1714</EventRecordID>
<Channel>Application</Channel>
<Computer>ADMINRG-T59RE8R</Computer>
<Security />
</System>
<EventData>
<Data>x264_8bit_x86.exe</Data>
<Data>0.152.2851.0</Data>
<Data>59581c4e</Data>
<Data>FRIMSource.dll</Data>
<Data>0.0.0.0</Data>
<Data>596070dd</Data>
<Data>c0000409</Data>
<Data>0002ca1a</Data>
<Data>eec</Data>
<Data>01d375ea0f98f4a8</Data>
<Data>C:\Users\johndoe\Downloads\BD3D2MK3D\BD3D2MK3D\toolset\x264_8bit_x86.exe</Data>
<Data>C:\Users\johndoe\Downloads\BD3D2MK3D\BD3D2MK3D\toolset\FRIMSource.dll</Data>
<Data>3132e220-e0a2-4fc5-9cf2-256e90da8568</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

This is against the Valerian and the City of a thousand planets 1080p 3D ISO by ESiR release group

Let me know what logs are required to further troubleshoot. Thx

Last edited by viperlogic; 15th December 2017 at 22:27.
viperlogic is offline   Reply With Quote
Old Yesterday, 11:07   #1349  |  Link
r0lZ
PgcEdit daemon
 
r0lZ's Avatar
 
Join Date: Jul 2003
Posts: 7,085
It seems that you are experiencing the same problem that Wildfire has reported above. Can you try another version of x264 (older here, or another build here or here) ? Unfortunately, I can't reproduce the problem so I can't check myself.

Also, I note in your two logs "Fault Module Name: FRIMSource.dll", so the problem might be caused by FRIMSource as well. So, please try to set Settings -> MVC Decoder -> Use DGMVCSource and/or set the Hardware Acceleration to Disabled.

Thanks anyway for having reported the problem, and welcome to the Doom9 forum, viperlogic !
__________________
r0lZ
PgcEdit homepage (hosted by VideoHelp)
BD3D2MK3D A tool to convert 3D blu-rays to SBS, T&B or FS MKV

Last edited by r0lZ; Yesterday at 11:20.
r0lZ is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 09:04.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2017, vBulletin Solutions Inc.