Crash - Windows 7 - 64

[Former user]

It will normally process 2-4 clips before crashing. Larger clips, 2000+ frames, might crash mid conversion. I also noticed that it will start on one clip then try to process a second or a third before crashing.

I had several crashes before giving up and switched to MLV Converter 1.9.2, which, so far, is running just fine, and has proved to be bullet proof. No problems.

The Windows crash reports are below, logs are attached.

After crash #2, I rebooted and did not open any other app, still crashed.

After crash #3 I opened the SYSCONFIG and clicked "Selective Start up, clicked the services tab, clicked the "Hide all Microsoft Services" then unchecked all but a handful of items. I then clicked the startup tab and unchecked most everything. Still crashed.

Thank you!

Problem signature: Problem Event Name: APPCRASH Application Name: mlrawviewer.exe Application Version: 0.0.0.0 Application Timestamp: 514e2c2f Fault Module Name: bitunpack.pyd Fault Module Version: 0.0.0.0 Fault Module Timestamp: 544160fa Exception Code: c0000005 Exception Offset: 00002a33 OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional Information 1: 0a9e Additional Information 2: 0a9e372d3b4ad19135b953a78882e789 Additional Information 3: 0a9e Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

---

Problem signature: Problem Event Name: APPCRASH Application Name: mlrawviewer.exe Application Version: 0.0.0.0 Application Timestamp: 514e2c2f Fault Module Name: ntdll.dll Fault Module Version: 6.1.7601.18247 Fault Module Timestamp: 521ea8e7 Exception Code: c0000005 Exception Offset: 000343e0 OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional Information 1: 0a9e Additional Information 2: 0a9e372d3b4ad19135b953a78882e789 Additional Information 3: 0a9e Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

---

Problem signature: Problem Event Name: APPCRASH Application Name: mlrawviewer.exe Application Version: 0.0.0.0 Application Timestamp: 514e2c2f Fault Module Name: python27.dll Fault Module Version: 2.7.6150.1013 Fault Module Timestamp: 527fcf52 Exception Code: c0000005 Exception Offset: 000f9615 OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional Information 1: 0a9e Additional Information 2: 0a9e372d3b4ad19135b953a78882e789 Additional Information 3: 0a9e Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

---

Problem signature: Problem Event Name: APPCRASH Application Name: mlrawviewer.exe Application Version: 0.0.0.0 Application Timestamp: 514e2c2f Fault Module Name: python27.dll Fault Module Version: 2.7.6150.1013 Fault Module Timestamp: 527fcf52 Exception Code: c0000005 Exception Offset: 000f9615 OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional Information 1: 0a9e Additional Information 2: 0a9e372d3b4ad19135b953a78882e789 Additional Information 3: 0a9e Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

[Andrew Baldwin]

I noticed a couple of strange things in the log - one python exception which could only happen if a frame with no frames is found (divide by zero). That's quite an odd situation for the program to be in since it must have loaded an otherwise valid MLV file.

The other thing was that your MLV file names don't have the usual naming structure (Mxx-nnnn.MLV) and there are no split files. Did you rename them manually or some other way? Is it possible, for instance, that some .Mnn split files got renamed to .MLV by accident? That could certainly cause trouble. Otherwise how large are the files - more than 4GB?