Premiere 2019 - BSOD

[Christoffer Glans]

Did a regular 1080p job with some 4K material and all of a sudden, boom, BSOD crash. I've been working with PP 2018 for a while and no problems, but PP 2019 gave me two BSOD crashes in a row.
I tried searching online for any info, but mostly just "support-like" jargons that don't help at all.

Checking the code on the BSOD and it shows WHEA_UNCORRECTABLE_ERROR

The best answer I got was that a Gigabyte X299 board a few years ago had this problem and that the solution was to go into bios and reduce the CPU voltage. But I own an Asus X299 and an Intel i9 with 16 cores and water cooling. 64gb RAM. The code relates to hardware problems, but I've only encountered BSOD with Premiere 2019 and actually ONLY that since I bought the system 10 months ago.

How can Premiere 2019 do hardware errors that result in a BSOD? I've read that some people with the old Gigabyte issues got their PC to crash so hard that it wouldn't restart. If this is true, then there's no way I'm using 2019 until Adobe fixes their shit.

Anyone else got similar problems?

 

[Phil Holland]

First and foremost look deeper into that error. If you have any overclocking enabled, disable it. It's likely something related to that or even a bad radiator. It's the load Premiere is pushing on the CPU that's putting it in that state. Which would happen with other heavy lifter multi-threaded packages too. I've seen the error twice in the past, both were due to to cooler or overclocking a bit beyond what it should be.

 

[Christoffer Glans]

First and foremost look deeper into that error. If you have any overclocking enabled, disable it. It's likely something related to that or even a bad radiator. It's the load Premiere is pushing on the CPU that's putting it in that state. Which would happen with other heavy lifter multi-threaded packages too. I've seen the error twice in the past, both were due to to cooler or overclocking a bit beyond what it should be.

The setup is brand new, water-cooling, no overclocking, use hyperthreading but it doesn't go over the Ghz limit for the processor. No other software does this, I get it by editing 1080p MP4 material in PP 2019, but editing, grading and compositing 6K R3D files in Resolve works great, same goes for RCX and Avid. I can do it with PP 2018 which still works, it's just PP 2019 that does this.

So all points on Adobe screwing up the code. If it is like the old bug that I mentioned, it's that Premiere pushes the processor to draw more wattage, which is a crazy bug that could damage the setup.
If pushed it through CineBench by letting it go over and over and it pushes the system to its limits without any problems occurring.


I will use PP 2018 for now, hopefully Adobe will fix this since it's a very scary bug to say the least.

 

[Christoffer Glans]

I've continued editing in PP 2018 without problems so far. It more and more leans towards some really shitty code in PP 2019 by Adobe.

 

[Steve Sherrick]

what is Adobe’s response to you? I find that with so many computer configurations out there, you have to work directly with these companies to assess your unique situation so they can diagnose problem, then find a solution for you or if indeed bad code make a fix in next rev.

 

[Steve Delahoyde]

I can't even get 2019 to open on my Mac, that's how bad it is here. I've installed and re-installed several times and it'll work for a few minutes occasionally, freeze up, then I can't even get the program to open at all.

 

[Joel Arvidsson]

You get what you pay for...wait a minute then it should run solid!!! Adobe need to step up there game. I still edit in 2017 since its the smoothest playback on my workstation. Im trying to go to 2019 for some cc thoe but I get black video when I switch over to ipp2. But that problem is not to be discussed in this thread. Best luck to you.

 

[Christoffer Glans]

You get what you pay for...

Except my rig is top of the line, literary the top priced and carefully chosen parts for high-end post. So, it's Adobe bullshit. I don't mind crashing bugs and stuff like that, just keep auto-saves fresh and it'll work fine. But a crash that might risk the integrity of the entire desktop, that's so badly coded it's downright laughable.

 

[DJ Meyer]

PP 2019 working great for me, FWIW. (on windows 10). Cutting multi layered 8K monstro.

 

[Christoffer Glans]

PP 2019 working great for me, FWIW. (on windows 10). Cutting multi layered 8K monstro.

It's not the performance that's the problem, it's that it seems to feed more voltage into the processor. I didn't get problems with Red footage, but with regular 1080p mp4 videos.
What motherboard and processor do you have?

 

[DJ Meyer]

WHEA_UNCORRECTABLE_ERROR is a pretty generic error and it could be any number of things.

Which CPU do you have? If its one that has Quick Sync you could be getting a conflict between that and Nvidia hardware decode of h.264 footage if Adobe has changed the way they handle that in 2019.

It could also be something seemingly unrelated like audio drivers that the mp4 files are triggering.

Go into Device Manager and make disable audio devices one by one to see if you can find what is causing the problem.

You could also try editing an mp4 that does not have an audio track at all and see if it crashes.

 

[Christoffer Glans]

WHEA_UNCORRECTABLE_ERROR is a pretty generic error and it could be any number of things.

Which CPU do you have? If its one that has Quick Sync you could be getting a conflict between that and Nvidia hardware decode of h.264 footage if Adobe has changed the way they handle that in 2019.

It could also be something seemingly unrelated like audio drivers that the mp4 files are triggering.

Go into Device Manager and make disable audio devices one by one to see if you can find what is causing the problem.

You could also try editing an mp4 that does not have an audio track at all and see if it crashes.

I would like to, but if each BSOD is a risk to brick my computer I'm not doing it. Other software crashes, fine, but not such an alarming issue.
My processor is the Intel Core i9 7960X 2.8 GHz 22MB. It handles realtime decode of Monstro 8K, but in Premiere 2019, seems to fail to handle 1080p mp4 :thumbdown:

 

[DJ Meyer]

I would like to, but if each BSOD is a risk to brick my computer I'm not doing it. Other software crashes, fine, but not such an alarming issue.
My processor is the Intel Core i9 7960X 2.8 GHz 22MB. It handles realtime decode of Monstro 8K, but in Premiere 2019, seems to fail to handle 1080p mp4 :thumbdown:

Up to you man. I have never seen an OS BSOD damage a system except in the case where the hardware was failing anyway (which was causing the BSOD).

Whether or not you bought top of the line is not really relevant as even the highest end boards etc have some bad ones in the mix.

 

[Johnny Hurberg]

I have a very similar setup as you Christoffer, also had BSOD with Adobe PP 2019. No overclocking with my system either, I backed down in PP model and it solved it.

Later upgrading another workstation shifting some computer components both systems got BSOD, the thing that solved it for me that time and may be related to the first BSOD is that I somehow during upgrades and different Windows 10 edition managed to have the same original key for Windows installed on both machines, so after being in Microsofts telephone line for 45 min (with some really freaky backround music that they use for some reason) I gave up and bought a new copy of Windows 10 Pro.

After that, no BSOD.

I now run PP 2019.

 

[Christoffer Glans]

I have a very similar setup as you Christoffer, also had BSOD with Adobe PP 2019. No overclocking with my system either, I backed down in PP model and it solved it.

Later upgrading another workstation shifting some computer components both systems got BSOD, the thing that solved it for me that time and may be related to the first BSOD is that I somehow during upgrades and different Windows 10 edition managed to have the same original key for Windows installed on both machines, so after being in Microsofts telephone line for 45 min (with some really freaky backround music that they use for some reason) I gave up and bought a new copy of Windows 10 Pro.

After that, no BSOD.

I now run PP 2019.

Weird, but good to know that the issue is replicated. I don't however have two copies of Windows, only a brand new bought copy of Windows 10 Pro for this build. So, not sure what that means.
I can stick with Premiere Pro 2018 for now, I can still use Media Encoder to code ProRes masters outside of Premiere, which is nice. I probably won't call Microsoft, hate freaky music

 

[Christoffer Glans]

Whether or not you bought top of the line is not really relevant as even the highest end boards etc have some bad ones in the mix.

Of course, however, after nearly 20 years of fixing my own tech problems, it has in 99% of the cases been about bad software coding rather than hardware, except for memory issues on cheap RAM. But high end systems have rarely failed in hardware. This has been very true everytime an actual solution comes from workaround people, finding some bad little irrelevant setting in a config file somwhere, hack-changed it and fixed all problems with major software releases. THAT shows how bad big corp softwares really are, especially with giving out firmware fixes fast on problems that are major. The best indication that my hardware isn't the problem is that I can edit in Premiere 2018 fine, I can encode using 2019 media encoder, I can grade 6K R3Ds in Resolve with almost realtime playback at full premium with tons of nodes, and pretty much any post production without any major problems. But a single 1080p sequence of MP4 clips in 2019 kills my rig, I don't have to deduce much to figure out that it's premiere 2019 that's the problem.