Hi everybody!

Have been putting p3d on hold for a few months but now when I tried starting it up again, it just quickly shows the screen where you select the aircraft and airport and such and then immediately closes... this is the note from the event viewer:

Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5364881c934f6ce8\nvwgf2umx.dll

Has anybody seen a similar issue and knows how to solve it?

 

EDIT: 

Im using the latest NVIDIA driver version 466.11

 

Edited April 21, 20215 yr by Nuggit82

24 minutes ago, Nuggit82 said:

Hi everybody!

Have been putting p3d on hold for a few months but now when I tried starting it up again, it just quickly shows the screen where you select the aircraft and airport and such and then immediately closes... this is the note from the event viewer:

Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5364881c934f6ce8\nvwgf2umx.dll

Has anybody seen a similar issue and knows how to solve it?

 

EDIT: 

Im using the latest NVIDIA driver version 466.11

 

Hi

 

There were some threads earlier on here about issues with the recent NVidia Drivers, specifically the last two updates causing CTD's for P3D.

Try to load an earlier driver up to 461.92 and see if that resolves your issue

 

Hope this helps

iam curious to why there is a reference to "amd64" in your faulting path if you use nvidia ?

PS iam no expert here lol

probably  why the  ctd 🙂

There are dozens of amd64 files in the C:\Windows\System32\DriverStore\FileRepository folder irrespective of the display type, that's normal.

 

If the file C:\Users\(you)\AppData\Roaming\Lockheed Martin\Prepar3D v4\Prepar3D.cfg file is edited so that the sim does not show the scenario window:

[USERINTERFACE]
SHOW_SCENARIO_WINDOW=0

That will start the simulator in the simulation rather than in the scenario window. If no CTD it might CTD when the simulation is ended and goes back to the scenario window.

 

The fault may be in the aircraft showing in the Vehicle box or the way the window is rendered on the system.

In the C:\Users\(you)\AppData\Local\Lockheed Martin\Prepar3D v4 folder, temporarily edit the file Prepar3D_Default.fxml so that sim value is empty and the simulator may then start without CTD but will complain about the missing vehicle reference:       

        <Section Name="Sim.0">
            <Property Name="Sim" Value="" />
 

Going back to an older driver may cure it as @Tokitaumelie already said.

 

That particular CTD is known to be an Nvidia driver issue. Lots of posts about it. Just use 461.92 and all should be well.

5 hours ago, sonny147 said:

amd64

AMD64 is the CPU instruction set type. It doesn't, BTW, mean that the CPU is an AMD chip, just that the AMD64 instruction set is in use.

If you'll recall, back in the days when 32-bit ruled the land, Intel came out with a 64-bit processor architecture know as Itanium. This was not a superset of the 'classic' x86 architecture and the chips were not directly compatible. AMD, on the other hand, came up with a set of 64-bit extensions to the x86 architecture which let you do 64-bit operations but was a superset of x86 so you could directly run x86 code on them. This instruction set came to be know as AMD64, while Itanium was IA64. Intel adopted the AMD64 instruction architecture for its own 64-bit successors to the x86 range, which is why Intel and AMD 64-bit desktop processors are entirely compatible, and that architecture is still know as AMD64 although these days people usually say x64. 

So that message just indicates that the problem was on a 64-bit system. It has nothing to do with the type of GPU - that's just a coincidence 🙂

My head hurts 😌thanks for the explanation though !

It's the driver. Roll it back, Solved it for me.

Thanks everybody for your answers, downgrading the nvidia driver worked!