Jump to content

Search the Community

Showing results for tags 'error'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • World of Warships - News and Information
    • News And Announcements
    • Update Notes
    • Public Test
    • Surveys
  • General WoWS Discussion
    • General Game Discussion
    • Team Play
    • Support
    • Discussions about Warships
    • Historical Discussions and Studies
    • Player Modifications
  • Support
  • International Forums
    • Foro en Español
    • Fórum Brasileiro
  • Contest Entries
  • Contest Entries
  • New Captains
  • Guías y Estrategias
  • Árboles Tecnológicos
  • Fan Art and Community Creations
  • Community Created Events and Contests
  • Support

Calendars

  • World of Warships Event Calendar

Found 130 results

  1. Hello Colleagues, I would like to report an error In the Moscow, when you use the Aurora SpaceWarship camouflage, the fire of the chimneys remains on the commemorative flags as you will see in the pictures below Excuse my bad english Best regards
  2. BigWorld Error

    Hi, After getting the Windows Update, I could not launch any games, including WoWs. I got this error message while trying to launch WoWs: https://www.scribd.com/document/379906284/WorldOfWarships-Error. I have tried restarting my computer and reinstalling drivers.
  3. i have gotten this crash at least 12 times, causing me to get banned for match dodging, so that sucks. I am on a new iMac
  4. My friends game wont open.

    My friends game keeps crashing when he tries to open it. I have found similar stuff, tried doing those things to fix it. Like deleting the cashe, didnt work. When he was in game, half of his screen would go black. You would not be able to see his ship, nor more of anything else. But you would see the water and part of stuff like maybe the outline. I can get more info, but it will take time and I will need to know what you will need. Please help?
  5. I've looked around for things about "cPickle", but to no avail. ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- Application C:/Games/World_of_Warships/worldofwarships.exe crashed 03.11.2018 at 18:22:42 Message: Failed to import cPickle module. System info: OS Name: Windows 8.1 or later OS Version: 6.6 OS Architecture: x86_64 Memory info: Virtual memory: 602292Kb/4194176Kb (15%) Working set (process physical memory): 311820Kb/4194176Kb (7%) Commit charge (working set + process page file usage): 389904Kb/4194176Kb (9%) Global physical memory: 4024324Kb/16768052Kb (23%) Global commitable memory (physical + pagefile): 4882916Kb/33545268Kb (15%) System info: COMPUTERNAME = ANOTHER APPLICATION = "C:\Games\World_of_Warships\worldofwarships.exe" wows_wait_for_mutex -safe 8 PROCESSOR(S) = 0 - 6 1e05 DISPLAYDEVICE 0 = \\.\DISPLAY1, NVIDIA GeForce GTX 1050 Ti, PCI\VEN_10DE&DEV_1C82&SUBSYS_62553842&REV_A1 DISPLAYDEVICE 1 = \\.\DISPLAY2, NVIDIA GeForce GTX 1050 Ti, PCI\VEN_10DE&DEV_1C82&SUBSYS_62553842&REV_A1 DISPLAYDEVICE 2 = \\.\DISPLAY3, NVIDIA GeForce GTX 1050 Ti, PCI\VEN_10DE&DEV_1C82&SUBSYS_62553842&REV_A1 DISPLAYDEVICE 3 = \\.\DISPLAY4, NVIDIA GeForce GTX 1050 Ti, PCI\VEN_10DE&DEV_1C82&SUBSYS_62553842&REV_A1 Extended info: Current thread #1544 native trace: (0) : worldofwarships.exe!0x01102F7D (0) : worldofwarships.exe!0x01102536 (0) : worldofwarships.exe!0x01534DC7 (0) : worldofwarships.exe!0x01521407 (0) : worldofwarships.exe!0x013AAF5D (0) : worldofwarships.exe!0x013A3AD2 (0) : worldofwarships.exe!0x01109C20 (0) : worldofwarships.exe!0x01109C20 (0) : worldofwarships.exe!0x00D288BF (0) : worldofwarships.exe!0x0111A574 (0) : worldofwarships.exe!0x0111A541 (0) : worldofwarships.exe!0x0111A500 (0) : worldofwarships.exe!0x01112A2B (0) : ucrtbase.DLL!0x6C03E87F (0) : KERNEL32.DLL!0x75617C04 Frozen threads: Thread #7564 native trace: (0) : worldofwarships.exe!0x011B9BDC (0) : worldofwarships.exe!0x011A5429 (0) : worldofwarships.exe!0x011A94E4 (0) : worldofwarships.exe!0x011A0929 (0) : worldofwarships.exe!0x0105CEEF (0) : worldofwarships.exe!0x0170ED6F (0) : worldofwarships.exe!0x0170EA0E (0) : worldofwarships.exe!0x0171A024 (0) : worldofwarships.exe!0x017DA6DE (0) : worldofwarships.exe!0x0171ABDF (0) : worldofwarships.exe!0x017D938D (0) : worldofwarships.exe!0x017CB8A8 (0) : worldofwarships.exe!0x017D3710 (0) : worldofwarships.exe!0x0178620B (0) : worldofwarships.exe!0x01786296 (0) : worldofwarships.exe!0x01786958 (0) : worldofwarships.exe!0x0181B2AF (0) : worldofwarships.exe!0x0181B831 (0) : worldofwarships.exe!0x0176E056 (0) : worldofwarships.exe!0x0181B2AF (0) : worldofwarships.exe!0x0181B831 (0) : worldofwarships.exe!0x0176E056 (0) : worldofwarships.exe!0x0181B2AF (0) : worldofwarships.exe!0x0181B831 (0) : worldofwarships.exe!0x0176E056 (0) : worldofwarships.exe!0x0181B2AF (0) : worldofwarships.exe!0x0181B831 (0) : worldofwarships.exe!0x0176E056 (0) : worldofwarships.exe!0x0181B2AF (0) : worldofwarships.exe!0x017E339C (0) : worldofwarships.exe!0x0157F037 (0) : worldofwarships.exe!0x0157B09C (0) : worldofwarships.exe!0x013B8F4F (0) : worldofwarships.exe!0x0139B381 (0) : worldofwarships.exe!0x0139D1F4 (0) : worldofwarships.exe!0x01398993 (0) : worldofwarships.exe!0x013976ED (0) : worldofwarships.exe!0x01221913 (0) : KERNEL32.DLL!0x75617C04 Thread #3404 native trace: (0) : ntdll.dll!0x7720C33C (0) : KERNELBASE.dll!0x757E2C02 (0) : worldofwarships.exe!0x015623B4 (0) : worldofwarships.exe!0x01112A2B (0) : ucrtbase.DLL!0x6C03E87F (0) : KERNEL32.DLL!0x75617C04 Thread #5104 native trace: (0) : ntdll.dll!0x7720C75C (0) : worldofwarships.exe!0x0111AAA9 (0) : worldofwarships.exe!0x01112A2B (0) : ucrtbase.DLL!0x6C03E87F (0) : KERNEL32.DLL!0x75617C04 Thread #8164 native trace: (0) : ntdll.dll!0x7720C33C (0) : KERNELBASE.dll!0x757E2C02 (0) : worldofwarships.exe!0x0111A54A (0) : worldofwarships.exe!0x0111A500 (0) : worldofwarships.exe!0x01112A2B (0) : ucrtbase.DLL!0x6C03E87F (0) : KERNEL32.DLL!0x75617C04 Thread #6232 native trace: (0) : ntdll.dll!0x7720C33C (0) : KERNELBASE.dll!0x757E2C02 (0) : worldofwarships.exe!0x0111A54A (0) : worldofwarships.exe!0x0111A500 (0) : worldofwarships.exe!0x01112A2B (0) : ucrtbase.DLL!0x6C03E87F (0) : KERNEL32.DLL!0x75617C04 Thread #3584 native trace: (0) : ntdll.dll!0x7720C33C (0) : KERNELBASE.dll!0x757E2C02 (0) : worldofwarships.exe!0x0111A54A (0) : worldofwarships.exe!0x0111A500 (0) : worldofwarships.exe!0x01112A2B (0) : ucrtbase.DLL!0x6C03E87F (0) : KERNEL32.DLL!0x75617C04 Thread #3236 native trace: (0) : ntdll.dll!0x7720C33C (0) : KERNELBASE.dll!0x757E2C02 (0) : worldofwarships.exe!0x0111A54A (0) : worldofwarships.exe!0x0111A500 (0) : worldofwarships.exe!0x01112A2B (0) : ucrtbase.DLL!0x6C03E87F (0) : KERNEL32.DLL!0x75617C04 Thread #4296 native trace: (0) : ntdll.dll!0x7720DDEC (0) : KERNEL32.DLL!0x75617C04 Thread #6796 native trace: (0) : ntdll.dll!0x7720DDEC (0) : KERNEL32.DLL!0x75617C04 Thread #4420 native trace: (0) : ntdll.dll!0x7720C8AC (0) : combase.dll!0x75A2B822 (0) : combase.dll!0x75A2B89C (0) : combase.dll!0x75A63F50 (0) : combase.dll!0x75A534C6 (0) : KERNEL32.DLL!0x75617C04 Thread #5244 native trace: (0) : ntdll.dll!0x7720C33C (0) : KERNELBASE.dll!0x757E2C02 (0) : worldofwarships.exe!0x00C861A3 (0) : ucrtbase.DLL!0x6C03E87F (0) : KERNEL32.DLL!0x75617C04 Thread #4688 native trace: (0) : ntdll.dll!0x7720C33C (0) : KERNELBASE.dll!0x757E2C02 (0) : worldofwarships.exe!0x00C861A3 (0) : ucrtbase.DLL!0x6C03E87F (0) : KERNEL32.DLL!0x75617C04 Thread #3516 native trace: (0) : ntdll.dll!0x7720C33C (0) : KERNELBASE.dll!0x757E2C02 (0) : worldofwarships.exe!0x00C861A3 (0) : ucrtbase.DLL!0x6C03E87F (0) : KERNEL32.DLL!0x75617C04 Thread #7332 native trace: (0) : ntdll.dll!0x7720C33C (0) : KERNELBASE.dll!0x757E2C02 (0) : worldofwarships.exe!0x00C861A3 (0) : ucrtbase.DLL!0x6C03E87F (0) : KERNEL32.DLL!0x75617C04 Thread #7336 native trace: (0) : ntdll.dll!0x7720C33C (0) : KERNELBASE.dll!0x757E2C02 (0) : worldofwarships.exe!0x00C861A3 (0) : ucrtbase.DLL!0x6C03E87F (0) : KERNEL32.DLL!0x75617C04 Thread #6140 native trace: (0) : ntdll.dll!0x7720C33C (0) : KERNELBASE.dll!0x757E2C02 (0) : worldofwarships.exe!0x00C861A3 (0) : ucrtbase.DLL!0x6C03E87F (0) : KERNEL32.DLL!0x75617C04 Thread #7340 native trace: (0) : ntdll.dll!0x7720C33C (0) : KERNELBASE.dll!0x757E2C02 (0) : worldofwarships.exe!0x00C861A3 (0) : ucrtbase.DLL!0x6C03E87F (0) : KERNEL32.DLL!0x75617C04 Thread #7348 native trace: (0) : ntdll.dll!0x7720C33C (0) : KERNELBASE.dll!0x757E2C02 (0) : nvwgf2um.dll!0x6664A8B2 (0) : nvwgf2um.dll!0x66649A73 (0) : nvwgf2um.dll!0x66C07095 (0) : nvwgf2um.dll!0x66F7459E (0) : nvwgf2um.dll!0x66F746C6 (0) : KERNEL32.DLL!0x75617C04 Thread #8116 native trace: (0) : ntdll.dll!0x7720C33C (0) : KERNELBASE.dll!0x757E2C02 (0) : nvwgf2um.dll!0x666ACFCA (0) : nvwgf2um.dll!0x666ACEF0 (0) : nvwgf2um.dll!0x66F7459E (0) : nvwgf2um.dll!0x66F746C6 (0) : KERNEL32.DLL!0x75617C04 Thread #6320 native trace: (0) : ntdll.dll!0x7720C33C (0) : KERNELBASE.dll!0x757E2C02 (0) : nvwgf2um.dll!0x666ACFCA (0) : nvwgf2um.dll!0x666ACEF0 (0) : nvwgf2um.dll!0x66F7459E (0) : nvwgf2um.dll!0x66F746C6 (0) : KERNEL32.DLL!0x75617C04 Thread #5644 native trace: (0) : ntdll.dll!0x7720C33C (0) : KERNELBASE.dll!0x757E2C02 (0) : nvwgf2um.dll!0x666ACFCA (0) : nvwgf2um.dll!0x666ACEF0 (0) : nvwgf2um.dll!0x66F7459E (0) : nvwgf2um.dll!0x66F746C6 (0) : KERNEL32.DLL!0x75617C04 Thread #212 native trace: (0) : ntdll.dll!0x7720C33C (0) : KERNELBASE.dll!0x757E2C02 (0) : nvwgf2um.dll!0x666ACFCA (0) : nvwgf2um.dll!0x666ACEF0 (0) : nvwgf2um.dll!0x66F7459E (0) : nvwgf2um.dll!0x66F746C6 (0) : KERNEL32.DLL!0x75617C04 Thread #6492 native trace: (0) : ntdll.dll!0x7720C33C (0) : KERNELBASE.dll!0x757E2C02 (0) : nvwgf2um.dll!0x666ACFCA (0) : nvwgf2um.dll!0x666ACEF0 (0) : nvwgf2um.dll!0x66F7459E (0) : nvwgf2um.dll!0x66F746C6 (0) : KERNEL32.DLL!0x75617C04 Thread #5376 native trace: (0) : ntdll.dll!0x7720C33C (0) : KERNELBASE.dll!0x757E2C02 (0) : nvwgf2um.dll!0x666ACFCA (0) : nvwgf2um.dll!0x666ACEF0 (0) : nvwgf2um.dll!0x66F7459E (0) : nvwgf2um.dll!0x66F746C6 (0) : KERNEL32.DLL!0x75617C04 Thread #3380 native trace: (0) : ntdll.dll!0x7720C33C (0) : KERNELBASE.dll!0x757E2C02 (0) : nvwgf2um.dll!0x666ACFCA (0) : nvwgf2um.dll!0x666ACEF0 (0) : nvwgf2um.dll!0x66F7459E (0) : nvwgf2um.dll!0x66F746C6 (0) : KERNEL32.DLL!0x75617C04 Thread #7656 native trace: (0) : ntdll.dll!0x7720C33C (0) : KERNELBASE.dll!0x757E2C02 (0) : nvwgf2um.dll!0x666ACFCA (0) : nvwgf2um.dll!0x666ACEF0 (0) : nvwgf2um.dll!0x66F7459E (0) : nvwgf2um.dll!0x66F746C6 (0) : KERNEL32.DLL!0x75617C04 Thread #7660 native trace: (0) : ntdll.dll!0x7720C8AC (0) : worldofwarships.exe!0x01311EA4 (0) : KERNEL32.DLL!0x75617C04 Thread #7664 native trace: (0) : ntdll.dll!0x7720C33C (0) : KERNELBASE.dll!0x757E2C02 (0) : worldofwarships.exe!0x012C93FC (0) : KERNEL32.DLL!0x75617C04 Thread #7672 native trace: (0) : ntdll.dll!0x7720C33C (0) : KERNELBASE.dll!0x757E2C02 (0) : worldofwarships.exe!0x012B6C01 (0) : KERNEL32.DLL!0x75617C04 Thread #7676 native trace: (0) : ntdll.dll!0x7720C33C (0) : KERNELBASE.dll!0x757E2C02 (0) : worldofwarships.exe!0x012C2E5A Thread #7696 native trace: (0) : ntdll.dll!0x7720C8AC (0) : KERNEL32.DLL!0x75617B89 (0) : XAudio2_8.dll!0x6D932AD0 (0) : XAudio2_8.dll!0x6D93166D (0) : XAudio2_8.dll!0x6D9327AB (0) : KERNEL32.DLL!0x75617C04 Thread #7700 native trace: (0) : ntdll.dll!0x7720C8AC (0) : KERNEL32.DLL!0x75617B89 (0) : nvwgf2um.dll!0x66BEAC98 (0) : nvwgf2um.dll!0x66C07095 (0) : nvwgf2um.dll!0x66F7459E (0) : nvwgf2um.dll!0x66F746C6 (0) : KERNEL32.DLL!0x75617C04 Thread #7704 native trace: (0) : ntdll.dll!0x7720C8AC (0) : USER32.dll!0x7538DE93 (0) : USER32.dll!0x7538DBDF (0) : gdiplus.dll!0x606933BA (0) : gdiplus.dll!0x6069C225 (0) : KERNEL32.DLL!0x75617C04
  6. This error shows me some during the time I am playing
  7. Critcal Error Occured Application C:/Games/World_ofWarships/worldofwarships.exe crashed 03.03.2018 at 20:05:54 Message: The BigWorld Client has encountered an unhandled exeception and must close (EXECEPTION_ACCESS_VIOLATION : 0XC0000005 @ 0X018895A0) (Read @ 0x00000000) Current thread #11136 native trace: (0) :worldofwarships.exe!0x018895A0 (0) :worldofwarships.exe!0x018897DD (0) :worldofwarships.exe!0x01989162 (0) :worldofwarships.exe!0x016E0B78 (0) :worldofwarships.exe!0x016E1A31 (0) :worldofwarships.exe!0x016DB254 (0) :worldofwarships.exe!0x012DD294 (0) :worldofwarships.exe!0x016D8A23 (0) :worldofwarships.exe!0x016D776D (0) :worldofwarships.exe!0x01561913 (0) :KERNEL32.DLL!0x76328654 System Info: OS Name: Windows 8.1 or later OS Version: 6.6 OS Architecture: x86_64 Memory Info: Virtual memory: 481008Kb/4194176Kb (12%) Working set (process physical memory): 262036Kb/4194176Kb (6%) Commit charge (working set + process fire usage): 277572Kb/4194176Kb (6%) Global Physical memory: 2716036Kb/8312856Kb (32%) Global commitable memory (physical + pagefile): 2786776Kb/11851800Kb (24%)
  8. I keep getting disconnected from the server about once per round in Random Battle. As I'm playing, the screen will freeze for a few seconds and then I'm taken back to the World of Warships login page with the orange Login button. I can reconnect right away, but my ship was idle while disconnected and I'm usually nearly dead by that time. I'm on a 100 Mbps cable connecting which has low ping. I don't have problems with any other online games. Do you have any ideas on what I can try to troubleshoot this? The connection only happens while playing World of Warships. Thank you in advance.
  9. Game crashed with Critical Error

    Recently updated World of Warships and tried playing it and got this error...
  10. Beginning 4 days ago (January 20), my PC began locking up while playing World of Warships. This doesn't happen every time I play and I can't find any combination of in-game actions, length of session, or other factors which would explain it. I've been playing off and on since shortly after release (stopped playing for most of 2017 & returned just before Christmas) and have never had this issue before with this or any program on my machine. My stats: Intel I7-6700K 4GHz 16 GB RAM Windows 10 Home NVIDIA GeForce GTX 1070 Water-cooled with multiple fans, all working flawlessly The machine itself is about 18 months old, and again I have had absolutely zero issues with it until the past couple days. Things I have already tried: Updated all drivers (only the NVIDIA driver was out of date) Confirmed that all power save options were disabled Ran Memory Check Ran Disc Check Ran System File Check Manually adjusted virtual memory to manufacturer recommended settings Clean install of WoWs I don't believe this is a bug with WoWs specifically, as I'd played dozens of games between the last update and when these crashes began happening. Two other significant changes were made right before the issues began, however: a windows security patch was issued/installed (I have since uninstalled the patch which made no difference), and our modem was replaced with a new XFinity modem/router combo. I currently have bridge mode enabled on the new modem to continue using my existing router (NETGEAR Nighthawk X4S AC2600), which I connect to via a USB stick. I mention this because yesterday evening the USB stick "crashed", which was resolved by unplugging it and then reinserting...I did notice that the connector was very hot to the touch when I first removed it from the USB port. I've ordered a replacement unit (I've been using the current one for about a year), which should be here later today. At this point I'm at a total loss on what to do next. I was running Performance Monitor on my second screen during the most recent lock and saw absolutely no spikes before the machine locked up. Going through the notification logs has shown no errors reported prior to the crashes, and no error messages which hadn't been happening intermittently for months without causing problems (things like Windows Hello for Business not being compatible). If any of you more technologically inclined folks have any other suggestions, I'd love to hear them...I'm not really up on advanced PC tinkering, but I'm not afraid of doing some providing I know exactly what to do & why. Again, I have only had this issue while WoWs was running on the PC (several times while playing and once while running in the background). EDIT: I do have Aslain's mod pack installed on the computer, but I am not currently using any of its mods in the game.
  11. I haven't been able to play wows for a couple weeks because of classes but when I finally got back, I noticed that wows had sent me this email (check attached screenshot) saying I got these rewards, but when I logged on, they didn't show up. Any help?
  12. Saludos: Hoy al querer iniciar mi juego desde el escritorio como siempre hago me sorprendio ver un reporte de error de Crasheo del juego apenas pulse el boton jugar. Al ver esta situación intente varias cosas: .-Probé a lanzar el juego un par de veces mas y nada seguía apareciendo el reporte de error .-Probé con el modo seguro y lo mismo .-Intente con la herramienta que revisa la integridad de los datos del juego y nada .-Reinicie mi pc y volví a repetir el proceso de revisar el juego abrir en modo seguro y nada, el reporte de error sigue apareciendo No quiero tener que reinstalar el juego porque es perder el día completo en descargar el juego y todas sus actualizaciones nuevamente
  13. https://imgur.com/a/yZLdF win 10 - 64bit reinstalled firewall to default reinstalled NIC reinstalled game reinstalled windows Same result
  14. PTS 0.7.0 Game Crash

    Selected battle mode CO-OP. Saw some hint texts. Clicked on the start button around 5-6 seconds left and got a "Critical Error Occurred" message. "The BigWorld client has encountered an unhandled exception and must close (EXCEPTION_ACCESS_VIOLATION: 0xC0000005 @ 0x01964A73) (Write @ 0x00000000 )." I did not include the dump of the thread IDs.
  15. i just press the play button and it does this. i reinstalled i 3 time restarted my computer im out of ideas. was working fine 3 days ago. NVM somehow restarting my computer one more time did it im so confused right now.
  16. Critical error on startup

    Just updated the game and now every time I try to launch it, it has a critical error and fails. The launcher boots up fine but a few seconds after I hit play I get the critical error message that says world of warships has crashed. I saw a few people had this problem back in July but I've never experienced this before and the last time I played was back in October. I recently did a windows updated don't know if that would make a difference though. So is this because the update moved things around or the windows update screwd up some files or is it just bad luck, ether way how do I fix this?
  17. Game Launches into some korean prelaunch version

    I was playing WoWs and I needed to restart my computer. The restart was not related to WoWs in any way and when I went to launch back into the game, the game client loading screen looked like this picture. There was more text on the screen at one point but could not capture it in time because it was freaking me out. It looks like Korean text on the screen and I am at a loss for what it says. I noticed the Pre-Alpha version on the top left of the screen but holy heck am I at a loss for what happen. The game is supposed to launch into the NA server but some how ended up with this. Can anyone let me know if WG is working on a Korean client and it somehow has files in everyone's WoWs directory? After the loading bar spams sliding from left to right, it eventually loaded up to the NA server log in page but I'm too paranoid to jump on any more. HALP!!!
  18. Cannot Gift a Ship

    Hello, I'm trying to gift my buddy the USS Texas but when I click on the Visa option, the icon will spin for a couple of seconds and then nothing will happen. This happens with the PayPal and any other option too. If I try to buy the ship for myself, it takes me to the right screen. Is anyone else having this issue? If it helps, my buddy's account is level 13 and he's only been playing for a couple of weeks now. Thank you!
  19. yesterday I had a memory access violation exception which I believe is WoWs client exe trying to access a protected address in memory. This crash happened at the end of the match. This crash I think is resolved by disabling DEP or making an exception rule for the app. but not fix for bug, fix would be not to access protected memory by the exe. 2nd crash I have as of today after the patch is at the very beginning of the match. Crashes to the desktop, no error stack trace. Not sure what this is. No mods here or nothing funky. little digging, found crash dump files for 2nd type of crash that started occurring today at the beginning of the match. Appears to error similar to crash type 1 above... app is trying to access protected memory and windows is shutting her down. I'm going to create a DEP exception rule allowing wows to access memory it should not and see if that helps. Scratch that Idea it does not work. Crashed on second attempt after disabling DEP. WorldOfWarships.exe Stopped working 12/5/2017 9:31:05 PM All Users 0xc0000005 Access Violation 0x00733919 WorldOfWarships.exe Debugged crash with VS2015 and it is pointing the crash to a particular dll, UCRTBASE.DLL appears to be causing the crash. Possible Solution 1 Still digging looks like a common problem this thread hints at problem is more than one audio driver installed. I currently have a USB Dolby 7.1 gaming headphone that has its own audio Driver.... I'm going to uninstall that bad boy today and give it a shot. Possible Solution 2 If the audio driver thing does not work out, here is a writeup for this dll for shadow of war causing issues. This describes needing the exe to be launched as admin. I'm going to try this after the audio driver suggestion. https://steamcommunity.com/app/356190/discussions/0/1484358860944996931/ Possible Solution 3 Read that Preferences.xml causes issues like this sometimes... I'm going to try kneecapping that and see if it persists. **Update** after opening ticket with support solution 3 is the recommended first try. **Final Update Resolved** Option 3 resolved it as WG Support called it. Possible Solution 4 This suggest it might just be a good old fashioned programming bug. https://stackoverflow.com/questions/38286268/exception-thrown-at-0x0f640e09-ucrtbased-dll-in-consoleapplication5-exe-0xc00 Possible Solution 5 WOT had similar issues after a major release. Devs recommended resetting display settings in launcher. This may do solution 3 item above among other things. Going to try that today. https://worldoftanks.com/en/news/general-news/core-3-0/
  20. Critical error Occurred???

    Download aslain, then booted up game, logged into one game and was botted, now every time I try I get Critical error occurred message sayng Message The Bigworld client encountered an unhandled exception and must close(Exception ACCESS_VIOLATION current thread #7172 native trace and a bunch of other stuff, I have had this happen in the past, but I did a check and repair game integrity and or rebooted my computer and it fixed it. Not this time any ideas??
  21. when i logged in today and i loaded my dock it showed my currency with warning symbol on it, i was and still am not able to buy anything
  22. Hi guys! So, us at Hinon were chatting about the newly announced Salem and looking at the model, when @RivertheRoyal pointed out, "Are Salem's guns longer than DM's? I was just wondering, because DM's guns always seemed stubby to me, and I don't get that feeling from Salem." So, started a round of comparing DM's rifles to Salem's from @renegadestatuz @Nuk_ @Jnobsir and I, and low and behold... Des Moines. Salem. Notice the barrel's length and size? IRL Des Moines for clarification. So I started staring at it, and thought, "Those look like 6"/47s more than 8"/55s." So the comparison was made: Cleveland. Des Moines. Close up comparing the two. Especially the #2 turret looks very off. And it very much appears to be a 6" gun and not an 8" gun. (Visually, and just the barrel, not the turret, not game performance wise) For added reference, here is Baltimore with her guns (Same gun, same caliber, just different loading system): With DM's, and Cleveland's guns for reference. So it appears that while the turrets are not Cleveland's, nor are the guns really, Des Moines' guns are still too short. What are your thoughts? Are we just seeing something that isn't there? Or are we onto something that has been hidden since beta and only now with the Salem coming out do we have a point of reference. If it is a visual error, I'd like to bring it up to @Pigeon_of_War Credits go to River for pointing this out and for Cleveland and Des Moines on Ocean port. Jnobsir for the rest of the images that are not historical photos. Fair winds and following season captains!
  23. Can't install game

    So I have been playing this game for over a year and never really had any problems. A few days ago I tried launching the game, only to get an error saying it couldn't launch. After many failed attempts I decided to just uninstall and reinstall the game. The download was very slow so it spanned over hours. Since I had to leave for a long time, I didn't want the pc to stay on for that long, so I stopped the installation for the time being. After I came back I resumed installation, but after awhile it would just sit there, it would never resume. Since It didn't download that much, I decided to uninstal it again and tried to reinstall. Took another day. Before I went to bed I saw it only had a few gigs left. Cool it would take only a few hours. When I awoke this morning it had closed itself. I reopened the launcher, but it would refuse to resume. After a few more tries it would pop an error screen after I tried resuming. I have no idea why it won't complete the download. I have plenty of space on my pc, and all of my other games haven't had this much trouble installing. I would appreciate any feedback. It'd be great to finally get back to this game...
  24. wg's fictional refits created some weird problem: apparently some helmsmen must have eyes like x-men to navigate their vessels this is kaiser's second hull - as you can see additional rangefinder on top of the turret is completelly obstructing view from the navigation bridge konig's second hull has the exact same issue emile bertin's helmsman also received this challenge with additional bofors. however unlike german bb's this could be fixed with some effort. with moving the bofors on top of the conning tower the navigation bridge will have free view again. however some surrounding devices will be still obstructed. but this is probably better solution the very same thing arrived with british battleships as well...this is second hull for iron duke in this case the solution is pretty simple since the platform is very convenient. just lift that a bit higher and visibility wont be obstructed orion has this problem as well while in her case navigation bridge has clear view. only view from conning tower is blocked and again this can be easily fixed
  25. Hi! So I just got done trying relentlessly to install the latest update, and it goes to the installing portion then stops and says "Critical error, this application cannot continue. Check logs" (Which is attached) I run no mods, and am on windows 10. any help? thanks!
×