Constant program lock out, destroying my will to live.

SchrodingerDeeps wrote on 9/16/2020, 12:53 PM

Hello,

Today Video Pro X started to constantly lock up. The software ceases to respond, no items can be clicked on. I must force shutdown via ctrl+alt+del.

This occurs regardless of project, or even if no project is loaded typically within about two minutes.

Strangely, if a video is playing it will continue to play. I can not however click on anything at all. Pressing ESC will stop the video, but then the software is totally frozen.

Currently at my wits end, was just started a brand new project and this is costing my so much time.

Thank you all for your help.

EDIT: It may be worth mentioning that the program even without having a video loaded is sitting at 7.5GB ram usage... When crashed.

Version 17.03.68

GPU 1070TI

CPU I7, 6700K

RAM 16GB

Windows 10

Comments

johnebaker wrote on 9/16/2020, 1:15 PM

@SchrodingerDeeps

Hi

This could be related to this topic issue - see the solution there.

John EB

Lateral thinking can get things done!

VPX 12, MEP Premium 2021, and earlier versions 2015 and 2016, Music Maker Premium 2021.

Running Windows 10 Professional 20H2 64bit on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 3 x 2Tb internal HDD + 60GB internal SSD, + 6 ext backup HDDs, Sony FDR-AX53 Video camera, Contour HD 1080 and Sony HDR-AS30V Sports cams.

SchrodingerDeeps wrote on 9/16/2020, 1:36 PM

Very many thanks! I didn't reinstall the software or delete the files. I simply reinstalled the C++ runtime library.

It is still eating a crazy amount of RAM for reasons unknown, but it isn't crashing now.

(for others just google C++ runtime library and download it from the Microsoft website)

CubeAce wrote on 9/16/2020, 1:37 PM

@SchrodingerDeeps

Hi Matthew.

As well as John's reply which very well could be the reason. in my own personal experience, whenever a program constantly locks up it is a sign of a lack of a hardware resource. The main one being available free drive space on the C: drive. If your projects are large you should have at least the amount of free space on the hard drive as the size of the combined files in use pus extra so the files can be moved around during the editing process or effects added also use additional space a the instruction sets are laid down as well. My C: drive is only 340GB and I try hard to always leave a third of that free. I may be being overcautious but I've not suffered any lock-ups with VPX 11.

Windows itself takes up just under 5GB.

Make sure you don't have too many background applications running. Check that by opening task manager without running VPX. Opening VPX without loading a project should settle the memory usage by just over an extra 1GB.

 

Some of the temp files VPX makes while a project is open can be very large. This is just for a video just under 8 minutes long although a longer project may take up more or less disk space and memory depending on file sizes and effects in use.

Ray.

Last changed by CubeAce on 9/16/2020, 1:39 PM, changed a total of 1 times.

Windows 10 Enterprise. Version 20H2 OS build 19042.844. Direct X 12. Bios version 1401 latest hardware updates for Western Digital hard drives. Page file space 4.75GB.

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

Intel i9900K Coffee Lake 3.6 to 5.1GHz CPU with Intel UHD 630 Graphics .Driver version 27.20.100.9168, with 32GB of 3200MHz Corsair DDR4 ram.

1000 watt EVGA modular power supply.

1 x 250GB SSD D: drive for current project. 1 x 250GB SamSung Evo 970 drive for Operating System. + x2 WD BLACK 2TB internal SATA 7,200rpm hard drives.I for internal backup and 1 for Library clips/sounds/music/stills. Total 12TB of four external WD drives for backup.

Gigabyte NVIDIA G Force GTX 1650 Super . nVidia driver version 460.89: 1280 CUDA cores Direct X 12. Memory interface 128bit Memory bandwidth 192.03GB/s 4GB of dedicated GDDR6 video memory, shared system memory 16307MB PCi Express x16 Gen3.

Running MEP Premium 20.0.1.79. and VPX 17.0.3.68 (UDP3)

M Audio Axiom AIR Mini MIDI keyboard Ver 5.10.0.3507

SchrodingerDeeps wrote on 9/16/2020, 1:43 PM

Thank you,

I performed a bit of a C: spring clean before getting here. It IS eating resources, more than I expected.

Regardless, I store my projects on a separate drive which has enough space to grow.

Weirdly it has not occurred again since the C++ runtime install, and if it is indeed a space issue I really think that should post an error. Here's to hoping its fixed!

CubeAce wrote on 9/16/2020, 1:58 PM

@SchrodingerDeeps

Hi Matthew.

Yes it can be resource hungry.

Remember if a website is quoting minimum specs that means it will run but maybe not that well and worth keeping drivers and operating system up to date and if needed shutting down some background applications. Glad it's sorted for you anyway.

What has the memory requirement settled down to now on your system?

Ray.

Windows 10 Enterprise. Version 20H2 OS build 19042.844. Direct X 12. Bios version 1401 latest hardware updates for Western Digital hard drives. Page file space 4.75GB.

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

Intel i9900K Coffee Lake 3.6 to 5.1GHz CPU with Intel UHD 630 Graphics .Driver version 27.20.100.9168, with 32GB of 3200MHz Corsair DDR4 ram.

1000 watt EVGA modular power supply.

1 x 250GB SSD D: drive for current project. 1 x 250GB SamSung Evo 970 drive for Operating System. + x2 WD BLACK 2TB internal SATA 7,200rpm hard drives.I for internal backup and 1 for Library clips/sounds/music/stills. Total 12TB of four external WD drives for backup.

Gigabyte NVIDIA G Force GTX 1650 Super . nVidia driver version 460.89: 1280 CUDA cores Direct X 12. Memory interface 128bit Memory bandwidth 192.03GB/s 4GB of dedicated GDDR6 video memory, shared system memory 16307MB PCi Express x16 Gen3.

Running MEP Premium 20.0.1.79. and VPX 17.0.3.68 (UDP3)

M Audio Axiom AIR Mini MIDI keyboard Ver 5.10.0.3507

SchrodingerDeeps wrote on 9/16/2020, 3:01 PM

Well right now its encoding a 45 minute video, sitting happy about 2.5Gb.

Funny considering earlier with no project at all I was over 7.5.