win32dll.dll causing high CPU load & stuttering in FSX

[Guest Mik75]

Yes, it's important to find out which specific DLL or process is being managed by rundll32.exe, as it would be that DLL causing the problem - not rundll32.exe itself.

Understood! I'll give it a go and I'll report back here with the results!

[Guest Mik75]

Hi there!

This is what I came up with:

 

[mgh 89]

Remember FSX isn't the only process that needs rundlll32.exe. If you want risk to crashing your system then by all means remove runddll32.exe!

[Guest Mik75]

Remember FSX isn't the only process that needs rundlll32.exe. If you want risk to crashing your system then by all means remove runddll32.exe!

Sure, but in the last 6-7 flights, everything went completely flawlessly. I'd like to know the reason behind that issue. But for now, shutting it down on every flight sim session, is an acceptable workaround for me.

[mgh 89]

Then you have a problem with your system.

[codechris 9]

Agree with mgh, you need to get to the bottom of that as you have a serious problem somewhere

[Guest Mik75]

Does the screenshot of the Process Explorer give any hint to someone with more knowledge about these system files / processes than I have?

As far as I understand it, the ntdll.dll does seem to eat up all this CPU power. But this dll is used by a lot of programs and processes, right?

What really surprises me, is that ending the rundll32.exe doesn't have any negative consequences.

[mgh 89]

rundll32.exe should not use 24.56% of CPU consistently. My systems shows it doesn't use any CPU with FSX running.

Thread 6808 shows that something is wrong. It shows several calls for _misaligned_access and also MsiInvalidateFeaturecache - possibly in running a loop?

 

Rundll performs the following steps:

    It parses the command line.
    It loads the specified DLL via LoadLibrary().
    It obtains the address of the <entrypoint> function via GetProcAddress().
    It calls the <entrypoint> function, passing the command line tail which is the <optional arguments>.
    When the <entrypoint> function returns, Rundll.exe unloads the DLL and exits.

https://support.microsoft.com/en-us/kb/164787

 

That suggests that the problem is not with rundll32.exe but with the .dll it is trying ro run.