Plan-G crash c0000005 at 0CF40480 after Powershell-Update

Started by PlanGFlyer, July 20, 2019, 11:01:07 PM

Previous topic - Next topic

PlanGFlyer

Hi,

running Win7-64, I updated Powershell from 2.0 to 5.1 today (seems related as I never had such a Plan-G crash before).

After the update and some script development, I started Plan-G and it crashes immediately after the airports are loaded.

Event Viewer shows first an "event 1026 .NET runtime":
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 0CF40480

then an "event 1000 Application error"
Faulting application name: Plan-G3.exe, version: 3.2.1.151, time stamp: 0x5aae80f5
Faulting module name: GTII-OSD.dll, version: 2.0.3.2, time stamp: 0x5be93141
Exception code: 0xc0000005
Fault offset: 0x00030480
Faulting process id: 0x173c
Faulting application start time: 0x01d53f44ec2c8084
Faulting application path: C:\Games\Plan-G v3.2.1\Plan-G3.exe
Faulting module path: C:\Program Files (x86)\ASUS\GPU TweakII\GTII-OSD\Win7\x86\GTII-OSD.dll
Report Id: 2c076ce7-ab38-11e9-a2f0-ac9e17ec5720

After several crashes, I tried to remove user.config from AppData\Local and did a reboot, then it worked again for a short time.
As OpenStreetMap doesn't load, I selected OpenCycleMap, no crash, then OpenTopoMap, now it crashes again.
I deleted user.config again, no relief.

What I don't understand: the faulting module path points to ASUS GPU Tweak ?!?

Supplement: Plan-G works again.
I read the "Faulting module path" as I copied the event message into this thread.
Afterwards, I looked closer on the ASUS GPU TweakII:
on the monitor part of the GPU Tweak is a button "OFF/OSD"
I never touched this button but I saw that OSD was activated, so I set it to off.
Now Plan-G runs again.

Nevertheless, I don't understand the relationship between the ASUS tool and the Plan-G crashes... ???





tim arnot

For the OSM issue, install the beta at the top of this forum.

The crash is almost certainly related to the changes you made to your PC.

Tim. @TimArnot