Ray Proudfoot wrote: ↑Fri Sep 24, 2021 1:30 pm
Well it seems I spoke too soon. I setup a flight from Bordeaux to Madrid and at 6,000ft paused the sim to have some lunch. When I returned 40 mins later the dreaded DXGI_HUNG message greeted me. Looking at my moving map software on a WideFS PC it froze at 10,000ft so just a minute or two after being paused.
Looking in Event Viewer I'm seeing a new warning message:-
Error 4109. Application Prepar3D.exe has been blocked from accessing Graphics hardware. But that message is timed at 13:12 - some 30 mins after pausing the sim so seems strange.
I've reloaded the flight and expect it to continue without issue.
For those interested try pausing the sim and see what happens. If it does it consistently it should be helpful to LM. This is the first time in ages I've paused a flight and this happens even with the TdrDelay=0 entry. Odd, very odd. I can fly hundreds of miles without this problem but it occurs very soon after a pause.
@ Ray Proudfoot ,
You mentioned:
Looking at my moving map software on a WideFS ?
Which moving map software?
Did you previously mention moving map software on a WideFS PC (a two PC setup) ?
@Jorgen, thanks. Ran SFC and it did report corrupt files and repaired them. Also ran DISM twice with the parameters supplied and that was fine.
I'll reboot and then start P3D and then with a default Cub pause it at an airport. I'll leave it for a while and see what happens.
@Martyson, I've run two PCs for years without any issues. I use Aivlasoft's EFB and LittleNavMap both via SimConnect / WideFS. I don't see how that is relevant.
Ray Proudfoot wrote: ↑Fri Sep 24, 2021 2:25 pm
@Jorgen, thanks. Ran SFC and it did report corrupt files and repaired them. Also ran DISM twice with the parameters supplied and that was fine.
I'll reboot and then start P3D and then with a default Cub pause it at an airport. I'll leave it for a while and see what happens.
@Martyson, I've run two PCs for years without any issues. I use Aivlasoft's EFB and LittleNavMap both via SimConnect / WideFS. I don't see how that is relevant.
@ Ray Proudfoot ,
My question was :
Did you previously mention moving map software on a WideFS PC (a two PC setup) ?
If you had then I missed it in this topic.
When looking into a problem everything is relevant.
All add-ons installed (applications, scenery, vehicles, etc.)
Changes made to your system – overclocking, graphics accelerators (NVIDIA Inspector), debuggers
@Martyson, I’d appreciate it if you didn’t comment on this topic please. Your posts are of no help and I find your questions irritating. I’ve run exactly the same setup for years with both P3Dv3 and v4 without this annoying error.
What has changed? Installing P3Dv5. And yet no help from the people who write the code. That is poor, very poor.
In this previous post you requested more brainstorming ?
But, just now learning more about your custom 2 PC setup and hardware problems.
Maybe time for the General Debugging Steps or a P3D reinstall with testing in a default setup (without add-ons).
If you honestly believe a second computer is the cause of this I’m staggered. Sensible brainstorming I should have said.
I’ve installed the latest Nvidia drivers and will test with that. At this stage there’s no way I’m uninstalling and reinstalling only to test with a default aircraft at a default airport. That is pointless given the problem never occurs near addon airports and v5 is fine providing I don’t pause the sim.
Suggestion to LM. Turn off the DXGI_ERROR_DEVICE_HUNG message in the next point release and let us see if there really is a DirectX issue with the graphics engine.
Maybe, just maybe it’s a false positive that is causing this trigger because there’s absolutely no evidence of a graphics problem before that message is displayed.
In any case the option to ignore it and continue doesn’t work anyway. I’m curious about how Windows will handle this error.
I know you won’t respond but perhaps you could try it anyway.
Not a bad suggestion, if indeed the message is issued by P3D.
It might, however, originate from the driver (or elsewhere) and only be passed on by P3D. This is where my knowledge of programming runs out, apart from dBase IV my last programming experience was with PL/1 in the 70's.
@JorgenSA, agreed. I suspect it's generated by P3D but only a LM programmer would know. But they're not talking are they? Why not? It's a perfectly reasonable request.
Did you read your license agreement? The reason why they are not talking is in section 6.
Now, it would be different if you had a service contract.....
And, on occasion, answers actually do come. But then again, today is Saturday, even in the U.S., and everyone is entitled to their weekends. It is just us unpaid maniacs that are here on weekends and holidays.
Yes, read it and know the situation. The reason I'm suspicious of the warning is because if there really was instability in DX12 surely it's more likely to cause the problem when located at complex airports like Heathrow with 100+ Ai aircraft injected into the sim and the graphics engine working hard.
But I've never had a crash at any busy airport. Instead it happens at altitude in areas with no real graphical demands.
I can remember having these graphical problems on another non-FS PC several years ago. The display just went blank for a couple of seconds and then reappeared followed by a message saying the display wasn't responding.
But for P3D to generate a message and for it to be visible the graphics card has to be working. Hence my suspicion it's a momentary false positive. Hence why TdrDelay=0 (turning the message off) works on all my flights bar yesterday's paused one.
No hurry for a reply from them if they choose to reply. Monday 17:00 UT is fine. And you do a great job Jorgen!
