Ray Proudfoot

P3D running but CPU not running at max speed

Recommended Posts

I have personal software I build myself, not from .NET and C++ libs, that can look at the system and determine what happens under the hood entirely. And so on another thread a P3D user discovers that P3D can no longer read the available aircraft. The software I provide, Ideal Flight, continues to work and describes all the aircraft on this malformed system. This is because that addon is built to a specification, and throughout, uses more sophisticated methods to ensure success. That can only be achieved with deep understanding of the system and P3D. An addon working better than P3D rather than messing P3D around, could be a first on AVSIM

Edited by SteveW
  • Like 1
  • Upvote 1

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

Some might see that I use problem solving terminology: 'Error Package'.

What do I mean by that. This is the minimum system to reproduce the error. That must be established first. Trouble is, problem solving on fully configured FS systems with lots of joysticks and addons and paraphernalia all added in can be like picking through a dog's dinner. Making peeling it back to the working system can be more time consuming than a re-install.

 

Share this post


Link to post

I have decided on a strategy. I shall log the problem with Chillblast just in case it’s a problem with the motherboard. That will safeguard my warranty. But given I never have any problems when flying that seems a remote possibility.

I will live with the issue until P3D v5 is released. It’s a simple fix after all. At that point I will uninstall v4 and reinstall a clean copy of Windows 10.

Once that is finished I will add my hardware one device at a time testing it with dxdiag. If there are problems when I do that I’ll consider my options.

If there aren’t any then it’s problem solved and I just need to install P3D v5 plus associated software. The PC is only used for flight sim.

There’s a good chance I’ll be getting a new yoke and pedals in the next few months anyway. Probably new throttle quadrant too. Having two Logitech USB quadrants does cause issues in P3D as they have to be plugged into the same sockets otherwise they swap IDs as far as FSUIPC5 is concerned.

Share this post


Link to post

..you're absolutely correct to not suspect the hardware Ray, none the less, a good idea to log the possibility with the supplier for their record. There's no indication for me in your posts that suggests your PC hardware is a problem. An ntdll.dll error basically tells you that some software does not get to talk to some other software in a timely manner. There's always a possibility that hardware can cause that but it would come with other obvious problems.

  • Like 1

Share this post


Link to post

Steve, glad you agree with my strategy. I’ve given it quite a bit of thought and can’t think of a better alternative.

I had a reply from CH and they said their hardware needs no special drivers, just the standard HID ones supplied by Microsoft. That’s why there’s no option to uninstall the driver supporting their hardware.

Onward and upward.

  • Like 1

Share this post


Link to post

Sure thing Ray, seems good. That's right about the CH item I mentioned to try in the startup in fact accesses those, that is of course what I was saying.

Share this post


Link to post

...by the way. Most engineers will say Driver and mean several different things, because folk know what a driver is - it is what they have to download and it updates something. When we install a joystick or any USB device it might install it's own driver or it might invoke the MS one - it's still a driver. However it might also install associated drivers, that you might not think of as drivers in your terms because it's not the thing you download. The thing was - not to worry about whether it's a driver or a program or whatever it is - the thing was to realise that the cross check with that could throw some clues into the foreground. Onward and upward.

Edited by SteveW

Share this post


Link to post

Thank you Steve and Ray for working this issue. I learned a lot in this thread.

  • Like 2

Share this post


Link to post

For Kevin's sake i'll explain a little more about that....

The CH installation, I didn't know if Ray had put it on from the CD included in the CH Pedals box. He may have. If not then there was a fresh trial of the system to be had with that. The CH installation creates device drivers (not supplied by MS) for the CHManager to implement virtual inputs like keystroke combinations. That would have tested out a large amount of stuff. The item in the startup group can't run on those under certain circumstances during the bootup which could have indicated to me that the system is held up in some aspect. So you  can see a very wide area can be covered in a few minutes testing, and it's easy to remove as I said.

  • Like 1
  • Upvote 1

Share this post


Link to post

I couldn't install from a CD as the pedals were bought around 15 years ago plus the PC has no DVD drive. I downloaded the software from the CH site. Maybe with a yoke more things could have been tested but with pedals we're talking 3 axes. Those axes worked fine in the standard Game Controller utility in Control Panel.

Share this post


Link to post
On 12/7/2018 at 1:52 AM, SteveW said:

..you're absolutely correct to not suspect the hardware Ray

Unless Ray ventures to tinker with his BIOS settings around some default values you've made a very very moot assumption, Steve.

  • Like 1

Share this post


Link to post
27 minutes ago, Dirk98 said:

Unless Ray ventures to tinker with his BIOS settings around some default values you've made a very very moot assumption, Steve.

I made it very clear in earlier posts to check it through, as you did Dirk - my words were 'put it to bed'. It is and was with reservations, that I agree with Ray on the hardware. There's been no BSODs. But you are correct, booting up twice with a different result is a possible clue something is wrong there.

Edited by SteveW
  • Like 1

Share this post


Link to post

...However, booting into Windows twice with a different result is more or less what happens anyway. So we must be careful. What instead we could be seeing is the order of systems functionality arriving. This could cause a lot of problems if one driver is held up for a logged on user rather than one of the system admins - not real people just processes that run as..

Share this post


Link to post

There are more and more red flags appear in this thread that are pointing to a hardware problem if you ask my 5 cents.

Share this post


Link to post
10 minutes ago, Dirk98 said:

There are more and more red flags appear in this thread that are pointing to a hardware problem if you ask my 5 cents.

Which hardware? And how can it be proved beyond any doubt that hardware x is the issue?

I’m about to hit the sack but I’ll leave you all to mull over this. I noticed a folder named windows.old on my C drive which I suspect is the OS prior to the big update I did to 1809.

These disappear after 30 days apparently so I’ve just performed a disk backup containing C.

Is it possible to roll back to the previous version utilising Windows.old and if so how is it done?

I would need to switch back to the current state if running dxdiag on that earlier build didn’t work.

Something for you to chew over. I’ll pick up replies in the morning.

Share this post


Link to post
1 hour ago, Ray Proudfoot said:

Which hardware? And how can it be proved beyond any doubt that hardware x is the issue?

No savings account in the bank can prove 100% of your savings, so don't ask about your hardware adversity and expect anything fixed in exchange from me.

1 hour ago, Ray Proudfoot said:

I’m about to hit the sack but I’ll leave you all to mull over this. I noticed a folder named windows.old on my C drive which I suspect is the OS prior to the big update I did to 1809.

That one is really easy - just Disk Cleanup it!

1 hour ago, Ray Proudfoot said:

Is it possible to roll back to the previous version utilising Windows.old and if so how is it done?

Not sure, most probably - yes, but always try using your Acronis  O/S saves instead and in the first place. You may ask me more about Acronis if you will.

 

 

Edited by Dirk98

Share this post


Link to post

Well, I would try switching BIOS to default first. Then, if it didn't work, a complete uninstall of P3D and derivatives, then reinstall of P3D might be helpful. If didn't work again - a complete reinstall of OS and P3D then. 

Edited by Dirk98

Share this post


Link to post
7 hours ago, Dirk98 said:

Well, I would try switching BIOS to default first. Then, if it didn't work, a complete uninstall of P3D and derivatives, then reinstall of P3D might be helpful. If didn't work again - a complete reinstall of OS and P3D then. 

Thanks but no thanks. I'll stick to my original plan.

  • Upvote 1

Share this post


Link to post

You might save a lot of time for yourself just doing #1 (setting BIOS to less ambitious values towards the default ones). Name your mobo (I know you mentioned it somewhere above) and I'll tell you how exactly to save your current settings, no matter how they frighten you into not doing that.

Share this post


Link to post
8 hours ago, Dirk98 said:

.. but always try using your Acronis  O/S saves instead and in the first place. You may ask me more about Acronis if you will.

I don’t use Acronis. Aomei is my preferred utility.

  • Like 1

Share this post


Link to post

Ray, you're a very experienced flight simmer, I'm really surprised how you haven't turned your BIOS and hardware inside out yet with this problem. Seriously. 

Edited by Dirk98

Share this post


Link to post

I for one start pulling RAM sticks out one by one when I see some really weird behavior like in your case.  :biggrin:

Edited by Dirk98

Share this post


Link to post
2 hours ago, Dirk98 said:

Name your mobo (I know you mentioned it somewhere above) and I'll tell you how exactly to save your current settings, no matter how they frighten you into not doing that.

Hi Dirk,

A bit strong as well as inaccurate, don’t you think? We know you mean well and are only trying to be helpful, but making statements like that are bound to irritate. Ray’s MoBo is in his signature and he has the user manual. In any case, Ray has made his position very clear and we should be respecting that. Are you aware of the conditions described in the 3 year warranty provided by Chillblast? If Ray starts meddling needlessly and then has to return to Chillblast cap-in-hand I doubt whether they would show much sympathy and it’s likely this would be reflected in the bill for their work and time spent restoring the status quo.

I doubt very much that Ray’s issues have anything to do with his core PC build. Nor do I suspect a system memory fault as he has stated repeatedly that Prepar3D runs fine for extended periods once the initial hurdle has been circumvented using his simple workaround.

Recommending a reinstall of the operating system has a familiar ring to it and is a complete turnoff as far as I am concerned. Never mind the effort invested into creating what could be quite a complex installation, such an action is not only being very generous with someone else’s time, but undermines their ability to troubleshoot an issue. Contrary to what many believe, such advice is usually completely irrelevant and unnecessary and should only ever be used as a last resort. Can’t recall the last time I was forced down that route. 

Regards,

Mike

  • Like 2

Share this post


Link to post
21 minutes ago, Cruachan said:

Hi Dirk,

A bit strong as well as inaccurate, don’t you think?

Of course!! :biggrin:

Thanks.

PS: how about shuffling those boards in the box though? ))

Edited by Dirk98

Share this post


Link to post

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