CPU and RAM maxing out during rendering, rendering before export causes an error or crashes

Every one of these pro apps is coded to use the system and available hardware differently. So depending on a bunch of factors, one may do better on your system for X than another. And on someone else's rig, it's reversed. Same media, but different hardware.

I use Resolve quite a bit also, as I work for/with/teach pro colorists. It's got a much better grading setup as of course it started as a like $20,000 grading app. That has had editing/audio/fusion grafted into it. I teach colorists how to work in Premiere when they have to for some reason.

On my desktop, Premiere and Resolve work quite well, both of them. On my 4-year old Acer laptop, Pr24.x runs great, but Resolve is such a dog I removed it. Others have opposite experience, which is to be expected.

They're tools. Use what works. And in general, Premiere still has a bunch of things like number of assignable keyboard shorts, text editing, multicam, and on, that are still far 'deeper' than Resolve. Which keeps adding things of course.

When I have very long videos to encode, I break them into smaller videos.  When they are encoded, I use Shutter Encoder to merge the videos.  It merges the videos quickly and does not reincode the them.

Just ... wow.

First, that is not just VFR, variable frame rate, that's the widest framerate variance I've ever seen! "Nominal" fps is 60, but the variance goes between the slowest at 20fps to the fastest of 62.5fps. I'm stunned Premiere can work with that media at all.

I'm used to seeing a range of maybe 51 to 62 for "60fps" VFR media, but ... 20 to 62? I'm ... boggled here. Never seen anything remotely that  varied before!

I would say to convert that entire VOD to CFR ... constant framerate ... in either Handbrake or ShutterEncoder prior to importing into Premiere.  It would work vastly better!

Next, the long-GOP thing? That's got the relevant numbers in the 'format' line. M=3, N=120. That second, N figure, says there's up to 120 frames between complete iframes. Holy Terwilligers Batman! That's ... as nasty as any drone media I've ever seen. And again, if you get normal playback of that within Premiere, just ... wow. Your system ain't doing to bad.

But combining the massive load of that wide framerate constantly shifting, and the load of computing probably over 150 frames just to be able to compute and render any specific single frame ... yea, that's putting a MASSIVE load on your system.

Your footage also seems to be variable framerate, this adds a whole new level issues. The usual advice is to trancode it to constant framerate using a third party program like Handbrake.

Long-GOP is a process that is used in many cameras, especially phones & drones, most prosumer cams, and most screen recording apps.

It's great for quickly mashing the data down to a much lower level of stuff to write to card or disk. Because it's based (for all camera work) on having specialized chips in the device to do the encoding process.

It has complete actual video frames called iframes only every so often. Between 9 and 30 was the old standard, but now some drones push this up above 100 frames apart. In between are datasets called p and b frames. And they are datasets, not images, of 1) the pixels that have changed since the last iframe or 2) the pixels that will change before the next iframe or 3) both.

And some drones and other devices use "partial iframes" to push the numbers way past 100 frames between complete actual video images.

So the computer needs to create the entire stretch of frames between up to 200 frames, do all the decoding/decompressing for all those frames, and store to RAM/cache ... in order to display the next frame sequentially.

It's not too hard on simple players, because they don't put any load on the system. But an NLE, like Premiere, just in running, puts a load on the system. Now ... to grab a few seconds of long-GOP clip here and there, it's doing a TON of decoding/decompressing/writing to RAM/cache before it can display a sequence.

Or, in your case, do an export.

So the next question is, what is your CPU? Some Intel and Arc CPUs come with hardware to help with long-GOP work. Some don't. AMD CPUs ... fuhgedaboudit. (I run a 24 core Ryzen 3960x, but avoid long-GOP like the plague it is ...)

Long-GOP?

What format/codec are those VOB files?

Premiere needs 4-5 times the expected file size available while doing render or export work. Do you have adequate free space?

I don't know if it's important, but I should add that when a render fails without crashing the software, it won't release the RAM it's used. In addition, if I render before exporting, the render files are beyond ridiculous in size. The final files for these VODs have ranged from 20 to 45 GB, and this last rendered file hit 88.7 GB when the program crashed, and it wasn't even halfway done yet. The program also apparently isn't cleaning up after itself. The drive it's using to store these started out today at 1.1 - ish TB free, now it's down to about 850 GB, so it's just EATING hard drive space with all of these failed attempts.