Sign in to follow this  
stratfordman10

Continual Crashing to Desktop

Recommended Posts

For some reason as of yesterday after about 10-20 minutes of flying the sim stops and just reverts to my PC welcome page.

 

This is not a Vas issue and there is no fatal error shown either-the sim just cuts out totally.

 

I have Active Sky Next running and the usual Orbyx products i.e FTX Global and Open LC Europe and FTX England but I have at least 1.2 g of Vas Left when it cuts out.

 

Earlier I checked the Task Manager and it stated that the monitor was not responding.

 

I downloaded the latest Nvidia driver yesterday.

 

Any thoughts/comments would be appreciated.

 

Michael

Share this post


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

Is this a TDR issue?  

 

I have this as well with Windows 10 and Nvidia 355.60, but it's actually happened on every driver released for Windows 10.  Unfortunately there appears to be no solution, assuming that this is your problem.

Share this post


Link to post
Share on other sites

Roll back to your previous driver What happened to you is why I never download the latest driver from Nvidia.. ever!!!

Share this post


Link to post
Share on other sites

Roll back to your previous driver What happened to you is why I never download the latest driver from Nvidia.. ever!!!

 

It might not help OP, it certainly didn't help me, i have rolled back all the way to 352.84 (the first non-beta driver on Windows 10) it made little difference to me, other than i got two hours out of the sim before a BSOD, rather than the 10 minutes and TDR i get on 355.60 and all previous versions.

 

It's is good advice for the OP.

Share this post


Link to post
Share on other sites

Hi,many thanks for your replies.

 

Yes,the problem may be the latest driver.

 

Forgive my ignorance but how do I uninstall the latest driver and go back and install a previous version and which version would be best.

 

My OS is windows 7

 

Many thanks.

 

Michael

Share this post


Link to post
Share on other sites

Hi again,

 

Many thanks for your advice.

 

Could I uninstall through the start menu rather than downloading the software?

 

Also,which driver would you recommend to reinstall.

 

Sorry to be a pain but you are really helping me out here.

 

Many thanks,

 

Michael

Share this post


Link to post
Share on other sites

Hi again,

 

Many thanks for your advice.

 

Could I uninstall through the start menu rather than downloading the software?

 

Also,which driver would you recommend to reinstall.

 

Sorry to be a pain but you are really helping me out here.

 

Many thanks,

 

Michael

 

I use 347.88 Works great with Windows 7 and P3D. 

Share this post


Link to post
Share on other sites

Hi again,

 

I uninstalled the new driver and then installed driver 347.88 but after 20 minutes of flying the same issue occurred and the sim stopped totally and I was left with my PC windows screen,so nothing changed.

 

I have never experienced anything like this before and I am now at a total loss as obviously I cannot use the sim beyond 20 to 30 minutes.

 

A previous post mentioned about this possibly being a TDR issue and I am wondering what this means etc.

 

Any further help/ advice would be very appreciated.

 

Michael

Share this post


Link to post
Share on other sites

A previous post mentioned about this possibly being a TDR issue and I am wondering what this means etc.

Any further help/ advice would be very appreciated.

Michael

Hi Michael,

 

I assume he was referring to 'Timeout Detection and Recovery'. A Google search will provide you with Microsoft's explanation.

 

I wish people would stop using acronyms without qualification in their posts unless they are in common usage and are well known to everyone. It is not helpful and implies (whether intentional or otherwise) a sense of ill-founded superiority over the rest of us. Use of acronyms should be restricted to those instances where the item is referred to repeatedly in a post. In this instance the poster should have stated the first instance as 'Timeout Detection and Recovery (TDR)'. Thereafter it would be reasonable to use 'TDR' by itself as a shorthand way of abbreviating the text.

 

Just in my humble opinion (IMHO), of course, for what it's worth (FWIW).

 

Mike :)

Share this post


Link to post
Share on other sites

Hi Mike,

 

 

Many thanks for your reply.

If it is a TDR issue is there any way that I can rectify the problem?

 

Many thanks.

 

Michael

Share this post


Link to post
Share on other sites

 

 


I assume he was referring to 'Timeout Detection and Recovery

 

Yes that was me, very sorry for not explaining it; i have been looking at mine for around 3 weeks now, so i have TDR running around in my dreams.

 

 

 


If it is a TDR issue is there any way that I can rectify the problem?

 

Firstly it's worth checking if it actually is a TDR issue.  Go into Event Viewer (after the problem has occurred), look in System for a Warning 4101 saying something along the lines of:

 

Display driver nklddmkm (if nVidia) stopped responding and has successfully recovered.

 

Assuming you have this, you can try removing all over-clocks and cleaning the fan on the card, it's recommended, i would be surprised if it works.

 

Unfortunately the best fix is finding a driver that doesn't cause them, you can manipulate registry values, but i have had no success with this.  When in Windows 7 i had good luck with 352.86, it's quite an old driver and caused stuttering in GTA V but other than that was pretty stable.

 

Please be aware that some of the older drivers don't cause TDR errors (at least on my machine) they cause hard blue screens of death, which is much worse.

 

Assuming that you feel like editing the TDR values try this (very much at your own risk):

 

https://forums.geforce.com/default/topic/694754/geforce-drivers/tdr-manipulator-v1-1-02-23-2014-/

 

I would take the time to read and understand the comprehensive description provided.

 

Hope that helps and once again sorry for not explaining myself better, i certainly don't think i am superior to anybody, just a lapse on my part.

Share this post


Link to post
Share on other sites

Thanks for your reply again,

 

Before receiving your reply just now I tried another flight and after about 15 minutes it crashed to desktop 'PDx3 exe has stopped working' and it showed the following information;

 

Fault Module Name   ai_player.dll

 

Fault Module Version  2.5.12946.0

 

Fault Module Timestamp  555f2e53

 

Exception Code  c0000005

 

Exception offsett  00045d69

 

Before investigation TDR further I am wondering whether I might have a faulty dll file here.

 

I apologise if the answer is obvious.

 

I was flying the 737 NGX at the time of the crash and I still had 1.7 vas left.

 

Many thanks in anticipation.

 

Michael

Share this post


Link to post
Share on other sites

The faulting module is not always the reason for the crash. However, that it ISN'T a kernel or driver error being reported is a clue that this is NOT likely to be a TDR error, but is most likely related to either power supply or temperature issues. Clean the fans as advised.

 

If not it could be as simple as needing the UIAutomationCore.dll fix, which you can google. This often presents as a sudden crash at a regular interval.

Share this post


Link to post
Share on other sites

HI louis,

 

Many thanks I shall download the UIAutomationCore fix first and take it from there.

 

Michael

Share this post


Link to post
Share on other sites

Hi Mike,

 

If it is a TDR issue is there any way that I can rectify the problem?

 

Michael

Hi Michael,

 

Having wasted a huge amount of time in my life fruitlessly chasing problematic issues, such as this one is proving to be, I have learned that it's always worth checking the memory modules for any faults before embarking on what could be a lengthy troubleshoot.

 

If I were you I would download the latest MemTest86:

http://www.memtest86.com/download.htm

 

Under Windows Downloads choose the 'Image for creating a bootable USB drive'.

 

When the file is unzipped you will see several files - read the included instructions and you will soon have your bootable USB flash drive with MemTest86 ready to run. You may have to enter the System BIOS to ensure your system will be booting from the USB drive.

 

If your System has been overclocked then return it to standard clock before proceeding any further.

 

Test each RAM module in turn using the slot your motherboard manual advises you to use if only one module is installed.

 

Plug in the USB flash drive and boot.

 

Each MemTest test pass consists of 10 sub tests. Allow it to run 3 test passes and if ANY red text lines appear in the lower half of the MemTest screen you should regard this as a FAIL. If the first stick passes then power down, remove it, insert the second stick and reboot the system with the USB flash drive still in situ. This process may take several hours to complete so be patient.

 

Once you are sure all memory sticks are okay you can then move on to consider other possible causes.

 

Good luck!

Mike

Share this post


Link to post
Share on other sites

I have tried nearly everything and yet still after 10-20 minutes p3d closes down and it goes straight to the desktop.

 

I then open the task manager and states the following;

 

Monitor IPC - 1454332 not responding

 

Active Sky running

Ezdok Camera running

UT2 services running

 

For some reason it appears that the monitor could be the problem.

 

Would appreciate further comments.

 

Michael

Share this post


Link to post
Share on other sites

Hi Michael,

 

Found this:

 

"There are various IPC’s which allows a process to communicate with another processes, either in the same computer or different computer in the same network.

 

Pipes – Provides a way for processes to communicate with each another by exchanging messages. Named pipes provide a way for processes running on different computer systems to communicate over the network.

 

Shared Memory – Processes can exchange values in the shared memory. One process will create a portion of memory which other process can access.

 

Message Queue – It is a structured and ordered list of memory segments where processes store or retrieve data.

 

Semaphores – Provides a synchronizing mechanism for processes that are accessing the same resource. No data is passed with a semaphore; it simply coordinates access to shared resources.

 

Now, I would be the first to acknowledge that I may be barking up the wrong tree. However, until you have eliminated a faulty memory module from the equation I don't believe you should be spending too much time exploring other possibilities. If it does turn out to be a memory address fault/s then the solution is simple - change the affected module and test again.

 

You cannot assume that your memory sticks are fault free. I know, it has happened to me on a couple of occasions over the years. A system can appear to be working normally until the right conditions come along to produce a problem. Brief memory testing such as occurs at POST (Power-On Self-Test): http://www.webopedia.com/DidYouKnow/Hardware_Software/BootProcess.asp

are insufficiently rigorous to unmask many memory address faults. MemTest86 while not infallible, is far more reliable and if each module passes then you can be pretty confident that it will deliver reliable service while running within specifications.

 

Regards,

Mike

 

Mike

Share this post


Link to post
Share on other sites

Many thanks Mike.

 

As I am not technically that savvy I will discuss this with the company that I purchased the PC from this year but I really appreciate you kind help and assistance.

 

Michael

Share this post


Link to post
Share on other sites

I am getting a similar crash that I'm working through.  Mine goes to a black screen and the sound card buzzes.  Checking the event log, I found that I had a dump file.  Did a bit of googling and found an app called WhoCrashed that read through the dumps on my computer and pointed out that the causes were TDR mostly and a USB3 driver sometimes.  Pretty nice app.  Simple to use and there's a free home edition.

 

http://www.resplendence.com/whocrashed

 

EDIT: Rolling back to 347.25 seems to have solved the TDRs for me.  I didn't try any drivers in between...I just remembered that it was a good driver for me so I used it.

Share this post


Link to post
Share on other sites

Most problems are fixed by updating your drivers.   This is one of the recommendations in the AVSIM CTD Guide.

 

Best regards,

Share this post


Link to post
Share on other sites

 

 


Most problems are fixed by updating your drivers. This is one of the recommendations in the AVSIM CTD Guide.

 

Yes, seems to have helped.  But, I also think that the settings in NI can cause the issues as well...perhaps some settings cause code to get used that isn't stable or cause some arrays to overflow.

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