22 minutes ago, Luke said:

Or NVidia. Don't forget that most of the optimization that the drivers bring to applications is running their own GPU code instead of the original software's.

Cheers!

Don’t quite follow that Luke. If it was an Nvidia issue wouldn’t MSFS be affected too?

No, the driver substitutes its own GPU code for that which the program is executing. Not saying that is happening here, but that's what the drivers do - when they detect a particular non-optimized code stream that they have been coded to recognize, they ignore it and execute their own code.

Cheers!

Edited November 27, 20214 yr by Luke

3 hours ago, Luke said:

No, the driver substitutes its own GPU code for that which the program is executing. Not saying that is happening here, but that's what the drivers do - when they detect a particular non-optimized code stream that they have been coded to recognize, they ignore it and execute their own code.

Cheers!

There’s an “If” in your post. That suggests some doubt. So why wouldn’t MSFS be affected when P3D is? Rhetorical question really because even if you explained it I probably wouldn’t understand. 😉

4 hours ago, Ray Proudfoot said:

There’s an “If” in your post. That suggests some doubt. So why wouldn’t MSFS be affected when P3D is? Rhetorical question really because even if you explained it I probably wouldn’t understand. 😉

Yes, there's doubt - remember, no one knows what is the actual cause of the driver hangs so it's incredibly difficult to say who is to blame, but that doesn't stop a lot of people.

Why would one application be affected while others are not? Easy - we think of drivers as a standard interface layer to the hardware which behaves the same no matter what app is calling it. In most cases that is true, but not with NV drivers (and to a lesser extend AMD). The driver detects what is calling it and runs with different settings and in many cases different code depending on the app. But there too is doubt because I don't work for NV or write their driver code.

Cheers!

On 11/28/2021 at 3:49 AM, Luke said:

Yes, there's doubt - remember, no one knows what is the actual cause of the driver hangs so it's incredibly difficult to say who is to blame, but that doesn't stop a lot of people.

Such a reaction is perfectly understandable and always justified when it is invited by those Developers who fail to take ownership of such issues. Hiding behind a cloak of secrecy is bound to engender negative feelings which may or may not be expressed effectively by their user base. If reputations are tarnished as a consequence then so be it, they only have themselves to blame. What is surprising is the fact that none of this is new and yet there is little or no evidence that this business model is about to change anytime soon.

My assumption is that the responsibility for this persistent reticence lies far above the pay grade of the hapless coding wizards who are being systematically muzzled by their employer’s accountants and legal teams.

It seems very few are prepared to admit fault these days unless the pressure to do so becomes relentless and unavoidable. Such an attitude guarantees serious lasting loss of respect from those who simply desire a solution.

Mike

Reverted back to the 471.96 drivers along with the registry changes and managed a flight without the HUNG error.  Hopefully this is a working temp fix.

2 minutes ago, MarkW said:

Reverted back to the 471.96 drivers along with the registry changes and managed a flight without the HUNG error.  Hopefully this is a working temp fix.

I have remained with those drivers since finding the Registry “hack”.

I hope you continue to enjoy problem free flights Mark. 😁

Has anyone experienced the sim freezing for a few seconds with a buzzing from the sim speakers? I get it occasionally and suspect it’s a by-product of the Registry hack. As P3D continues as normal after the freeze I can live with it.

1 hour ago, Ray Proudfoot said:

I have remained with those drivers since finding the Registry “hack”.

I hope you continue to enjoy problem free flights Mark. 😁

Has anyone experienced the sim freezing for a few seconds with a buzzing from the sim speakers? I get it occasionally and suspect it’s a by-product of the Registry hack. As P3D continues as normal after the freeze I can live with it.

I get the occasional pause but not the buzzing.  I will add more stress on next flight when I use the FSL A320 flying at EGLL.

20 minutes ago, MarkW said:

I get the occasional pause but not the buzzing.  I will add more stress on next flight when I use the FSL A320 flying at EGLL.

I've never had the problem at EGLL. Just had it at LEBL in the PMDG737 after parking and pax offload. Just sitting there on GND PWR and I get it. Crazy and totally unpredictable.

Hi Ray,

I have had several sim freezes with buzzes in different situations besides the infamous blue screens and after countless tests done with no reports of problems attributable to my hardware, I remembered that before installing the ver. 3004 BIOS on my Asus Z390-P, these problems are not there never manifested and then I had decided to install the previous version but last November 23rd ASUS has released BIOS Ver. 3006 for the Z390-P with the generic note "Improve system's compatibility ".

I installed this new BIOS with the same setup I had on the previous one and so far, after about 80 hours of operation, about half of which you have spent flying on P3D, I have not encountered any problems.

Obviously it's early and it will take many more days to find out if my problems are solved as it is obvious that the same problems, precisely because of the non-uniformity of the hardware
installed on our PCs, they can be attributed to different factors with different solutions and this post of mine is just to report my experience on sim freezing, buzzing and blue screens that I have had
and hopefully solved with this new BIOS version.

47 minutes ago, Ray Proudfoot said:

I've never had the problem at EGLL. Just had it at LEBL in the PMDG737 after parking and pax offload. Just sitting there on GND PWR and I get it. Crazy and totally unpredictable.

Ray - are you using Latin VFR LEBL ?

44 minutes ago, MarkW said:

Ray - are you using Latin VFR LEBL ?

I’ve turned the system off but I think it is.

@RobPol471, I have to hold my hand up and admit I’ve never updated the BIOS since I bought the system 3 years ago. Remiss perhaps but it’s always something I’ve avoided doing working on the basis “if it’s working leave well alone”.

But W10 tells me my computer is not compatible with W11 which I know it is so I’m guessing it’s because of an old BIOS. And your statement that you’ve not had any buzzing or freezes since updating suggests it would be a good idea.

So maybe I can kill two birds with one stone with an update. Mine is the Asus Z370 Mk 2 (from memory) and although I have used Asus Suite to overclock the CPU those settings should not be affected with an update.

Something to put on the ‘to do” list tomorrow.

4 hours ago, Cruachan said:

Such a reaction is perfectly understandable and always justified when it is invited by those Developers who fail to take ownership of such issues. Hiding behind a cloak of secrecy is bound to engender negative feelings which may or may not be expressed effectively by their user base. If reputations are tarnished as a consequence then so be it, they only have themselves to blame. What is surprising is the fact that none of this is new and yet there is little or no evidence that this business model is about to change anytime soon.

You say this with such certainty as to who is to blame, and who is "failing to take ownership". Is it Microsoft, LM, NVidia or the hardware makers? Right now you have an issue that affects a small percentage of people, but more importantly cannot be consistently and predictably reproduced. In any competent software house that's going to get triaged way below other issues or bugs.

You have a limited amount of developer time - do you spend it on a bug or enhancement that is well-understood and planned that affects tens of thousands of users of a popular title, or spend it hunting down some obscure edge case that affects some percentage of users of a relatively insignificant title and even then might require a specific hardware/driver combination and hundreds of hours of man-hours just trying to reproduce? If my pension was invested in that company, you know which I would pick.

4 hours ago, Cruachan said:

My assumption is that the responsibility for this persistent reticence lies far above the pay grade of the hapless coding wizards who are being systematically muzzled by their employer’s accountants and legal teams.

I would go higher. The Iluminati and the United Nations are involved, after much prodding from Dr. Fauci and the Queen.

Cheers!

I updated my BIOS this morning. Let's see if that prevents the freezes and buzzing which occur at random in around 30% of my flights both when airborne and on the ground.