Jump to content

Game crashing to desktop


Go to solution Solved by micman113,

Recommended Posts

I have a few Q's.
I have noticed those crashes happend often after an update from Windows, if it happends to me then alway's after that.

I notice there is maybe a connection with an update  while playing on a 64bit machine,
then for a test I started manualy the game in 32bit mode by hand, by clicking, as an ADMIN, the file GAMES/WORLD_OF_TANKS/WIN32/WorldOfTanks.exe ,
I had the whole day no crash.
After 1 or 2 day's tryed again normally in 64bit mode and all went well.

I alway's start and look into the Gamecentre, but never start a game there.
Normaly I alway's start a game manualy as an admin by hand in 64bit mode.

Maybe it is wort to try this to find out if there is a connetction.

greetz Willy

Link to comment
  • Moderator
17 hours ago, PinkiPassion said:

I removed some more and still crashing...

 

I only have the following left;

 

XVM Crew Return
-= NON XVM =-
Better Reticle Size
Tank Rating Color
Aim Helping INFINIT LOCK
Lebwa MoE Calculator
Gold Ammo Visibility BLUE
Better Context Menu
Repairs by Izeberg
Six Sense Timer 40+
Unanonmyzer on Battle Results
TRICKS Tank Carousel X2
Skin of destroyed tank WHITE
Players Panel HP Bar

 

 


compared all mod configs posted in here and narrowed it down further
these are the mods and/or files people have, if you want to delete 1 by 1 i would start with these
xvm and pmod have a wide variety of options inside the installer so those will be difficult to narrow down inside the installer (possible later if we found the culprit)

name of mod in installer /  file name inside mods/1.23.0.1/

                    /   net.openwg.fix.battleresultscache_1.8.0.wotmod
AA+              / mod_autoaim_indicator.wotmod
Pmod collection mod    /  me.poliroid.pmod_1.70.0.wotmod
                                 /me.poliroid.modslistapi_1.4.6.wotmod
                                / izeberg.modsettingsapi_1.5.7.wotmod
tankratingcolors         / champi.tankratingcolors_1.31.007.wotmod
                               / champi.settingsgui_1.55.wotmod
                               /AntiMirror.wotmod
xvm                        / com.modxvm.xfw folder

hope this help, will also continue searching/testing 

Link to comment
  • Solution
Posted (edited)
On 1/3/2024 at 9:06 AM, Willy said:

I have a few Q's.
I have noticed those crashes happend often after an update from Windows, if it happends to me then alway's after that.

I notice there is maybe a connection with an update  while playing on a 64bit machine,
then for a test I started manualy the game in 32bit mode by hand, by clicking, as an ADMIN, the file GAMES/WORLD_OF_TANKS/WIN32/WorldOfTanks.exe ,
I had the whole day no crash.
After 1 or 2 day's tryed again normally in 64bit mode and all went well.

I alway's start and look into the Gamecentre, but never start a game there.
Normaly I alway's start a game manualy as an admin by hand in 64bit mode.

Maybe it is wort to try this to find out if there is a connetction.

greetz Willy

 This did not work for me...I thought it might be the issue.

 

On 1/3/2024 at 10:16 AM, Theolitius said:


compared all mod configs posted in here and narrowed it down further
these are the mods and/or files people have, if you want to delete 1 by 1 i would start with these
xvm and pmod have a wide variety of options inside the installer so those will be difficult to narrow down inside the installer (possible later if we found the culprit)

name of mod in installer /  file name inside mods/1.23.0.1/

                    /   net.openwg.fix.battleresultscache_1.8.0.wotmod
AA+              / mod_autoaim_indicator.wotmod
Pmod collection mod    /  me.poliroid.pmod_1.70.0.wotmod
                                 /me.poliroid.modslistapi_1.4.6.wotmod
                                / izeberg.modsettingsapi_1.5.7.wotmod
tankratingcolors         / champi.tankratingcolors_1.31.007.wotmod
                               / champi.settingsgui_1.55.wotmod
                               /AntiMirror.wotmod
xvm                        / com.modxvm.xfw folder

hope this help, will also continue searching/testing 

This however has given me hope....I removed tank rating colors...18 battles all good...using v7

Thanks to all

Edited by micman113
  • Upvote 1
Link to comment
Am 25.12.2023 um 19:07 schrieb PinkiPassion:

The last 2 days I've been experiencing this also.... I even tried to slim down the instal with no XVM and problem persists... 

So I did the following this morning to try and remedy the issue;

- uninstalled the complete game + Aslain, 

- Deleted both folders (AppData + Instal Folder)

- DDU my display drivers and updated them.

- Rebooted and re-downloaded/installed game/Aslain

 

Sadly problem still persists unless I play the game without any mods or in Safe Mode

Aslains_WoT_Logs.zip 153.65 kB · 4 Downloads

Same here!

Link to comment
  • Administrator

CHAMPi will look into this issue, he said that some 3d skins dont like it when the mod removes the camo. He need replays from the crashed games.

 

Meanwhile you can try to uncheck this option in his mod: image.png.3d5e1175846d4e3994ae9697069a0ddf.png

Link to comment
16 hours ago, Aslain said:

He need replays from the crashed games.


Looking through the replays where I crashed they're pretty unhelpful. The battles where I crashed on the loading screen over and over the replay begins when I finally got in. For the battles where I randomly crashed during battle there is no replay file at all like that battle never happened. Unless I managed to get back in after crashing, when again the replay begins mid-battle after restarting the game.

Because of that the point of the crash is never actually captured, even though it happened many, many times.

Link to comment
  • 1 month later...

finally found out what the problem was for me.

 

Intel (specially) 13900K and 14900k processors can cause this problem even if you don`t overclock them (like me).

I run watercooling on my PC and temperatures were never to high.

 

my mobo did set the powertargets min/max to 4096W for the processor per default.

 

Changed it to 253W and it works just fine now.

 

  • Upvote 1
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use and Privacy Policy.