Known Participant

Question

Persistent Premiere Crashing on Export

Forum|Forum|1 year ago
April 25, 2024
6 replies
2392 views

System specs:

PC, Windows 11 v23H2

11th Gen Intel(R) Core(TM) i7-11700F @ 2.50GHz 2.50 GHz

64GB RAM
NVIDIA GeForce RTX 2060 (drivers updated as of 4/24/2024)
Premiere Pro 24.3

Media Encoder 24.3

During any export, either in Premiere or Media Encoder, the system crashes randomly during encoding. Either the program closes without notice/error message or I get the blue screen. This issue exists for Premiere 2023 and Media Encoder 2023. It happens on a variety of content of difference sources and difference projects. I've tried reinstalling each of the programs to no avail. I've had the PC performance monitor up while exports occur, CPU jumps and is between 98%-100%, RAM remains at more than 50GB free prior to crashes.

please help 😞

This topic has been closed for replies.

MyerPj

Braniac

Not a bad way to go. When I'm in that situation, I usually get a new boot drive/SSD, and install clean Windows on that. Then I can have the other one preserved, and use it as a data disk if I like. Glad you're working again...

MyerPj

Braniac

Those BSOD codes are not very helpfull so don't bother with that. Make sure you have the latest driver, like PB has suggested, also make sure you have no OSD type apps running the monitor frame rates and stuff like that. Also, overclocks, etc...

T

T - Sal

Inspiring

A friend of mine lost an Intel Core i9 CPU due to an error that started exactly like that. Based on his experience, I would strongly recommend testing the hardware first to rule out any underlying issues that could lead to significant problems.

When it comes to the Blue Screen of Death (BSoD), figuring out whether it's caused by hardware or software can be a bit tricky. But here's the scoop:

Hardware-Related BSoD:

RAM Issues: Sometimes, faulty or incompatible RAM can cause these errors, especially during demanding tasks like rendering.
Overheating: If your CPU or GPU gets too hot due to poor cooling, it can lead to a BSoD.
Faulty Components: Problems with your motherboard, CPU, GPU, or storage devices (like a failing hard drive) can also trigger BSoD errors.
Driver Problems: Outdated or corrupted device drivers can mess things up and cause hardware-related BSoD issues.

Software-Related BSoD:

Driver Conflicts: Incompatible or old device drivers can also lead to system crashes.
OS Errors: Sometimes, the operating system itself might have issues like corrupted files or misconfigurations.
Software Clashes: Certain apps or software configurations can clash with system processes, causing BSoD errors too.

It's hard to put an exact percentage on hardware-related BSoD, but taking good care of your hardware and keeping everything updated can definitely help prevent these headaches. It might be worth running some hardware diagnostics, updating drivers, and checking for software conflicts to troubleshoot the problem. And hey reaching out to a tech-savvy friend or professional can be a lifesaver!

T-Sal

kanej18275536Author

Known Participant

performed a memory test, no issues found

Peru Bob

Braniac

Try updating or rolling back your graphics driver directly from the video card manufacturer’s site. Do a clean installation of the latest Studio Driver (NOT the Game Driver).

kanej18275536Author

Known Participant

Hello. I rolled back to previous graphics drivers using the Studio driver. When first dealing with the crashes I updated my graphics driver and that didn't resolve so I went backwards, no improvement, went backwards again and no improvment. I've now rolled back my premiere to an even older variant (23.6) and no improvement.

I can take in h.264 30FPS and export it alone just fine, but if I add any adjustment layers (keeping the same encoding) both Premeire and Encoder will crash. If i try to export to h.265 or Quicktime it also crashes.

kanej18275536Author

Known Participant

I've been able to document a few of the sad-face blue screen codes, they differ on each crash:
K_MCODE_EXCEPTION
DRIVER_IRQL_ACUSS..
MEMORY_MANA...
SYSTEM_SERVICE_EXCEPTION

If it's not a sad-face blue screen Adobe Encoder just closes during the export either prompting the "adobe had to close" survey window or it just closes without that prompt.

I've only made headway in discovering that I can export an h.264 30FPS (the source source mat'l encoding) directly back out (event recode to h.265) and it's fine using GPU acceleration, but when i add a single adjustment layer (to the 5 min clip) that leads to crashing. It's repeatable to remove the layer, export fine, re-insert the layer and crash. I've deleted the layer and re-built it but same crashes occur. There's no other effects, just the single layer video with an adjustment layer.

MyerPj

Braniac

<<blue screens last less than 2 seconds>> Just wondering what this means.

Most people refer to blues screens (BSOD) as locking up windows. Thus you need to hold power down for several seconds to get the machine to reboot.

kanej18275536Author

Known Participant

apologies. I get the blue screen with the sad face. as quick as it shows up windows automatically restarts before i can see any error codes. i'll try and record with a phone to catch the code.

MyerPj

Braniac

Did you try exporting to a different codec. Like ProRes, or even h.265 or 264 depending on what the problem format is.

How about your drives. did you have adequate space (like 3 times) to do the export, and on all your involved drives. Try exporting to a different drive, etc.

kanej18275536Author

Known Participant

tried an export using h.265 and it went through with no issue surprisingly. I repeated the same process with all the same settings and it blue screened around 75'ish percent. blue screens last less than 2 seconds so i can't see if there are any error codes presented. Currently trying to figure out how to see windows crash logs..

kanej18275536Author

Known Participant

for added context using adobe premiere/media encoder are the only programs that generate this crash. computer runs ultra stable othewise.

T

T - Sal

Inspiring

Hello,

Review BSoD Error Codes: When your system crashes and shows a BSoD, it typically displays an error code (e.g., "DPC_WATCHDOG_VIOLATION", "KERNEL_SECURITY_CHECK_FAILURE", etc.). Make a note of this error code as it can provide valuable information about the root cause of the crash.

Check System Event Logs: After a BSoD, Windows usually logs events related to the crash in the Event Viewer. Open Event Viewer (eventvwr.msc from the Run dialog) and navigate to Windows Logs > System. Look for any critical or error events around the time of the crash for more details.

Test Hardware Components: Use diagnostic tools like MemTest86 to thoroughly test your RAM modules for any errors. Similarly, you can use tools like Prime95 and FurMark to stress test your CPU and GPU to check for stability issues.

Check for Disk Errors: Use the built-in Windows Disk Check tool (chkdsk) to scan and repair disk errors on your system drive and other storage devices.

Consider System Restore: If the BSoD issues started recently after a specific change (such as a driver update or software installation), consider using System Restore to roll back your system to a previous state when it was stable.

Contact Manufacturer Support: Since you're experiencing frequent BSoD crashes on a relatively new system with high-end hardware, reaching out to the manufacturer's support team (e.g., Dell, HP, etc.) can be beneficial. They may have specific diagnostics and troubleshooting steps tailored to your system.

Backup Important Data: As a precautionary measure, ensure that you have backups of important data stored on your system in case of hardware failure or data loss due to recurring BSoD errors.

If the issue persists even after following these steps, consider seeking professional assistance from a qualified technician or contacting Microsoft Support for further guidance on resolving persistent BSoD errors.

T-Sal

kanej18275536Author

Known Participant

the error comes up as an Adobe "Adobe Media Encoder had to close" and I'm offered a *.dmp file that I don't know what to do with.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded