after patch, persistent rundll32 100% cpu, followed by system

[major0noob]

only solved by uninstalling the game...

ftplog.txt has thousands of lines of 

*** fceGetInteger

preceded by

 

 

E:\Games\Battleground Europe\Battleground Europe\/wwiiol_1.36.1.1-1.36.1.2.exe' opened
R: 150 Opening BINARY mode data connection for /wwiiol_1.36.1.1-1.36.1.2.exe (2115680 bytes)
*** fceGetInteger
*** fceGetInteger
*** fceGetInteger
<307:422.731>
recv(2656):1023
*** fceGetInteger
recv(2656):1023
*** fceGetInteger
recv(2656):1023
*** fceGetInteger
recv(2656):1023
*** fceGetInteger
recv(2656):1023
*** fceGetInteger
recv(2656):1023
*** fceGetInteger
recv(2656):1023
*** fceGetInteger
recv(2656):1023
*** fceGetInteger
recv(2656):1023
*** fceGetInteger
recv(2656):1023
*** fceGetInteger
recv(2656):1023
*** fceGetInteger
recv(2656):979
*** fceGetInteger

[PITTPETE]

 

[Augetout]

Sounds like the problem I had, @PITTPETE

[PITTPETE]

yup

[Augetout]

Major0noob, I had the same issue, and in fact that issue has made it so I can no longer play my windows chess, despite having been remedied for WW2Online.  It isn't a ww2online deal---it's one of the last windows 7 updates (I do not know which) that is causing the issue.

The fix I was given included a 'do at your own risk' piece of advice, and ended up being some sort of online download that renames the rundll32 boondoggle, so when Windows 7 looks for it, (in my case as it pertains to ww2online) it doesn't find it and thus the game works fine.  @PITTPETE I think it was @OLDZEKE (if memory serves) who had the 'do at your own risk' fix.

[geeezer]

I had geeks look at drivers, programs, for malware etc.  and then uninstalled and then downloaded game and still goes to 100% cpu.   Did second round of delete and re-download. Still skyrockets to 100% CPU.    Giubg to miss this game!  

 

[Scking]

1 minute ago, geeezer said:

I had geeks look at drivers, programs, for malware etc.  and then uninstalled and then downloaded game and still goes to 100% cpu.   Did second round of delete and re-download. Still skyrockets to 100% CPU.    Giubg to miss this game!  

 

yeah.. Unfortunately it seems Microsoft has had some type of patch that caused this issue. Only way we have seen people fix this issue is by following the instructions we pointed you to in the other thread you posted in. I will point to it here as well for you: http://ubeogesh-things.blogspot.com/2012/08/resolve-it-finally-game-explorer-aka.html

So far it seems like everyone who has used the recommendations from that website have fixed their issue. 

[major0noob]

just did a fresh install and followed the instructions, still happens but i can get in by starting the game a second time and killing the rundll32 process in task manager

better than a system crash...

[blkfalcon]

Rename the file 'gameux.dll' in windows/syswow folder. You'll need to take ownership to change permissions before you can change it.

[major0noob]

yup, did both syswow and system32, ownership and permissions set. still get it

only working method for me is open twice and use task manager to kill the process

[Augetout]

@major0noob I have found that I have to shut down background programs in order for the run32dll/100% CPU deal to come right back.  Hell, I can't even play my MS Chess without planting my CPU at 100%...  Same if I forget not to turn MS Teams off before loading game.

Methinks Microsoft wants us on 10??   bastages.

[blkfalcon]

Hmmm, worked for me....changed to gameux.mjl in syswow folder only.

[snappled]

I've had windows updates turned off this past year or so ... but have been seeing the same problem since 1.36 was released. CPU goes straight to 100% after any computer restart (soft). Cold-boot does not create the same issue.

[PITTPETE]

Everyone i directed to this fix has had success>>  http://ubeogesh-things.blogspot.com/2012/08/resolve-it-finally-game-explorer-aka.html

[wockawocka]

Some thoughts from Wocka:

 

"There must be another way than renaming files in the system folder":
Best solution to this would probably be if the game was not launched with rundll32.dll at all.
My knowledge about why we use a 32-bit launcher is low. Although I would guess this is due wwiionline being old of course.

So if we did a collection of money some years ago, to make this 64-bit proof for Mac, didn't we make the game 64-bit-proof for Windows as well?

Because now it seems Microsoft has begun removing parts that were used in Vista/Windows7 in all of their distributions (like MAC did probably), so this rundll32.dll is a good example what happens if Microsoft just de-activate a [censored] component like this Games Explorer.

 

Reality:
So in Windows8 and 10 the Game Explorer is de-activated

In Vista/Windows7 something went wrong, and renaming the gameux.dll is one way of fixing it.

Although: I would not call it "fixing it" because Game Explorer is still being called upon by rundll32.dll.

 

Scary fact:
For the nerdy bunch I tried to go a bit deeper, and it seems like "Games Explorer" is calling Microsoft on an address stated in a regKey (
HKEY_CLASSES_ROOT\Local Settings\Software\Microsoft\Windows\GameUX\ServiceLocation) each time a game is launched. And about 2072 old games (that have a reference in GameUXLegacyGDFs.dll next to gameux.dll file) are "calling home". But only if you have ever started Games Explorer on your Vista/Windows7 computer with a game installed.

 

Possible easy fixes without fiddling with Windows:
One easy way of getting around this problem for the devs (without making the game a native 64-bit application) could actually be to rename all game executables.

OR

Let the user install the game to a path that has never been used after Games Explorer was last run. This has not been tested by me, although it seems that Games Explorer remembers all paths you ever used historically, and even the drive number of all drives you have run the executable on. But only IF you start Games Explorer. So don't start Games Explorer! Ever!

Tried a part of this solution by simply making a copy of ww2.exe -> wwiionline.exe, and then making a shortcut to it. 

Result: rundll32.dll never got a problem, meaning, no 100% CPU utilized by rundll32.dll.

Summary:
Games Explorer was "invented" in 2009, and that is why the proposed fix from "Ubeogesh" from 2012 still works.

And in the end, even I had to crawl in and, and rename a file in my system folder. Although I do NOT like fiddling in my system folders, so a final tip for all. Remove your full access to the renamed file (gameux.dll.Ubeogesh if you ran the bat-file). Otherwise we all open up a possible attack vector (very remote, but still a file in a system folder that is fully accessable by a user that is not "TrustedInstaller")

 

Wocka out