![]() ![]() (The SkyTrak is working fine with the SkyTrak app by the way.) The standard "PG Sim Connector has stopped working" message has been followed several times by another message: "The instruction at 0x000000006E8D5423 referenced memory at 0x0000000092900DF0. After a total clean install of Steam and JNPG, the new computer is no longer crashing and showing bluescreens, but I'm still having major problems with the PG Sim Connector not working. ![]() The computer runs great for everything except JNPG. I decided to get a new computer to see if that would normalize the increasing JNPG problems and provide improved overall performance.įriday, I set up my new computer, which is a Dell XPS 8920 with 16k RAM, i7 CPU, NVidia 1070, Win 10, and a SSD drive. Rather than upgrading my old computer for memory, processor, graphics card, OS, etc. I was even getting total system crashes at times, with the dreaded bluescreen and the computer (a Dell PC) re-starting on its own. I had been having this problem with increasing frequency over the past couple of months, with PG sometimes not connecting normally and sometimes crashing during game play mid-round. The underneath registry record inside the zip will do that for you.I have been having major problems with getting the "PG Sim Connector has stopped working" error message when the JNPG game software is trying to connect (or has recently connected) with my SkyTrak unit. This key is absent as a matter of course so should be made. The above registry settle will kill the popup discourse for the present client, in the event that you need the setting to influence all clients on the PC then a comparable registry key should be made in the registry at HKEY_LOCAL_MACHINE. Just make sure you name it DontShowUI and then set the value to 1 by double clicking on your new entry. If you don’t have an entry called DontShowUI you can create one by right clicking an empty space in the right pane and selecting New > DWORD. Double click the entry on the right side called DontShowUI.Ĥ. Use the left side navigation to go to: HKEY_CURRENT_USER\Software\Microsoft\Windows\Windows Error Reportingģ. Type regedit into a new run command (windows key + r) and select OK to open the Group Policy Editor.Ģ. If the above method is not available to you in your version of windows then the alternative method is to use RegEdit.ġ. Select Enabled on from the radio buttons on the left and click OK Disable the Error Dialog Through Registry Editor ![]() Double click on "Prevent display of the user interface for critical errors" in the properties section on the right.Ĥ. Use the left side navigation to go to: Computer Configuration > Administrative Templates > Windows Components > Windows Error Reporting or for Windows XP Computer Configuration > Administrative Templates > System > Error Reporting.ģ. Type gpedit.msc into a new run command (windows key + r) and select OK to open the Group Policy Editor.Ģ. This method is not available in Home or Basic versions of Windows.ġ. If you have the GPO editor available to you in your version of windows this is the best way to disable the popup as it doesn't include any manual registry altering. Disable the Error Dialog Through the Group Policy Editor Here are a couple of ways to prevent the window from showing. This can also cause issues If you have applications which restart services if they go down. This error dialog prevents monitormyweb from detecting if the application has stopped running. This error dialog prevents your application from exiting unless you press one of the options such as "Close the program". A problem caused the program to stop working correctly". On the off chance that an application runs into an error it will probably display a popup window with the message "appname.exe has stopped working. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |