FATAL ERROR: EXCEPTION

[Skaanderbeg 6]

Intel drivers updated but nothing...

[szl0834 0]

On 25/06/2019 at 08:10, relliK said:

one thing you guys seem to have in common is that you got systems (laptops ?!) with an intel / nvidia gpu combo (nVidia Optimus)

and according to szl0834s crash dumps it's the intel driver that is crashing...

 

while the intel gpu should only be used to display the pictures the nVidia gpu is rendering it looks as if there may be a problem with

this combination (just an assumption !) and ofc this does not explain why the 32bit version is running oO. however if the 32bit client

is indeed running flawlessly that's a viable workaround imho (until the root cause of this issue is found and fixed).

 

i would have recommended to have a look into the intel gpu drivers (update them if possible) but according to the driver date in the

crash dump of szl0834 at least his intel drivers appear to be quite recent... so,,,, i dont know =/

Thanks, you help me a lot. I fix the problem by install a older version intel driver.

here is the link:  https://downloadcenter.intel.com/download/26836

Edited June 26, 2019 by szl0834

[Skaanderbeg 6]

 

edit

Edited June 28, 2019 by Skaanderbeg

[Vladimir_Putin3 0]

Here I have the same problem, I have played this and other games that would require a modern graphic card with almost no problem other than a bit slower game in landscapes that are massive in size, but only with maximum graphic settings, high is low enough to make it fast again, but this is a laptop with an intel Core i5 and Windows 10 Creators edition  using hardware acceleration with AMD graphic drivers and Radeon  GPU controllers; Here the problem: I have done every step that I have read in this and still I just got Fatal Error: Exception, I do not have cache files, I have made diagnostics with the launcher and another diagnostic of advanced applications plus analysing and re-analysing game files with no luck. Any hint from a technical counsellor? PD: Eliminating War Thunder from computer, too much is left unusable just because of something I cannot even start.

Edited July 4, 2019 by Vladimir_Putin3
Elimination of the game, no longer required to have this here.

[Skaanderbeg 6]

the problem are Intel drivers

[GPLOctive 0]

On 25/06/2019 at 01:10, relliK said:

one thing you guys seem to have in common is that you got systems (laptops ?!) with an intel / nvidia gpu combo (nVidia Optimus)

and according to szl0834s crash dumps it's the intel driver that is crashing...

 

while the intel gpu should only be used to display the pictures the nVidia gpu is rendering it looks as if there may be a problem with

this combination (just an assumption !) and ofc this does not explain why the 32bit version is running oO. however if the 32bit client

is indeed running flawlessly that's a viable workaround imho (until the root cause of this issue is found and fixed).

 

i would have recommended to have a look into the intel gpu drivers (update them if possible) but according to the driver date in the

crash dump of szl0834 at least his intel drivers appear to be quite recent... so,,,, i dont know =/

My pc:

GTX 1060 3GB

AMD FX8350 4.2GHz

8GB of ram

1TB storage

and "it gets the job done" motherboard

so I don't see how this problem is related to intel

it could be related to Nvidia but I have reinstalled my drivers twice and this still hasn't fixed the problems plz help me fix this problem I have had since just after the release of 1.89  

I have attached the crash report? please tell me what's wrong and then we could all fix this problem

bpreport.log

[GPLOctive 0]

This is what I found in the crash report can any one help me find whats wrong? Full copy below.

---- crash ------
product: WarThunder
timestamp: 1562436861
systemId: 3a156a6d-29e3-4e95-9c86-84649a73053c
user Id: 0
type: Exception
---- stats ------
host: client-stats.warthunder.com:20010
Stats init ok: prefix - production.client.windows_10_64bit.nvidia.crashreport.Exception.
Stats send: 'production.client.windows_10_64bit.nvidia.crashreport.Exception.start:1|c'
Stats send: 'production.client.windows_10_64bit.nvidia.crashreport.Exception.decline:1|c'
User refused to submit report

bpreport.log

[relliK 3,227]

when does the crash happen ? do you even get to the hangar ?

[GPLOctive 0]

Soon as I press the game window appears after the start button is pressed.

But you can still see the hangar but the mouse just doesn't work.

After clicking exception button it instantly shuts down.

 

Thanks for trying to help me 

[relliK 3,227]

do you use a custom hangar by any chance ? (if so, disable it in the config.blk and try again)

when did this start to happen ? was it rifgt after a game patch or a windows update ?!

 

(if you are on Win10 version 1903 and got a gamepad / joystick connected you should unplug

 it and test without it...)

 

other than that could you maybe upload the latest client log (*.clog) and one of the crash dumps

from the ..\War Thunder\.game_logs\  folder !?

 

[GPLOctive 0]

Thanks unplugging my speed link joystick worked.

[swagmasterj20 0]

Yeah I have gotten the same problem the game was working all of a sudden doesn't, with the same pop up. I am not really good with this kind of stuff so I tried to follow what they had said on here but still doesn't Work If some one could help that would be great

[NanoFighterBR 4]

so, I got the same problem... I read other topics like these but found no solution...
my problem happened after I changed some PC parts. The game was working properly but in the next day I had this error.

 

EDIT 1: 32-bit version of "aces.exe" is working tho

Edited July 20, 2019 by NanoFighterBR

[nz_sky 2]

Same problem here i am running amd ryzen 5 cpu and radeon gpu rx 5700 xt, new pc with windows 10 64bit

[alejito480 2]

I have the same problem. 3 times in 10 minutes. Damn it 

[Salty_tuna 0]

In one murky day this game starting say about crash, i spended many time using advices techsupport but no one help me. Then i just unpluging speedlink receiver and game launch properly. Strange, because i many times launched game with reciver was connected. Thanks guy above who suggested this method.

[Skaanderbeg 6]

i still have this problem, what i should  do?

[gfriedline 47]

I am having similar crash issues since the 1.93.0.50 (Update 7.11.2019) dropped. Attempted to update display drivers, then DDU on display drivers and clean install on older Nvidia drivers, newer Nvidia drivers, and back to the latest display drivers. I have re-installed video drivers at least 6 times. I am seeing the client launch, hanger, and I can load into (1) test flight or match. Upon exiting that match, it is typically giving me a fatal before going back to hanger. After this, the client hangs at startup before login screen. Restart gives me client ability to launch into (1) session and then same fatal on ending of that session. I have reviewed a lot of prior advice given and attempted those fixes, but none of those seemed to work. Curious if anyone can point me in the right direction here.

 

 

Thank you in advance.

2019_11_18_20_40_38__6076.clog bpreport.log DxDiag2.txt

[Banzonho 0]

I`m having the exception error too! after last update, already tried uninstall drivers, DDU, reinstall the game, yet, cant even enter the launcher. I have a Alienware Area 51m, i9900k, RTX 2080. please, help!!

[gfriedline 47]

5 hours ago, Banzonho said:

I`m having the exception error too! after last update, already tried uninstall drivers, DDU, reinstall the game, yet, cant even enter the launcher. I have a Alienware Area 51m, i9900k, RTX 2080. please, help!!

 

I have posted one solution in another thread here, but what are you outputting audio to? Are you using an Nvidia audio device (monitor speakers), or do you have alternative hardware as your primary out?

At least for my issues, this appears to be related to NVidia audio drivers and the recent sound changes/updates.

Try changing your default Audio device to something else, restart, try again.

[JJOHNSONFAN 12]

im starting to have the same issue, i get to this point and i get the exception error

i validated my game and nothings changed



i got: 
windows 7
1050ti
i5 4670k
16 gigs of ddr3? (<- pretty sure)

id love to continue playing! can someone please help me?

right, since no one has helped me, i managed to fix it, it was the custom hanger crashing my game, i hate how it was my custom hanger crashing my game and i think its due to the easy cheat system been added... great....

Edited November 21, 2019 by JJOHNSONFAN
help!!!

[Banzonho 0]

My error happens before opening the launcher! I use a Logitech G930 headset, with USB connector. but the problems happens with the onboard audio too. I can`t initialize. I tested already with the old graphic driver, nothings happens. I tried too download the stand alone game, but it always link it with my steam download game.

[Banzonho 0]

Here is the error.

[felix_ardyan 2]

On 20/11/2019 at 19:36, gfriedline said:

 

 

On 19/11/2019 at 08:59, gfriedline said:

I am having similar crash issues since the 1.93.0.50 (Update 7.11.2019) dropped. Attempted to update display drivers, then DDU on display drivers and clean install on older Nvidia drivers, newer Nvidia drivers, and back to the latest display drivers. I have re-installed video drivers at least 6 times. I am seeing the client launch, hanger, and I can load into (1) test flight or match. Upon exiting that match, it is typically giving me a fatal before going back to hanger. After this, the client hangs at startup before login screen. Restart gives me client ability to launch into (1) session and then same fatal on ending of that session. I have reviewed a lot of prior advice given and attempted those fixes, but none of those seemed to work. Curious if anyone can point me in the right direction here.

 

 

Thank you in advance.

2019_11_18_20_40_38__6076.clog 516.72 kB · 2 downloads bpreport.log 3.44 kB · 1 download DxDiag2.txt 50.26 kB · 2 downloads

did you use pc or laptop mybe check your hard drive mybe you hard drive dying or just bad cable (i have same issue the cable is broken)

Edited November 23, 2019 by felix_ardyan

[Banzonho 0]

On 22/11/2019 at 12:26, Banzonho said:

Here is the error.

 

 

Someone can help me, please??