27 minutes ago, Cruachan said:

Hi Ray,

You kicked off this thread by mentioning TdrDelay=0 as if it was still present in your Registry whereas you told us you had deleted this entry in favour of TdrLevel=0 in the previous thread. 

 

The two appear to do the same thing. Yes, I started with TdrDelay as that's what I found when searching for a solution. Later on I found the FS Labs post that said TdrLevel fixed it for those users. So I switched to that one.

You don't say if you have this problem and are using either of these settings. Are you?

3 hours ago, Ray Proudfoot said:

You don't say if you have this problem and are using either of these settings. Are you?

Hi Ray,

I hoped you wouldn’t ask..lol!

I too was experiencing the occasional ‘HUNG’ variant of this issue and this appeared to resolve with a change in driver set...this was several months ago. I have been away from flight simulation since then, but have maintained an active interest on the forums.

I’ve been keeping MSFS up to date (not all that easy on 10-11 Mbps d/l) but haven’t flown it in anger for ages. Not sure I really want to right now, but will likely dip into it over the upcoming winter months.

Prepar3D is my primary platform and is likely to remain so. Considerable time, effort and cash have been invested and I’m not about to throw that away any time soon. As such it’s in my interests to keep abreast of developments and record any relevant fixes/workarounds that appear from time to time. If I can contribute in any way then I’m happy to do so. I intend to update to the latest version in the not too distant future (files are downloaded and ready), at which point I want to be prepared for any eventuality. If the issue under discussion rears it’s ugly head again then I’m content in the knowledge that there are a few things I can try. Hence my gratitude for all your efforts with this somewhat vexatious problem.

You might have noted that I am currently on the latest NVidia driver set. So, all bets are off as to how this will work out!

Regards,

Mike

Mike, I may switch to 472.12 game drivers, not Studio ones. It’s important you run the latest version of P3D so you’re aligned with me. 5.2HF1. I just updated the client which is the recommended procedure.

The huge forced updates of MSFS much be exasperating whatever your internet speed. Beta software for several more months it would appear.

Another two flights today with no DXGI issues although a lengthy pause with a buzzing from the case was slightly alarming when taxiing out at LFPG. The sim continued and nothing in Event Viewer. I wonder if it’s related to the DXGI thing.

hmm i have DWORD 32 bit and QWORD 64 bit option - which one is it ? 

 

sorry got it QWORD it is 

Michael Moe

Edited September 29, 20214 yr by Michael Moe

15 minutes ago, Michael Moe said:

sorry got it QWORD it is 

Correct. 64-bit software requires the 64-bit entry.

11 hours ago, Ray Proudfoot said:

Correct. 64-bit software requires the 64-bit entry.

Normally i would see a DXGI at FSDT KORD in the MaddogX using gimbal camera after some time sitting at the gate but after 1 hour and night it did not crash so this is in for good.

 

Thanks

Michael Moe

On 9/25/2021 at 5:58 PM, Ray Proudfoot said:

Indeed I did. The reloaded flight with the older drivers was fine.

Well, it finally happened to me. Using the 472.12 drivers which were working fine, this morning during a flight, I needed to access a shortcut (because I couldn't remember the program  name), on the desktop. As soon as I shrunk the screen, it paused and after a few seconds the dreaded DXGI message came up.

I will also try the Registry entry and see if it solves my problem as well.

 

5 hours ago, IanHarrison said:

Well, it finally happened to me. Using the 472.12 drivers which were working fine, this morning during a flight, I needed to access a shortcut (because I couldn't remember the program  name), on the desktop. As soon as I shrunk the screen, it paused and after a few seconds the dreaded DXGI message came up.

I will also try the Registry entry and see if it solves my problem as well.

 

So please for the love of God one of the IT gurus here, tell me how shrinking the screen and it dxgi ctding cant be a software coding issue. 

I've had a ctd before with the same thing (but not a dxgi) a Standard hang and then poof it disappers. 

How is it not a coding error with a 20 plus year old sim. 

 

 

On 9/30/2021 at 1:37 PM, IanHarrison said:

Well, it finally happened to me. Using the 472.12 drivers which were working fine, this morning during a flight, I needed to access a shortcut (because I couldn't remember the program  name), on the desktop. As soon as I shrunk the screen, it paused and after a few seconds the dreaded DXGI message came up.

Hi Ian,

Perhaps it was about to happen during the flight and shrinking the screen was an unhappy coincidence leading to confusion as to the actual cause. Can this be reproduced?

Regards,

Mike

12 minutes ago, Cruachan said:

Hi Ian,

Can this be reproduced?

Regards,

Mike

I have put the suggested Registry entry in as a precaution and the latest flight of 13 hours had no interruptions. I even tried shrinking the screen just after take-off and nothing untoward happened. I don't know what might occur if that entry is not there. Maybe I'll try a flight without it and see what ensues.