Sign in to follow this  
penta_a

Short pauses and occasional CTD with no error message (possible FIX)?

Recommended Posts

Hi Ryan

 

Another pause-freeze today and i open DPC Latency checker v1.3 .

Well during the froze   current latency was  63 ms and maximum 326 ms , no DPC spike @ all .

Share this post


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

I use a Creative Sound Blaster X-Fi Titanium Fatal1ty Pro Series Sound Card but i also have freezes for few seconds but the DPC spike where very good no high points  non above the greenline far below. CPU i get not more then 40% full use incl windows ect.

 

Even on a sunnyday without clouds i still have this freeze its just 1 time totaly each flight.

 

I gona wait for a SP till them i keep the plane in hangar.

Share this post


Link to post
Share on other sites

Hello all,

I had the exact same problem.  I figured it wasn't the PMDG 777, but I was still trying to figure out what was happening (it only happened with the 777).  I then tried the DPC latency checker.  Sure enough, when running the 777, I saw an issue (Windows 7 was trying to use the wrong audio driver, possibly due to the new 777 sound files) .  I went into the device manager and noticed that some abandoned sound card drivers had somehow become enabled again.  Anyway, I disabled all of the NVIDIA audio drivers and kept my Sound Blaster driver enabled.  This has  solved my problem.  Also, I had a 4 gig DIMM go bad (blue screens etc) previously and am now running on only 4 gig of RAM.  I can definitely see why a minimum of 8 gigs is recommended (I think though that I'll take it all the way up to 16 gig-- might save me some headaches down the road.  Thanks PMDG for a great product!

Share this post


Link to post
Share on other sites

Hello,

 

I too have the "CTD with no error message" problem with the PMDG777.

 

I just changed my FSX directory by uninstalling like said in the PMDG forum, and re-installing addons (cleaning up in the process!) afterwards. I changed directory and was on a SSD beforehand but lacked storage space.

 

Before changing, everything ran fine and I managed to not have any CTD with the 777 (although I had some (mind you, they had Error messages and were from the PMDG777x.dll) in the beginning and managed to solve them) ever since.

 

But now that I reinstalled FSX, I never could load the PMDG even once.

 

I tried multiple scenarii : Default flight FSX, default flight with PMDG, loading a FSX flight and switching aircraft, different airports, ... nothing changed :

 

The loading screen gone, 777's textures start to load their "brownish" structure, and when real Boeing/PMDG textures are about to load, game shuts down without any error (no message, no event in the Event Manager, ...).

 

I should say that I also have the 737s NGX and I have no issue with any of them, even when loading them right off the bat from "Fly now!".

 

I tried loading in a different view (Virtual/Cockpit, Outside spot) or livery, and nothing solves the issue. Even from Outside perspective, the game crashes right when it's about to put "colors" on the plane.

I also tried the lag tool you provided and nothing is spiking on the loading, everything stays green.

 

 

If anyone can help me with that, that would be very much appreciated, as I really love flying the T7 and am really sad I can take her for her daily trip :D

Share this post


Link to post
Share on other sites

Do you have HIGHMEMFIX=1 in your FSX.cfg?

 

There are so many things that can your problems, so I will give you my usual list of things.

If that does not help then you shoukd contact PMDG.

 

My suggestions:

(note: I did not invent this stuff....this is info I gathered by experience and from others (hardware/software specialist) who know what they are talking about......still though some might disagree)

 

-I use DX9. If you use DX10 (of which I know nothing)....then maybe try switching back to DX9 (it might not be the cause....but I say back to basics first!)

 

-check the list of known bugs (they will be fixed in SP1) and make sure you are not causing the CDT due to a known bug.

 

-If you have overclocked you CPU or RAM or GPU, make sure you set your Bios back to default when you have problems.

(just because airplane A has no problems on your current OC that does not mean that airplane B will also have no problems!)

Again, back to basics.

 

-I know reinstalling is not the first thing to try.....but if you installed anything (FSX,WIN7 or whatever addon) WHILE being overclocked....then it is very possible your install (FSX, WIN7, etc) is corrupted. NEVER INSTALL SOFTWARE WHILE BEING OVERCLOCKED. (not even when you think you are stable!)

First reset Bios, then instal software.

 

-If you reinstall....then Install all software you thrust (FSX, PMDG) with the antivirust scanner OFF

(the virus scanner can prevent some files from being installed)

 

-Install all software at the same security level (either all as ADMIN or non as ADMIN).

 

-create a clean FSX.cfg file with only these two very basic additions.

HIGHMEMFIX=1 (required!) and WIDEVIEWASPECT=true (for wide monitors)

 

you can add the rest of your tweaks (one by one!) after the problem has been solved.

 

-If you are using ANY other software alongside FSX, then close all of it.

If the problem stops then start adding them back one at the time.

As said, back to basics.

 

-leave an FSX default FSX aircraft as your default flight.

I just left that Tryke flight FSX comes with, as default.

Do not change a PMDG aircraft to be the default flight!

 

-Create a fresh flight and choose the PMDG aircraft from the FSX interface.

choose you weather, location and time and then press fly now.

Do NOT first open a flight with a default FSX aircraft to then change in that opened flight to a PMDG!

After the PMDG has initialized (countdown finished) choose the panael state you want (but dont choose Cold and Dark for now as it has known bugs)

 

-run windows on Highperformance power plan.

Make sure it does not throttle back the CPU or shut down USB devices or harddiscs to save energy!

 

-if you use FSUIPC then update it to the latest version.

 

-did you update a driver recently?

If so, uninstall it and reinstall the previous driver (do not use driver rollback)

Never change a winning team....if all is fine dont update drivers....it will not make things better usually!

Note: Turn windows auto updating off so you can select the updates to install.

This prevents windows from automatically updating drivers without you knowing it.

 

 

Thats all I can think of right now.

Well, there is one more thing....but that might not be possible for everyone.

But I think you should use a dedicated Windows FSX boot with no other software to interveine! 

Share this post


Link to post
Share on other sites

Thank you for your extensive post. I think re-doing the FSX.cfg file did the trick. Not sure what was bugging it but definitely working now! Cheers

Share this post


Link to post
Share on other sites

I have problem (FSX freezes with milky screen) on long flights >6hrs.

usually I am doing something with the mouse when it happens e.g. clicking on FMC buttons.

I run FSX windowed on single monitor. Plenty of OOM room because it can happen even in sparse default scenery area.

 

FSXcrash.jpg

Share this post


Link to post
Share on other sites

Thank you for your extensive post. I think re-doing the FSX.cfg file did the trick. Not sure what was bugging it but definitely working now! Cheers

Hey cool, that is great. you're welcome.

I have problem (FSX freezes with milky screen) on long flights >6hrs.

usually I am doing something with the mouse when it happens e.g. clicking on FMC buttons.

I run FSX windowed on single monitor. Plenty of OOM room because it can happen even in sparse default scenery area.

 

FSXcrash.jpg

No idea.

 

Looks like a GPU problem that is not related to the 777 to me. Maybe ask around at the DX10 forums.

Share this post


Link to post
Share on other sites

Realy tired about this....

 

I never finish a flight because the "blue circle of death". No matter what I do, always the FSX crash with this plane. FSX SP2 genuine and default with no add-on less 737NGX and T7...

 

Obviously, if this issue isn't solved with the SP1 I will not buy the 300ER and I will ask a refund :(

Share this post


Link to post
Share on other sites

Blue Screens of Death are often due to hardware failures (RAM memory sticks most often). You should try testing them with MemTest for 6+ hours (best is starting the tests in the morning and let it run the whole day when you're a work, or a whole night if you don't mind letting your computer powered) and see if any error is found.

 

In some cases, BSoD can be due to SSDs' BIOS failures but those are rare and known bugs. 

Best bet is on a defectuous memory stick.

Share this post


Link to post
Share on other sites

Realy tired about this....

 

I never finish a flight because the "blue circle of death". No matter what I do, always the FSX crash with this plane. FSX SP2 genuine and default with no add-on less 737NGX and T7...

 

Obviously, if this issue isn't solved with the SP1 I will not buy the 300ER and I will ask a refund :(

 

So I also have become tired of these issues. But I have so many addons, that I really couldn't say if it is really the PMDG 777.

 

So I decided to go through the painful issue of reinstalling FSX. I have an iMac using Bootcamp and took the opportunity to do a format and clean installation of Windows 7.

 

I installed FSX, and service packs. I then installed my various addons, REX, Orbx, Active Sky. Then I installed the PMDG 737NGX. I spent a week doing various flights on NGX, and had no issues what so ever.

 

I then installed the PMDG 777. I did a short flight from Brisbane to Sydney, and quick turnaround to head back to Brisbane. About 30 minutes into the flight spinning blue wheel started and FSX crashed.

 

It clearly has something to do with the PMDG 777 (NGX, J4100, Coolsky DC9, A2A C172 have no issues). I'm not saying it is not an interaction with some other add-on, but given it only happens with 777, means something isn't right. 

 

Hopefully SP1 fixes this.

 

____________________________________________________________________________

Ryan P

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