|
Post by finforfun on Jul 8, 2019 11:38:15 GMT -5
Hello all, I fired up FS9(WIN 7) after updating the latest AI, and the program stuttered and took ages to load. My first instinct was blame something in the AI update, but reloading the previous AI didn't cure the problem. FSX runs fine with about 15% CPU usage, but with FS9 CPU usage is at 100% from the very beginning. Closing the program takes for ever, and on shutting down the PC to clear the problem, a message comes up to say "Waiting for background program to close" before shutting down. This only happens after trying to run FS9. My local computer support guy said automatic updates can cause problems with "Copy Protect". The PC details a Critical Windows Update yesterday morning, that was before I tried running FS9
Any Ideas?
Thanks
Fin Fraser
|
|
|
Post by Tom/CalClassic on Jul 8, 2019 13:54:49 GMT -5
Try loading the default Cessna at Sea Tac Flight.
Try renaming the fs9.cfg file and starting FS.
Try setting the Compatibility mode to Win XP.
|
|
|
Post by chris_c on Jul 9, 2019 0:21:39 GMT -5
I had something very similar with FS9 and another sim. The cause was a runaway Rundll32.exe file that pushed up the CPU usage and remained running after FS9 closed. It also affected starting the program and sometimes FS9 would not run although the program was showing as active in the Task Manager.
The consensus on another Forum was that the root cause is a Windows-7 update and my problems started after a big one (12-updates) a couple of weeks ago.
Next time this happens, check the Task Manager after closing FS9 and see if Rundll32.exe is still running. If so close it using the End Process button on the Task Manager.
If you are seeing this, go to the folder Windows\SysWOW64\... and check to see if there is a file named gameux.dll. If so, this is probably the root cause of your Rundll32.exe problem.
You cannot delete this gameux.dll but I renamed the file extension from gameux.dll to gameux.xxx and this completely cured the high CPU usage and runaway Rundll32.exe issue. You will need to set Administrator permissions to change the file extension. If this works, do a cold boot to make sure there are no unintended consequences but I have experienced no further problems with high CPU usage since editing that gameux.dll file.
Good luck, if this is your problem and the fix works that's great. If not, restoring the status quo is pretty straightforward.
Chris
|
|
|
Post by nmlw on Jul 9, 2019 10:17:00 GMT -5
I agree. Renaming the gameux.dll file solved my problem also.
|
|
|
Post by finforfun on Jul 9, 2019 10:29:56 GMT -5
Tom, and Chris, thanks for your suggestions. Tom, I ran FS9 in compatibility for XP mode and processor usage dropped to between 40-50%, and the program will run without stutter. Chris, I couldn’t change gameux.ddl extension though, the message displayed is “You require permission from Trustedinstaller to make changes to this file”, and Rundll.exe doesn’t show in the Task Manager, however on following the steps I have to take to get FS9 to fly this is what became apparent:
CPU usage is running at about 1% on start up. On first double clicking the FS9 icon a tab comes up asking if you want to run the program, click yes and CPU usage jumps up to 60% before settling down at about 30-40%, but FS9 does not run, but obviously something IS running, but nothing is showing in the Task Manager applications window. Double click on FS9 icon again and then FS9 runs, but with elevated CPU use rate, but not 100% as before.
On shutting down the PC the message comes up from Task Manager saying that a program is still running, before turning off after about 10 Seconds. The program is not identified, Task manager is aware of it but as I said above it is not displayed the applications window.
I will struggle on, but at least I can fly.
Fin Fraser
|
|
|
Post by chris_c on Jul 9, 2019 10:49:57 GMT -5
@fin Fraser,
I use a process management utility called Process Lasso that provides more details and options for managing CPU usage and it shows what's happening in the CPU in much more detail than the Windows Task Manager. See if you can get your computer support guy to talk you through the process of setting Administrative permissions for Windows system files or gameux.dll specifically. This will allow you to change the file extension for gameux.dll and should solve the CPU usage issue. Microsoft made certain that when it comes to system files and folders, some Administrators are more equal than others.
Chris
|
|
|
Post by johnhinson on Jul 9, 2019 12:44:44 GMT -5
|
|
|
Post by chris_c on Jul 9, 2019 13:36:30 GMT -5
The badly misnamed TrustedInstaller and the memory-eating CompaTelRunner are two of the worst CPU hogs inflicted on Windows users by the Microsoft software bureaucracy of bad ideas. Fortunately once support ends for Win-7 next year, they can be completely disabled and consigned to the dustbin of horrible operating system programs.
Chris
|
|
|
Post by Erik on Jul 11, 2019 8:42:22 GMT -5
For your info, I have been able to replicate the situation of 100% CPU use by rundll32.exe and FS9 only starting by launching a second instance of it. I also seem to have cured it by disabling the Game Explorer gameux.dll, confirming most of the above. Note that I do not run FS9 in compatibility mode under either Win7 or Win10 and it works fine. The apparent cure was indeed disabling gameux.dll in both mentioned system folders (/System32 and /SysWOW64). The easiest way for me to do this was to Take ownership of these files, after which they can be renamed. How to Take ownership can be found online and should not be a problem for a bit of a compu-techy. In other words: this is the option I would definitely (have someone) try. In case it's of interest, the following seems to be happening from what I gather. - Upon launching FS9 and other legacy 'games', gameux.dll will try to go online and check for updates. It has been a known fact that 'fs9 phones home', at least once a day if able, and therefore launching it without an internet connection can take very long: it keeps trying. - Possibly, a somewhat recent Win7 update aggravated the situation, resulting in rundll32.exe eating up one processor core's capacity for a very long time, with fs9 waiting to actually launch. - Starting fs9 a second time, it seems 'aware' the online check has already been initiated and launches without further delay. Obviously, this can lead to problems thereafter, if the first instance of fs9 becomes active as well. I could imagine this leading to a corrupted fs9.cfg for instance.
- With gameux.dll disabled all of the above is avoided.
And If all that is correct, the problem should not really exist on Win7 machines where the Game explorer is still active but can go online. I will try and test that too tomorrow.
Erik
|
|
|
Post by Pixel Pilot on Jul 11, 2019 9:21:26 GMT -5
Thank you Erik for your information. After reading this thread I looked at Task Manager on my Win 7 system to see what processes were running and I found that there were two instances of run32dll.exe running. One was using 0% processor and the other was using about 20% processor. FS9 was using about 35% processor. It takes about 30 to 40 seconds for FS9 to load on my system. I'm going to try disabling gameux.dll and see what improvements there are.
Ed
|
|
|
Post by chris_c on Jul 11, 2019 10:39:50 GMT -5
For what it may be worth, a copy of gameux.dll still exists in my System32 folder but it seems to have zero effect on FS9 and I have not disabled it because it does not appear to produce any negative effects. Disabling that same file in the SysWOW64 folder solved the runaway Rundll32.exe CPU usage issue and being on or off line does not seem to matter, at least on my rig.
Chris
|
|
|
Post by Erik on Jul 11, 2019 10:50:50 GMT -5
Hopefully that will help, Ed. Thanks Chris. And I just found out I still had the 64 bit version active and did not get mentioned problems... That was on Win7-64 and the 32 bit version of gameux was disabled, for completeness. Have you tested starting FS9 for the first time in 24 hours without being offline? I always have the impression the 'call home' is executed just once daily (though I'm not sure of that either).
Erik
|
|
|
Post by Pixel Pilot on Jul 11, 2019 12:30:47 GMT -5
I just finished disabling gameux.dll(renamed them to gameux.txt) in both my Windows/System32 and Windows/SysWOW64 folders. I restarted Windows and then started Task Manager. I then started FS9 and looked at the processes tab on Task Manager. FS9 was using about 35% of the CPU. Same as before. There was no instance of run32dll.exe running. I'm going to leave my system this way as I don't see any reason to have run32dll.exe running and using 20% of my CPU. Once again thanks Erik for your information.
Ed
|
|
|
Post by Pixel Pilot on Jul 12, 2019 9:14:03 GMT -5
Well as it turns out having gameux.dll available in Windows/System32 is important. Without it none of the games installed in Win 7 are available. You know things like solitaire, minesweeper, freecell, or hearts. So I renamed gameux.txt back to gameux.dll in Windows/System32 and everything is fine. There is still no instance of run32dll.exe running even after starting FS9 which is what I wanted.
Ed
|
|
|
Post by johnhinson on Jul 12, 2019 11:43:34 GMT -5
Well as it turns out having gameux.dll available in Windows/System32 is important. Without it none of the games installed in Win 7 are available. You know things like solitaire, minesweeper, freecell, or hearts. So I renamed gameux.txt back to gameux.dll in Windows/System32 and everything is fine. There is still no instance of run32dll.exe running even after starting FS9 which is what I wanted. Nobody has said you should remove the file from System32 and it should be left alone there,
Odd that this fix has been available since 2012 but FS users have only recently become affected.
John
|
|