Solved Someone please help with this issue

[RicePanda]

I've been to several forums and still no one has actually replied with an actual fix or actual answer that would lead me in the right direction of if something is actually wrong with my GPU or something else. I need to know if I need to RMA my GPU or not.
Can't edit in Premiere without this error making my monitor go black and freezing my mouse and everything else until it comes back about 10 seconds later. It seems to ONLY happen in Premiere Pro, ONLY when using my GPU for playback is enabled. It doesn't happen with gaming so I'm confused as to why it's happening only with Premiere, I also get an error in Blender sometimes that says "CUDA Error - Failed to create CUDA context (Illegal Address) when attempting to render or preview my render.

"The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer."

Specs are
Windows 10
EVGA RTX 2080 Super
AMD Ryzen 9 3900x
x570 Aorus Elite
32GB (2x16) G.Skill ram
Corsair RMX 750x

I have also tried:
• Turning Digital Vibrance back to 50 on both monitors
• Reinstalling Premiere with no plugins
• Disabling XMP
• Using DDU to remove and re-install video drivers
• Installing Windows updates
• Uninstalling Windows updates
• Reinstalled Windows 10 64 bit completely fresh on an entirely new drive
• Disabling my second monitor
• Playing on a lower resolution
• Modifying the registry to increase the TdrDelay setting (up to 60 seconds)
• Monitored my GPU and CPU temps and there's no overheating
• Turning off GSYNC (I run fixed refresh)
• Turning off anti-virus
• Reseating the GPU AND switching to other PCIE lane
• Underclocking GPU
• Uninstalling MSI Afterburner
• Uninstalling Ryzen Master
• Turning off GPU LED's
• Ensuring Chrome is closed when editing
• Changing Windows power options to use max performance, with Link State Power Management off as well
• Entering Bios and making sure CSM Supports - Enabled/Disabled (neither helped) and Storage Boot Option Control - UEFI only (someone on another forum said to do this cuz it may help)
• Installing Studio Drivers (didn't help either! I've also tried downgrading to both game ready and studio driver versions 472.12 and still have the driver crash)

I have speccy and 3DMark Firestrike results as well as HWInfo if anyone needs that to try and help me figure this out.
Attached are images of HWInfo screenshots while firestrike was running.

 

[Pyro]

For the Blender issue, does it happen with specific files? A couple articles suggests it could be scene objects, resolution, or Optix. Another suggested it is the version, are you running the latest version? Here and here

This article references a lack of memory, have you watched to see if any system resources run out when you attempt to render?


Regarding your possibly faulty GPU, do you have another graphics card you could plug into the system and test against?


Attaching your speccy would be helpful for anyone wanting to chime in with suggestions.

 

[RicePanda]

For the Blender issue, does it happen with specific files? A couple articles suggests it could be scene objects, resolution, or Optix. Another suggested it is the version, are you running the latest version? Here and here

This article references a lack of memory, have you watched to see if any system resources run out when you attempt to render?


Regarding your possibly faulty GPU, do you have another graphics card you could plug into the system and test against?


Attaching your speccy would be helpful for anyone wanting to chime in with suggestions.

Hi there, the black screen/driver crash/pc freeze issue only happens in Premiere (As far as I know) I'm also currently running Blender 3.0 because the projects/plugins I use as far as I'm aware only work on 3.0. I should try latest yes but I'm afraid they won't work on it haha.

As for having another GPU, the only thing I have is an HD7770. The issue didn't start until a couple months ago which is quite odd as I haven't changed anything internal besides maybe a new Samsung m.2 nvme drive.

I also tried underclocking my GPU because it came factory OC'd and that didn't help with the illegal context in blender.

Here is my Speccy. http://speccy.piriform.com/results/eBaYH1tVjDFctXjQ56JKVNd

 

[RicePanda]

I probably should also say underclocking my core clocks and memory clock on my GPU didn't help with the driver crash in premiere either. As for the blender crash happening with only specific files, it happened in any file I tried viewing in rendered preview, and sometimes the project would crash mid render.

 

[Pyro]

You could attempt to install Blender to a different drive that way you can test the waters with the new version while keeping your old version intact as well.

Have you tried removing plugins? Sometimes such things can cause collisions with one another.

You could always try the HD7770, it'll be quite the step down, but if you want to test before you assume it's the GPU, it should work just fine.
Looks like the Ryzen 9 3900x doesn't have integrated, otherwise I would opt to just pull the unit.

I'm seeing two monitors here, one running at 240hz, and another at 60hz, is that correct?

 

[RicePanda]

You could attempt to install Blender to a different drive that way you can test the waters with the new version while keeping your old version intact as well.

Have you tried removing plugins? Sometimes such things can cause collisions with one another.

You could always try the HD7770, it'll be quite the step down, but if you want to test before you assume it's the GPU, it should work just fine.
Looks like the Ryzen 9 3900x doesn't have integrated, otherwise I would opt to just pull the unit.

I'm seeing two monitors here, one running at 240hz, and another at 60hz, is that correct?

Yes that is correct. 240hz and 60hz. I've been running that for quite some time, since I first built the PC. Could that cause a driver crash while editing in premiere? I just put the 240hz monitor on 60hz and the crash still occured.

 

[Pyro]

Heads up, you replying to every message isn't necessary, it can cause things to get a bit messy if done too much, replies can be typed right into the text box and the website will handle all continuity.

Could be, varying refresh can cause confusion sometimes, it's worth ruling out!

Setting your higher monitor to 60hz, or unplugging one of the monitors might make a change.

Unplugging a monitor and trying with one alone is a good idea regardless, if your monitor supports overclocking (from 240hz to 280hz or something of that nature) it may be worth turning that off.

 

[RicePanda]

Alright, sorry about that haha. I unplugged the 60hz monitor since changing the 240 to 60hz didn't help with the crashing and let you know what happens. Will update shortly!

 

[RicePanda]

Alright, that didn't help at all. I unplugged the 60hz and it seemed fine at first during playback in premiere. I kept pausing, playing, scrubbing footage and it was okay but then after doing it a couple of times it crashed the same way as before. I also noticed that every time I paused Premiere, my mouse would skip and kinda lag for a second or so every time I paused. The crash happened when I paused, and then clicked the premiere icon in my task bar to minimize the project but I'm not sure that is info that really helps.

 

[Pyro]

I see,

Is premiere up to date?

If so, have you attempted a reinstall/repair?

Did you notice any spikes in usage/temperature, can you recreate the problem while task manager is open (Or another program of your choice, MSI Afterburner, NZXT CAM, etc).

Have you tried other premiere files, do blank or smaller ones make a difference?

 

[RicePanda]

The thing is right, this is a new installation of windows. I had the issue previously and couldn't solve it so I decided to wipe the slate clean and try with a new install. Premiere is up to date and is a clean installation. I can check the temps and usage of my GPU with task manager while using Premiere and see if I can replicate to show you it. Give me a moment and I'll attempt it.

 

[RicePanda]

I really have no idea how to read this but the crash seemed to happen when it reached the red circle, PC froze and after a few minutes screen turned black and then the driver recovered. I have no honest idea why it went that high, temps were fine and stayed stable the entire time. When it crashes like this the video in Premiere is just a black screen and it forces me to restart Premiere after the driver finally recovers. Also if you see my driver date and ask why it's so old, its an older one because I was testing to see if an older would fix the issue which it did not.

 

[Pyro]

Does the same thing happen with your CPU?

When a CPU reaches 100% utilization, which is possible in rendering/editing especially, it can bring the entire system to a grinding halt.

I did a quick search, have you tried the steps below? If not a software issue, it's possible it's a setting.

1. Go to Premiere top bar and -> FILE
2. Project Settings -> General
3. Change the “Renderer” to -> the default option which is the “Mercury Playback Engine Software Only” or other option (that you might have)
4. And voila, it should be fixed!
5. You should see your output monitor again

 

[RicePanda]

See, I would use software playback only but doing that means it's using my CPU to preview the video and not my GPU which is extremely slow and choppy if the project gets big. I'll go ahead and check my CPU now to see if it spikes as well.

 

[RicePanda]

Alright, I have no idea if the CPU did it because uhh.... yeah. And when the driver came back, I had to close and reopen task manager because other wise it's a black box on my screen and the CPU graph was empty and just started back.

 

[RicePanda]

Alright.. I just tried doing the “Mercury Playback Engine Software Only” just to see and it crashed as well. CPU does not spike, it's only the GPU that spikes, even when using software only.

 

[Pyro]

Does it happen on everything you open in premiere or only certain files?

 

[RicePanda]

Every single project, even a new one with one singular video file.

 

[Pyro]

I see,

I'm not entirely sure what could be causing this, if you haven't tried swapping the GPU already, that could show you something, although these sound more like software-related issues to me.

Hopefully someone else can tag some people in who know more about this than I do.

 

[RicePanda]

I hope so haha. It's interfering with my work and I really am just as confused as you are I appreciate you trying to help a ton.