Having Problem With My Computer Build Loading The Game Engine
#1
Posted 24 June 2017 - 07:02 AM
I am having a problem loading the game engine, windows decides the crash and exit the game everytime.
I can get into the menu part of the game after logging in, I can also start the process of starting a game like in quick match selecting game type as well as map, it gets to the loading screen, and crashes after that, the game crashes 100% of the time at this point. I have a support ticket but every suggestion has come up dry.
Please Help
#2
Posted 24 June 2017 - 07:19 AM
Uninstalling and re installing the game, verifying the game files through steam, uninstalling using ddu and reinstalling the gtx1050 drivers and doing a clean install with it, shutting off all of the backgroud apps, shutting off windows defender, shutting off all of windows invasive apps. Also here is my computer specs
[color=#ACB2B8]CPU: Intel core i5-7400[/color]
[color=#ACB2B8]RAM: 8 gigs ddr4[/color]
[color=#ACB2B8]Video card: Nvidia GeForce GTX 1050[/color]
[color=#ACB2B8]OS: win10 home 32bits[/color]
#3
Posted 24 June 2017 - 08:43 AM
About the only thing I can sugest to get MWO working is try using the MWO Portal from this site if it is not working with Steam.
sorry.
#4
Posted 24 June 2017 - 09:06 AM
Rogue Jedi, on 24 June 2017 - 08:43 AM, said:
About the only thing I can sugest to get MWO working is try using the MWO Portal from this site if it is not working with Steam.
sorry.
okay i will try this and report back
#5
Posted 24 June 2017 - 01:50 PM
#6
Posted 24 June 2017 - 03:33 PM
#7
Posted 25 June 2017 - 12:57 AM
#8
Posted 25 June 2017 - 01:20 AM
mailin, on 25 June 2017 - 12:57 AM, said:
as he has reinstalled Windows since then I suspect it has been turned back on.
Windows Defender can stop stuff from working, so disableing it can be useful for troubleshooting, but as you say it is also a Windows 10 PCs main inbuilt line of defense so it should idealy be on if you are connected to the internet and have no other protection on the computer
#9
Posted 25 June 2017 - 10:05 AM
In your future computer buying endeavors, if it says "32 bits", say "No thanks." Never buy a 32 bit system. We're not in the 90s anymore.
#10
Posted 25 June 2017 - 01:51 PM
I think the problem was a bit odd, since you can execute the 32 bit client on 64 OS just fine, even in faction warfare it doens't use more memory than what it could.
Rogue Jedi, on 24 June 2017 - 08:43 AM, said:
This is becoming a moot point but no, system RAM and VRAM are not adressed as whole. Therefore the whole VRAM does not eat up the address space of 4 GB allowed by 32 bit system. Some of the memory space is reserved for things like graphics cards, but not whole whole of the VRAM.
Edited by Teer Kerensky, 25 June 2017 - 02:55 PM.
#11
Posted 25 June 2017 - 02:55 PM
Teer Kerensky, on 25 June 2017 - 01:51 PM, said:
I think it is most likely something along the lines of him having 2GB+ of RAM on the GPU, leaving less than 2GB of system RAM for Windows and MWO to share.
#12
Posted 25 June 2017 - 03:04 PM
So if you had, say, 16 gigs of RAM, a program could only use 4 gigs before it crashes, while I could still use all 16 gigs of ram in many applications.
64 bit systems allow you to run 5, 8, even 12 gigabyte RAM programs without an issue provided you have the RAM for it.
MWO runs between 1.5 and 3 gigabytes of RAM usually. It is exceptionally high on CPU use, though.
Edited by Koniving, 25 June 2017 - 03:07 PM.
#13
Posted 25 June 2017 - 03:40 PM
Koniving, on 25 June 2017 - 03:04 PM, said:
MWO runs between 1.5 and 3 gigabytes of RAM usually. It is exceptionally high on CPU use, though.
By default the limit per executable is actually 2 GB, on 32 bit Windows. Programs which use multiple executables, can use, combined, more that than.
On 64 bit system the default might be 4 GB, per 32 bit program. Im not sure, it's likely more anyway than on 32 bit Windows.
There is a fairly unused option to extend the limit to 3 GB. I used it on my 4 GB WinXP system as it allowed Firefox to work better. It's downside was whenever Firefox used up nearly all of the 3 GB it could, instead of just crashing, it crashed the whole system. It was still slighly better.
https://msdn.microso...y/ff556232.aspx
#14
Posted 28 June 2017 - 08:32 AM
#15
Posted 28 June 2017 - 09:35 AM
Torezu, on 28 June 2017 - 08:32 AM, said:
Shytallica already has upgraded to 64 bit.
It was mentioned it in the threads 5th post, made 4 days ago where he said switching to 64 bit had fixed it and thanked me for the information about 64 bit.
#16
Posted 29 June 2017 - 02:39 AM
Torezu, on 28 June 2017 - 08:32 AM, said:
I guess the OP received one of those "upgrade to Win10" offers on an older machine with 32-bit Win7/8 and just used that key when assembling a new box. I had one of those too, and the upgrade would only allow me to get the 32-bit version.
#17
Posted 29 June 2017 - 03:05 AM
#18
Posted 30 June 2017 - 07:16 AM
3 user(s) are reading this topic
0 members, 3 guests, 0 anonymous users