Sign in to follow this  
ega

Win10 Update: CPU always at 100%

Recommended Posts

I just upgrade from Win7 64  bit to W10. Had a few problems I could solve but one I couldn´t: FSX-SE doesnot start - it shows the splash screen and it stays there. Did delete the fsx.cfg but disdn´t solve this issue.

 

By checking the Task Manager I see that  my CPU is always at "CPU, 100%, 5.80GHz" (I do have a i7-2600k OC). That is odd!

 

If CPU is always at 100% (with nothing running), it is clear that FSX cannot start.

 

Does anyone have some idea what is going on?  Why is the CPU always at 100%??

 

I would be grateful for any help!

 

PS: It seems this is a problem related to Sandy Bridge 2600k CPU - it is likely a MoBo Bios update is required. As this CPU is quite popular did anyone faced this issue?   

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

If the CPU is running at 100%, there must be something running.Did you click on "App History" and the "Details" tab? 

Share this post


Link to post
Share on other sites

Thanks Jude - yes, I did but it shows in Details Tab that CPU is 0 in all processes.Therefore it  is not possible to have a 100 CPU usage.  

 

As I  added into my original message, it seems this a problem related to Sandy Bridge CPU. I am worried because FSX does not run at all - I presume it may be related to this problem but I am not sure because I think this is just a faulty indication (the 100%CPU) .

Share this post


Link to post
Share on other sites

I have a Sandy Bridge i5 2500k @ 4.5GHz and I've been using W10 fine since August.

 

The only "issue" I have is Task Manager displaying an incorrect clock speed. It says I'm running the CPU at 6.19GHz, but one could only dream of that.

 

If you open the Task Manager to the default screen (first tab), you can see which program is using the CPU. Click "CPU" near the top and it will sort in descending order. You should see whatever is using 100% of the processor. Also, make sure your BIOS is up to date (especially if you have an older processor like Sandy Bridge. Back up first), and update all your other drivers.

Edited by linux731

Share this post


Link to post
Share on other sites

Obrigado Diego.

 

It is indeed documented that this behavior is typical of Sandy Bridge CPUs and it is solved by a bios update - I know this is not that simple - should you have a link on how to do it I will be grateful (I do have a Asus P9P67 Pro Mobo).

Share this post


Link to post
Share on other sites

Thanks Jude. As W10 64 bit is not listed, I presume I have to select W8.1 64 bit as operating system. 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this