Jump to content


Crash to Desktop (CTD) Tracking


  • Please log in to reply
8 replies to this topic

Catch21 #1 Posted 24 December 2017 - 12:52 PM

    Senior Master Sergeant

  • Closed Beta Tester
  • 2224 battles
  • 316
  • [DOG5] DOG5
  • Member since:
    05-19-2013

I'm not sure this is the right place to post, but I'm a relative newcomer (other than a battle or 2 pre-2.0 before I decided not for me), and I don't want to clog up the support system (such as it (currently) is).

 

If anyone knows anything on this or can help, please add or correct me, but when you get a CTD, it looks as though 3 files are generated in %appdata%->wargaming.net->World of Warplanes (for those unfamiliar, %appdata% a generic windows system location that differs from PC to PC, but typing this in the Windows Explorer address bar will always take you to yours). To help, when you get to %appdata% look for a folder called wargaming.net, then within that World of Warplanes (could vary slightly depending on your install names), then within that a folder called logs.

 

Within the logs folder, you'll get 3 files when you crash (sort the folder on column 'date modified' to make it easy to see ordered time stamps for files):

 

1) crash.tmp which contains a reason for the crash such as (example):

Spoiler

 

2) A .dmp file (format YYMMDD_[unique ID].dmp), contains info that I can't read (memory dump?) or in some (most?) cases nothing at all (file has size 0).

3) A .log file (format as above but ending in .log extension), containing logged events since you loaded WoWP, at the end of the file you should find something indicating the reason for the crash, which in my case matched what was in the crash.tmp file:

Spoiler

 

With this info, I've at least a place to start looking for why I'm out of memory on a system with 8GB.

 

I'm not looking for specific help on my issue here (it's likely a mod), rather if anyone can suggest or point or add to what I'm finding here (and given obvious difficulty getting through to support over Christmas).



Ace_BOTlistic_Cosmo #2 Posted 24 December 2017 - 02:32 PM

    First Lieutenant

  • Member
  • 361 battles
  • 2,668
  • [3NIC] 3NIC
  • Member since:
    01-26-2014

Make sure WG Game center is closed, do not run it except for updates

make sure you have nothing running in the background, ALL updates turned off

make sure you clear cache and delete that folder you're fascinated with before every launch

update the drivers for your video to the latest ver.

check Task Manager for a few hours... see what's wasting your memory, see what's freaking out your system

good luck and tell us how it goes...

I always have more ideas to keep you busy... hehe

Merry Christmas

 

we'll get into hardware next

:ohmy:

 


Edited by Ace_BOTlistic_Cosmo, 24 December 2017 - 02:34 PM.

if the pilot's good, see, I mean, if he's really..sharp, he can barrel that baby in so low [he spreads his arms like wings and laughs],

you oughtta see it sometime, it's a sight. A big plane like a '52. VRROOM! There's jet exhaust, fryin' chickens in the barnyard.


Perco_lator #3 Posted 24 December 2017 - 03:17 PM

    Senior Master Sergeant

  • Member
  • 11 battles
  • 454
  • Member since:
    08-15-2015
It's just the same old same old, the game suffers from memory leaks & is the main cause of this issue.

"Come find me in the game, tough guy.  We'll see who knows stuff."


rurickjames #4 Posted 25 December 2017 - 03:47 AM

    Senior Airman

  • Closed Beta Tester
  • 755 battles
  • 13
  • Member since:
    01-26-2012

Catch21, I'm seeing the same; however, I have 16gb RAM and been watching via task manager.  My WoWP never uses/d more than 3gb of this memory.  Total system usage at time of crashes is 20-30% CPU (4690K@4.3ghz) and 15-18% of memory. FWIW, I am using a GTX1060 w/6gb.

 

( error 8007000e:E_OUTOFMEMORY(0x8007000e): Direct3D could not allocate sufficient memory to complete the call. ), name:texture/F04D93151CEE86F364C3E392D750739B
Runtime error (0xE06D7363) at 0x774308B2
Out of Memory error: (null)


Edited by rurickjames, 25 December 2017 - 03:49 AM.


Ace_BOTlistic_Cosmo #5 Posted 25 December 2017 - 03:48 PM

    First Lieutenant

  • Member
  • 361 battles
  • 2,668
  • [3NIC] 3NIC
  • Member since:
    01-26-2014

try this guys fix:

 

https://answers.ea.c...TO/td-p/5261777

 

 


if the pilot's good, see, I mean, if he's really..sharp, he can barrel that baby in so low [he spreads his arms like wings and laughs],

you oughtta see it sometime, it's a sight. A big plane like a '52. VRROOM! There's jet exhaust, fryin' chickens in the barnyard.


Wombatmetal #6 Posted 25 December 2017 - 09:47 PM

    Command Chief Master Sergeant

  • Member
  • 750 battles
  • 708
  • Member since:
    06-02-2013

View Postrurickjames, on 24 December 2017 - 07:47 PM, said:

Catch21, I'm seeing the same; however, I have 16gb RAM and been watching via task manager.  My WoWP never uses/d more than 3gb of this memory.  Total system usage at time of crashes is 20-30% CPU (4690K@4.3ghz) and 15-18% of memory. FWIW, I am using a GTX1060 w/6gb.

 

( error 8007000e:E_OUTOFMEMORY(0x8007000e): Direct3D could not allocate sufficient memory to complete the call. ), name:texture/F04D93151CEE86F364C3E392D750739B
Runtime error (0xE06D7363) at 0x774308B2
Out of Memory error: (null)

 

Nvidia released a new driver on 12/20. You might try that

Catch21 #7 Posted 26 December 2017 - 05:00 PM

    Senior Master Sergeant

  • Closed Beta Tester
  • 2224 battles
  • 316
  • [DOG5] DOG5
  • Member since:
    05-19-2013

View PostAce_BOTlistic_Cosmo, on 25 December 2017 - 03:48 PM, said:

 

Thanks. I'm coming back to this issue in 2018. Will try then. Happy holidays!

 

View PostDestroyer_Suzukaze, on 25 December 2017 - 09:47 PM, said:

Nvidia released a new driver on 12/20. You might try that

 

Thanks. Yes, check. Usually 1st port of call on game crashes.



Ace_BOTlistic_Cosmo #8 Posted 26 December 2017 - 11:47 PM

    First Lieutenant

  • Member
  • 361 battles
  • 2,668
  • [3NIC] 3NIC
  • Member since:
    01-26-2014

View PostCatch21, on 26 December 2017 - 12:00 PM, said:

 

Thanks. I'm coming back to this issue in 2018. Will try then. Happy holidays!

 

 

Thanks. Yes, check. Usually 1st port of call on game crashes.

Happy New Year


if the pilot's good, see, I mean, if he's really..sharp, he can barrel that baby in so low [he spreads his arms like wings and laughs],

you oughtta see it sometime, it's a sight. A big plane like a '52. VRROOM! There's jet exhaust, fryin' chickens in the barnyard.


Catch21 #9 Posted 27 December 2017 - 12:37 PM

    Senior Master Sergeant

  • Closed Beta Tester
  • 2224 battles
  • 316
  • [DOG5] DOG5
  • Member since:
    05-19-2013

OK here's the deal (I posted @ Reddit too, since the same issue is there), some of this may help others, at least in diagnosis. I crash once in every 5-10 games, no rhyme or reason I can tell, it just says 'no' and crashes. But when you have a crash the system will (should?) write the following files in %appdata%\wargaming.net[YOUR WORLD OF WARPLANES DIRECTORY]\logs:

  1. crash.tmp - the immediate cause of the problem with the name of a .dmp file into which program state is dumped. 
  2. The .dmp file as above 
  3. A .log file which contains information on the WoP session until the crash.

 

You can read these using a text editor like Notepad++ (the .dmp file is indecipherable though without programming tools). In my latest crash (.tmp file) I see:

 

EXCEPTION_CPP Runtime error (0xE06D7363) at 0x764408B2 Out of Memory error: (null)

 

I'm running with an overclocked G3258 CPU (3.9GHz), 8 GB of RAM and an Nvidia GTX 750 TI GC (driver updated)- Windows 10 64 Bit. With Speccy running for temps (CPU gets to 60 never more, GC always OK) and Task Manager for processes I can see no bottlenecks. At CPU stock speed still crashes. If I look at the .log file I see:

 

2747.474 WARNING: [MetaParticleSystem]: name: particles/planes/aim_trail_on_engine.xml: won't loaded. Particle system graphics option is higher than current graphics settings options. 2747.509 ERROR: RenderContext::createTexture - could not create texture map size 2048x1024x12. ( error 8007000e:E_OUTOFMEMORY(0x8007000e) : Direct3D could not allocate sufficient memory to complete the call. ), name DSLOADER Runtime error (0xE06D7363) at 0x764408B2 Out of Memory error: (null)

 

which matches what the crash.tmp file is saying, but indicates it's a memory problem perhaps with DirectX (I'm using version 12)? Nvidia's GE Force has supposedly optimized settings for the game, but since it mentions (and I think atm this is the problem) "Particle system graphics option is higher than current graphics settings options." I'm going to try setting this down in game settings today and see what happens. That or it's a WoP program error. 

 

If anyone has any other ideas (or wants more information to help), please let me know. If a WG support person sees this, I have copies of all 3 files for every crash (I'll mail support post-2017), the 3 files diagnosis part might help others. Thanks.


Edited by Catch21, 27 December 2017 - 12:38 PM.





1 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users