j.wienenb16_ESO wrote: »I've noticed that ESO is starting at 2gb and slowing moving up to 3.55gb where it eventually crashes. With 32bit only supporting up to 3.5gb might this be the problem that's causing the crashes?
Wily_Wizard wrote: »Do you have Windows 10 32 bit, with 4GB RAM?
Wily_Wizard wrote: »Do you have Windows 10 32 bit, with 4GB RAM?
marten_philip wrote: »Wily_Wizard wrote: »Do you have Windows 10 32 bit, with 4GB RAM?
I actually do run the game on a 32 bit with 3gb(4gb total but 32 doesn't support 4gb or higher)
And the game crashes within mere seconds when I'm trying to play, I just did a repair hopefully that'll do the trick.
Wily_Wizard wrote: »Here is a WEBPAGE that shows the limitations of both kernel mode and user mode in x86 and 64bit windows...and here is a WEBPAGE that explains the difference in kernelmode and usermode.
Remember, 32 bit ESO.exe runs in user mode space, which is limited to 2GB on a 32 bit OS, (and 4GB on a 64bit OS, ONLY if the IMAGE_FILE_LARGE_ADDRESS_AWARE was set during the compile process). I have no idea if ESO was compiled with the IMAGE_FILE_LARGE_ADDRESS_AWARE set, ZENI would have to chime in on that. Here's a quick EXPLANATION on that.
@marten_philip , Your ESO is definitely limited to 2GB of usermode space. You can easily change that by setting the /3GB Switch in your windows bootup. Normally your system runs on 2GB usermode + 2GB kernelmode memory, if you set the /3GB switch to default, your system will run on 3GB usermode(which helps ESO) + 1GB kernelmode(which could potentially cause problems). If you have a gaming video card, chances are 512MB of system RAM are reserved for that driver in kernelmode, so you might want to alter the /3GB switch to something like 2.5GB usermode + 1.5GB kernelmode. That latter option will give the game some more space to run, and insure any kernelmode drivers have adequate memory to run stable. You can always experiment with larger or smaller numbers until you find a stable point. Here's a WEBPAGE that explains it all. Here is a non-windows WEBPAGE with easy directions to set the /3GB switch, and possibly a better explanation.
@j.wienenb16_ESO , It seems you are in the same boat as me, since your system can already address larger usermode memory space. Interesting find on the creeping memory up to 3.55GB. I haven't looked at that lately on mine, perhaps I need to revisit that myself. That might explain the sudden resurgence of crashing I have too. I'll post back with my findings.
On a side note, you can set the windows task manager to display kernelmode + usermode CPU process utilization simultaneously, instead of only usermode. It could potentially be helpful in identifying what is using most of your resources.
Here's an EXPLANATION to set that change.
.
marten_philip wrote: »Wily_Wizard wrote: »Here is a WEBPAGE that shows the limitations of both kernel mode and user mode in x86 and 64bit windows...and here is a WEBPAGE that explains the difference in kernelmode and usermode.
Remember, 32 bit ESO.exe runs in user mode space, which is limited to 2GB on a 32 bit OS, (and 4GB on a 64bit OS, ONLY if the IMAGE_FILE_LARGE_ADDRESS_AWARE was set during the compile process). I have no idea if ESO was compiled with the IMAGE_FILE_LARGE_ADDRESS_AWARE set, ZENI would have to chime in on that. Here's a quick EXPLANATION on that.
@marten_philip , Your ESO is definitely limited to 2GB of usermode space. You can easily change that by setting the /3GB Switch in your windows bootup. Normally your system runs on 2GB usermode + 2GB kernelmode memory, if you set the /3GB switch to default, your system will run on 3GB usermode(which helps ESO) + 1GB kernelmode(which could potentially cause problems). If you have a gaming video card, chances are 512MB of system RAM are reserved for that driver in kernelmode, so you might want to alter the /3GB switch to something like 2.5GB usermode + 1.5GB kernelmode. That latter option will give the game some more space to run, and insure any kernelmode drivers have adequate memory to run stable. You can always experiment with larger or smaller numbers until you find a stable point. Here's a WEBPAGE that explains it all. Here is a non-windows WEBPAGE with easy directions to set the /3GB switch, and possibly a better explanation.
@j.wienenb16_ESO , It seems you are in the same boat as me, since your system can already address larger usermode memory space. Interesting find on the creeping memory up to 3.55GB. I haven't looked at that lately on mine, perhaps I need to revisit that myself. That might explain the sudden resurgence of crashing I have too. I'll post back with my findings.
On a side note, you can set the windows task manager to display kernelmode + usermode CPU process utilization simultaneously, instead of only usermode. It could potentially be helpful in identifying what is using most of your resources.
Here's an EXPLANATION to set that change.
.
Unfortunately it had no effect
Game still crashes within a few seconds
The weird thing is my PC is dual boot now, Win7/Win10, and generally Win10 allows me to play ESO longer, even with both OS's on the same Nvidia driver version.j.wienenb16_ESO wrote: »@Wily_Wizard, Yea I couldn't find the problem until I remembered this game has only a 32bit version so I decided to look at the RAM usage. Because I really couldn't find anything else. Strange thing is tho, this is the same setup I used to play ESO with. And never had any problems before. The only thing that's different is a bunch of patches in ESO + windows 10.
j.wienenb16_ESO wrote: »marten_philip wrote: »Wily_Wizard wrote: »Here is a WEBPAGE that shows the limitations of both kernel mode and user mode in x86 and 64bit windows...and here is a WEBPAGE that explains the difference in kernelmode and usermode.
Remember, 32 bit ESO.exe runs in user mode space, which is limited to 2GB on a 32 bit OS, (and 4GB on a 64bit OS, ONLY if the IMAGE_FILE_LARGE_ADDRESS_AWARE was set during the compile process). I have no idea if ESO was compiled with the IMAGE_FILE_LARGE_ADDRESS_AWARE set, ZENI would have to chime in on that. Here's a quick EXPLANATION on that.
@marten_philip , Your ESO is definitely limited to 2GB of usermode space. You can easily change that by setting the /3GB Switch in your windows bootup. Normally your system runs on 2GB usermode + 2GB kernelmode memory, if you set the /3GB switch to default, your system will run on 3GB usermode(which helps ESO) + 1GB kernelmode(which could potentially cause problems). If you have a gaming video card, chances are 512MB of system RAM are reserved for that driver in kernelmode, so you might want to alter the /3GB switch to something like 2.5GB usermode + 1.5GB kernelmode. That latter option will give the game some more space to run, and insure any kernelmode drivers have adequate memory to run stable. You can always experiment with larger or smaller numbers until you find a stable point. Here's a WEBPAGE that explains it all. Here is a non-windows WEBPAGE with easy directions to set the /3GB switch, and possibly a better explanation.
@j.wienenb16_ESO , It seems you are in the same boat as me, since your system can already address larger usermode memory space. Interesting find on the creeping memory up to 3.55GB. I haven't looked at that lately on mine, perhaps I need to revisit that myself. That might explain the sudden resurgence of crashing I have too. I'll post back with my findings.
On a side note, you can set the windows task manager to display kernelmode + usermode CPU process utilization simultaneously, instead of only usermode. It could potentially be helpful in identifying what is using most of your resources.
Here's an EXPLANATION to set that change.
.
Unfortunately it had no effect
Game still crashes within a few seconds
Have you tried the following:
- Run the launcher as admin
- Set the compatibility mode to win 7/8
ZOS_AlexTardif wrote: »This is likely because of a particle system leak, which tends to show its ugly head in more intense PVP scenarios. The system itself has been completely rewritten and thoroughly vetted for these kinds of issues. It is going out with the Thieves Guild patch, in addition to the new 64-bit client.
Wily_Wizard wrote: »@marten_philip , mine is crashing in less than 1 second after loading old characters. Win 764bit, 16GB RAM, latest drivers.
bchulettub17_ESO wrote: »I know it's a little while before it happens but I'm hoping the 64 bit client helps a lot with these issues. From what I've read there is an existing particle effects memory leak, so maybe in the mean time you could adjust the maximum particle systems and see if that reflects with memory usage.ZOS_AlexTardif wrote: »This is likely because of a particle system leak, which tends to show its ugly head in more intense PVP scenarios. The system itself has been completely rewritten and thoroughly vetted for these kinds of issues. It is going out with the Thieves Guild patch, in addition to the new 64-bit client.
Not saying it's the cause of what you're running into but it may help messing with those values.
Wily_Wizard wrote: »The weird thing is my PC is dual boot now, Win7/Win10, and generally Win10 allows me to play ESO longer, even with both OS's on the same Nvidia driver version.j.wienenb16_ESO wrote: »@Wily_Wizard, Yea I couldn't find the problem until I remembered this game has only a 32bit version so I decided to look at the RAM usage. Because I really couldn't find anything else. Strange thing is tho, this is the same setup I used to play ESO with. And never had any problems before. The only thing that's different is a bunch of patches in ESO + windows 10.
My PC used to run ESO fine too, but its been a love/hate affair the whole time. It started out crashing a lot, then after a few patches, it was running smooth for months, then hit a bad patch and it started getting somewhat unstable, then hit another bad patch, and now its unusable.
BTW, I checked my memory usage with Win 7 64bit, 16GB RAM...
Once fully in-game ESO was using just over 2GB, and my total RAM usage was at 4.4GB. The ESO never went higher than 2.1GB, but it still crashed while I was standing still in a town and watching it.
I checked it several times and noticed something new, I could usually get ESO to crash by clicking on or closing the task manager window, even though it was on another monitor and outside of the fullscreen-windowed game. I tried running mine in both fullscreen, and fullscreen-windowed, and it made zero difference in the crashes.
.
j.wienenb16_ESO wrote: »@Wily_Wizard, any progress/update in your situation?
j.wienenb16_ESO wrote: »Hi,
I recently had the urge to play ESO again. So yesterday I downloaded/installed ESO (On a freshly installed win10), at first it kept crashing in character select
which I fixed by tweaking the usersettings file (d3d11 to d3d9). That solved atleast the crashing in character select.. But now the game crashes everytime around 5min ingame.. I've noticed that ESO is starting at 2gb and slowing moving up to 3.55gb where it eventually crashes. With 32bit only supporting up to 3.5gb might this be the problem that's causing the crashes?
I have the following:
- Clean install ESO
- Clean install win10
- Updated drivers
- Updated directX
KhajitFurTrader wrote: »Are you using Windows Insider builds? There have been reports to the effect that the game (others as well) immediately crashes after launching on "Build 11102.rs1_release.160113-1800".
j.wienenb16_ESO wrote: »Hi,
I recently had the urge to play ESO again. So yesterday I downloaded/installed ESO (On a freshly installed win10), at first it kept crashing in character select
which I fixed by tweaking the usersettings file (d3d11 to d3d9). That solved atleast the crashing in character select.. But now the game crashes everytime around 5min ingame.. I've noticed that ESO is starting at 2gb and slowing moving up to 3.55gb where it eventually crashes. With 32bit only supporting up to 3.5gb might this be the problem that's causing the crashes?
I have the following:
- Clean install ESO
- Clean install win10
- Updated drivers
- Updated directX
What is your Gfx card / drivers version,
I am using Nvidia with the lastest version and made me crash until i reverted back to 350.12
Pretty annoying if you ask me.