• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Persistent Premiere Crashing on Export

Explorer ,
Apr 25, 2024 Apr 25, 2024

Copy link to clipboard

Copied

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 😞

TOPICS
Crash , Error or problem , Freeze or hang , Hardware or GPU

Views

407

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Apr 25, 2024 Apr 25, 2024

Copy link to clipboard

Copied

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.S

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Apr 25, 2024 Apr 25, 2024

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Apr 25, 2024 Apr 25, 2024

Copy link to clipboard

Copied

It's really important to take the Blue Screen of Death (BSoD) issue seriously. The BSoD signals a critical error in your operating system or hardware, and ignoring it could lead to more serious problems like system instability, data loss, or even damage to your hardware. It's best to address this issue promptly to figure out what's causing it and find a solution. By taking proactive steps now, you can ensure that your system stays reliable and stable. Don't hesitate to reach out for help or guidance if needed!

T.S

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Apr 25, 2024 Apr 25, 2024

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Apr 25, 2024 Apr 25, 2024

Copy link to clipboard

Copied

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..

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Apr 25, 2024 Apr 25, 2024

Copy link to clipboard

Copied

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

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Apr 25, 2024 Apr 25, 2024

Copy link to clipboard

Copied

and yes, significant memory exists beyond the required file size on the drive. I've also tried multiple drives (also separate partitions within those drives)

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Apr 25, 2024 Apr 25, 2024

Copy link to clipboard

Copied

<<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.

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Apr 25, 2024 Apr 25, 2024

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Apr 25, 2024 Apr 25, 2024

Copy link to clipboard

Copied

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).

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
May 04, 2024 May 04, 2024

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
May 04, 2024 May 04, 2024

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
May 04, 2024 May 04, 2024

Copy link to clipboard

Copied

The "DRIVER_IRQL_NOT_LESS_OR_EQUAL" error in Windows is a common Blue Screen of Death (BSOD) error. This error typically indicates that a driver tried to access a memory address at an incorrect IRQL (Interrupt Request Level). This error can be caused by faulty hardware, incompatible device drivers, or corrupt system files.

The "K_MCODE_EXCEPTION" error in Windows typically indicates a problem related to a machine code exception. Machine code is the lowest level of instructions that a computer understands and executes. When an error occurs at this level, it often indicates a serious problem with the system's hardware or drivers.

MEMORY_MANA... This error indicates that the system's memory management subsystem encountered a problem. It can occur due to various reasons, including faulty hardware, corrupt system files, driver issues, or software conflicts.

SYSTEM_SERVICE_EXCEPTION This error indicates that a system service failed to execute properly. It can be caused by various factors, including faulty hardware, corrupt system files, incompatible drivers, or software conflicts.

If reinstalling drivers and software hasn't fixed the error, it might be time for a clean install of Windows. Before doing so, it's important to make sure hardware isn't causing the issue. Run diagnostics to check components like RAM, CPU, GPU and hard drive for faults please. Address any hardware problems found before reinstalling Windows.

 

T.S

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
May 04, 2024 May 04, 2024

Copy link to clipboard

Copied

thank you. i just did a hard drive check and no faults were found. gonna check out RAM diagnostics next.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
May 04, 2024 May 04, 2024

Copy link to clipboard

Copied

A good stress test for Windows can help identify hardware issues, test system stability, and assess performance under heavy loads. One popular tool for stress testing Windows systems is Prime95. Here's how you can use it:

Download and Install Prime95: You can download Prime95 from its official website (https://www.mersenne.org/download/). Install the application on your Windows system.

Run Prime95: Once installed, open Prime95. You'll be presented with various options for stress testing your system's CPU, RAM, and overall system stability.

Choose a Stress Test: Prime95 offers different stress test options, including Small FFTs, Blend, and Large FFTs. Each test stresses different components of your system, such as CPU, memory, or both. You can select the test that best suits your needs.

Monitor System Temperatures and Stability: While running the stress test, monitor your system's temperatures and overall stability. You can use monitoring software like HWMonitor or Core Temp to keep an eye on CPU temperatures, and observe system behavior for any signs of instability, such as crashes or freezes.

Run the Test for an Extended Period: For a thorough stress test, it's recommended to run Prime95 for an extended period, such as several hours or overnight. This allows you to assess the system's stability under sustained load.

Review Results: After completing the stress test, review the results to identify any issues or anomalies. If Prime95 encounters errors or your system exhibits instability during the test, it could indicate hardware problems that may need further investigation or troubleshooting.

While Prime95 is a popular choice for stress testing, there are other tools available as well, such as AIDA64, IntelBurnTest, and MemTest86, each with its own set of features and capabilities. Choose the tool that best suits your needs and hardware configuration.

Keep in mind that stress testing can put a significant load on your system, so it's important to monitor temperatures and ensure adequate cooling to prevent overheating. Additionally, be prepared for increased power consumption and noise from system fans during the stress test.

 

One last piece of advice: considering the potential bugs and stability issues with Windows 11, I recommend switching back to Windows 10 for your professional work. Windows 10's reliability is well-established and trusted in professional environments, ensuring smooth operations without unexpected interruptions.

 

T.S

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
May 04, 2024 May 04, 2024

Copy link to clipboard

Copied

Try this as well, Open PowerShell with administrative privileges. You can do this by right-clicking on the Start button and selecting "Windows PowerShell (Admin)".  

Type: sfc /scannow

This command will scan your system for corrupted files and attempt to repair them automatically.

If the SFC scan finds corrupted files but cannot repair them, you may need to use additional commands or tools to resolve the issue. One such command is the Deployment Image Servicing and Management (DISM) tool, which can repair the Windows image used by SFC. You can run the following command to repair the Windows image using DISM: 

DISM /Online /Cleanup-Image /RestoreHealth

OR

Repair-WindowsImage -Online -CheckHealth

This command checks for corruption and attempts to repair it automatically.

OR

Repair-WindowsImage -Online -RestoreHealth

This command scans for corruption, downloads replacement files from Windows Update, and attempts

After running the repair commands, restart your computer to apply any fixes.

 

T.S

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Apr 25, 2024 Apr 25, 2024

Copy link to clipboard

Copied

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...

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Apr 25, 2024 Apr 25, 2024

Copy link to clipboard

Copied

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.S

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
May 05, 2024 May 05, 2024

Copy link to clipboard

Copied

performed a memory test, no issues found

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
May 05, 2024 May 05, 2024

Copy link to clipboard

Copied

CPU and GPU the most important in your case

T.S

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
May 06, 2024 May 06, 2024

Copy link to clipboard

Copied

As an update/closure I've stopped trying to diagnose the issue. My belief is somewhere in the adobe installation or third-party plug-in something was corrupted. I ended up wiping and reinstalling windows and my adobe programs, not installing the MotionArray plug-in (this was the last one to install when things crashed occasionally). I had been using the Dropbox plug-in and it had been stable and fine. Prior to reformatting the system i had uninstalled the plug-ins one at a time and it did not change the failure rate.

Currently I'm back to editing in a stable way on windows 11 with premiere 2024 and encoder 2024 but wasted a ton of time and didn't learn anything from a crash perspective. thanks to those that offered some diagnosis methods.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
May 06, 2024 May 06, 2024

Copy link to clipboard

Copied

LATEST

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...

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines