Since new patch 1.6.5, constant crash reporter.

phairdon

After the latest patch (last night), tried running the game twice, received a fatal crash both times. Currently running repair, hoping this might fix whatever is causing the crash.
ESO is installed on windows 7 & windows 8.1. Now experienced the same fatal error on both installs.

Uberkull

Bad_LeroyBrown wrote: »

The crash to Crash Reporter without error code is still present with the latest update to 1.6 today if using the recommended "Quality" to the highest with Geoforce Experience, once I throttled it down in custom settings to half way between quality and performance works fine again.

At least Greenshade isn't broken anymore with this update.

In the actual Settings > Video section in ESO, what are the selections once you made the change?

BTW 1.6.6 did nothing for me.

Bad_LeroyBrown

uberkull wrote: »

Bad_LeroyBrown wrote: »

The crash to Crash Reporter without error code is still present with the latest update to 1.6 today if using the recommended "Quality" to the highest with Geoforce Experience, once I throttled it down in custom settings to half way between quality and performance works fine again.

At least Greenshade isn't broken anymore with this update.

In the actual Settings > Video section in ESO, what are the selections once you made the change?

BTW 1.6.6 did nothing for me.

SET MouseRawInput "1"
SET MouseSensitivityFirstPerson "0.50000000"
SET MouseSensitivityThirdPerson "1.00000000"
SET MouseSmoothing "0"
SET InvertMouseWheel "1"
SET InvertMouseY "1"
SET InvertMouseX "1"
SET MAGELIGHT_LIGHTS_VISIBLE "1"
SET PFX_SUPPRESS_DISTANCE_v2 "50.00000000"
SET PFX_GLOBAL_MAXIMUM "1024"
SET MULTI_GPU_CHECK "1"
SET CachedRLREnabled "0"
SET CachedReflectionResolution "0"
SET CachedShadowFiltering "6"
SET ScreenshotFormat.2 "PNG"
SET PregameGammaCheckEnabled "0"
SET HardwareCheckEnabled.3 "0"
SET SUB_SAMPLING "2"
SET REFLECTION_QUALITY_v3 "0"
SET PARTICLE_DENSITY "2"
SET HIGH_RESOLUTION_SHADOWS "1"
SET SHADOWS "3"
SET GAMMA_ADJUSTMENT "113"
SET VIEW_DISTANCE "1.00000000"
SET GPUSmoothingFrames "10"
SET MIP_LOAD_SKIP_LEVELS "0"
SET RAIN_WETNESS "1"
SET LENS_FLARE "1"
SET GOD_RAYS_v2 "1"
SET ANTI_ALIASING_v2 "1"
SET AMBIENT_OCCLUSION "0"
SET COLOR_GRADING_v1 "0"
SET BLOOM "1"
SET DEPTH_OF_FIELD "1"
SET TONE_MAPPING "1"
SET COLOR_CORRECTION "1"
SET SOFT_ALPHA "1"
SET DISTORTION "1"
SET CHARACTER_LIGHTING "1"
SET DIFFUSE_2_MAPS "1"
SET DETAIL_MAPS "1"
SET NORMAL_MAPS "1"
SET SPECULAR_MAPS "1"
SET CLUTTER_2D "1"
SET SIMPLE_SHADERS "0"
SET WATER_FOAM "1"
SET VSYNC_INTERVAL "1"
SET VSYNC "0"
SET MAX_ANISOTROPY "2"
SET PreferMaximizedWindow "0"
SET PreferExclusiveFullscreen "0"
SET FULLSCREEN_v5 "1"
SET FullscreenHeight "1080"
SET FullscreenWidth "1920"
SET WindowedHeight "768"
SET WindowedWidth "1024"
SET FOVChangesAllowed "1"
SET AgreedToPEGI "0"
SET VoiceChatAutoJoinChannels.2 "0"
SET VoiceChatEnabled.3 "1"
SET LuaMemoryLimitMB "64"
SET GamepadSensitivityFirstPerson.2 "0.72000003"
SET GamepadSensitivityThirdPerson.2 "0.85000002"
SET GamepadInvertX "0"
SET GamepadInvertY "0"
SET GamepadVibrationEnabled "1"
SET SOUND_ENABLED "1"
SET FOOTSTEPS_VOLUME "50.00000000"
SET FOOTSTEPS_ENABLED "1"
SET SPEAKER_SETUP "0"
SET BACKGROUND_AUDIO "0"
SET VO_VOLUME "70.00000000"
SET VO_ENABLED "1"
SET UI_VOLUME "70.00000000"
SET UI_ENABLED "1"
SET AMBIENT_VOLUME "70.00000000"
SET AMBIENT_ENABLED "1"
SET SFX_VOLUME "70.00000000"
SET SFX_ENABLED "1"
SET MUSIC_VOLUME "70.00000000"
SET MUSIC_ENABLED "1"
SET AUDIO_VOLUME "100.00000000"
SET AUDIO_ENABLED "1"
SET TooltipFilter "-1"
SET TooltipNumOptions "2"
SET Language.2 "en"
SET GraphicsDriver.7 "D3D11"
SET PatchDataPath "game:/GameData/"
SET CacheDataPath "machine:/Cache/"
SET ViewedAddOnEULAVersion "-1"
SET AcceptedAddOnEULAVersion "-1"
SET AcceptedEULAVersion "3"
SET DirectionalDamageIndictorVisibleInThirdPerson "0"
SET CameraFramingTransitionEnabled "1"
SET SkipPregameVideos "0"
SET HasPlayedPregameVideo "1"
SET RangedKillCamera "0"
SET PlayerKillCamera "1"
SET LastMonsterKillCamera "1"

Been solid since I throttled my GTX 760 down, way down, from the default Geoforce Experience Quality settings; settings which looked great and worked up until 1.6.5 patch and 1.6.6

Uberkull

Bad_LeroyBrown wrote: »

Been solid since I throttled my GTX 760 down, way down, from the default Geoforce Experience Quality settings; settings which looked great and worked up until 1.6.5 patch and 1.6.6

Interesting, you are missing some entries that I always modify to correct stutter and previous crashes.

Threading and CPU -

SET RequestedNumJobThreads "-1"
SET RequestedNumWorkerThreads "-1"

The default is -1 for both. Setting it as follows does:
0 - One thread
1 - Two Threads
(Support said some users have set it as high as 15 that owned a 8 core hyperthread CPU, I never tried past 1)

When I see stutter on a new OS install, I try to adjust this setting first. I'm testing it for MY crash on 1 because I've exhausted all other attempts.

If you want your better quality graphics back, you could MOVE your usersettings file to a backup directory and make sure the current one is deleted. That's what the move should do.

Then delete the ShaderCache.cooked file located in the same directory as usersettings.

Then start the game, it will recreate the usersettings file and 'should' add the thread entries above. It will also recook the shaderchache, this takes some time during the loading screen.

Once your in town or in game, at that point you can try setting things as you like in the Video settings, then exit. Then open the new usersettings file and adjust the two thread settings above as you want. Maybe 1 for both first, just match them always.

Play for awhile...or go to a place you always crashed and test. If it still crashes try another number...0 or 1 for the thread setting.

If it still doesn't resolve your crash, just exit the game, overwrite your new usersettings file with your backup version and delete the shadercache file again. Let it cook a new shadercahce file again based on your current usersettings file.

Myril13peb18_ESO

News. Good news (at least for me:)

Today i was installed new SSD Disc, install fresh Windows 7 64 bit and game running splendidly. I've installed NVidia Expirience too. High ultra settings.

First i'm trying about 2 hours leveling, no crashes. I then installed the Minion and addons. Overall i played about 5 hours and no crashes or other problems

polarbehr76

Myril13peb18_ESO wrote: »

News. Good news (at least for me:)

Today i was installed new SSD Disc, install fresh Windows 7 64 bit and game running splendidly. I've installed NVidia Expirience too. High ultra settings.

First i'm trying about 2 hours leveling, no crashes. I then installed the Minion and addons. Overall i played about 5 hours and no crashes or other problems

i just rebuilt my pc 2 weeks before i bought ESO, reinstalling is not the answer here

yogarogue

I have been having this issue since the latest update.

I first received the crash as an error report, but now when I crash the game freezes and my screen turns black and I am forced to reboot. THe last time I did this my driver actually crashed and i had to uninstall and reinstall it.

My crashes arent happening as frequently as others, but I still hope this issue gets fixed pronto..

yogarogue

I should ask.

I first received the crash as an error report. Now the screen freezes and turns black?? IS there any reason for this?? IS it the same error??

HiP

uberkull wrote: »

HiP wrote: »

Chill out man !
first, i did say what type of crash, earlier in the thread, and in the posts just above, if you care to read what others say, you would know... and i do get the crash reporter when my game crashes like 99% of crashes that happen in the game so calling your type of crash "crash reporter" is nonsense... narrowing down when or what triggers your crashes is a requirement.
:

Reviewed all your posts here. You never mentioned Crash Reporter. And many crashes reported are different then gracefully crashing with the EOS Crash Reporter UI. Screen freezes, bsod, hung process, crash to desktop. Those all have been reported and are different than a caught exception reported in Crash Reporter.

So maybe you should read before you post. I'm trying to diagnose a specific type of crash.

maybe you should learn to read before you answer...
i said that i mentionned in my earlier posts what type of crash i had, because you accused me of not mentionning that.

my solution did not work for you, that's too bad, but it worked for others.

so if you want to play it high and mighty, insulting and rejecting people that are only trying to help, you should just do it all alone, and not on a forum.
you seem happy to revel in your frustation, in whatever you're trying to accomplish which is clearly not diagnosing or fixing anything at all.

HiP

yogarogue wrote: »

I should ask.

I first received the crash as an error report. Now the screen freezes and turns black?? IS there any reason for this?? IS it the same error??

usually if you have to reboot because you cannot do anything, not even alt tab, move your mouse or ctrl+alt+suppr, it means it might be a hardware problem or a very bad driver.
you might want to change your driver version, and check if nothing overheats Inside your computer.

Uberkull

1.6.6 had no change for me

HiP wrote: »

uberkull wrote: »

HiP wrote: »

Chill out man !
first, i did say what type of crash, earlier in the thread, and in the posts just above, if you care to read what others say, you would know... and i do get the crash reporter when my game crashes like 99% of crashes that happen in the game so calling your type of crash "crash reporter" is nonsense... narrowing down when or what triggers your crashes is a requirement.
:

Reviewed all your posts here. You never mentioned Crash Reporter. And many crashes reported are different then gracefully crashing with the EOS Crash Reporter UI. Screen freezes, bsod, hung process, crash to desktop. Those all have been reported and are different than a caught exception reported in Crash Reporter.

So maybe you should read before you post. I'm trying to diagnose a specific type of crash.

maybe you should learn to read before you answer...
i said that i mentionned in my earlier posts what type of crash i had, because you accused me of not mentionning that.

my solution did not work for you, that's too bad, but it worked for others.

so if you want to play it high and mighty, insulting and rejecting people that are only trying to help, you should just do it all alone, and not on a forum.
you seem happy to revel in your frustation, in whatever you're trying to accomplish which is clearly not diagnosing or fixing anything at all.

I'm not insulting you in any way. You honestly just can't read. In what earlier posts did you mention the type of crash? No posts on this thread.

And I'm the one actually posting potential solutions that I have tried, with detailed instructions. That's far more than you've done.

You must be reading a different forum. Don't add fictitious drama here.

Uberkull

yogarogue wrote: »

I should ask.

I first received the crash as an error report. Now the screen freezes and turns black?? IS there any reason for this?? IS it the same error??

You can try HWMonitor to check temps in your PC. http://www.cpuid.com/softwares/hwmonitor.html

ZOS_TristanK

Hi, folks. Crashing is a fairly complex issue and can happen to different rigs for different reasons. We highly recommend getting in touch with our Technical Support Team and sending along your game consultant file so that they can take a closer look at what might be happening.

One thing to note is that if you downloaded a driver update just prior to Update 6's launch, it may be causing conflicts. If this is the case, you may need to roll back your video drivers. If you aren't sure, please check in with Support. They'll be able to use the game consultant file to help you figure out if that's the issue.

We know crashing is no fun and we appreciate your patience!

Gyudan

ZOS_TristanK wrote: »

Hi, folks. Crashing is a fairly complex issue and can happen to different rigs for different reasons. We highly recommend getting in touch with our Technical Support Team and sending along your game consultant file so that they can take a closer look at what might be happening.

One thing to note is that if you downloaded a driver update just prior to Update 6's launch, it may be causing conflicts. If this is the case, you may need to roll back your video drivers. If you aren't sure, please check in with Support. They'll be able to use the game consultant file to help you figure out if that's the issue.

We know crashing is no fun and we appreciate your patience!

It would be nice if we had access to a list of "known issues" updated as CS tickets are submitted.
For example:
- Player A sends a ticket because a sorcerer activating Overload and blocking makes staves reappear in players' hands in a weird position.
- CS rep checks the bug report and enters the following : "Visual bug with Overload when blocking"
- Using the /help window now displays a list of bugs to be confirmed. Players can select and aknowledge them as valid.
- "Visual bug with overload when blocking" now appears in the list of known issues, visible ingame from the CS panel and a specific page on the website.
- A few weeks later the issue is fixed by a patch and removed from the list.

This would reduce the amount of identical CS tickets received again and again and help spot real issues.

david.kinnaneb14_ESO

ZOS_TristanK wrote: »

Hi, folks. Crashing is a fairly complex issue and can happen to different rigs for different reasons. We highly recommend getting in touch with our Technical Support Team and sending along your game consultant file so that they can take a closer look at what might be happening.

One thing to note is that if you downloaded a driver update just prior to Update 6's launch, it may be causing conflicts. If this is the case, you may need to roll back your video drivers. If you aren't sure, please check in with Support. They'll be able to use the game consultant file to help you figure out if that's the issue.

We know crashing is no fun and we appreciate your patience!

Yeahhhhh... you guys also said during one of your recent ESO live things that getting stuck at a load screen is a result of, and i'm paraphrasing here, "having a crappy PC". While I do agree there's an under performing system in play, it's not mine.

One of the first steps in troubleshooting a problem is identifying what changed. I too experience game locks and crashes and the ONLY thing that has changed on my PC is 1.6 went live. Other than ESO, everything else is working with out incident on my machine.

Uberkull

ZOS_TristanK wrote: »

Hi, folks. Crashing is a fairly complex issue and can happen to different rigs for different reasons. We highly recommend getting in touch with our Technical Support Team and sending along your game consultant file so that they can take a closer look at what might be happening.

One thing to note is that if you downloaded a driver update just prior to Update 6's launch, it may be causing conflicts. If this is the case, you may need to roll back your video drivers. If you aren't sure, please check in with Support. They'll be able to use the game consultant file to help you figure out if that's the issue.

We know crashing is no fun and we appreciate your patience!

I hope you were generalizing your statement to others in the thread because I created this thread based on a ticket I already have open. Really it's just as easy for you to mention some things to try based on the tickets or issues your getting. I think everyone on this thread at one point has mentioned they've reinstalled drivers or tried different versions.

As far as my latest response from my tech support ticket, it seems there's multiple tickets being submitted for crash issues on 1.6 and they revolve around 32bit systems and directX. I was told:

We're going to raise this to the Dev Team for investigation now that we've linked enough cases, so that should be investigated properly. In the meantime, you can open your UserSettings and change the following setting:

SET GraphicsDriver.7 "D3D11"
to
SET GraphicsDriver.7 "OPENGL"

This should help alleviate the crashing while we get it looked into, though it will lower the graphics quality.

I had to LOL at the results of changing this setting. At the logon screen there was no text anywhere, no menu on the left, not field labels for username and password, no submit/login button. Just the two text boxes. And I couldn't see what was typed into the username field. I exited and changed it back to D3D11.

melodeath

ZOS_TristanK wrote: »

Hi, folks. Crashing is a fairly complex issue and can happen to different rigs for different reasons. We highly recommend getting in touch with our Technical Support Team and sending along your game consultant file so that they can take a closer look at what might be happening.

One thing to note is that if you downloaded a driver update just prior to Update 6's launch, it may be causing conflicts. If this is the case, you may need to roll back your video drivers. If you aren't sure, please check in with Support. They'll be able to use the game consultant file to help you figure out if that's the issue.

We know crashing is no fun and we appreciate your patience!

no offence but eso is not the only video game on this planet.. if you keep telling everyone it is our pc including the bug fixing guy that had a little time to talk on one of the eso live streams than i wonder why my pc has no problem whatsoever with all the other games that are far more demanding than this game after every patch or after every driver update that i do.. if you go in-game and ask who is having issues than you will see no one who doesnt have an issue... so by eso logic everyone has a bad computer it seems...

Uberkull

melodeath wrote: »

no offence but eso is not the only video game on this planet.. if you keep telling everyone it is our pc including the bug fixing guy that had a little time to talk on one of the eso live streams than i wonder why my pc has no problem whatsoever with all the other games that are far more demanding than this game after every patch or after every driver update that i do.. if you go in-game and ask who is having issues than you will see no one who doesnt have an issue... so by eso logic everyone has a bad computer it seems...

How the hell they gonna get this on console? Err...you can't blame Xbox One or PS4 if the game crashes....lol. Last time I had a game crash on my Xbox One was never.

June will be fun.

Warraxx

uberkull wrote: »

Latest crash reporter - At dye station and clicked a dye color, went to apply it to boots....crash reporter.

Seriously, ZOS acknowledge that patch 1.6 has a problem and that you are working on it. Otherwise this thread will go on.

I bet there was an EP zerg nearby causing it...

The_Drexill

Having it since the latest patch too, always while teleporting.

Uberkull

The latest I head is they are looking at a potential memory issue and 32bit systems. Not sure that's the right spot to look since there are 64bit users crashing...I've exhausted all avenues of troubleshooting, I'm done.

It's the patch, that's my conclusion.

nickszalinskieb17_ESO

StrangerFull wrote: »

After patch game always crashes after loading screen if I try enter outlaws quarters in Belkarth. In other zones I don't try but think problem same. Even with all addons disabled crashes persists.

I had this problem with Daggerfall Outlaws Refuge on the PTR. Now I have the same problem with Alik'r Desert, making me unable to play because I cannot return to the leveling zone.

PS. The character is in the place where it was before teleportation after I re-log.

mrowmrif2

Just throwing this out there guys... i posted on another thread but cant seem to find it... if i do i'll post this there as well to help out those following it or having the same issues... i have been crashing since 1.6 as well, and i've tried so many things to troubleshoot... including talking to my ISP to test if i'm dropping packets while connected to my game to uninstalling and reinstalling ESO completely... yay 5-6 hour downloads. i crash consistently whenever i change characters, teleport using a waypoint, enter a building and talk to an NPC... things that require a change of perspective or a load seem to be causing dropped pings to megaserver and a disconnect of game. fast forward 3 week to today. i started using the addon "ESO_Launcher" which is a custom launcher from someone's thread posted on tamrielfoundry.com forum - the screenshots sold me of the enhanced graphics (plug Sorien's coding, sexy visuals man). but when i was using this launcher, i still experienced crashing like before... only this time, he has an embedded trace that lets you tell him what is causing the crash so he can help troubleshoot/fix if it is his addon. here is the result of 3 separate crashes:

[00420BD2] eso:
[00AAF6CB] eso:
[00AAFB66] eso:
[00AB0005] eso:
[00E40F02] eso:
[00DAEB57] eso:
[00D73D53] eso:
[00A94F0E] eso:
[007DA90E] eso:
[00A91BF0] eso:
[0042100C] eso:
[0044AD19] eso:
[0044B7A5] eso:
[00AA5F3D] eso:
[776EEE1C] kernel32: BaseThreadInitThunk
[775B37EB] ntdll: RtlInitializeExceptionChain
[775B37BE] ntdll: RtlInitializeExceptionChain
[775B37BE] ntdll: RtlInitializeExceptionChain

[01309983] eso:
[00D33DFC] eso:
[00D3924E] eso:
[00A4116C] eso:
[00A40E4A] eso:
[00A40F54] eso:
[00A6AD19] eso:
[00A6B7A5] eso:
[010C5F3D] eso:
[776EEE1C] kernel32: BaseThreadInitThunk
[775B37EB] ntdll: RtlInitializeExceptionChain
[775B37BE] ntdll: RtlInitializeExceptionChain
[775B37BE] ntdll: RtlInitializeExceptionChain

[01309983] eso:
[00D33DFC] eso:
[00EAA8AB] eso:
[00EAADC2] eso:
[010CCFFB] eso:
[776EEE1C] kernel32: BaseThreadInitThunk
[775B37EB] ntdll: RtlInitializeExceptionChain
[775B37BE] ntdll: RtlInitializeExceptionChain
[775B37BE] ntdll: RtlInitializeExceptionChain

The common theme here... "kernel32: BaseThreadInitThunk" almost for sure an OS kernel 32-bit problem not playing nice with ESO host. long story summarized: my Win7 64-bit OS install disc and serial are on their way. i will just pull the trigger and upgrade and expect it to work perfectly, just the way it has been working since beta.

Uberkull

Great find, but seriously I'm not investing anymore in something that worked in 1.5 and 1.6 broke it.

Utterly redicious that they released something that fails on 32 bit systems.

They now going to change their minimum required specs for the game because of 1.6? Awesome...say goodbye to a ton of customers starting tomorrow with the release. You think the threads for crashing are bad now, wait for later this week.

The history of ZOS addressing issues isn't stellar. I had thought this was a AAA game, but I was mistaken as when I did some research. They just don't have those type of resources to fully support this game.

melodeath

i dont have a 32 bit system tho

xeonotrix

Add me to the list of the CTD with a crash report screen out of nowhere. I was running along in my mount towards my destination quest when it happened. I just installed the game again tonight.

And since its our PC's this are my specs:

CPU Intel i5 2500k
Windows 8.1 64bit
2x 256 GB SSD (2 SSD's)
8 GB Ram
Nvidia Gforce 780 3GB
750 watt PSU corsair

I also run other games besides TESO so if they cannot fix it i just uninstall easy fix and no hassle.

HiP

The_Drexill wrote: »

Having it since the latest patch too, always while teleporting.

nickszalinskieb17_ESO wrote: »

StrangerFull wrote: »

After patch game always crashes after loading screen if I try enter outlaws quarters in Belkarth. In other zones I don't try but think problem same. Even with all addons disabled crashes persists.

I had this problem with Daggerfall Outlaws Refuge on the PTR. Now I have the same problem with Alik'r Desert, making me unable to play because I cannot return to the leveling zone.

PS. The character is in the place where it was before teleportation after I re-log.

@The_Drexill @nickszalinskieb17_ESO
it looks like you both had the same problem i had.
i posted the solution earlier in the thread. i hope it fixes it for you too.

Uberkull

It's much worse now with the release of TU. I'm assuming it's because of more people.

At this point, I can't play. Going to ask for sub credit as I still hold a carry over sub.

AureateRN

Today, March 18, increasingly frequent "black screen restarts" have been necessary even after I have taken all steps possible to make absolutely sure the issue is not on my end, including deleting addons (the two very simple ones I use through Curse), doing complete diagnostics on my custom pc and Win 8 Pro OS, which is always clean and maintained and used to browse gaming and political/news related sites ie, little risk of picking up viruses, though I have ample protections in place for that sort of thing as we have a Best Buy "geek" in the family. He helps me with my pc issues. We ran the game repair, for starters, and he moved on from there into geeky stuff even I do not fully understand, but to say he was thorough is a vast understatement.

Long story short, having done everything possible to rule out a problem on my end, with professional assistance, it is now fully logical to relate the stuttering and increasingly frequent black screen crashes to the newly implemented Justice System, since I did not have those issues in the past, ever.

Somehow the Justice System has bugged the game in a very serious way and the patches/fixes ZOS has thus far applied have not worked as of March 18. In fact the problem appears to be escalating, seriously, and not only in beginner zones, which of course are going to be flooded (or so ZOS hopes) with newbies and returnees trying out the new system.

Obviously, I fully expected some issues related to the addition of JS and1.6.-.---- in its entirety. I'm no MMORPG neophyte. Being a closed beta tester was fun, and being what some call a "paying beta tester" was also fun, and at worst cost me a few dollars a month, so I was never that fussed about it. Overall this game is magnificent and I have every hope it will continue to get better and better now that a lot more cash will be rolling in. It remains to be seen whether that will break down into people paying more than $15 per month once the initial rush of boxes sells, but if so I can only hope "some" of it will go into game improvements long needed, like some character rendering repairs female players especially (but NOT exclusively) have been awaiting with varying degrees of patience for almost a year now, but I digress.

That "black screen of death" is forcing me to manually shut down my pc every time it happens, which just today has been twice in less than an hour, both times when I was doing something directly related to the Justice System.

When these pc-wide black screens occur I cannot even get to any other screen on my pc; the glitch is that pervasive and far reaching. Continual manual turning off of the pc without proper shutdown of programs, even though I have trimmed down my running/startup programs to only those required to run the game properly and protect my pc, is certainly not a healthy situation.

This pc was custom built for me with a great deal of tender loving care by a family member at his own expense as a gift. It has been tweaked and tricked out to perform extremely well, which it HAS, until the Justice System was added. This is a shame too, because I really enjoy this addition to the game! My pc makes the beautifully rendered world of Tamriel truly come alive. It is a very valuable machine made even moreso by sentiment. It has no gaming value, however, if this Justice System issue makes ESO unplayable.

I hope ZOS takes these concerns seriously, as there is only so much their amazingly dedicated and always helpful customer service personnel can do.

AureateRN

uberkull wrote: »

I noticed that a lot of people who have the game crashes, have 32bit system. In week i will install new SSD and 64bit system. News ater this....

From whar I read and noticed is that ESO is coded to the 2gig ram ceiling for 32bit games, is a 32bit game, and uses.1 core, ignoring multicore cups.

You can have 8gig, 16gig but ESO won't use it. And not coded for 64bit.

Oh that's "brilliant".

How discouraging. I try to be a cup half full kind of person but...SRSLY???

Thank you for the information!