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

Why I keep crashing?

17 comments in this topic

Recommended Posts

Beta Tester
404 posts
1,148 battles

Recently, I am crashing during the games

post-2002431206-0-39383600-1478524533.jp

It happens in almost every games, which is extremely annoying

the ping didn't bump up before crashing

and it usually happens when there are lots of enemies in sight

 

I didn't install any mods

I tried lowering the graphical setting

the situation improved a bit, but it's still happening and the graphical setting has already been low

 

can anyone explain what's happening and what can I do to solve it?

Edited by CarbonMonoxide

Share this post


Link to post
Share on other sites
Alpha Tester
1,637 posts
7,230 battles

I too was getting the same message after my game would crash, always right at end of battle just before the victory/defeat screen.

 

More RAM and 64 bits fixed it for good- just as YetAnotherNoob says.

 

 

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. 

 

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. 

did tried this fix on my PC that keeps crashing while playing WOWS and it did help minimize crashing.

Share this post


Link to post
Share on other sites
Beta Tester
404 posts
1,148 battles

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. 

 

I too was getting the same message after my game would crash, always right at end of battle just before the victory/defeat screen.

 

More RAM and 64 bits fixed it for good- just as YetAnotherNoob says.

 

 

 

seems to be a borderline minimum PC

like above

increase your RAM and/or Use better Windows

 

Insert more RAM and use 64 bit Windows

 

thanks all of you

It gets much smoother after increasing the limit of the virtual memory

and the error hasn't occurred again by now

 

but about the RAM and 32/64 bit problem

it seems troublesome to upgrade to 64 bit or even buy a new computer

so probably I should insert some more RAM

Share this post


Link to post
Share on other sites
Member
227 posts
2,651 battles

but about the RAM and 32/64 bit problem

it seems troublesome to upgrade to 64 bit or even buy a new computer

so probably I should insert some more RAM

 

You must use 64 bit Windows to get the benefit from having more than 4GB RAM

 

Share this post


Link to post
Share on other sites
Member
24 posts

im sure when WOWS is already out of Open Beta and is a regular game, WG may compress and re size the game client like what they did to WOT and it would probably eliminate that game client crashing problem......WOT had similar problem before when the game client file size was @ 24GB, while playing WOT, my PC would post thIs error message VIRTUAL MEMORY TOO LOW and moments later, the screen would just freeze.

 

hopefully WG wont just move away with win xp / vista x86 / 32bit O/S....but maybe they will stop supporting these O'S in the future.....League of Legends PH already stop supporting win xp SP2 and early version of windows vista only this November.....so for the moment,  we may have to start saving some money for a newer computer 

 

 

Share this post


Link to post
Share on other sites
Senior Moderator
4,798 posts
1,924 battles

 

hopefully WG wont just move away with win xp / vista x86 / 32bit O/S....but maybe they will stop supporting these O'S in the future.....League of Legends PH already stop supporting win xp SP2 and early version of windows vista only this November.....so for the moment,  we may have to start saving some money for a newer computer 

 

 

 

why would anyone writing software support something the original vendor no longer supports?

You can only allow for so many systems.

 Supporting a 15 year old operating system, that was dropped by it's writer 5 years ago is asking a bit much don't you think?

Share this post


Link to post
Share on other sites
Member
227 posts
2,651 battles

im sure when WOWS is already out of Open Beta and is a regular game, WG may compress and re size the game client like what they did to WOT and it would probably eliminate that game client crashing problem......WOT had similar problem before when the game client file size was @ 24GB, while playing WOT, my PC would post thIs error message VIRTUAL MEMORY TOO LOW and moments later, the screen would just freeze.

 

hopefully WG wont just move away with win xp / vista x86 / 32bit O/S....but maybe they will stop supporting these O'S in the future.....League of Legends PH already stop supporting win xp SP2 and early version of windows vista only this November.....so for the moment,  we may have to start saving some money for a newer computer

 

the particles system is testing the new DirectX (dunno if it's DX10 or DX11), new year will likely receive the change and say goodbye to Windows XP support.

Share this post


Link to post
Share on other sites
Member
1 post
4,721 battles

Mine PC is win10 64bit with CPU: I7 6700 GTX970 card and 8G memory but have the same problem with you. And also I can not connect to server randomly or while playing, my PC restart itself with no sign.

Share this post


Link to post
Share on other sites
Beta Tester
404 posts
1,148 battles

 

You must use 64 bit Windows to get the benefit from having more than 4GB RAM

 

I have exactly 4GB RAM

so I must switch to a 64 bit OS

but can I just upgrade my OS to 64 bit?

some said that I can do so if my CPU supports 64 bit, and I've checked my Pentium® Dual-Core E5400 does

 

the particles system is testing the new DirectX (dunno if it's DX10 or DX11), new year will likely receive the change and say goodbye to Windows XP support.

now I'm a bit afraid that my computer will also lose support soon...

Share this post


Link to post
Share on other sites
Member
227 posts
2,651 battles

I have exactly 4GB RAM

so I must switch to a 64 bit OS

but can I just upgrade my OS to 64 bit?

some said that I can do so if my CPU supports 64 bit, and I've checked my Pentium® Dual-Core E5400 does

now I'm a bit afraid that my computer will also lose support soon...

 

Windows 7 likely runs on par with Windows XP, without some really outdated hardware, you only need new drivers for Windows 7 x64 after installing it.

 

Nearly all CPU you can get on the market is x64, so the choice is yours, so, WIndows 7 x64 all the way to go.

Edited by YetAnotherNoob

Share this post


Link to post
Share on other sites
Senior Moderator
4,798 posts
1,924 battles

 

Windows 7 likely runs on par with Windows XP, without some really outdated hardware, you only need new drivers for Windows 7 x64 after installing it.

 

Nearly all CPU you can get on the market is x64, so the choice is yours, so, WIndows 7 x64 all the way to go.

 

As much as I hate saying this, you are better off going to Windows 10 if you are buying a new PC.

This will future proof you as much as possible against changes.

 

Share this post


Link to post
Share on other sites
Beta Tester
404 posts
1,148 battles

 

Windows 7 likely runs on par with Windows XP, without some really outdated hardware, you only need new drivers for Windows 7 x64 after installing it.

 

Nearly all CPU you can get on the market is x64, so the choice is yours, so, WIndows 7 x64 all the way to go.

 

new drivers for Windows 7 x64

is it something included when I upgrade to Windows 7 x64?

so I just need to upgrade it or do I need to get the driver additionally?

Share this post


Link to post
Share on other sites

×