Hi there!

I recently un- and reinstalled FSX on my Win7 64bit machine. Before that, my 2 years old install of FSX would show bad stuttering and high CPU load most of the time. So I decided to make a fresh start. I ran out of SSD space anyway, so that new install gave me the opportunity to clean things up! ;-)

The "new" FSX (DX9, and the only two tweaks being Highmemfix and Affinitymask) performed absolutely fantastic, with fps well above 20 in the heavy hitters over and on complex scenery and most of the times with values of over 30! CPU load was 60-85% and all was stutter free!

Until yesterday, when I took the NGX for a short flight from ENVA to ENBR (both Aerosoft). Already on the ground, CPU load went above 90%, and in the air, it went up to 100% really often. FPS were still ok, but stutters apperead and the fluidity was gone. I opened up the task manager and had a look at the performance monitor. All 4 cores were pretty much maxed out, most of the time. Then I had a look at the running applications and services. FSX consumed the most CPU cycles, 50-80%. But directly underneath it, the win32dll.dll showed up with a usage of 20-30%!

I ended the flight, shut down FSX and the win32dll.dll (via task manager) and my system was idling at 0-2% CPU usage. I fired up FSX once again, this time to do a flight from ENBR to ENGM v2 (both Aerosoft) in the NGX (B736), this time with FS2Crew, to put a maximum load on my machine. All went flawlessly, CPU load maxed out at 85%, with an average of around 70-75%, and I had a complete stutter free flight with frames at or above 25 on the ground, and well above 30-40 in the air!

Anybody knows what the win32dll.dll really does and if it is ok to delete or deactivate it (by renaming it) permanently without any negative consequences?

According to Google :

 

A Win32 DLL is a binary file (written in C or C++ and using calls to the Win32 API rather than to MFC classes), that acts as a shared library of functions that can be used simultaneously by multiple applications. Visual C++ will create workspace and project files for your program that you then add your own code to

 

So no I would not disable or delete. Something running is using that dll, so you will need to find it. FS2Crew ?

According to Google :

 

A Win32 DLL is a binary file (written in C or C++ and using calls to the Win32 API rather than to MFC classes), that acts as a shared library of functions that can be used simultaneously by multiple applications. Visual C++ will create workspace and project files for your program that you then add your own code to

 

So no I would not disable or delete. Something running is using that dll, so you will need to find it. FS2Crew ?

I googled for it as well, but there has been no definite answer. As I wrote above, I did a complete flight, with all the bells and whistles (including FS2Crew), and I had zero problems and a very smooth flight!

How could a "lower level" (without any real knowledge about the importance of this dll) system file cause such an immense CPU load?

I made 3 more succesful flights with the win32dll.dll service stopped.

ASN, the PMDG NGX, T7 and Coolsky DC-9, FTX Global, Vector, FS Global 2010 mesh, FTX Open LC, Aerosoft airports, the ARCARS of the VA I am flying for and FS2Crew worked without any problems!

My FSX experience has never been more fluid!

Win32DLL.dll, which is the file that seems to be causing problems on your system, is NOT a Windows system file. Note carefully the naming convention.

 

The Microsoft system file, which is required for Windows to function properly, is Win32.dll... The file you are referring to is Win32DLL.dll It has a .dll extension, and also contains the letters "DLL" as part of the file name.

 

I Googled this, and though there is no solid evidence that this file is malware, neither is it a genuine system file that is part of the core MS operating system. At least one reference listed the file as the product of a Chinese manufacturer - perhaps part of a device driver for a piece of hardware in your machine?

 

In any case, if the name is, in fact, Win32DLL.dll, then disabling it is not going to crash your OS.

Found this... more research is necessary.

 

It appears to be associated with DriverMax, a program I believe updated Windows application drivers. If the file you have is associated with DriverMax then it's conceivable that it was searching your drivers and checking to see if they needed updated.

 

win32dll.dll is a Win32dll belonging to RC-UMH from Rainbow China Co.,Ltd Non-system processes like win32dll.dll originate from software you installed on your system. Since most applications store data in your system's registry, it is likely that over time your registry suffers fragmentation and accumulates invalid entries which can affect your PC's performance. It is recommended that you .

Edited May 27, 201511 yr by DaveCT2003

Thanks a lot for your input guys!

The name of the file is indeed win32dll.dll.

My system gets regularly checked for malware and viruses (using the scanning function of my anti virus software), and I never used or installed a software like "DriverMax". So, I have no idea how this file found its way onto my system.

But after a few succesful flights, I am pretty sure that it doesn't have any vital function on my system, other than eating CPU cycles like crazy!

(20-30%, according to the task manager).

Hi there!

I had another look today, to be sure what the exact name of the process is.

Its name is quite different, it´s called rundll32.exe, Google says it´s a normal Windows process.

I found out, that it starts, as soon as Active Sky Next connects to my FSX. That is the exact moment, the CPU load goes as high as 100%.

As stated above, ending it, doesn´t seem to cause any negative consequences, at least on my last 4 flights.

Here is a screenshot of the taskmanager:

 

win32dll.dll is not a Microsoft Windows file and is not included in a FSX installation, so you must have added it..

 

rundll32.exe is a a Microsoft Windows file.

win32dll.dll is not a Microsoft Windows file and is not included in a FSX installation, so you must have added it..

 

rundll32.exe is a a Microsoft Windows file.

It´s been my fault, the name is rundll32.exe.

I´ve read on the web, that it can be a malware. From the taskmanager, is there a way to find out where the executed exe file is located? A CPU load of almost 30% in average isn´t normal for that kind of file, right?

Plus, ending the process, doesn´t change anything in Terms of stability.

In Process Explorer move the mouse over  rundll32.exe to show its details.

In Process Explorer move the mouse over  rundll32.exe to show its details.

Thanks, but unfortunately, that doesn´t seem to work. (Win7 64bit).

I can right click the process, then the menu to end the process, etc. pops up.

It´s been my fault, the name is rundll32.exe.

I´ve read on the web, that it can be a malware. From the taskmanager, is there a way to find out where the executed exe file is located? A CPU load of almost 30% in average isn´t normal for that kind of file, right?

Plus, ending the process, doesn´t change anything in Terms of stability.

While malware MIGHT disguise itself as rundll32.exe, I doubt that is what is happening to you.

 

Rundll32.exe is indeed a standard Windows component. It's purpose is to load and run other DLL files. There are probably hundreds of DLLs that might load using rundll32.exe - it is a very generic program. There are other Windows operating system files that work in a similar way, like Taskhost.exe, or Svchost.exe

 

If you use a program like Process Explorer, that can show all running processes on your computer, you might well see 5 or 6 separate instances of rundll32.exe, each managing a different DLL.

 

Unfortunately, the default Windows task manager will not show enough details to know which underlying DLL is being managed by rundll32.exe that might be tying up your CPU. You will need Process Explorer to find out more info. It is a utility program that is absolutely free, and available from Microsoft. A quick Google search should give you a download link.

While malware MIGHT disguise itself as rundll32.exe, I doubt that is what is happening to you.

 

Rundll32.exe is indeed a standard Windows component. It's purpose is to load and run other DLL files. There are probably hundreds of DLLs that might load using rundll32.exe - it is a very generic program. There are other Windows operating system files that work in a similar way, like Taskhost.exe, or Svchost.exe

 

If you use a program like Process Explorer, that can show all running processes on your computer, you might well see 5 or 6 separate instances of rundll32.exe, each managing a different DLL.

 

Unfortunately, the default Windows task manager will not show enough details to know which underlying DLL is being managed by rundll32.exe that might be tying up your CPU. You will need Process Explorer to find out more info. It is a utility program that is absolutely free, and available from Microsoft. A quick Google search should give you a download link.

Thanks a lot for your very detailed answer!

I´ll have a look at the Process Manager for sure!

I´d really like to find out what´s going on with this process.

I just ended another NGX flight with the rundll32.exe being turned off, and no problems at all and a super fluid FSX... Very strange!

Thanks a lot for your very detailed answer!

I´ll have a look at the Process Manager for sure!

I´d really like to find out what´s going on with this process.

I just ended another NGX flight with the rundll32.exe being turned off, and no problems at all and a super fluid FSX... Very strange!

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.