Game wont stop crashing on launch

[Isaac_Watson]

Whenever i launch the game and enter my password i load in, my war frame begins to stand up inside the ship and then the game freezes mid stand up and stays frozen for 5 seconds then closes with no message or report or anything, I have tried all recommended solutions none have worked, update my drivers and windows, verified game files and then optimized, uninstalled programs that cause the game crashing, ran multiple virus scans and cleared all and any, completely updated my PC but the game still crashes at the same point.

[krc473]

2 minutes ago, Isaac_Watson said:

my PC but the game still crashes at the same point.

Does your PC meet the minimum specs to play the game?

 

Otherwise, check the logs and see if anything stands out as odd. Windows event viewer might give you something. Find the error code for when it crashed and google it. 

[Isaac_Watson]

2 hours ago, krc473 said:

Does your PC meet the minimum specs to play the game?

 

Otherwise, check the logs and see if anything stands out as odd. Windows event viewer might give you something. Find the error code for when it crashed and google it. 

My pc meets the requirements fine, u already have 136 hours in the game from when i played before on this PC, how do i check the logs? using event viewer or otherwise?

[fr4gb4ll]

2 hours ago, Isaac_Watson said:

My pc meets the requirements fine, u already have 136 hours in the game from when i played before on this PC, how do i check the logs? using event viewer or otherwise?

for the event logs: on windows 10 it's better to just type "event" while the startmenue is open - the the correct option then should be right on top of the list. otherwise you could ofc creep through the setting and the many sub-settings or you create a "god-mode-folder" by creating a new folder and name it " GodMode.{ED7BA470-8E54-465E-825C-99712043E01C}  "  - whithout the "" and the name GodMode being optional - just put anyname there... windows will then put about every service setting that has a gui as links into this new folder.

krc473 missed to mentioned where to look too: in the event viewer, check "system", the subsection of the "windows logs" and look for errors and warnings related to your video card (e.g. everything with nvidia gpus and susequent drivers of them will have something with 'nv' in there - the explanation usually is everything but clear if you aren't used to work deeply into a system, but the usual problem with vid-cards and and especially in connection with warframe are ID13 errors where the driver stoped working and windows restarted it... sadly warframe won't usually 'survive' this procedure and either crashes back to the desktop or will freeze. in addition, it might be best to restart the whole system after this happened since windows is not always doing a good job with the driver-restart-on-the-fly... at least, keep that in mind if the crash/freez repeat itself after only restarting the game (goes not only for warframe here).

another culprit when it comes to crashes in warframe (and some other games too) is a vid-card that run in overclocked mode (oc) - regardless of you having done oc yourself or if the manufacturer sold this 'feature' as 'boost' or somthing similar... if you don't know this behavior or your card, you can check it by first getting the 'normal' clock-values of the GPU and the memory by just google them (nvidia and amd both have specs-site for all GPUs the ever made - there you can find them even if the manufacturer is someone else, like asus or msi). next, get an oc-tool, not for overclocking but to get the real values your card uses when under load (meaning, when a game is running and using the card, otherwise you only get displayed the very low idle values). if the "on-load" values are higher then what the spec for a normal, gpu are, the card gets 'boosted' for better performance...

the problem with the oc in warframe is that seemingly the engine can't really handle this well and tend to crash or freez the game. in all my years with warframe i only had one card out of about a dozent (all nvidia btw) that could run the game for hours without any problems while oc'ed - the others crashed very fast, sometimes in a matter of minutes. when using an oc-tool like MSIafterburner (my personal favorite one since it works well with every card and GPU manufacturer) to set the clocks to the default value and therefore stop the card from 'boosting' it up for more performance, warframe runs smoth (mostly) again.

• there are ofc other possible sources of trouble: GPU-temperature (you can check that also with most oc-tools) running to high and either start producing lags cuz of 'down-clocking' to prevent the thermal destruction of the GPU.
• problems with the powersupply unit (PSU) - either it is too weak to provide enough power to the card or worse yet, the voltage stabilizers are not working correct anymore (e.g. after they got 'hit' by an overload in the power grid but not didn't completely burned out then - or they just got too old and the regulation goes too far up or down of what the hardware of the computer can work with, especially those power-eater like a video card. testing this is kinda hard if you don't have an oscilloscope and the PSU is otherwise working fine... if you have a spare one put it in and see if the problems stop (or not). watching the voltage value via any 'onboard tools' is pretty much useless, as is any logging of them on the computer itself (since if an over- or under voltage is happening, either the system will crash or it's happening far too fast for it to getting logged).
• as to the above mentioned "look into the event-log", i had found several possible culprits over the years, some where faulty hardware like memory or the hdd/ssd the game was running on but also the game itself, or more specific the engine sending out 'iligal opcodes' occasionally which the GPU might or might not handle well and thus crashes the driver - if that is the case, the event log will mention such iligal opcode 'accident' in name... ofc, those are the in-deep-bug the devs should fix, but as someone who works with computerhardware daily, i can say that those problems are very tricky to pin down if you don't have the exact same hard AND software configuration as the one who get the errors - and even then it might not be possible due to different 'ages' of the hardware or degradations of the software environment. in the end, usually devs ignore those freak-accidents since they would waste tons of time and workforce to iron them out - in short, everything that they can't recreate on their test-rigs will be ignores (you usually see such commends from devs saying they can't recreate this bug or behaviour)... in such cases you can only help yourself by 'changing' your own hard- and software environment by replacing hardware and/or setting on a new, fresh and clean system... and... test again, hoping for the best ^^)

you might also try running the game not in fullscreen mode but in borderless mode (not windowed mode, mind you) - the reason might be that windows handels those modes differently and seemingly is better with the borderless mode (not only in warframe). ofc, old games can't run this way and some even crashes when getting out of fullscreen if you alt-tab out of them... luckily, warframe isn't such a game. oh, but better make sure you run the same resolution in game as you do in 'native' windows otherwise you might get some 'strange' effects.

[HeartPurity]

Play in windowed/ borderless fullscreen mode

Set the graphic settings to the lowest to see if the crash still remains

Check whether is it your firewalls blocking the game

Try reinstalling the game. 

Upgrade your RAM

[fr4gb4ll]

15 hours ago, HeartPurity said:

Set the graphic settings to the lowest to see if the crash still remains

sure, but since he already say the speca aren't an issue i would belive him until he posts them and maybe prove they ain't... also, if if hapens right at launch, i doubt that the setting per se are a problem... but what you say can still hold true if, for example, he installed a new vid-card and then started the game... even with a card nearly the same as the old one, it might lead to such a crash (i had this once after replacing my card too). better then trying anything in the launcher settings (and the othere settings aren't useable when it crashes right after trying to start the game via the launcher) is to delete/rename/remove the file for the graphic settings (filename is "settings" with no extension on it, placed in the folder with the hexadecimal name in the " ..\Users\USERNAME\AppData\Local\Warframe\ " location - the file will be recreated when starting the launcer and setting the first options in there - the rest have to be done in the options ingame. and no worries about the key-bindings, those are stored in the EE.cfg file along with some other stuff... though, i think there are some video settings at the bottom of the file too regarding the base starting values, so maybe he should remove this config file too...

16 hours ago, HeartPurity said:

Check whether is it your firewalls blocking the game

no. this won't crash this game or any other i every played - it only can gives you trouble to connect or even login anywhere... same with every other faulty network settings like NAT or the manual port forwarding.

16 hours ago, HeartPurity said:

Try reinstalling the game. 

Upgrade your RAM

reinstalling should only be the second last option here for it nearly never solves anything - even a clean reinstallation of windows itself is more usefull before that... but ofc, if one has the time and bandwidth to waste, why not?

and ram upgrading? again i guess that if he say that the specs aren't the issue (ofc he did not posted them, so it still might be) then the system RAM should be just fine - a lack of video ram is far more a problem - but then again, if he's playing on a mobile computer, both might be one and the same... sadly often this also means there is no further upgrading to the ram.

OP did not state if the game was running fine on his rig before this problem and therefore we can only do guesswork until he specify the circumstances and/or posting his used hardware specs.

[krc473]

5 hours ago, fr4gb4ll said:

sure, but since he already say the speca aren't an issue i would belive him until he posts them and maybe prove they ain't

People who claim their specs are fine but don't post them usually have low specs. OP could see a benefit by turning down their graphics. But we also don't know what level of graphics OP is running. They haven't really provided any information.

[Isaac_Watson]

15 hours ago, krc473 said:

People who claim their specs are fine but don't post them usually have low specs. OP could see a benefit by turning down their graphics. But we also don't know what level of graphics OP is running. They haven't really provided any information.

Processor: Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (8 CPUs), ~3.6GHz

RAM: 16GB

that's fine right?

[Isaac_Watson]

On 2020-08-21 at 3:52 AM, fr4gb4ll said:

for the event logs: on windows 10 it's better to just type "event" while the startmenue is open - the the correct option then should be right on top of the list. otherwise you could ofc creep through the setting and the many sub-settings or you create a "god-mode-folder" by creating a new folder and name it " GodMode.{ED7BA470-8E54-465E-825C-99712043E01C}  "  - whithout the "" and the name GodMode being optional - just put anyname there... windows will then put about every service setting that has a gui as links into this new folder.

krc473 missed to mentioned where to look too: in the event viewer, check "system", the subsection of the "windows logs" and look for errors and warnings related to your video card (e.g. everything with nvidia gpus and susequent drivers of them will have something with 'nv' in there - the explanation usually is everything but clear if you aren't used to work deeply into a system, but the usual problem with vid-cards and and especially in connection with warframe are ID13 errors where the driver stoped working and windows restarted it... sadly warframe won't usually 'survive' this procedure and either crashes back to the desktop or will freeze. in addition, it might be best to restart the whole system after this happened since windows is not always doing a good job with the driver-restart-on-the-fly... at least, keep that in mind if the crash/freez repeat itself after only restarting the game (goes not only for warframe here).

another culprit when it comes to crashes in warframe (and some other games too) is a vid-card that run in overclocked mode (oc) - regardless of you having done oc yourself or if the manufacturer sold this 'feature' as 'boost' or somthing similar... if you don't know this behavior or your card, you can check it by first getting the 'normal' clock-values of the GPU and the memory by just google them (nvidia and amd both have specs-site for all GPUs the ever made - there you can find them even if the manufacturer is someone else, like asus or msi). next, get an oc-tool, not for overclocking but to get the real values your card uses when under load (meaning, when a game is running and using the card, otherwise you only get displayed the very low idle values). if the "on-load" values are higher then what the spec for a normal, gpu are, the card gets 'boosted' for better performance...

the problem with the oc in warframe is that seemingly the engine can't really handle this well and tend to crash or freez the game. in all my years with warframe i only had one card out of about a dozent (all nvidia btw) that could run the game for hours without any problems while oc'ed - the others crashed very fast, sometimes in a matter of minutes. when using an oc-tool like MSIafterburner (my personal favorite one since it works well with every card and GPU manufacturer) to set the clocks to the default value and therefore stop the card from 'boosting' it up for more performance, warframe runs smoth (mostly) again.

• there are ofc other possible sources of trouble: GPU-temperature (you can check that also with most oc-tools) running to high and either start producing lags cuz of 'down-clocking' to prevent the thermal destruction of the GPU.
• problems with the powersupply unit (PSU) - either it is too weak to provide enough power to the card or worse yet, the voltage stabilizers are not working correct anymore (e.g. after they got 'hit' by an overload in the power grid but not didn't completely burned out then - or they just got too old and the regulation goes too far up or down of what the hardware of the computer can work with, especially those power-eater like a video card. testing this is kinda hard if you don't have an oscilloscope and the PSU is otherwise working fine... if you have a spare one put it in and see if the problems stop (or not). watching the voltage value via any 'onboard tools' is pretty much useless, as is any logging of them on the computer itself (since if an over- or under voltage is happening, either the system will crash or it's happening far too fast for it to getting logged).
• as to the above mentioned "look into the event-log", i had found several possible culprits over the years, some where faulty hardware like memory or the hdd/ssd the game was running on but also the game itself, or more specific the engine sending out 'iligal opcodes' occasionally which the GPU might or might not handle well and thus crashes the driver - if that is the case, the event log will mention such iligal opcode 'accident' in name... ofc, those are the in-deep-bug the devs should fix, but as someone who works with computerhardware daily, i can say that those problems are very tricky to pin down if you don't have the exact same hard AND software configuration as the one who get the errors - and even then it might not be possible due to different 'ages' of the hardware or degradations of the software environment. in the end, usually devs ignore those freak-accidents since they would waste tons of time and workforce to iron them out - in short, everything that they can't recreate on their test-rigs will be ignores (you usually see such commends from devs saying they can't recreate this bug or behaviour)... in such cases you can only help yourself by 'changing' your own hard- and software environment by replacing hardware and/or setting on a new, fresh and clean system... and... test again, hoping for the best ^^)

you might also try running the game not in fullscreen mode but in borderless mode (not windowed mode, mind you) - the reason might be that windows handels those modes differently and seemingly is better with the borderless mode (not only in warframe). ofc, old games can't run this way and some even crashes when getting out of fullscreen if you alt-tab out of them... luckily, warframe isn't such a game. oh, but better make sure you run the same resolution in game as you do in 'native' windows otherwise you might get some 'strange' effects.

I checked event viewer for the crash and it says this 

Faulting application name: Warframe.x64.exe, version: 2020.8.13.14, time stamp: 0x5f35857c
Faulting module name: RzChromaSDK64.dll_unloaded, version: 3.4.3.52, time stamp: 0x5dce193b
Exception code: 0xc0000005
Fault offset: 0x00000000000013e4
Faulting process ID: 0x3968
Faulting application start time: 0x01d678a76ce71300
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Warframe\Warframe.x64.exe
Faulting module path: RzChromaSDK64.dll
 

Does this mean chromasdk is the issue? if so i uninstalled all of and can't find it on my pc anywhere?

[Isaac_Watson]

boys we fixed it, i just sat and waited an hour for my computer to scan any file name with RzChromaSDK64 in the name and admin deleted it and it works now, no clue why it didn't tell me the location of the file name just searching for it but whatever, ty for all the help!

[fr4gb4ll]

15 hours ago, krc473 said:

People who claim their specs are fine but don't post them usually have low specs.

first and all, that's a bias out of the book... more often i found people just don't know that posting their specs will help everyone to help them with their problem - usually because they can use their rig but have no technical knowleged about computer whatsoever beyond that, and they shouldn't need to either...

in any case by now he did post more infos, so lets see about it...

22 minutes ago, Isaac_Watson said:

Processor: Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (8 CPUs), ~3.6GHz

RAM: 16GB

that's fine right?

cpu and ram is all dandy, but even more important is what your graphic hardware looks like: especially if you use any onboard graphic (notebooks for example) it's important to know that the usual intel graphic chips are very, very bad for most 3d-games - they can run but crashes, bad fps and other annoying issues are practically guaranteed. when playing on a notebook with a decent nvidia or amd graphic chip (or even a full card - yes, this also is possible with notebooks) it's importants to know that most of the times the available ram is shared between the graphic and the rest of the system - 16gb sound good though in any case and also sound more like a 'normal' desktop/tower pc than a notebook for they usually only come with 16gb  when they are designed for gaming too and not only for working on them.

25 minutes ago, Isaac_Watson said:

RzChromaSDK64.dll

ok... this little bugger is known for creating trouble with games, letting them crash just like you experienced. it also is known to be hard getting out of the system.

start with trying just to deactivate it and if that won't help deinstall or maybe better doing a clean driver inatallation without this 'feature' - not sure if the option is there since i don't use the razer. if it runs as service, you can deactivate it either via console or powershell, or use microsofts sysinternals "autoruns" program to do this - the gui version of it ( https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns ) autorunsc is the console version of it, so use the other one.

ofc, it might also be just because of the version of it, so a newer or an older version might also fix this issue.

[fr4gb4ll]

13 minutes ago, Isaac_Watson said:

boys we fixed it, i just sat and waited an hour for my computer to scan any file name with RzChromaSDK64 in the name and admin deleted it and it works now, no clue why it didn't tell me the location of the file name just searching for it but whatever, ty for all the help!

oh great - gj

[VENOM-BG]

I dont have this file RzChromaSDK64 but the game keeps freezing on me and i`m going crazy