2 minutes ago, srcooke said:

Yes I have both entries set Ray.

I'll add the other one when I land. Just passed Toulouse and all is okay. Famous last words! 🤣

I've just landed at Manchester and no problems during the flight. No pauses with a buzzing noise. Just a nice flight with no problems. Tomorrow I'll add the other entry to the Registry. Time for a brew!

The sad thing is that if you address your problem in the P3D forum, there are users who instead of doubling down on LM to make a statement, instead give you such ingenious tips like using the newest graphics driver or deactivating the Intel integrated graphics driver in BIOS...  Yeah, or cleaning the GPU pins...  The next user will soon recommend you to swap the screws of the computer case for a different color 😄

28 minutes ago, Afterburner said:

  The next user will soon recommend you to swap the screws of the computer case for a different color 😄

Blow that! You mean it doesn't work?

Now I am stuck. 

OR maybe it depends on the colour.

3 hours ago, Ray Proudfoot said:

I've just landed at Manchester and no problems during the flight. No pauses with a buzzing noise. Just a nice flight with no problems. Tomorrow I'll add the other entry to the Registry. Time for a brew!

I removed the registry entry this morning during flight, as I thought nothing would happen until a reboot.

Two minutes later, P3D froze and although I left it to recover, the PC rebooted itself.

I have now put those 2 entries in the Registry and will see what difference it makes.

1 hour ago, Afterburner said:

The sad thing is that if you address your problem in the P3D forum, there are users who instead of doubling down on LM to make a statement, instead give you such ingenious tips like using the newest graphics driver or deactivating the Intel integrated graphics driver in BIOS...  Yeah, or cleaning the GPU pins...  The next user will soon recommend you to swap the screws of the computer case for a different color 😄

It does open you up to some strange suggestions. And they never say if they have / had the problem and what fixed it for them. None of those ideas I’m sure.

25 minutes ago, IanHarrison said:

I removed the registry entry this morning during flight, as I thought nothing would happen until a reboot.

Two minutes later, P3D froze and although I left it to recover, the PC rebooted itself.

I have now put those 2 entries in the Registry and will see what difference it makes.

Maybe coincidence, maybe not. I don’t know the impact of editing the Registry on the fly (excuse the pun). I’d be more inclined to do it with nothing running then reboot.

2 hours ago, Afterburner said:

The next user will soon recommend you to swap the screws of the computer case for a different color 😄

YES ! that's thing :-)

I had exactly this problem...

I had to resolve issues with a home built computer and found the motherboard was loose due to having been screwed into the case with the wrong screws.

Had to replace the mounting posts and screws, and the screws were a different colour.

So there you have it, the right colour screws fixed the problem, heh.

Cheers

8 hours ago, Ray Proudfoot said:

Maybe coincidence, maybe not. I don’t know the impact of editing the Registry on the fly (excuse the pun). I’d be more inclined to do it with nothing running then reboot.

I know, that's what I should have done, so probably my fault.

This I wrote this morning on the LM forum:

"I only intervene to say: so far 10 pages for many tips from" users "to try to solve this problem that is now has been running on P3D for ... years and I wonder: but someone from LM "official" who can give us explanations about it is there or we have to think that   DXGI_DEVICE_HUNG is ... included in the purchase price of P3D? "

19 hours ago, srcooke said:

It is decimal Ray.

In case you missed the link: https://substance3d.adobe.com/documentation/spdoc/gpu-drivers-crash-with-long-computations-128745489.html

Sorry but why is it here an DWORD value? I thought it should be QWORD?

8 minutes ago, mobiel said:

Sorry but why is it here an DWORD value? I thought it should be QWORD?

It should be a QWORD and that’s what I entered. That Adobe article refers to a 32-bit OS.

35 minutes ago, mobiel said:

Sorry but why is it here an DWORD value? I thought it should be QWORD?

The existing entries created by a clean install of Win10 64bit Pro in the graphics sub-section are DWORD, I see no reason for the Tdr entries to be different.

2 minutes ago, srcooke said:

The existing entries created by a clean install of Win10 64bit Pro in the graphics sub-section are DWORD, I see no reason for the Tdr entries to be different.

Stephen. I fail to understand the logic that a 64-bit program running in a 64-bit OS would require the TdrDelay entry to be 32-bit. 

The vast majority if not all OS created entries are DWORD Ray.

6 minutes ago, srcooke said:

The vast majority if not all OS created entries are DWORD Ray.

In that case I’ll swap the QWORD for DWORD. Thanks. Perhaps done for backward compatibility.