Jump to content
You need to play a total of 10 battles to post in this section.
_Umbra

Critical Error

9 comments in this topic

Recommended Posts

0
[-TBF-]
Member
4 posts
894 battles

Hey guys,

 

Been getting this error the last couple of days and no idea how to rectify. Its not a hardware issue, as this PC im on has run the game fine before. 

 

 

Cheers!

Share this post


Link to post
Share on other sites
Member
141 posts
6,599 battles

Did you install mods recently? Installing unidentical version of mod will crash when game client initializing.

Go to client ,setting and press data check, the client will repair files itself

it takes time , but better than reinstall the whole game, manually delete mod pack files doesnt work so dont do this

Share this post


Link to post
Share on other sites
Member
24 posts

Hey guys,

 

Been getting this error the last couple of days and no idea how to rectify. Its not a hardware issue, as this PC im on has run the game fine before. 

 

 

Cheers!

 

it always happen to my pc....its not game related but its the operating system we use....im still using window xp sp3 x86 or 32bit so my virtual memory is limited to 4gb only....this WOWS game consume a lot of memory and when im playing it i, my pc will be using @ 2.2 - 2.6gb of memory and when i tried to open a web browser then it will further increase memory usage until it reached the limit and will encounter that critical error.....those pc who are using 64bit operating system like windows 8 or windows 10 have more virtual memory capacity so their computer will never encounter this problem....the key is if your playing WOWS, do not open any other application or web browser and you can play WOWS with less problem or none at all.....all those patches have made this game more and more memory consuming and its game file size is much bigger than WOT. 

Share this post


Link to post
Share on other sites
Member
105 posts
13,273 battles

graphic driver got bug with WoWs

Application C:/Games/World_of_Warships/worldofwarships.exe crashed 11.05.2016 at 07:22:38
Message:
Allocate: can't allocate 16172037 bytes.
System info:
 OS Name: Windows 8 or later
 OS Version: 6.6
 OS Architecture: x86_64

Memory info:
 Virtual memory: 4115284Kb/4194176Kb (99%)
 Working set (process physical memory): 1747632Kb/4194176Kb (41%)
 Commit charge (working set + process page file usage): 2650820Kb/4194176Kb (63%)
 Global physical memory: 4741296Kb/8322580Kb (56%)
 Global commitable memory (physical + pagefile): 7167960Kb/9371156Kb (77%)
 

System info:
COMPUTERNAME = BULL-PC
APPLICATION = "C:\Games\World_of_Warships\worldofwarships.exe" wows_wait_for_mutex
4 PROCESSOR(S) = 0 - 6 5e03
DISPLAYDEVICE 0 = \\.\DISPLAY1, NVIDIA GeForce GTX 650 Ti BOOST, PCI\VEN_10DE&DEV_11C2&SUBSYS_00000000&REV_A1
DISPLAYDEVICE 1 = \\.\DISPLAY2, NVIDIA GeForce GTX 650 Ti BOOST, PCI\VEN_10DE&DEV_11C2&SUBSYS_00000000&REV_A1
DISPLAYDEVICE 2 = \\.\DISPLAY3, NVIDIA GeForce GTX 650 Ti BOOST, PCI\VEN_10DE&DEV_11C2&SUBSYS_00000000&REV_A1
DISPLAYDEVICE 3 = \\.\DISPLAY4, NVIDIA GeForce GTX 650 Ti BOOST, PCI\VEN_10DE&DEV_11C2&SUBSYS_00000000&REV_A1

Share this post


Link to post
Share on other sites
Member
24 posts


1.  Client crashes on configurations with 32-bit OS or a small amount of RAM



 



Hello, everyone!



 



The amount and quality of the content in our game is constantly increasing, and a lot of new functionality is being added. This, unfortunately, does not come “free”, in terms of the use of computer resources. On high-performance configurations, players very rarely encounter any problems related to insufficient resources, but on the configurations with the 32-bit OS’s or a small amount of RAM the client may freeze or crash. In theory, you may never face this problem at all, unless “the stars align” in a certain manner – for example, you get a “heavy” map with the high tier ships. 



 



Still, recently the number of resorts to the support related to the World of Warships client crashing on 32-bit OS or small amount of RAM increased. Because of this, we would like to share some advices, which will help many players to up the “survivability” of the client.



 



From the technical side, the problem is related to the physical limit of the maximum amount of virtual memory allocated for the process in the operating system. Official information can be found on the Microsoft website - https://msdn.microso...a366778(v=vs.85).aspx The first line in the table is what is of interest for us, namely:



 



What does it mean?



It means that for the game process on x86 systems (Windows XP 32bit, Windows Vista 32bit etc.) the maximum amount of "virtual" memory for the process is 2 Gb, even if the RAM installed is bigger. For the x64 operating systems, the limit is 4 Gb.



 



What is the “virtual memory” of the process”? It’s a full amount of memory, including all the application memory allocation + system calls + DirectX + mapping files into the memory + mapping the video-memory into the process spaceIt’s important to understand that the “virtual memory” of the process is not the same as what you see in the Windows Task Manager.



 



With the 2 Gb limit, you can only play with the “Low” graphics preset, even if your configuration technically allows playing comfortably with the “Very high” (“texture quality” setting affect the likelihood of crashing the most).



 



Currently, we are actively working to minimize the likelihood of this kind of crashes, but if you are experiencing this problem, try the possible solutions listed below.



 



If your computer has more than 2Gb of RAM, it is recommended to install a 64-bit OS. If for any reason you can’t do so, read on.



 



1. Increasing the limit on the use of the virtual memory by the process up to 3 GB (only for x86 OS)



a. For 32-bit versions of Windows Vista/7/8, you should do the following:




  • 1. 1. Run the command prompt as an administrator. To do so, in the Start menu/start display enter cmd, press the icon with the right mouse button click and pick “Run as administrator” option.
  • 2. Enter bcdedit /set IncreaseUserVa 3072 in the Command Prompt window


  • 3. Restart the computer.


Video instruction





бFor the Windows XP it’s different. You need to carefully edit the Boot.ini file




  • 1. With the right mouse button click My Computer and pick Properties.
  • 2. Click Additional tab, click Startup and Recovery, and click Edit next.

  • 3. The Boot.ini file will open, there will be a line looking like: multi(o)disk(o)rdisk(o)partition(2)\WINDOWS=""Microsoft Windows XP Professional"" /fastdetect 4.

  • Copy this line to paste it below, then change the line you pasted to multi(o)disk(o)rdisk(o)partition(2)\WINDOWS="Microsoft Windows XP Professional 3GB" /3GB /userva=2900 /fastdetect

  • 5. Restart the computer. The system will ask you, which version of the OS you’d like to download. Pick "Microsoft Windows XP Professional  3GB".  

  • If everything goes right, use the version of OS with 3 GB. If not, you can go back to the initial version by picking the version without 3GB.


Video instruction





2. For the systems with small amount of RAM (2 Gb) and integrated videocard (IntelHD and others) (for x86 and x64 OS)



Switch on the “paging file” (also called swap file). This solution may cause a small drop in performance when the available physical memory limit is hit, but will prevent the crashes by the in-memory system starting to use the swap file.



Video instruction





 



2. Long loading time on Windows 7



 



In the Windows 7 OS, there’s a defect, which can slow down the time of loading to port and battle more than twice. This problem manifested itself the worst after the client packing.



This defect was fixed in one of the Windows 7 updates after the Service Pack 1. The issue appeared in the build "Windows 7  64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_rtm.101119-1850)", and was solved in  "Windows 7 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_ldr.160408-2045)". Accordingly, this defect affects all builds between them. If you are experiencing a very slow loading into battle (over a minute) and you have Windows 7, try to install the latest updates for this operating system - likely that the problem will go away. 


 

Edited by Santcoder, 17 August 2016 - 10:08 PM.


Share this post


Link to post
Share on other sites
Member
24 posts

1.  Client crashes on configurations with 32-bit OS or a small amount of RAM

 

Hello, everyone!

 

The amount and quality of the content in our game is constantly increasing, and a lot of new functionality is being added. This, unfortunately, does not come “free”, in terms of the use of computer resources. On high-performance configurations, players very rarely encounter any problems related to insufficient resources, but on the configurations with the 32-bit OS’s or a small amount of RAM the client may freeze or crash. In theory, you may never face this problem at all, unless “the stars align” in a certain manner – for example, you get a “heavy” map with the high tier ships. 

 

Still, recently the number of resorts to the support related to the World of Warships client crashing on 32-bit OS or small amount of RAM increased. Because of this, we would like to share some advices, which will help many players to up the “survivability” of the client.

 

From the technical side, the problem is related to the physical limit of the maximum amount of virtual memory allocated for the process in the operating system. Official information can be found on the Microsoft website - https://msdn.microso...a366778(v=vs.85).aspx The first line in the table is what is of interest for us, namely:

 

What does it mean?

It means that for the game process on x86 systems (Windows XP 32bit, Windows Vista 32bit etc.) the maximum amount of "virtual" memory for the process is 2 Gb, even if the RAM installed is bigger. For the x64 operating systems, the limit is 4 Gb.

 

What is the “virtual memory” of the process”? It’s a full amount of memory, including all the application memory allocation + system calls + DirectX + mapping files into the memory + mapping the video-memory into the process spaceIt’s important to understand that the “virtual memory” of the process is not the same as what you see in the Windows Task Manager.

 

With the 2 Gb limit, you can only play with the “Low” graphics preset, even if your configuration technically allows playing comfortably with the “Very high” (“texture quality” setting affect the likelihood of crashing the most).

 

Currently, we are actively working to minimize the likelihood of this kind of crashes, but if you are experiencing this problem, try the possible solutions listed below.

 

If your computer has more than 2Gb of RAM, it is recommended to install a 64-bit OS. If for any reason you can’t do so, read on.

 

1. Increasing the limit on the use of the virtual memory by the process up to 3 GB (only for x86 OS)

a. For 32-bit versions of Windows Vista/7/8, you should do the following:

  • 1. 1. Run the command prompt as an administrator. To do so, in the Start menu/start display enter cmd, press the icon with the right mouse button click and pick “Run as administrator” option.
  • 2. Enter bcdedit /set IncreaseUserVa 3072 in the Command Prompt window
  • 3. Restart the computer.

Video instruction

бFor the Windows XP it’s different. You need to carefully edit the Boot.ini file

  • 1. With the right mouse button click My Computer and pick Properties.
  • 2. Click Additional tab, click Startup and Recovery, and click Edit next.
  • 3. The Boot.ini file will open, there will be a line looking like: multi(o)disk(o)rdisk(o)partition(2)\WINDOWS=""Microsoft Windows XP Professional"" /fastdetect 4.
  • Copy this line to paste it below, then change the line you pasted to multi(o)disk(o)rdisk(o)partition(2)\WINDOWS="Microsoft Windows XP Professional 3GB" /3GB /userva=2900 /fastdetect
  • 5. Restart the computer. The system will ask you, which version of the OS you’d like to download. Pick "Microsoft Windows XP Professional  3GB".  
  • If everything goes right, use the version of OS with 3 GB. If not, you can go back to the initial version by picking the version without 3GB.

Video instruction

2. For the systems with small amount of RAM (2 Gb) and integrated videocard (IntelHD and others) (for x86 and x64 OS)

Switch on the “paging file” (also called swap file). This solution may cause a small drop in performance when the available physical memory limit is hit, but will prevent the crashes by the in-memory system starting to use the swap file.

Video instruction

 

2. Long loading time on Windows 7

 

In the Windows 7 OS, there’s a defect, which can slow down the time of loading to port and battle more than twice. This problem manifested itself the worst after the client packing.

This defect was fixed in one of the Windows 7 updates after the Service Pack 1. The issue appeared in the build "Windows 7  64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_rtm.101119-1850)", and was solved in  "Windows 7 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_ldr.160408-2045)". Accordingly, this defect affects all builds between them. If you are experiencing a very slow loading into battle (over a minute) and you have Windows 7, try to install the latest updates for this operating system - likely that the problem will go away. 

 

Edited by Santcoder, 17 August 2016 - 10:08 PM.

found this fix in another WOWS forum and tried it....although it did not fully eliminated the crashing of game client or that critical error, at least it was minimized.

Share this post


Link to post
Share on other sites

×