Why is every version of DaVinci closing?

Hey!
Up until a few days ago, my Davinci resolve has not been able to stay open. It randomly closes and I find this error in my event logger. I have run multiple tests on all my HW to which I believe there to be no faults and all drivers are up-to-date.
I have gone as far back as 18.1.
I have tried deleting my config files but still the issue remains.
My 4090 is selected in preferences also.

I have the log files but the file is too large to upload.
Can someone tell me which file is needed to understand the issue?

Any help is greatly appreciated as I am struggling to find an answer

[Peter Chamberlain]

First, try re-install the GPU driver.

We need the full resolve generated diagnostic logs.

yes they can be big.
put then on dropbox or similar with a link here, and a space in the path for the link so the forum doesnt see it as a path.

Thanks for the prompt response!

I have reinstalled 4/5 different GPU drivers - backdated to November last year (issues started earlier this month)

Logs: https://www. dropbox. com/scl/fi/6x2izl6bgxroh4fa63zj2/DaVinci-Resolve-logs-20240326-182959.zip?rlkey=xucwano8jjsagiua4tjqgril4&dl=0

[Dwaine Maggart]

And if you provide a Resolve diagnostics log, also provide a Windows System Information .NFO file.

Could it be as simple as overheating? Davinci is hungry obviously so maybe that is the culprit whereas other apps are not affecting so much.

Could it be as simple as overheating? Davinci is hungry obviously so maybe that is the culprit whereas other apps are not affecting so much.

I believe this to be the case but its kinda… strange.
I run several programs, stream and game at the same time without any overheating issues.
The moment I zoom in/out or cut and davinci needs to provide new thumbnails, it spikes to 100 and closes.
I have now changed this option to simple mode and I have not had any crashes yet.
I believe there is an issue with the generating of thumbnails.
I have a 13900k with updated drivers.

My replies are slow because they need approval, apologies!

The problem of the user comes from the CPU.

Seems that the thread 24 (what CPU do you have?) has encountered errors. WHEA errors are hardware errors.

Do you have any OC or under-volting on your machine? They could also be attributed to some RAM issues, bad RAM OC but in this case you are more prone to actual crashes and BSOD.

EDIT: i didn't fully paid attention to the last post, it is indeed a 32 thread CPU.

Overheating in general shouldn't come with crashes, the new CPUs are designed to throttle their performance down to a crawl when Tj Max (The maximum temperature allowed by the manufacturer) is reached to protect the CPU.

If no OC or other settings are changed try reseating the cooler.

Edit2: Found today and it is insane that this thing slipped trough Intel and Mother board manufacturers. They simply go beyond the CPU's specifications and they might cause issues.

This screenshot is from and Unreal Engine 5 game.

GJrBwfbXoAAojHS.png (47.74 KiB) Viewed 2132 times

Source link: https://steamcommunity.com/games/156669 ... 1?snr=2___

The problem of the user comes from the CPU.

Seems that the thread 24 (what CPU do you have?) has encountered errors. WHEA errors are hardware errors.

Do you have any OC or under-volting on your machine? They could also be attributed to some RAM issues, bad RAM OC but in this case you are more prone to actual crashes and BSOD.

EDIT: i didn't fully paid attention to the last post, it is indeed a 32 thread CPU.

Overheating in general shouldn't come with crashes, the new CPUs are designed to throttle their performance down to a crawl when Tj Max (The maximum temperature allowed by the manufacturer) is reached to protect the CPU.

If no OC or other settings are changed try reseating the cooler.

Edit2: Found today and it is insane that this thing slipped trough Intel and Mother board manufacturers. They simply go beyond the CPU's specifications and they might cause issues.

This screenshot is from and Unreal Engine 5 game.

The attachment GJrBwfbXoAAojHS.png is no longer available

Source link: https://steamcommunity.com/games/156669 ... 1?snr=2___

Thanks for this!
I'm going to download Cinebench now and run some tests.
I'll upload my temps.
I am struggling to capture my spikes with Davinci before it closes :/

Unfortunately XTU wont open on my system so I may need to do this manually from the BIOS.
I do have the latest BIOS update.

Edit:
Cinebench couldn't complete a multi-core test (only single).
I have disabled Enhanced multicore performance and will report back

Edit2:
With EMP turned off, I was able to complete a test on Cinebench.
Started using Davinci and turned on thumbnails again.
No crashes as of yet (3 hours)

Enhanced Multicore is a stupid setting that MB manufacturers came up with. It will OC the CPU out of spec.

I believe it solved your problem.

Enhanced Multicore is a stupid setting that MB manufacturers came up with. It will OC the CPU out of spec.

I believe it solved your problem.

I think so!
Thank you for your help!

Something I found funny was that both Intel and ICUE came out with updates yesterday...
Unsure if linked but I found it extremely coincidental

The short story of MCE is that it will OC all cores to the max turbo setting, while in reality the Intel Turbo boosts only some cores to max clocks and the rest will be lower gradually (it is documented on their spec sheet)

MCE is motherboard OC, and if your CPU can't handle all those clocks at the default voltages you start experiencing crashes like this.

The short story of MCE is that it will OC all cores to the max turbo setting, while in reality the Intel Turbo boosts only some cores to max clocks and the rest will be lower gradually (it is documented on their spec sheet)

MCE is motherboard OC, and if your CPU can't handle all those clocks at the default voltages you start experiencing crashes like this.

Thanks for the info!
Yes... after a lot of digging I found a lot of people having issues with 13th and 14th gen Intel chips because of this. I also discovered that it is apparently 'usual' for the CPU temps to be that of 100c. I started to doubt the thermal paste and my H150i mounting to be at fault and was considering a contact frame. Glad I found this option first.

Do you believe the latest update that was released yesterday would be worth downloading? I am in two minds as my PC has worked flawlessly today and I wouldnt want to brake something that isnt broken...

I am however concerned with the high temps and wondering if this update would fix this :/

No idea what to say, usually things go like this: don't fix it if it's not broken.

But these new chips do run hot just so you know.

No idea what to say, usually things go like this: don't fix it if it's not broken.

But these new chips do run hot just so you know.

It has started crashing again with the 551.86 Nvidia drivers.
Reverting back to older driver and seeing if that fixes it.

Reverted drivers back but Davinci 18.6 has started crashing AGAIN today after being fine yesterday...

Can someone check these logs?
I now have 0 warnings in Event Viewer

https://www.dropbox.com/scl/fi/0t0wu2aq ... tl339&dl=0

No idea what to say, usually things go like this: don't fix it if it's not broken.

But these new chips do run hot just so you know.

It has started crashing again with the 551.86 Nvidia drivers.
Reverting back to older driver and seeing if that fixes it.

Did you used Display Driver uninstaller?

No idea what to say, usually things go like this: don't fix it if it's not broken.

But these new chips do run hot just so you know.

It has started crashing again with the 551.86 Nvidia drivers.
Reverting back to older driver and seeing if that fixes it.

Did you used Display Driver uninstaller?

I did not.
But I did install the Studio driver to see if that would help but still crashes.
I did however find this thread: viewtopic.php?uid=16&f=21&t=190176&start=0

It seems like a very similar situation.
I have disabled the Intel UHD graphics in device manager and so far (15mins) no crashes.
I come back when I know more...

Damn it man. I feel like sometimes our hardware is working against us.

When i had an Intel CPU, all my problems with Premiere Pro at that time went away when i disabled the iGPU from BIOS as well.

Stay far away from Intel GPUs.

Damn it man. I feel like sometimes our hardware is working against us.

When i had an Intel CPU, all my problems with Premiere Pro at that time went away when i disabled the iGPU from BIOS as well.

Stay far away from Intel GPUs.

Worked for about an hour before it restarted my PC
Completely at a loss now...
Some people say turn off e-cores, others say lower the CPU voltage...
I duno.
I'll try your method of uninstalling the driver and reverting back to an older one.

Edit: Can someone read my log files and tell me what the issue is relating to?

If your whole machine is restarting, it’s a hardware issue. I’d check the power supply first, but faulty RAM or overheating components could be other suspects. DR is challenging the hardware like very few other softwares.

If your whole machine is restarting, it’s a hardware issue. I’d check the power supply first, but faulty RAM or overheating components could be other suspects. DR is challenging the hardware like very few other softwares.

I REALLY wish I could believe this but unfortunately I think this is a compatibility issue with DR. After multiple tests on my HW I cant find any indication that any of my components are faulty. I'm going to revert back to an older version of DR as it seemed a little more stable and turn off thumbnails.

DR crashes with or without EMP turned on and XMP 1 on/off.

If someone could take a look at the previous logs, that would be great as I am not experienced to read them.

[Dwaine Maggart]

Did I mention that if you sent a log, we also need a Windows System Information .NFO file?

Please also provide a project export .drp of the Hauntii project.

Did I mention that if you sent a log, we also need a Windows System Information .NFO file?

Please also provide a project export .drp of the Hauntii project.

Apologies, please find them here: https://www.dropbox.com/scl/fo/1ewbudao ... 8pirj&dl=0

[Dwaine Maggart]

Is the issue only happening when you use the Tintensity Fusion plugin?

What appears to be crashing Resolve is the msmpeg2vdec.dll file. This is Microsoft DTV-DVD Video Decoder.

Since you are using free Resolve, perhaps that's the decoder that gets used for one of the file types in your project. Not really sure what the exact Windows apps are that get used with the free version.

Do you have any other apps open that might be trying to use that?

If you are still getting WHEA Internal Parity Error that indicates instability of your system that isn't GPU but motherboard+CPU+memory related (see https://www.intel.com/content/www/us/en ... ssors.html), which can be "overclocking" triggered. To test your system (including video card) OCCT will do better job than XTU.

If you are suspecting video driver update is now triggering something new DDU is best way to roll back.

Is the issue only happening when you use the Tintensity Fusion plugin?

What appears to be crashing Resolve is the msmpeg2vdec.dll file. This is Microsoft DTV-DVD Video Decoder.

Since you are using free Resolve, perhaps that's the decoder that gets used for one of the file types in your project. Not really sure what the exact Windows apps are that get used with the free version.

Do you have any other apps open that might be trying to use that?

This is great info, thank you!

I have used Tintensity a few times previously without issues - probably the good part of a month.
I have also created multiple short form clips where this plugin is not applicable and still crashes.

The apps I have open while editing are (but not limited to):
Discord
Chrome
Steam
ICUE
GoXLR app
Intel driver & support assistant
Logitech GHUB
Lumia Stream (Lights app)
Nvidia Geforce
Stream deck (Elgato)
TotalAV (Installed after crashes incase of virus)
Windows defender
Mail app

If you are still getting WHEA Internal Parity Error that indicates instability of your system that isn't GPU but motherboard+CPU+memory related (see https://www.intel.com/content/www/us/en ... ssors.html), which can be "overclocking" triggered. To test your system (including video card) OCCT will do better job than XTU.

If you are suspecting video driver update is now triggering something new DDU is best way to roll back.

Thanks for this!

I have ran the test and all pass (Twice).
I couldn't actually get XTU to open on my system despite matching the compatibility settings.

My next step will be DDU.
I have however, just completed my project by setting simple mode (no thumbnails) after system recovery to two days ago.

My system was fine all day yesterday as previously mentioned in replies and assumed it was down to EMP being turned off. So today I installed the latest Nvidia drivers and installed a windows update.

I am starting to wonder if these windows updates are screwing with me as before all this started, I ran a windows update and then the issues arose.

Edit:
Something to point out quickly is that the WHEA Internal Parity Error has actually been around since Nov last year to which my DR was absolutely fine so I believe I should focus on this msmpeg2vdec.dll file?

Something to point out quickly is that the WHEA Internal Parity Error has actually been around since Nov last year to which my DR was absolutely fine so I believe I should focus on this msmpeg2vdec.dll file?

If it is still internal parity error it is possible to have condition in the system that doesn't show its face for a while until right circumstances are met. Code update triggering it doesn't automatically mean it is code's fault, it can mean code changed route it takes and now stepped into mine that wasn't there before. Also, overclocking can lead to "silicone deterioration". Or unstable system can lead to Windows corruption. And some of the apps you are using are known to be troublemakers. I will let BMD support suggest what you should focus on as they analyze your logs.

Something to point out quickly is that the WHEA Internal Parity Error has actually been around since Nov last year to which my DR was absolutely fine so I believe I should focus on this msmpeg2vdec.dll file?

If it is still internal parity error it is possible to have condition in the system that doesn't show its face for a while until right circumstances are met. Code update triggering it doesn't automatically mean it is code's fault, it can mean code changed route it takes and now stepped into mine that wasn't there before. Also, overclocking can lead to "silicone deterioration". Or unstable system can lead to Windows corruption. And some of the apps you are using are known to be troublemakers. I will let BMD support suggest what you should focus on as they analyze your logs.

I think I understand what you're saying. Another point, I did replace my AIO back in January as it for some reason just... failed. I do have experience building PC's so fitting the new one was no issue and I believe it is sitting correctly but this is all making me doubt myself xD
I have also only had this PC for a little under a year so would be a shame if its deteriorated so quickly.

I might just RMA and upgrade to a 14900k but I fear this may not remove the issue if it is software related

Another point, I did replace my AIO back in January as it for some reason just... failed.

Now that sounds as too much of a coincidence. Your motherboard / power supply could be pumping too much voltage to CPU and/or peripherals. Which power supply you are using?

I believe it is sitting correctly but this is all making me doubt myself

Only way to validate that is by doing CPU stress test and observing is any of the cores coming close to TJmax / throttling down.

I have also only had this PC for a little under a year so would be a shame if its deteriorated so quickly.

Anything is possible when it comes to too much voltage _IF_ it is the voltage. It can be years, it can be seconds.

I might just RMA and upgrade to a 14900k but I fear this may not remove the issue if it is software related

You shouldn't jump to RMA based on assumptions, you need to systematically identify culprit through tests and elimination process, starting with simplest easiest quickest one first. When testing memory use USB bootable version of MemTest86 with no less than 6 passes. It will also help if you could build yourself another boot disk with fresh install of Windows, Resolve and nothing else.

Another point, I did replace my AIO back in January as it for some reason just... failed.

Now that sounds as too much of a coincidence. Your motherboard / power supply could be pumping too much voltage to CPU and/or peripherals. Which power supply you are using?

Corsair Professional Series HX 1200W '80 Plus Platinum' Modular Power 1
Supply (CP-9020140-UK)

I believe it is sitting correctly but this is all making me doubt myself

Only way to validate that is by doing CPU stress test and observing is any of the cores coming close to TJmax / throttling down.

Results shown in previous message,s Intel test passed twice and user benchmark. Not really sure which other tests to do :/

I have also only had this PC for a little under a year so would be a shame if its deteriorated so quickly.

Anything is possible when it comes to too much voltage _IF_ it is the voltage. It can be years, it can be seconds.

I'm gunna need to take a look at lowering the voltage to 235w I think... Its easy on ASUS MB's but struggling to find a Z790 one. Apparently i'm looking for an 'Intel default setting'?

I might just RMA and upgrade to a 14900k but I fear this may not remove the issue if it is software related

You shouldn't jump to RMA based on assumptions, you need to systematically identify culprit through tests and elimination process, starting with simplest easiest quickest one first. When testing memory use USB bootable version of MemTest86 with no less than 6 passes. It will also help if you could build yourself another boot disk with fresh install of Windows, Resolve and nothing else.

Memtested several times, no issues there

Corsair Professional Series HX 1200W '80 Plus Platinum' Modular Power 1 Supply (CP-9020140-UK)

That is a good power supply, so it is less likely that could've been feeding too much power to peripherals causing AIO to die. Motherboard settings could do it though.

Results shown in previous message,s Intel test passed twice and user benchmark. Not really sure which other tests to do :/

Like I said, forget Intel's tests, they are too simplified, use OCCT. Its creator has YouTube video how to use it.

I'm gunna need to take a look at lowering the voltage to 235w I think... Its easy on ASUS MB's but struggling to find a Z790 one. Apparently i'm looking for an 'Intel default setting'.

You should consult those that are experts in motherboard you are using on enthusiast forums.

In the meantime work with Dwaine and try to get clean bare install on separate boot disk (like I said, number of software you are using has bad reputation for introducing issues). Oh, yeah, and I would try uninstalling all 3rd party plugins for Resolve you might have, starting with Tintensity, at least for the duration of troubleshooting.

Corsair Professional Series HX 1200W '80 Plus Platinum' Modular Power 1 Supply (CP-9020140-UK)

That is a good power supply, so it is less likely that could've been feeding too much power to peripherals causing AIO to die. Motherboard settings could do it though.

Yh...

Results shown in previous message,s Intel test passed twice and user benchmark. Not really sure which other tests to do :/

Like I said, forget Intel's tests, they are too simplified, use OCCT. Its creator has YouTube video how to use it.

Oh yh, OCCT, I'll check that out!

I'm gunna need to take a look at lowering the voltage to 235w I think... Its easy on ASUS MB's but struggling to find a Z790 one. Apparently i'm looking for an 'Intel default setting'.

You should consult those that are experts in motherboard you are using on enthusiast forums.

In the meantime work with Dwaine and try to get clean bare install on separate boot disk (like I said, number of software you are using has bad reputation for introducing issues). Oh, yeah, and I would try uninstalling all 3rd party plugins for Resolve you might have, starting with Tintensity, at least for the duration of troubleshooting.

I could reinstall it on a separate drive?

I could reinstall it on a separate drive?

What I mean is different boot disk, what they also call "dual boot". That way your original Windows install is untouched while you are troubleshooting with clean install.

I could reinstall it on a separate drive?

What I mean is different boot disk, what they also call "dual boot". That way your original Windows install is untouched while you are troubleshooting with clean install.

Thanks, I'll look into this!

Also, I ran OCCT for 10mins - no issues
I also checked online as other 13900k results and they all confirm that chip is designed to run at 100c.

Also, I ran OCCT for 10mins - no issues
I also checked online as other 13900k results and they all confirm that chip is designed to run at 100c.

Running single test for 10 minutes and calling it a day is insufficient. You didn't run GPU test, you didn't run PSU test. Get yourself familiar with all the options and test it thoroughly. I consider test success when it runs for much longer than 10 minutes.

Also, 100C is official Tjunction for your CPU. To quote others "That is the temperature at which transistor functionality begins to break down (become unreliable). Operating at this temperature is technically safe, but you're on the border of instability. Reaching it will cause the CPU to enable very aggressive thermal controls such as downclocking and reducing voltage, or turning the system off completely (though that doesn't seem to happen anymore). If the max is 100C, a few degrees beyond that point is called a thermal runaway event where the CPU no longer functions correctly and it becomes impossible to cool without shutting it down, potentially resulting in damage (but don't worry, you won't reach that point due to the countermeasures). Running that hot (99C) may reduce the lifespan and WILL reduce performance."

According to your HWInfo screenshots you are running P-cores at 5.5 GHz and E-cores at 4.3GHz. Intel's official Performance-core Max Turbo Frequency is 5.4 GHz. If I were you I would back off to 5.4 GHz before trying again. For any further advice on your hardware I would inquire in hardware enthusiast forums.

Also, I ran OCCT for 10mins - no issues
I also checked online as other 13900k results and they all confirm that chip is designed to run at 100c.

Running single test for 10 minutes and calling it a day is insufficient. You didn't run GPU test, you didn't run PSU test. Get yourself familiar with all the options and test it thoroughly. I consider test success when it runs for much longer than 10 minutes.

Also, 100C is official Tjunction for your CPU. To quote others "That is the temperature at which transistor functionality begins to break down (become unreliable). Operating at this temperature is technically safe, but you're on the border of instability. Reaching it will cause the CPU to enable very aggressive thermal controls such as downclocking and reducing voltage, or turning the system off completely (though that doesn't seem to happen anymore). If the max is 100C, a few degrees beyond that point is called a thermal runaway event where the CPU no longer functions correctly and it becomes impossible to cool without shutting it down, potentially resulting in damage (but don't worry, you won't reach that point due to the countermeasures). Running that hot (99C) may reduce the lifespan and WILL reduce performance."

According to your HWInfo screenshots you are running P-cores at 5.5 GHz and E-cores at 4.3GHz. Intel's official Performance-core Max Turbo Frequency is 5.4 GHz. If I were you I would back off to 5.4 GHz before trying again. For any further advice on your hardware I would inquire in hardware enthusiast forums.

New thermal paste and contact frame ordered but after several tests I think its safe to say that this is not a HW issue. Even if this doesn't fix the issue, it will still be good to have installed.

I do believe there is something conflicting with DR that is causing this issue. I run several different applications and multi-stream to several platforms with multiple tasks ongoing 3-4 hours minimum and nothing spikes my temps for 1-2 seconds to 100c. I am open to the idea that one of my apps is conflicting with DR to cause the crashes but as to which one, I am unsure.

I think for the time being, I'll transfer my project and recordings to my stream PC and edit from there. I'll install the same plugins and see if the issue arises.

In regards to the paid version of DR, does it use different decoders? Does this make a difference?
I fear I am in the same position as the OP in a previous thread where I am not conclusive as to whether I should purchase the paid version.

I will convert my USB into a bootable drive and have windows reinstall the necessary files if need be but it would be an absolute pain to fresh install.

I fear I am in the same position as the OP in a previous thread where I am not conclusive as to whether I should purchase the paid version.

Plenty of us are using Windows version of DR and aren't experiencing issue you are having. Further more in the last 2 years that I've been a member of this forum I don't remember anyone besides you having it (granted I don't read every single thread that is posted). At the same time plenty of non-Resolve users reported it with their systems, to the point Intel had to look into it and provide technical support article about it. So I think it is safe to say culprit is something about your system, even if gets triggered by Resolve, Resolve is not culprit per se.

So if I were you I would first find what it takes to have stable system with free version of Resolve. Only once you are there you should ask yourself should you purchase paid version. I have paid for my DR Studio, as I found it worth it, but before I did that I assured that foundation underneath it (my system) is as stable as humanly possible. Because if foundation everything else runs on isn't solid then nothing will be solid, you could be getting same issue when trying to use Premiere as you do now.

P.S. Do you have DaVinci Control Panels installed? If you don't have Speed Editor then uninstall them. Same thing for any other component you aren't actually using.

I fear I am in the same position as the OP in a previous thread where I am not conclusive as to whether I should purchase the paid version.

Plenty of us are using Windows version of DR and aren't experiencing issue you are having. Further more in the last 2 years that I've been a member of this forum I don't remember anyone besides you having it (granted I don't read every single thread that is posted). At the same time plenty of non-Resolve users reported it with their systems, to the point Intel had to look into it and provide technical support article about it. So I think it is safe to say culprit is something about your system, even if gets triggered by Resolve, Resolve is not culprit per se.

So if I were you I would first find what it takes to have stable system with free version of Resolve. Only once you are there you should ask yourself should you purchase paid version. I have paid for my DR Studio, as I found it worth it, but before I did that I assured that foundation underneath it (my system) is as stable as humanly possible. Because if foundation everything else runs on isn't solid then nothing will be solid, you could be getting same issue when trying to use Premiere as you do now.

P.S. Do you have DaVinci Control Panels installed? If you don't have Speed Editor then uninstall them. Same thing for any other component you aren't actually using.

I would hate to imagine a world where my system was not compatible

Yh, one of the first things I uninstalled

Edit: Premier pro and after effects works fine but I am trying to make the switch for the plugins.

Premier pro and after effects works fine but I am trying to make the switch for the plugins.

Have you tried uninstalling all 3rd party plugins for Resolve you might have, starting with Tintensity, yet? If not that is the very next thing I would try.

Premier pro and after effects works fine but I am trying to make the switch for the plugins.

Have you tried uninstalling all 3rd party plugins for Resolve you might have, starting with Tintensity, yet? If not that is the very next thing I would try.

Sorry, how do you uninstall a plugin?

This Tintensity plugin has been used before I started having issues though :/

Edit: Then again... I can edit 30 sec clips with minimal crashes

Premier pro and after effects works fine but I am trying to make the switch for the plugins.

Have you tried uninstalling all 3rd party plugins for Resolve you might have, starting with Tintensity, yet? If not that is the very next thing I would try.

Sorry, how do you uninstall a plugin?

I've never had to do it so I don't know the process, you will have to search, sorry.

This Tintensity plugin has been used before I started having issues though :/

Yes, but there must be a reason why Dwaine is inquiring about it so it costs you nothing to try.

Is the issue only happening when you use the Tintensity Fusion plugin?

What appears to be crashing Resolve is the msmpeg2vdec.dll file. This is Microsoft DTV-DVD Video Decoder.

Since you are using free Resolve, perhaps that's the decoder that gets used for one of the file types in your project. Not really sure what the exact Windows apps are that get used with the free version.

Do you have any other apps open that might be trying to use that?

Please help
<3

[Dwaine Maggart]

Your system seems to be having lots of weird issues. If you are certain the hardware is not at fault, my only other suggestion would be a clean rebuild on the system drive, i.e. reinstalling Windows from scratch and reinstalling your apps from scratch. Ideally on a new drive, keeping your current drive intact.

If you took such an approach, I'd recommend installing Resolve after the Windows install, and before anything else, to see how it behaves. If it works, then start installing other stuff, and see if something specific breaks Resolve.

If you are certain the hardware is not at fault, my only other suggestion would be a clean rebuild on the system drive, i.e. reinstalling Windows from scratch and reinstalling your apps from scratch. Ideally on a new drive, keeping your current drive intact.

If you took such an approach, I'd recommend installing Resolve after the Windows install, and before anything else, to see how it behaves. If it works, then start installing other stuff, and see if something specific breaks Resolve.

+1

Your system seems to be having lots of weird issues. If you are certain the hardware is not at fault, my only other suggestion would be a clean rebuild on the system drive, i.e. reinstalling Windows from scratch and reinstalling your apps from scratch. Ideally on a new drive, keeping your current drive intact.

If you took such an approach, I'd recommend installing Resolve after the Windows install, and before anything else, to see how it behaves. If it works, then start installing other stuff, and see if something specific breaks Resolve.

Gotcha, thanks!

To op and whoever might be experiencing similar issues: You might want to see following thread about issues with Intel 13th and 14th gen Raptor Lake CPUs

viewtopic.php?f=21&t=199480