Access Violation Error on VIDEO PRO14

JBDL wrote on 8/30/2022, 10:55 AM

Since installing MAGIX update for VIDEO PRO 14 the software doesn't work. I've uninstalled it a few times, refreshed it and now I'm fed up with it. Please can someone help me before losing complete will to live? I am NOT COMPUTER LITERATE. I only know what I've found interesting and this has finally done the head! Thank you in the hope that someone can help me..

Comments

CubeAce wrote on 8/30/2022, 11:32 AM

@JBDL

Hi.

When after the crash, you open the project again you should get a box requesting that you send a crash report in to Magix. Within that information box there should be the ability to see the crash report.

We would need to see that crash report posted here to try to understand what happened.

I personally probably could not make sense of that crash report but there may be one or two others here that can.

Ray.

 

 

Windows 10 Enterprise. Version 22H2 OS build 19045.5011

Direct X 12.1 latest hardware updates for Western Digital hard drives.

Asus ROG STRIX Z390-F Gaming motherboard Rev 1.xx with Supreme FX inboard audio using the S1220A code. Driver No 6.0.8960.1 Bios version 1401

Intel i9900K Coffee Lake 3.6 to 5.1GHz CPU with Intel UHD 630 Graphics .Driver version Graphics Driver 31.0.101.2130 for 7th-10th Gen Intel® with 64GB of 3200MHz Corsair DDR4 ram.

1000 watt EVGA modular power supply.

1 x 250GB Evo 970 NVMe: drive for C: drive backup 1 x 1TB Sabrent NVMe drive for Operating System / Programs only. 1X WD BLACK 1TB internal SATA 7,200rpm hard drives.1 for internal projects, 1 for Library clips/sounds/music/stills./backup of working projects. 1x500GB SSD current project only drive, 2x WD RED 2TB drives for latest footage storage. Total 21TB of 8 external WD drives for backup.

ASUS NVIDIA GeForce RTX 3060 12GB. nVidia Studio driver version 572.16 - 3584xCUDA cores Direct X 12.1. Memory interface 192bit Memory bandwidth 360.05GB/s 12GB of dedicated GDDR6 video memory, shared system memory 16307MB PCi Express x8 Gen3. Two Samsung 27" LED SA350 monitors with 5000000:1 contrast ratios at 60Hz.

Running MMS 2024 Suite v 23.0.1.182 (UDP3) and VPX 14 - v20.0.3.180 (UDP3)

M Audio Axiom AIR Mini MIDI keyboard Ver 5.10.0.3507

VXP 14, MMS 2024 Suite, Vegas Studio 16, Vegas Pro 18, Cubase 4. CS6, NX Studio, Mixcraft 9 Recording Studio. Mixcraft Pro 10 Studio.

Audio System 5 x matched bi-wired 150 watt Tannoy Reveal speakers plus one Tannoy 15" 250 watt sub with 5.1 class A amplifier. Tuned to room with Tannoy audio application.

Ram Acoustic Studio speakers amplified by NAD amplifier.

Rogers LS7 speakers run from Cambridge Audio P50 amplifier

Schrodinger's Backup. "The condition of any backup is unknown until a restore is attempted."

JBDL wrote on 8/30/2022, 1:19 PM

Ray, thank you for coming back to me. Here is the information of the crash report.....

----------------------------------------------------------------------
MAGIX Video Pro X14  30.08.2022  13:18
----------------------------------------------------------------------
CrashDump 20220830_131807_v20.0.3.169.dmp successfully written

Error in module "video_pro_x.exe" (Load address: 0x0000000140000000) to address 0x00000001402E258F (Exception 0xc0000005 "ACCESS_VIOLATION")

Main Thread   (ThreadID: 00003868)
  00000001402e2587   50 48 8b 89 f8 00 00 00
  00000001402e258f > 48 8b 01 4c 8d 4c 24 50
  00000001402e2597   45 33 c0 49 8b d2 ff 50

video_pro_x.exe    23.08.2022  10:56      4e8bf0fa

Memory Allocation
Base:        968
PE:        176
Pages:        65.536

PI:        7.872
PI_TEMP_DATA:    9.944
SI:        152.360
SI_TEMP_DATA:    43.752
FSI:        0

Blocks:        0
Temporary:    1.502.816
BE:        0
PLE:        0
BE Pool:        48
PLE Pool:        0
wHdr/inst:    0
Image Cache:    0
Video:        3.372.154(0/0)
Bitmap:        0

Thumbnail Cache:    0
SI Display Cache:    2.502.000
PLE Display Cache:    0

Buffer:        0
Pointer:        0

Title:        0
Memory GF:        0
Memory GF Zero:        0
Memory GF Zero_Dyn:        0
Memory GF Dyn:        0
Memory TT:        0
Audio Effect:        0
PPE:        0

Video Monitor:    0
malloc/free:    0
DIB:        0

VP: admin:        0
VP+Trans: privateData:        0
Transitions::        0

Frame Cache:    0
EXIF:        0
VSW:        0
DVDMAKER:    0
global UI (malloc):    0
global UI (valloc):    50.331.648
NOWAGGLE:    0
ReaderFrame:    0
MP3 Reader:    0
JPEG buffer:    0

Private Bytes:    527 MByte

TLS:        981
MXGUI:        87.641.540
Sum:        145.719.902

Processor [46]  3492MHz  4 Core(s)
Microsoft Windows NT 10.0 (Build 19044)
Used Memory: 865 MB             Max Used Memory: 865 MB
Free Virtual Memory: 25030 MB     Total Virtual Memory: 131072 GB

 Call stack:
Address   Frame
00000001402E258F  0000000000149A00  boost::serialization::singleton_module::unlock+AE3BF
00000001402E1F33  0000000000149BD0  boost::serialization::singleton_module::unlock+ADD63
00000001402E221D  0000000000149C40  boost::serialization::singleton_module::unlock+AE04D
00000001402D9E9A  0000000000149C90  boost::serialization::singleton_module::unlock+A5CCA
00000001401B2DEF  0000000000149CC0  boost::archive::codecvt_null<wchar_t>::do_encoding+A49BF
00007FFEB621CF0C  0000000000149CC8  0001:0001BF0C C:\Program Files\MAGIX\Video Pro X14\RegModule_x64\mxmpeg2_x64.dll
0000000000000001  0000000000149CD0  0000:00000000 C:\Program Files\MAGIX\Video Pro X14\video_pro_x.exe
0000000000149D80  0000000000149CD8  0000:00000000


----------------------------------------------------------------------
MAGIX Video Pro X14  30.08.2022  13:35
----------------------------------------------------------------------
CrashDump 20220830_133529_v20.0.3.169.dmp successfully written

Error in module "video_pro_x.exe" (Load address: 0x0000000140000000) to address 0x00000001402E258F (Exception 0xc0000005 "ACCESS_VIOLATION")

Main Thread   (ThreadID: 00002c38)
  00000001402e2587   50 48 8b 89 f8 00 00 00
  00000001402e258f > 48 8b 01 4c 8d 4c 24 50
  00000001402e2597   45 33 c0 49 8b d2 ff 50

video_pro_x.exe    23.08.2022  10:56      4e8bf0fa

Memory Allocation
Base:        968
PE:        176
Pages:        65.536

PI:        7.872
PI_TEMP_DATA:    9.944
SI:        152.360
SI_TEMP_DATA:    43.752
FSI:        0

Blocks:        0
Temporary:    1.502.816
BE:        0
PLE:        0
BE Pool:        48
PLE Pool:        0
wHdr/inst:    0
Image Cache:    0
Video:        3.372.154(0/0)
Bitmap:        0

Thumbnail Cache:    0
SI Display Cache:    2.502.000
PLE Display Cache:    0

Buffer:        0
Pointer:        0

Title:        0
Memory GF:        0
Memory GF Zero:        0
Memory GF Zero_Dyn:        0
Memory GF Dyn:        0
Memory TT:        0
Audio Effect:        0
PPE:        0

Video Monitor:    0
malloc/free:    0
DIB:        0

VP: admin:        0
VP+Trans: privateData:        0
Transitions::        0

Frame Cache:    0
EXIF:        0
VSW:        0
DVDMAKER:    0
global UI (malloc):    0
global UI (valloc):    50.331.648
NOWAGGLE:    0
ReaderFrame:    0
MP3 Reader:    0
JPEG buffer:    0

Private Bytes:    522 MByte

TLS:        982
MXGUI:        87.641.540
Sum:        145.719.902

Processor [46]  3482MHz  4 Core(s)
Microsoft Windows NT 10.0 (Build 19044)
Used Memory: 860 MB             Max Used Memory: 861 MB
Free Virtual Memory: 24718 MB     Total Virtual Memory: 131072 GB

 Call stack:
Address   Frame
00000001402E258F  0000000000149A00  boost::serialization::singleton_module::unlock+AE3BF
00000001402E1F33  0000000000149BD0  boost::serialization::singleton_module::unlock+ADD63
00000001402E221D  0000000000149C40  boost::serialization::singleton_module::unlock+AE04D
00000001402D9E9A  0000000000149C90  boost::serialization::singleton_module::unlock+A5CCA
00000001401B2DEF  0000000000149CC0  boost::archive::codecvt_null<wchar_t>::do_encoding+A49BF
00007FFE908ECF0C  0000000000149CC8  0001:0001BF0C C:\Program Files\MAGIX\Video Pro X14\RegModule_x64\mxmpeg2_x64.dll
0000000000000001  0000000000149CD0  0000:00000000 C:\Program Files\MAGIX\Video Pro X14\video_pro_x.exe
0000000000149D80  0000000000149CD8  0000:00000000


----------------------------------------------------------------------
MAGIX Video Pro X14  30.08.2022  14:42
----------------------------------------------------------------------
CrashDump 20220830_144204_v20.0.3.169.dmp successfully written

Error in module "video_pro_x.exe" (Load address: 0x0000000140000000) to address 0x00000001402E258F (Exception 0xc0000005 "ACCESS_VIOLATION")

Main Thread   (ThreadID: 00002498)
  00000001402e2587   50 48 8b 89 f8 00 00 00
  00000001402e258f > 48 8b 01 4c 8d 4c 24 50
  00000001402e2597   45 33 c0 49 8b d2 ff 50

video_pro_x.exe    23.08.2022  10:56      4e8bf0fa

Memory Allocation
Base:        968
PE:        176
Pages:        65.536

PI:        7.872
PI_TEMP_DATA:    9.944
SI:        152.360
SI_TEMP_DATA:    43.752
FSI:        0

Blocks:        0
Temporary:    1.502.816
BE:        0
PLE:        0
BE Pool:        48
PLE Pool:        0
wHdr/inst:    0
Image Cache:    0
Video:        3.372.154(0/0)
Bitmap:        0

Thumbnail Cache:    0
SI Display Cache:    2.502.000
PLE Display Cache:    0

Buffer:        0
Pointer:        0

Title:        0
Memory GF:        0
Memory GF Zero:        0
Memory GF Zero_Dyn:        0
Memory GF Dyn:        0
Memory TT:        0
Audio Effect:        0
PPE:        0

Video Monitor:    0
malloc/free:    0
DIB:        0

VP: admin:        0
VP+Trans: privateData:        0
Transitions::        0

Frame Cache:    0
EXIF:        0
VSW:        0
DVDMAKER:    0
global UI (malloc):    0
global UI (valloc):    50.331.648
NOWAGGLE:    0
ReaderFrame:    0
MP3 Reader:    0
JPEG buffer:    0

Private Bytes:    514 MByte

TLS:        982
MXGUI:        87.641.540
Sum:        145.719.902

Processor [46]  3491MHz  4 Core(s)
Microsoft Windows NT 10.0 (Build 19044)
Used Memory: 852 MB             Max Used Memory: 853 MB
Free Virtual Memory: 25032 MB     Total Virtual Memory: 131072 GB

 Call stack:
Address   Frame
00000001402E258F  0000000000149A00  boost::serialization::singleton_module::unlock+AE3BF
00000001402E1F33  0000000000149BD0  boost::serialization::singleton_module::unlock+ADD63
00000001402E221D  0000000000149C40  boost::serialization::singleton_module::unlock+AE04D
00000001402D9E9A  0000000000149C90  boost::serialization::singleton_module::unlock+A5CCA
00000001401B2DEF  0000000000149CC0  boost::archive::codecvt_null<wchar_t>::do_encoding+A49BF
00007FFE9D98CF0C  0000000000149CC8  0001:0001BF0C C:\Program Files\MAGIX\Video Pro X14\RegModule_x64\mxmpeg2_x64.dll
0000000000000001  0000000000149CD0  0000:00000000 C:\Program Files\MAGIX\Video Pro X14\video_pro_x.exe
0000000000149D80  0000000000149CD8  0000:00000000


----------------------------------------------------------------------
MAGIX Video Pro X14  30.08.2022  16:26
----------------------------------------------------------------------
CrashDump 20220830_162617_v20.0.3.169.dmp successfully written

Error in module "Video_Pro_X.exe" (Load address: 0x0000000140000000) to address 0x00000001402E258F (Exception 0xc0000005 "ACCESS_VIOLATION")

Unknown Thread   (ThreadID: 00001824)
  00000001402e2587   50 48 8b 89 f8 00 00 00
  00000001402e258f > 48 8b 01 4c 8d 4c 24 50
  00000001402e2597   45 33 c0 49 8b d2 ff 50

Main Thread
  fffffffffffffff8   ?? ?? ?? ?? ?? ?? ?? ??
  0000000000000000 > ?? ?? ?? ?? ?? ?? ?? ??
  0000000000000008   ?? ?? ?? ?? ?? ?? ?? ??

video_pro_x.exe    23.08.2022  10:56      4e8bf0fa

Memory Allocation
Base:        968
PE:        176
Pages:        65.536

PI:        5.248
PI_TEMP_DATA:    9.944
SI:        150.016
SI_TEMP_DATA:    43.752
FSI:        0

Blocks:        0
Temporary:    1.502.816
BE:        0
PLE:        0
BE Pool:        48
PLE Pool:        0
wHdr/inst:    0
Image Cache:    0
Video:        3.372.154(0/0)
Bitmap:        0

Thumbnail Cache:    0
SI Display Cache:    2.502.000
PLE Display Cache:    0

Buffer:        0
Pointer:        0

Title:        0
Memory GF:        0
Memory GF Zero:        0
Memory GF Zero_Dyn:        0
Memory GF Dyn:        0
Memory TT:        0
Audio Effect:        0
PPE:        0

Video Monitor:    0
malloc/free:    0
DIB:        0

VP: admin:        0
VP+Trans: privateData:        0
Transitions::        0

Frame Cache:    0
EXIF:        64
VSW:        0
DVDMAKER:    0
global UI (malloc):    0
global UI (valloc):    50.331.648
NOWAGGLE:    0
ReaderFrame:    0
MP3 Reader:    0
JPEG buffer:    0

Private Bytes:    619 MByte

TLS:        982
MXGUI:        87.641.540
Sum:        145.714.998

Processor [46]  3491MHz  4 Core(s)
Microsoft Windows NT 10.0 (Build 19044)
Used Memory: 951 MB             Max Used Memory: 955 MB
Free Virtual Memory: 23045 MB     Total Virtual Memory: 131072 GB

 Call stack:
Address   Frame
00000001402E258F  0000000041DEEB30  boost::serialization::singleton_module::unlock+AE3BF
00000001402E1F33  0000000041DEED00  boost::serialization::singleton_module::unlock+ADD63
00000001402E221D  0000000041DEED70  boost::serialization::singleton_module::unlock+AE04D
00000001402D9E9A  0000000041DEEDC0  boost::serialization::singleton_module::unlock+A5CCA
00000001401B2DEF  0000000041DEEDF0  boost::archive::codecvt_null<wchar_t>::do_encoding+A49BF
00007FFE94ADCF0C  0000000041DEEDF8  0001:0001BF0C C:\Program Files\MAGIX\Video Pro X14\RegModule_x64\mxmpeg2_x64.dll
0000000000000001  0000000041DEEE00  0000:00000000 C:\Program Files\MAGIX\Video Pro X14\Video_Pro_X.exe
0000000041DEEEB0  0000000041DEEE08  0000:00000000


----------------------------------------------------------------------
MAGIX Video Pro X14  30.08.2022  16:52
----------------------------------------------------------------------
CrashDump 20220830_165241_v20.0.3.169.dmp successfully written

Error in module "video_pro_x.exe" (Load address: 0x0000000140000000) to address 0x00000001402E258F (Exception 0xc0000005 "ACCESS_VIOLATION")

Unknown Thread   (ThreadID: 00003790)
  00000001402e2587   50 48 8b 89 f8 00 00 00
  00000001402e258f > 48 8b 01 4c 8d 4c 24 50
  00000001402e2597   45 33 c0 49 8b d2 ff 50

Main Thread
  fffffffffffffff8   ?? ?? ?? ?? ?? ?? ?? ??
  0000000000000000 > ?? ?? ?? ?? ?? ?? ?? ??
  0000000000000008   ?? ?? ?? ?? ?? ?? ?? ??

video_pro_x.exe    23.08.2022  10:56      4e8bf0fa

Memory Allocation
Base:        968
PE:        176
Pages:        65.536

PI:        5.248
PI_TEMP_DATA:    9.944
SI:        150.016
SI_TEMP_DATA:    43.752
FSI:        0

Blocks:        0
Temporary:    1.502.816
BE:        0
PLE:        0
BE Pool:        48
PLE Pool:        0
wHdr/inst:    0
Image Cache:    0
Video:        3.372.154(0/0)
Bitmap:        0

Thumbnail Cache:    0
SI Display Cache:    2.502.000
PLE Display Cache:    0

Buffer:        0
Pointer:        0

Title:        0
Memory GF:        0
Memory GF Zero:        0
Memory GF Zero_Dyn:        0
Memory GF Dyn:        0
Memory TT:        0
Audio Effect:        0
PPE:        0

Video Monitor:    0
malloc/free:    0
DIB:        0

VP: admin:        0
VP+Trans: privateData:        0
Transitions::        0

Frame Cache:    0
EXIF:        64
VSW:        0
DVDMAKER:    0
global UI (malloc):    0
global UI (valloc):    50.331.648
NOWAGGLE:    0
ReaderFrame:    0
MP3 Reader:    0
JPEG buffer:    0

Private Bytes:    568 MByte

TLS:        982
MXGUI:        87.641.540
Sum:        145.714.998

Processor [46]  3494MHz  4 Core(s)
Microsoft Windows NT 10.0 (Build 19044)
Used Memory: 903 MB             Max Used Memory: 904 MB
Free Virtual Memory: 22525 MB     Total Virtual Memory: 131072 GB

 Call stack:
Address   Frame
00000001402E258F  0000000040A2EB30  boost::serialization::singleton_module::unlock+AE3BF
00000001402E1F33  0000000040A2ED00  boost::serialization::singleton_module::unlock+ADD63
00000001402E221D  0000000040A2ED70  boost::serialization::singleton_module::unlock+AE04D
00000001402D9E9A  0000000040A2EDC0  boost::serialization::singleton_module::unlock+A5CCA
00000001401B2DEF  0000000040A2EDF0  boost::archive::codecvt_null<wchar_t>::do_encoding+A49BF
00007FFE7CB7CF0C  0000000040A2EDF8  0001:0001BF0C C:\Program Files\MAGIX\Video Pro X14\RegModule_x64\mxmpeg2_x64.dll
0000000000000001  0000000040A2EE00  0000:00000000 C:\Program Files\MAGIX\Video Pro X14\video_pro_x.exe
0000000040A2EEB0  0000000040A2EE08  0000:00000000

CubeAce wrote on 8/30/2022, 3:20 PM

@JBDL @johnebaker

Hi.

I'm not sure I'm reading this correctly so have copied in a moderator (John Baker) who is better at this stuff than I am.

Ideally the program needs a lot of physical ram and you seem to have a lot more virtual ram set up on your system than actual ram. That can cause problems especially if you don't have a lot of spare space on your C: drive for the virtual ram to swap data around on.

How much physical ram do you actually have? Most of us run a minimum of 16GBs but others much more. My system sometimes uses more than 32GB total (including GPU Vram) but I do a lot of intensive editing.

Lets see if I can get John's attention on this. I have copied him into this topic.

Ray.

 

 

Windows 10 Enterprise. Version 22H2 OS build 19045.5011

Direct X 12.1 latest hardware updates for Western Digital hard drives.

Asus ROG STRIX Z390-F Gaming motherboard Rev 1.xx with Supreme FX inboard audio using the S1220A code. Driver No 6.0.8960.1 Bios version 1401

Intel i9900K Coffee Lake 3.6 to 5.1GHz CPU with Intel UHD 630 Graphics .Driver version Graphics Driver 31.0.101.2130 for 7th-10th Gen Intel® with 64GB of 3200MHz Corsair DDR4 ram.

1000 watt EVGA modular power supply.

1 x 250GB Evo 970 NVMe: drive for C: drive backup 1 x 1TB Sabrent NVMe drive for Operating System / Programs only. 1X WD BLACK 1TB internal SATA 7,200rpm hard drives.1 for internal projects, 1 for Library clips/sounds/music/stills./backup of working projects. 1x500GB SSD current project only drive, 2x WD RED 2TB drives for latest footage storage. Total 21TB of 8 external WD drives for backup.

ASUS NVIDIA GeForce RTX 3060 12GB. nVidia Studio driver version 572.16 - 3584xCUDA cores Direct X 12.1. Memory interface 192bit Memory bandwidth 360.05GB/s 12GB of dedicated GDDR6 video memory, shared system memory 16307MB PCi Express x8 Gen3. Two Samsung 27" LED SA350 monitors with 5000000:1 contrast ratios at 60Hz.

Running MMS 2024 Suite v 23.0.1.182 (UDP3) and VPX 14 - v20.0.3.180 (UDP3)

M Audio Axiom AIR Mini MIDI keyboard Ver 5.10.0.3507

VXP 14, MMS 2024 Suite, Vegas Studio 16, Vegas Pro 18, Cubase 4. CS6, NX Studio, Mixcraft 9 Recording Studio. Mixcraft Pro 10 Studio.

Audio System 5 x matched bi-wired 150 watt Tannoy Reveal speakers plus one Tannoy 15" 250 watt sub with 5.1 class A amplifier. Tuned to room with Tannoy audio application.

Ram Acoustic Studio speakers amplified by NAD amplifier.

Rogers LS7 speakers run from Cambridge Audio P50 amplifier

Schrodinger's Backup. "The condition of any backup is unknown until a restore is attempted."

JBDL wrote on 8/30/2022, 3:33 PM

I've never had any issues before with amount of amount of RAM. Do these details assist below?
Processor    Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz   3.50 GHz
Installed RAM    8.00 GB (7.71 GB usable)
Device ID    Removed by Moderator
Product ID    Removed by Moderator
System type    64-bit operating system, x64-based processor
Pen and touch    No pen or touch input is available for this display

JBDL wrote on 8/30/2022, 3:44 PM

The Access Violation has only started since installing the MAGIX update yesterday.

Jim

PATIENT-X wrote on 8/30/2022, 4:38 PM

@JBDL

Hello, welcome

Your Pc Processor Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz   3.50 GHz
Installed RAM    8.00 GB (7.71 GB usable)

Pc specs required for software :Processor: - Intel 6th generation Core i-series or higher - AMD Ryzen or higher RAM:16 GB
I have removed your product and device I.D as its a public forum.

Magix states, Some advanced program features demand more of your computer's processing power. To get the most from these features, your system should at least meet the recommended requirements.

Stephen

Forum Moderator

Last changed by PATIENT-X on 8/30/2022, 4:46 PM, changed a total of 2 times.

Pc self build by me.

Azza Pyramid 804 case

Intel Core i5-13600K Processor 3.5GHz

Kingston FURY Beast 32GB (16GB x 2) 4800MHz DDR5

Geforce RTX2080 Founders edition

Firecuda 530 1tb SSD Nvme

Team Group T-FORCE DELTA MAX RGB LITE 2.5" 1TB SATA III

Corsair RM1000x 80 PLUS Gold Fully Modular ATX 1000 Watt Power Supply

5in LCD Screen

Lian Li UNI SL120 V2 triple fans

MSI Meg Unify Z690 motherboard

 

 

johnebaker wrote on 8/30/2022, 5:08 PM

@JBDL

Hi

Assuming you can open the program and the crash occurs when importing video or opening an existing project:

  • a graphics driver issue - in the case of your PC the Intel processor has a HD4000 integrated GPU, check that this has not been set as the default GPU in the Program settings, Device options tab, Import, Processing and Export options - these settings should be set to CPU.
     
  • the project file has become corrupt.

    Can you start a new project and import video files onto the timeline?
     
  • A video format issue

    Download and install MediaInfo and analyse one of the clips used in the project, assuming they are all the same, or a particular clip that triggers the error, and post the results, see this tutorial on how to setup MediaInfo and analyse a video clip for all the data required.

John EB
Forum Moderator

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 23H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

JBDL wrote on 8/30/2022, 5:27 PM

The crash happens the moment that I try to preview any video in the preview window. I cannot put anything on the timeline.. I cannot do anything in the programme. Is it possible that perhaps a Technician or somebody in the help department can look at my computer remotely? I am really sorry, but really I am not good with operating a computer and systems etc.

JBDL wrote on 8/30/2022, 5:27 PM

Thank you by the way

 

Jim

CubeAce wrote on 8/30/2022, 5:59 PM

@JBDL @johnebaker @PATIENT-X

Hi Jim.

First of all this is a public forum so never, never offer anyone you don't know personally to remote access your computer. That would be very bad practice at the best of times.

That now said, I did say I'm not the best at reading these crash reports but John EB's diagnosis looks accurate now I know what I'm looking at.

All he is asking you to do is alter the following settings.

They will look similar but not exactly the same as the images below.

Use the following folder path shown in the first image to get to the box in the second image.

Note which tab is open.

Change all three boxes highlighted in yellow to use the CPU in the second image.

Close the program and then restart the program and try again.

You need to do this because the program can't use the GPU in your system and it is probably that which is causing your system to crash.

Ray.

Last changed by CubeAce on 8/30/2022, 6:00 PM, changed a total of 1 times.

 

Windows 10 Enterprise. Version 22H2 OS build 19045.5011

Direct X 12.1 latest hardware updates for Western Digital hard drives.

Asus ROG STRIX Z390-F Gaming motherboard Rev 1.xx with Supreme FX inboard audio using the S1220A code. Driver No 6.0.8960.1 Bios version 1401

Intel i9900K Coffee Lake 3.6 to 5.1GHz CPU with Intel UHD 630 Graphics .Driver version Graphics Driver 31.0.101.2130 for 7th-10th Gen Intel® with 64GB of 3200MHz Corsair DDR4 ram.

1000 watt EVGA modular power supply.

1 x 250GB Evo 970 NVMe: drive for C: drive backup 1 x 1TB Sabrent NVMe drive for Operating System / Programs only. 1X WD BLACK 1TB internal SATA 7,200rpm hard drives.1 for internal projects, 1 for Library clips/sounds/music/stills./backup of working projects. 1x500GB SSD current project only drive, 2x WD RED 2TB drives for latest footage storage. Total 21TB of 8 external WD drives for backup.

ASUS NVIDIA GeForce RTX 3060 12GB. nVidia Studio driver version 572.16 - 3584xCUDA cores Direct X 12.1. Memory interface 192bit Memory bandwidth 360.05GB/s 12GB of dedicated GDDR6 video memory, shared system memory 16307MB PCi Express x8 Gen3. Two Samsung 27" LED SA350 monitors with 5000000:1 contrast ratios at 60Hz.

Running MMS 2024 Suite v 23.0.1.182 (UDP3) and VPX 14 - v20.0.3.180 (UDP3)

M Audio Axiom AIR Mini MIDI keyboard Ver 5.10.0.3507

VXP 14, MMS 2024 Suite, Vegas Studio 16, Vegas Pro 18, Cubase 4. CS6, NX Studio, Mixcraft 9 Recording Studio. Mixcraft Pro 10 Studio.

Audio System 5 x matched bi-wired 150 watt Tannoy Reveal speakers plus one Tannoy 15" 250 watt sub with 5.1 class A amplifier. Tuned to room with Tannoy audio application.

Ram Acoustic Studio speakers amplified by NAD amplifier.

Rogers LS7 speakers run from Cambridge Audio P50 amplifier

Schrodinger's Backup. "The condition of any backup is unknown until a restore is attempted."

JBDL wrote on 8/30/2022, 7:02 PM

Hi Ray, thank you Sir and your colleagues for your information and help. I've tried that and for now it appears that it has done the trick. I say that because it's now late but I'll have another try in the morning. Thank you all again for your help.

Jim

CubeAce wrote on 8/30/2022, 8:19 PM

@JBDL

Hi Jim.

Fingers crossed then 🤞.

If it doesn't seem to work or work as well as it was before the update, please come back and tell us here.

It is not unusual for a program update to change settings within a program or for a Windows update on occasion to cause problems for more complex programs such as VPX.

To be more precise, In my experience when anyone downloads the program for the first time it would seem the program looks at the system correctly and sets the programs base settings correctly for that system.

Updates don't always seem to do this and sometimes on some systems, the program update changes the base settings to what should work best in mainstream systems that meet the basic system requirements for the program. That normally means using the systems GPU where one exists.

I suspect when you first downloaded the program it correctly set the program to use your CPU but the update reset the program to use your GPU. This would not be the first time we have seen this happen to other systems in the past.

Anyway. Good luck. I hope the changes work for you.

Ray.

 

 

Windows 10 Enterprise. Version 22H2 OS build 19045.5011

Direct X 12.1 latest hardware updates for Western Digital hard drives.

Asus ROG STRIX Z390-F Gaming motherboard Rev 1.xx with Supreme FX inboard audio using the S1220A code. Driver No 6.0.8960.1 Bios version 1401

Intel i9900K Coffee Lake 3.6 to 5.1GHz CPU with Intel UHD 630 Graphics .Driver version Graphics Driver 31.0.101.2130 for 7th-10th Gen Intel® with 64GB of 3200MHz Corsair DDR4 ram.

1000 watt EVGA modular power supply.

1 x 250GB Evo 970 NVMe: drive for C: drive backup 1 x 1TB Sabrent NVMe drive for Operating System / Programs only. 1X WD BLACK 1TB internal SATA 7,200rpm hard drives.1 for internal projects, 1 for Library clips/sounds/music/stills./backup of working projects. 1x500GB SSD current project only drive, 2x WD RED 2TB drives for latest footage storage. Total 21TB of 8 external WD drives for backup.

ASUS NVIDIA GeForce RTX 3060 12GB. nVidia Studio driver version 572.16 - 3584xCUDA cores Direct X 12.1. Memory interface 192bit Memory bandwidth 360.05GB/s 12GB of dedicated GDDR6 video memory, shared system memory 16307MB PCi Express x8 Gen3. Two Samsung 27" LED SA350 monitors with 5000000:1 contrast ratios at 60Hz.

Running MMS 2024 Suite v 23.0.1.182 (UDP3) and VPX 14 - v20.0.3.180 (UDP3)

M Audio Axiom AIR Mini MIDI keyboard Ver 5.10.0.3507

VXP 14, MMS 2024 Suite, Vegas Studio 16, Vegas Pro 18, Cubase 4. CS6, NX Studio, Mixcraft 9 Recording Studio. Mixcraft Pro 10 Studio.

Audio System 5 x matched bi-wired 150 watt Tannoy Reveal speakers plus one Tannoy 15" 250 watt sub with 5.1 class A amplifier. Tuned to room with Tannoy audio application.

Ram Acoustic Studio speakers amplified by NAD amplifier.

Rogers LS7 speakers run from Cambridge Audio P50 amplifier

Schrodinger's Backup. "The condition of any backup is unknown until a restore is attempted."

JBDL wrote on 8/31/2022, 7:55 AM

Hi Ray,

The programme seems a little slower but the 'HELP@ facility doesn't launch now. Do you have any thoughts please?

Thank you.

Jim

PATIENT-X wrote on 8/31/2022, 9:05 AM

@JBDL

Hi

In certain situations your Pc will struggle at times keeping up with today's powerful software which is more demanding.

Stephen

Forum Moderator

Pc self build by me.

Azza Pyramid 804 case

Intel Core i5-13600K Processor 3.5GHz

Kingston FURY Beast 32GB (16GB x 2) 4800MHz DDR5

Geforce RTX2080 Founders edition

Firecuda 530 1tb SSD Nvme

Team Group T-FORCE DELTA MAX RGB LITE 2.5" 1TB SATA III

Corsair RM1000x 80 PLUS Gold Fully Modular ATX 1000 Watt Power Supply

5in LCD Screen

Lian Li UNI SL120 V2 triple fans

MSI Meg Unify Z690 motherboard

 

 

CubeAce wrote on 8/31/2022, 9:36 AM

@JBDL

Hi Jim.

I'm afraid not. I don't have your version of that program. I'm two versions behind on VPX 12.

Ray.

 

 

 

Windows 10 Enterprise. Version 22H2 OS build 19045.5011

Direct X 12.1 latest hardware updates for Western Digital hard drives.

Asus ROG STRIX Z390-F Gaming motherboard Rev 1.xx with Supreme FX inboard audio using the S1220A code. Driver No 6.0.8960.1 Bios version 1401

Intel i9900K Coffee Lake 3.6 to 5.1GHz CPU with Intel UHD 630 Graphics .Driver version Graphics Driver 31.0.101.2130 for 7th-10th Gen Intel® with 64GB of 3200MHz Corsair DDR4 ram.

1000 watt EVGA modular power supply.

1 x 250GB Evo 970 NVMe: drive for C: drive backup 1 x 1TB Sabrent NVMe drive for Operating System / Programs only. 1X WD BLACK 1TB internal SATA 7,200rpm hard drives.1 for internal projects, 1 for Library clips/sounds/music/stills./backup of working projects. 1x500GB SSD current project only drive, 2x WD RED 2TB drives for latest footage storage. Total 21TB of 8 external WD drives for backup.

ASUS NVIDIA GeForce RTX 3060 12GB. nVidia Studio driver version 572.16 - 3584xCUDA cores Direct X 12.1. Memory interface 192bit Memory bandwidth 360.05GB/s 12GB of dedicated GDDR6 video memory, shared system memory 16307MB PCi Express x8 Gen3. Two Samsung 27" LED SA350 monitors with 5000000:1 contrast ratios at 60Hz.

Running MMS 2024 Suite v 23.0.1.182 (UDP3) and VPX 14 - v20.0.3.180 (UDP3)

M Audio Axiom AIR Mini MIDI keyboard Ver 5.10.0.3507

VXP 14, MMS 2024 Suite, Vegas Studio 16, Vegas Pro 18, Cubase 4. CS6, NX Studio, Mixcraft 9 Recording Studio. Mixcraft Pro 10 Studio.

Audio System 5 x matched bi-wired 150 watt Tannoy Reveal speakers plus one Tannoy 15" 250 watt sub with 5.1 class A amplifier. Tuned to room with Tannoy audio application.

Ram Acoustic Studio speakers amplified by NAD amplifier.

Rogers LS7 speakers run from Cambridge Audio P50 amplifier

Schrodinger's Backup. "The condition of any backup is unknown until a restore is attempted."

browj2 wrote on 8/31/2022, 10:05 AM

@JBDL

Hi,

Assuming that you installed VPX14 to the default location, check that you have this file:

C:\Program Files\MAGIX\Video Pro X14\Help\EN\Content\Topics\Arbeitsflaechen\Projektfenster_VPX.htm

F1 opens this htm file.

John CB

 

John C.B.

VideoPro X(16); Movie Studio 2025 Platinum; Music Maker 2025 Premium Edition; Samplitude Pro X8 Suite; see About me for more.

Desktop System - Windows 10 Pro 22H2; MB ROG STRIX B560-A Gaming WiFi; Graphics Card Zotac Gaming NVIDIA GeForce RTX-3060, PS; Power supply EVGA 750W; Intel Core i7-10700K @ 3.80GHz (UHD Graphics 630); RAM 32 GB; OS on Kingston SSD 1TB; secondary WD 2TB; others 1.5TB, 3TB, 500GB, 4TB, 5TB, 6TB, 8TB; three monitors - HP 25" main, LG 4K 27" second, HP 27" third; Casio WK-225 piano keyboard; M-Audio M-Track USB mixer.

Notebook - Microsoft Surface Pro 4, i5-6300U, 8 GB RAM, 256 SSD, W10 Pro 20H2.

YouTube Channel: @JCBrownVideos

JBDL wrote on 8/31/2022, 10:16 AM

Thank you John CB - excellent! The file was there and now all appears to be working....thanks again everyone.

Jim

browj2 wrote on 8/31/2022, 10:53 AM

@JBDL

Great!

John C.B.

VideoPro X(16); Movie Studio 2025 Platinum; Music Maker 2025 Premium Edition; Samplitude Pro X8 Suite; see About me for more.

Desktop System - Windows 10 Pro 22H2; MB ROG STRIX B560-A Gaming WiFi; Graphics Card Zotac Gaming NVIDIA GeForce RTX-3060, PS; Power supply EVGA 750W; Intel Core i7-10700K @ 3.80GHz (UHD Graphics 630); RAM 32 GB; OS on Kingston SSD 1TB; secondary WD 2TB; others 1.5TB, 3TB, 500GB, 4TB, 5TB, 6TB, 8TB; three monitors - HP 25" main, LG 4K 27" second, HP 27" third; Casio WK-225 piano keyboard; M-Audio M-Track USB mixer.

Notebook - Microsoft Surface Pro 4, i5-6300U, 8 GB RAM, 256 SSD, W10 Pro 20H2.

YouTube Channel: @JCBrownVideos

johnebaker wrote on 8/31/2022, 11:27 AM

@JBDL

Hi

Good news and thanks for the feedback.

John EB

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 23H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

PATIENT-X wrote on 8/31/2022, 11:39 AM

@JBDL

I am happy for you that you got it sorted 👍

Stephen

Forum Moderator

Pc self build by me.

Azza Pyramid 804 case

Intel Core i5-13600K Processor 3.5GHz

Kingston FURY Beast 32GB (16GB x 2) 4800MHz DDR5

Geforce RTX2080 Founders edition

Firecuda 530 1tb SSD Nvme

Team Group T-FORCE DELTA MAX RGB LITE 2.5" 1TB SATA III

Corsair RM1000x 80 PLUS Gold Fully Modular ATX 1000 Watt Power Supply

5in LCD Screen

Lian Li UNI SL120 V2 triple fans

MSI Meg Unify Z690 motherboard

 

 

Craigster wrote on 9/7/2022, 4:05 AM

@JBDL @johnebaker @PATIENT-X

Hi Jim.

 

Change all three boxes highlighted in yellow to use the CPU in the second image.

Close the program and then restart the program and try again.

You need to do this because the program can't use the GPU in your system and it is probably that which is causing your system to crash.

Ray.

Ray and others --

So, I'm super curious as to why you are giving this guidance? He has a sweet NVidia GPU. Why are you suggesting that VPX (which should render much more quickly on his GPU) cannot utilize it? Is it because of too old of a CPU?

Interestingly, I'm having a rash of issues with the new update. I just updated today and have had dozens of crashes (VPX rejecting certain video files -- all from our RESI stream -- that have never had an issue before), giving me a bizarre "Error 0x1009: end of the file reached". I have sent a detailed ticket besides many crash reports to Magix. Oddly, if I trim the files with Bandicut, then VPX will receive them without issue.

Then, I started also getting crashes with an ACCESS_VIOLATION error.

I was pursuing some Rendering speed tests. I did a test of a 2-minute project with typical mix of features and effects for what I commonly do. Tests from 2 years ago (early Covid) prior to the enhancements, I usually got a 1.25:1 average encoder speed (through a dozen possible combinations, with little variance).

But since the AMD enhancements, with all 3 (Import / Processing / Export) set to my modest AMD rx560 card, I'm getting a .54:1 ratio. As in 65 seconds render for the 120 second file.

I swapped the Processing assignment to CPU (keeping the other 2 on the Radeon), and my time doubled: to 2:14, which is a 1.12:1 ratio; Almost as slow as 2 years ago. This was after enduring a couple crashes merely changing the single setting.

I gave up on running additional tests (of all CPU, of CPU Export only, of Intel 630, etc.) as merely making the changes kept immediately crashing VPX.

While I've had other prior issues, these were all completely new crash issues from the latest version recently released.

Is anyone else having issues? So exhausting to spend triple the time trying to get work done, and then many hours trouble-shooting with no clear conclusions.

 

Craig

-

System 1: Gigabyte Z390 Designare, i9-9900k, 64GB RAM, Radeon RX580/Intel 630, Apollo X6, multiple Black HDD & SSDs. System 2: Gigabyte Z390 Aorus Pro WiFi, i7-9700k, 64GB RAM, Radeon RX560/Intel 630, Audient iD44, multiple Black HDD & SSDs.

johnebaker wrote on 9/7/2022, 5:39 AM

@Craigster

Hi Craig

. . . .  I'm super curious as to why you are giving this guidance? He has a sweet NVidia GPU. . . .

If you are referring the images @CubeAce posted these are from Ray's PC.

As far as we know @JBDL does not have a Nvidia GPU that supports NVENC or AMD GPU which a capable of hardware acceleration (HWA) encoding, which gives faster export times.

Similarly the Intel iGPU the HD 4000 does not support DirectX 12, it does support DirectX 11, however this restricts its usage for effects and HWA is very restricted.

Switching to CPU is almost always slower - AFAICS no one has said it will be faster then a good GPU.

. . . . VPX rejecting certain video files -- all from our RESI stream -- that have never had an issue before), giving me a bizarre "Error 0x1009: end of the file reached". . . . .

AFAICS you did not respond back in this topic in February - did the issue go away or if fixed what fixed it?

Are the video files those from the Resi server or prepared for putting on the server?

In the previous post you commented that they were constant framerate - did you get this info from MediaInfo or from the file properties?

John EB

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 23H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

Craigster wrote on 9/7/2022, 5:06 PM

Hi John,

Sorry, somehow I initially thought I read that the OP had an NVidia 1650 gpu (which has Gen 1 NVENC). I understand that some of his info has been removed. The current info doesn't speak of a gpu that I can see. Maybe I misinterpreted...

Regarding the prior Feb. post:

- Thank you! I had literally forgotten that I have seen the "Error 0x1009: end of file reached" once previously!

- It was so odd (an errant download from Vimeo without a suffix) and non-recurring that I determined it wasn't the fault of VPX. So, I didn't bother with another post.

- I did add my PC specs to my signature back then (Feb.). And I always stay current on VPX updates.

- I use the info from MediaInfo always. (However, I am noting occasional discrepancies on the VPX info in the Project Folder. For example, we have shifted our process from having RESI export at 30FPS (vs. the prior 29.97), and we now also upload some content manually to Social Media Platforms at 30FPS. Yet, yesterday I pulled in several files that MediaInfo confirms are 30.0FPS and VPX shows them as 29.97. (Note: these were files that loaded and worked fine, from Bandicut.)

 

Regarding the current issues:

- I updated my Radeon GPU driver (from the 2nd latest to the latest). Did not improve.

- 100% consistent. Any recent or old video file from Resi is rejected and results in the Error 0x1009. Other than the singular Vimeo file with no suffix error from Feb., I've never encountered this before. I

- Meanwhile, the numerous Access Violation Errors simply increased with usage until I gave up. Particularly, I was unable to change the Device Options to include the CPU or the Intel 630. Immediate crash of the program. Not of Windows. (Multiple reboots didn't change anything.)

Would a Crash Log be helpful?

 

 

 

System 1: Gigabyte Z390 Designare, i9-9900k, 64GB RAM, Radeon RX580/Intel 630, Apollo X6, multiple Black HDD & SSDs. System 2: Gigabyte Z390 Aorus Pro WiFi, i7-9700k, 64GB RAM, Radeon RX560/Intel 630, Audient iD44, multiple Black HDD & SSDs.

johnebaker wrote on 9/8/2022, 3:05 AM

@Craigster

Hi Craig

A crash log excerpt from when the crash occurred and the data following it would help.

I think this one may need escalating up to support and a sample file sent to them along with the crash log.

You could, if you wish, also upload a sample file for us to test on our PC's - use Dropbox, Google Drive or One Drive tor another file sharing site to share the file.

Uploading to Social platforms will re-encode the video to their format(s) so exporting as a standard h.264 or h.265 encoded video and AAC encoded video should be sufficient.

John EB

Last changed by johnebaker on 9/8/2022, 3:07 AM, changed a total of 1 times.

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 23H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.