Jump to content


9.20 update game crash

9.20 Crashes

  • Please log in to reply
58 replies to this topic

PiratePurplePants #41 Posted Sep 25 2017 - 18:25

    Corporal

  • -Players-
  • 20718 battles
  • 10
  • [DD-S] DD-S
  • Member since:
    07-28-2013

View PostButtknuckle, on Sep 25 2017 - 07:30, said:

I was having similar issues but appear to have found a fix, or at least fixed enough that I've been able to play 50+ games without a game crash. The issue was with MSI Nahimic software. From what I could find on the web this causes problems with other games too.

 

Check our your event viewer and find the errors recorded when world of tanks crashed. If you have a fault with NahimicMSIOSD.dll that might be your issue. Below is the log from one of my crashes.

 

Faulting application name: worldoftanks.exe, version: 0.9.20.125, time stamp: 0x5996b443
Faulting module name: NahimicMSIOSD.dll, version: 0.0.0.0, time stamp: 0x56614f10
Exception code: 0xc0000005
Fault offset: 0x00004cd2
Faulting process id: 0xc5c
Faulting application start time: 0x01d333539cca74fb
Faulting application path: C:\Games\World_of_Tanks\worldoftanks.exe
Faulting module path: C:\Program Files\Nahimic\NahimicMSI\UserInterface\NahimicMSIOSD.dll
Report Id: 25a3462b-e7c7-445d-985a-e6b2f9b5308a
Faulting package full name:
Faulting package-relative application ID:

 

Fix was simple, just rename NahimicMSIOSD.dll, and restart your PC.

 

I renamed mine by putting "test" in front of the file name so I could find it again if it didn't work.

 

​I did exactly what you advised.  I went into the events viewer, found the log for the WoT crash and found the Nahmic file that was failing and renamed it to test_nahman.......    Restarted PC and Loaded world of tanks.  Was able to log completely in.  So far this fix works!!  

Buttknuckle #42 Posted Sep 25 2017 - 19:01

    Captain

  • Players
  • 41005 battles
  • 1,678
  • [GOONZ] GOONZ
  • Member since:
    03-19-2013

View PostPiratePurplePants, on Sep 25 2017 - 17:25, said:

 

​I did exactly what you advised.  I went into the events viewer, found the log for the WoT crash and found the Nahmic file that was failing and renamed it to test_nahman.......    Restarted PC and Loaded world of tanks.  Was able to log completely in.  So far this fix works!!

 

Nice. glad to see it work for someone else.

blitzer01 #43 Posted Sep 26 2017 - 09:13

    Private

  • Players
  • 11714 battles
  • 2
  • [SEA] SEA
  • Member since:
    11-23-2011

View PostPiratePurplePants, on Sep 25 2017 - 17:25, said:

 

​I did exactly what you advised.  I went into the events viewer, found the log for the WoT crash and found the Nahmic file that was failing and renamed it to test_nahman.......    Restarted PC and Loaded world of tanks.  Was able to log completely in.  So far this fix works!!  

 

HI bro how do you find the FIX log ?

 



blitzer01 #44 Posted Sep 26 2017 - 09:51

    Private

  • Players
  • 11714 battles
  • 2
  • [SEA] SEA
  • Member since:
    11-23-2011

View PostButtknuckle, on Sep 25 2017 - 06:30, said:

I was having similar issues but appear to have found a fix, or at least fixed enough that I've been able to play 50+ games without a game crash. The issue was with MSI Nahimic software. From what I could find on the web this causes problems with other games too.

 

Check our your event viewer and find the errors recorded when world of tanks crashed. If you have a fault with NahimicMSIOSD.dll that might be your issue. Below is the log from one of my crashes.

 

Faulting application name: worldoftanks.exe, version: 0.9.20.125, time stamp: 0x5996b443
Faulting module name: NahimicMSIOSD.dll, version: 0.0.0.0, time stamp: 0x56614f10
Exception code: 0xc0000005
Fault offset: 0x00004cd2
Faulting process id: 0xc5c
Faulting application start time: 0x01d333539cca74fb
Faulting application path: C:\Games\World_of_Tanks\worldoftanks.exe
Faulting module path: C:\Program Files\Nahimic\NahimicMSI\UserInterface\NahimicMSIOSD.dll
Report Id: 25a3462b-e7c7-445d-985a-e6b2f9b5308a
Faulting package full name:
Faulting package-relative application ID:

 

Fix was simple, just rename NahimicMSIOSD.dll, and restart your PC.

 

I renamed mine by putting "test" in front of the file name so I could find it again if it didn't work.

 

How do you rename it :)

 



Buttknuckle #45 Posted Sep 26 2017 - 17:00

    Captain

  • Players
  • 41005 battles
  • 1,678
  • [GOONZ] GOONZ
  • Member since:
    03-19-2013

View Postblitzer01, on Sep 26 2017 - 08:51, said:

 

How do you rename it :)

 

 

Locate the file, select it, press F2 to rename, type new name.

PiratePurplePants #46 Posted Sep 26 2017 - 19:17

    Corporal

  • -Players-
  • 20718 battles
  • 10
  • [DD-S] DD-S
  • Member since:
    07-28-2013

View Postblitzer01, on Sep 26 2017 - 09:13, said:

 

HI bro how do you find the FIX log ?

 

 

​I typed into Cortana "Event Viewer" then went thru the logs looking for "worldoftanks.exe" as the failing thing.  From there scroll down and it will tell you the path to the file.  Most likely it's in the Nahimic Folder in the User Interface folder.  once you've looked in the event viewer you will be able to see the file that crashed.  Mine was named different then Buttknuckles but when I changed the file name it specified it works perfect now.

MadHitter #47 Posted Sep 26 2017 - 23:47

    Corporal

  • Players
  • 38418 battles
  • 16
  • [ANVIL] ANVIL
  • Member since:
    02-25-2013
This worked for me, excellent job.  Just rename the file and it runs.  Its an MSI problem.

billy333 #48 Posted Sep 27 2017 - 00:37

    Private

  • Beta Testers
  • 26808 battles
  • 6
  • [ADOBE] ADOBE
  • Member since:
    09-03-2010

View PostPiratePurplePants, on Sep 26 2017 - 18:17, said:

 

​I typed into Cortana "Event Viewer" then went thru the logs looking for "worldoftanks.exe" as the failing thing.  From there scroll down and it will tell you the path to the file.  Most likely it's in the Nahimic Folder in the User Interface folder.  once you've looked in the event viewer you will be able to see the file that crashed.  Mine was named different then Buttknuckles but when I changed the file name it specified it works perfect now.

 

thank you very much for the problem fixing, it work for my ASUS also

Mr_RentAKill #49 Posted Sep 30 2017 - 06:40

    Staff sergeant

  • Players
  • 24033 battles
  • 419
  • [_F_] _F_
  • Member since:
    02-27-2014

View PostButtknuckle, on Sep 25 2017 - 06:30, said:

I was having similar issues but appear to have found a fix, or at least fixed enough that I've been able to play 50+ games without a game crash. The issue was with MSI Nahimic software. From what I could find on the web this causes problems with other games too.

 

Check our your event viewer and find the errors recorded when world of tanks crashed. If you have a fault with NahimicMSIOSD.dll that might be your issue. Below is the log from one of my crashes.

 

Faulting application name: worldoftanks.exe, version: 0.9.20.125, time stamp: 0x5996b443
Faulting module name: NahimicMSIOSD.dll, version: 0.0.0.0, time stamp: 0x56614f10
Exception code: 0xc0000005
Fault offset: 0x00004cd2
Faulting process id: 0xc5c
Faulting application start time: 0x01d333539cca74fb
Faulting application path: C:\Games\World_of_Tanks\worldoftanks.exe
Faulting module path: C:\Program Files\Nahimic\NahimicMSI\UserInterface\NahimicMSIOSD.dll
Report Id: 25a3462b-e7c7-445d-985a-e6b2f9b5308a
Faulting package full name:
Faulting package-relative application ID:

 

Fix was simple, just rename NahimicMSIOSD.dll, and restart your PC.

 

I renamed mine by putting "test" in front of the file name so I could find it again if it didn't work.

 

You sir, are a god among men!

I've been having the exact same issue as many others in this thread, where i'm completely unable to long in at all.  
I renamed that file, and played for almost 5 hours with the game crashing only once(Which, considering i've had a serious issue with crashing since a patch that was released almost 2 years ago, that's pretty damn good,).  

UPDATE: I've played for roughly 8-9 hours since changing that file name, and i've crashed only twice.  When I did, I was able to log right back in both times with no issues. Now, it might not sound too great that i've crashed twice in 8-9 hours, but considering even before the repeated crashes on startup, I would usually crash at least once an hour, sometimes much more, this is a massive improvement for me.  Thanks again!

Edited by Mr_RentAKill, Oct 02 2017 - 01:54.


MARINE_TANK_LEADER #50 Posted Oct 01 2017 - 02:37

    Corporal

  • -Players-
  • 50565 battles
  • 65
  • [SOYUZ] SOYUZ
  • Member since:
    04-22-2014
Yes, you are a good man.  I had the same problem on my brand new MSI computer and it fixed it.  Thank you!

teufelhunden222 #51 Posted Oct 01 2017 - 05:03

    Corporal

  • Players
  • 4988 battles
  • 13
  • [MCRD] MCRD
  • Member since:
    08-08-2013
I have an I7 6820 32 gb ram a gtx10708gb and a ssd. there is no way I am behind in hardware. It is another issue. 

teufelhunden222 #52 Posted Oct 01 2017 - 05:05

    Corporal

  • Players
  • 4988 battles
  • 13
  • [MCRD] MCRD
  • Member since:
    08-08-2013
Also I am paying for premium account that I can not use.....

mph65 #53 Posted Oct 02 2017 - 13:06

    Private

  • -Players-
  • 16729 battles
  • 1
  • Member since:
    05-12-2015

View PostButtknuckle, on Sep 25 2017 - 07:30, said:

I was having similar issues but appear to have found a fix, or at least fixed enough that I've been able to play 50+ games without a game crash. The issue was with MSI Nahimic software. From what I could find on the web this causes problems with other games too.

 

Check our your event viewer and find the errors recorded when world of tanks crashed. If you have a fault with NahimicMSIOSD.dll that might be your issue. Below is the log from one of my crashes.

 

Faulting application name: worldoftanks.exe, version: 0.9.20.125, time stamp: 0x5996b443
Faulting module name: NahimicMSIOSD.dll, version: 0.0.0.0, time stamp: 0x56614f10
Exception code: 0xc0000005
Fault offset: 0x00004cd2
Faulting process id: 0xc5c
Faulting application start time: 0x01d333539cca74fb
Faulting application path: C:\Games\World_of_Tanks\worldoftanks.exe
Faulting module path: C:\Program Files\Nahimic\NahimicMSI\UserInterface\NahimicMSIOSD.dll
Report Id: 25a3462b-e7c7-445d-985a-e6b2f9b5308a
Faulting package full name:
Faulting package-relative application ID:

 

Fix was simple, just rename NahimicMSIOSD.dll, and restart your PC.

 

I renamed mine by putting "test" in front of the file name so I could find it again if it didn't work.

 

This was it for me - on an MSI gaming laptop running Win 10.  The file was slightly different - in my case it was Nahimic2OSD.dll - renamed it - rebooted - haven't had the game crash since.

 

Full path in my case was C:\Program Files\Nahimic\Nahimic2\UserInterface\Nahimic2OSD.dll

 

Check your event log as suggested under Windows Logs / Application - the crashes should be listed there with the 'faulting module' named. 


Edited by mph65, Oct 02 2017 - 13:11.


ted100 #54 Posted Nov 10 2017 - 17:11

    Private

  • Players
  • 16221 battles
  • 5
  • [DHO2] DHO2
  • Member since:
    12-30-2012

SOLVED

i have read ggts post and solved my crashing issues turn off nvidia recording go to the gforce experience then setting turn off in-game overlay all issues solved,



Sippenhaft #55 Posted Nov 15 2017 - 15:07

    Corporal

  • Players
  • 21390 battles
  • 23
  • Member since:
    02-07-2012

View PostOracle414, on Sep 01 2017 - 20:17, said:

For anyone that is still experiencing crashes please post your DxDiag in your comment -- I need to verify your graphics card and dedicated memory is well within min req's.

If your system is well beyond these specifications and experiencing crashes, try adding this .bat file to your World of Tanks folder and restart the client. ( this fixed my tanks so I hope it helps thanks costumer support.

 

BAT FILE SEEMS TO WORK FOR ME....not more freezing during battles

 

---------------
Display Devices
---------------
          Card name: AMD Radeon HD 6900 Series
       Manufacturer: Advanced Micro Devices, Inc.
          Chip type: AMD Radeon Graphics Processor (0x6719)
           DAC type: Internal DAC(400MHz)
        Device Type: Full Device
         Device Key: Enum\PCI\VEN_1002&DEV_6719&SUBSYS_0B001002&REV_00
      Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
Device Problem Code: No Problem
Driver Problem Code: Unknown
     Display Memory: 5872 MB
   Dedicated Memory: 2032 MB
      Shared Memory: 3840 MB
       Current Mode: 1920 x 1080 (32 bit) (60Hz)
       Monitor Name: Philips 227E6 (21.5inch Wide LCD MONITOR 227E6)
      Monitor Model: PHL 227E6
         Monitor Id: PHLC0E5
        Native Mode: 1920 x 1080(p) (60.000Hz)
        Output Type: HDMI
        Driver Name: aticfx64.dll,aticfx64.dll,aticfx64.dll,amdxc64.dll
Driver File Version: 8.17.0010.1404 (English)
     Driver Version: 15.200.1062.1004
        DDI Version: 11.2
     Feature Levels: 11_0,10_1,10_0,9_3,9_2,9_1
       Driver Model: WDDM 1.3
Graphics Preemption: DMA
 Compute Preemption: DMA
           Miracast: Not Supported by Graphics driver
Hybrid Graphics GPU: Not Supported
     Power P-states: Not Supported
  Driver Attributes: Final Retail
   Driver Date/Size: 8/2/2015 7:00:00 PM, 1466744 bytes
        WHQL Logo'd: Yes
    WHQL Date Stamp: Unknown
  Device Identifier: {D7B71EE2-2459-11CF-CE76-0A2BBEC2C535}
          Vendor ID: 0x1002
          Device ID: 0x6719
          SubSys ID: 0x0B001002
        Revision ID: 0x0000
 Driver Strong Name: oem27.inf:cb0ae4140e401586:ati2mtag_NICayman:15.200.1062.1004:pci\ven_1002&dev_6719
     Rank Of Driver: 00D12001
        Video Accel: ModeMPEG2_A ModeMPEG2_C
        DXVA2 Modes: DXVA2_ModeMPEG2_VLD  DXVA2_ModeMPEG2_IDCT  DXVA2_ModeH264_VLD_NoFGT  DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT  DXVA2_ModeH264_VLD_Stereo_NoFGT  DXVA2_ModeVC1_VLD  DXVA2_ModeMPEG4pt2_VLD_AdvSimple_NoGMC  
   Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
                     {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {3C5323C1-6FB7-44F5-9081-056BF2EE449D}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                     {552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                     {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
       D3D9 Overlay: Not Supported
            DXVA-HD: Not Supported
       DDraw Status: Enabled
         D3D Status: Enabled
         AGP Status: Enabled
           MPO Caps: Not Supported
        MPO Stretch: Not Supported
    MPO Media Hints: Not Supported
        MPO Formats: Not Supported

 

       Operating System: Windows 10 Home 64-bit (10.0, Build 14393) (14393.rs1_release_inmarket.161102-0100)
                 Language: English (Regional Setting: English)
      System Manufacturer: Gigabyte Technology Co., Ltd.
             System Model: GA-870A-UD3
                     BIOS: Award Modular BIOS v6.00PG
                Processor: AMD Phenom™ II X6 1090T Processor (6 CPUs), ~3.2GHz
                   Memory: 16384MB RAM
      Available OS Memory: 16382MB RAM
                Page File: 7462MB used, 25302MB available
              Windows Dir: C:\WINDOWS
          DirectX Version: DirectX 12
      DX Setup Parameters: Not found
         User DPI Setting: 96 DPI (100 percent)
       System DPI Setting: 96 DPI (100 percent)
          DWM DPI Scaling: Disabled
                 Miracast: Not Available
Microsoft Graphics Hybrid: Not Supported
           DxDiag Version: 10.00.14393.0000 64bit Unicode



NIK1 #56 Posted Nov 16 2017 - 14:51

    Corporal

  • Players
  • 38765 battles
  • 96
  • Member since:
    03-09-2012
What does running the bat file actually do.

Sippenhaft #57 Posted Nov 20 2017 - 17:46

    Corporal

  • Players
  • 21390 battles
  • 23
  • Member since:
    02-07-2012
Launches the game and (probably) adjusts some settings....or puts some sort of tank porn on my system...all I know, is I can play now.

ThirtyPercentBeef #58 Posted Nov 20 2017 - 19:35

    Private

  • Players
  • 10925 battles
  • 3
  • [GTO] GTO
  • Member since:
    10-24-2013
yep, happens once or twice a day for me now, still there are games like fallout 4 that crashed and glitched for a month till patch that cost £50 so not going to lose sleep. just the abuse when you get back in the game that boils the blood.

Mr__Buttons #59 Posted Nov 24 2017 - 06:48

    First lieutenant

  • Players
  • 52562 battles
  • 776
  • [F0XEY] F0XEY
  • Member since:
    12-25-2011

View Postted100, on Nov 10 2017 - 11:11, said:

SOLVED

i have read ggts post and solved my crashing issues turn off nvidia recording go to the gforce experience then setting turn off in-game overlay all issues solved,

 

I have been crashing every game tonight and my FPS had gone to crap, 30 FPS with a GTX1080TI. I turned off Nvidia recording and FPS is now 125 and no crashing. 

 

Thank you!

 

David.







Also tagged with 9.20, Crashes

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users