My PC should also be more than enough for this game but for some reason its what I have to do. In the end, its much of a such. I usually forget to do it, get a freeze, then do it. No more freezes. It works 100% of the time for me. Hope it does for your also.
Its worth noting that this did not happen to me until the second to last beta weekend.
there is currently an issue with Nvidia drivers, at random points it makes the screen go black, and looks like the vid card is resetting itself, however its not occurring with everyone, download and install the drivers from last OCT, last known set that doesn't have this occurring with some people.
327.23 I think is the driver set, its what Ive been running after I kept getting black screens in planetside 2, and Borderlands 2, 327.23 is stable in both games, was logged in to PS2 for 6 hours on Friday and it didn't miss a beat.
There is a Beta driver at the moment , have tested it, still getting black screen but the frequency was a lot less.
I got a feeling about this, but that would mean that the Launcher and Awesomeium.exe are taking top priority over the game, and if its happening still when I have launcher and awesomeium.exe down, it means there is other hidden process that are taking priority over my game... but shouldn't my 3.2g dual core processor be able to handle that, my single core on my laptop can.
My computer is set to have best preformace for Progarams and not background services so the priority must be messed up somehow if this is working for you.
I also have both task folders empty so no tasks are running at the time this happens either.
Yeah, the dual core should be enough for that. It might not be optimal but with the current speed I seriously doubt that is the problem here.
I also doubt it is the driver, if the firewall isn't the problem, then submit a report to Zenimax since it probably is on their side then and is something they should know about.
Sorry, but the firewall being involved here is absurd. If network data was being interrupted, you may notice some strange things in the client but it would NOT systemlock as described.
This is quite obviously a caching problem... Most likely GPU RAM problems. Reverting your GPU driver may help... Or you could upgrade your RAM.. If you're sure you have enough RAM installed, you could try tinkering with your pagefile. Best practice is typically going to be minimum pagefile at 1.5*your RAM, with a maximum being 2*your ram... Allowing windows to manage the pagefile is going to yield inconsistent results.
My PC should also be more than enough for this game but for some reason its what I have to do. In the end, its much of a such. I usually forget to do it, get a freeze, then do it. No more freezes. It works 100% of the time for me. Hope it does for your also.
Its worth noting that this did not happen to me until the second to last beta weekend.
Altering the priority in the process hierarchy adjusts its position in the system memory and pagefile... This supports my theory that this issue may be related to a caching problem.
Sorry, but the firewall being involved here is absurd. If network data was being interrupted, you may notice some strange things in the client but it would NOT systemlock as described.
This is quite obviously a caching problem... Most likely GPU RAM problems. Reverting your GPU driver may help... Or you could upgrade your RAM.. If you're sure you have enough RAM installed, you could try tinkering with your pagefile. Best practice is typically going to be minimum pagefile at 1.5*your RAM, with a maximum being 2*your ram... Allowing windows to manage the pagefile is going to yield inconsistent results.
GPU Ram is at 1GB GDDR5, I usually turn off the paging file since it has always worked best in past games with it off. I should set that to 1.5* even with 1GB GPU ram?
I'm guessing it would maybe be the driver before its the GPU ram? Also wouldn't I see the same freezing if I ran other programs and games like Skyrim ect.
Sorry, but the firewall being involved here is absurd. If network data was being interrupted, you may notice some strange things in the client but it would NOT systemlock as described.
This is quite obviously a caching problem... Most likely GPU RAM problems. Reverting your GPU driver may help... Or you could upgrade your RAM.. If you're sure you have enough RAM installed, you could try tinkering with your pagefile. Best practice is typically going to be minimum pagefile at 1.5*your RAM, with a maximum being 2*your ram... Allowing windows to manage the pagefile is going to yield inconsistent results.
GPU Ram is at 1GB GDDR5, I usually turn off the paging file since it has always worked best in past games with it off. I should set that to 1.5* even with 1GB GPU ram?
I'm guessing it would maybe be the driver before its the GPU ram?
I'm pretty sure the pagefile is not used for the GPU RAM... I was referring to the system RAM.
Turning the pagefile off is NOT a good idea. Turn it on and place it on your fastest hard drive at min 1.5* your RAM and max 2* your RAM...
Symptoms described tell me that it is a caching problem (edit) especially with the way ESO uses RAM and virtual memory.. Pagefile being off is #1 suspect, but you should also consider reverting your GPU driver.
(edit) essentially, ESO looks for virtual memory FIRST for some major things, before looking for physical memory.. If you're seeing a lock often or at intervals, it's most likely that the core engine of the game is looking to write to virtual memory and stutters while it figures out what else it could do..
I can't think of a single reason, other than disk space concerns, to turn off your virtual memory... It's such a core feature in windows that you're really causing a lot of problems by having it off.
I'm pretty sure the pagefile is not used for the GPU RAM... I was referring to the system RAM.
Turning the pagefile off is NOT a good idea. Turn it on and place it on your fastest hard drive at min 1.5* your RAM and max 2* your RAM...
Symptoms described tell me that it is a caching problem.. Pagefile being off is #1 suspect, but you should also consider reverting your GPU driver.
I got 2 hours before install is complete, i'll test them all out, set the page file, look at drivers, check firewire, set priority... thanks for all the ideas so far.
I got 2 hours before install is complete, i'll test them all out, set the page file, look at drivers, check firewire, set priority... thanks for all the ideas so far.
yeah definitely disconnect all your IEEE 1394 cables. USB2 made that obsolete.
Ok, I tried the page file first, and it kept doing it, then I set the priority of ESO up to Realtime, and it acted funny. Then Set the Priority of ESO to High and it cleared it right up, I can horse down the road, swing my sword wildly, and jump around like a mad man and everything else and it is working 100% smooth and perfect on the top settings.
Not sure what the other things would do, but I'll explore with that later, as of now the High priority worked with both the launcher running and awesomium.exe as well. Thankyou.
Ok, I tried the page file first, and it kept doing it, then I set the priority of ESO up to Realtime, and it acted funny. Then Set the Priority of ESO to High and it cleared it right up, I can horse down the road, swing my sword wildly, and jump around like a mad man and everything else and it is working 100% smooth and perfect on the top settings.
Not sure what the other things would do, but I'll explore with that later, as of now the High priority worked with both the launcher running and awesomium.exe as well. Thankyou.
Setting priority High will not be a permanent solution. In most cases, it gets worse after a while.
Also - install your graphic card driver from your vendor's website and use a uninstall tool before doing that. They won't conlict with Windows ones and there won't be two drivers running at the same time. That is absurd. If it's really happening, there is a bigger problem with your machine.
Also - try unparking your cores (process lasso can do that). In some systems, it makes wonders.
And yes, never, never disable your virtual ram.
Stages of a new mmo: 1) It's just beta. It still has plenty of time before release. 2) It just launched. Give it time. WoW wasn't built in a day. 3) We don't need you anyway. 4) F2P announced. 5)Huge influx of players. 6) Look how much has changed. 7) Cash shop is the only thing developed lately. 8) It has been a long journey and we thank everyone who was part of it. Shutting down in 3 months. (Courtesy of Robokapp.)
In order to fix the Windows 8.1 freezing, crashing and stopping problem easily and quickly then you can use the automatic method insated of manual method since manual method take longer time. So, for automatic method you will need Reimage Repair tool
Comments
My PC should also be more than enough for this game but for some reason its what I have to do. In the end, its much of a such. I usually forget to do it, get a freeze, then do it. No more freezes. It works 100% of the time for me. Hope it does for your also.
Its worth noting that this did not happen to me until the second to last beta weekend.
there is currently an issue with Nvidia drivers, at random points it makes the screen go black, and looks like the vid card is resetting itself, however its not occurring with everyone, download and install the drivers from last OCT, last known set that doesn't have this occurring with some people.
327.23 I think is the driver set, its what Ive been running after I kept getting black screens in planetside 2, and Borderlands 2, 327.23 is stable in both games, was logged in to PS2 for 6 hours on Friday and it didn't miss a beat.
There is a Beta driver at the moment , have tested it, still getting black screen but the frequency was a lot less.
Sorry, but the firewall being involved here is absurd. If network data was being interrupted, you may notice some strange things in the client but it would NOT systemlock as described.
This is quite obviously a caching problem... Most likely GPU RAM problems. Reverting your GPU driver may help... Or you could upgrade your RAM.. If you're sure you have enough RAM installed, you could try tinkering with your pagefile. Best practice is typically going to be minimum pagefile at 1.5*your RAM, with a maximum being 2*your ram... Allowing windows to manage the pagefile is going to yield inconsistent results.
Altering the priority in the process hierarchy adjusts its position in the system memory and pagefile... This supports my theory that this issue may be related to a caching problem.
GPU Ram is at 1GB GDDR5, I usually turn off the paging file since it has always worked best in past games with it off. I should set that to 1.5* even with 1GB GPU ram?
I'm guessing it would maybe be the driver before its the GPU ram? Also wouldn't I see the same freezing if I ran other programs and games like Skyrim ect.
I'm pretty sure the pagefile is not used for the GPU RAM... I was referring to the system RAM.
Turning the pagefile off is NOT a good idea. Turn it on and place it on your fastest hard drive at min 1.5* your RAM and max 2* your RAM...
Symptoms described tell me that it is a caching problem (edit) especially with the way ESO uses RAM and virtual memory.. Pagefile being off is #1 suspect, but you should also consider reverting your GPU driver.
(edit) essentially, ESO looks for virtual memory FIRST for some major things, before looking for physical memory.. If you're seeing a lock often or at intervals, it's most likely that the core engine of the game is looking to write to virtual memory and stutters while it figures out what else it could do..
I can't think of a single reason, other than disk space concerns, to turn off your virtual memory... It's such a core feature in windows that you're really causing a lot of problems by having it off.
I got 2 hours before install is complete, i'll test them all out, set the page file, look at drivers, check firewire, set priority... thanks for all the ideas so far.
yeah definitely disconnect all your IEEE 1394 cables. USB2 made that obsolete.
Ok, I tried the page file first, and it kept doing it, then I set the priority of ESO up to Realtime, and it acted funny. Then Set the Priority of ESO to High and it cleared it right up, I can horse down the road, swing my sword wildly, and jump around like a mad man and everything else and it is working 100% smooth and perfect on the top settings.
Not sure what the other things would do, but I'll explore with that later, as of now the High priority worked with both the launcher running and awesomium.exe as well. Thankyou.
Ehm.. suit your self for using Windows 8... don't everyone knows that every second windows is trash?
Xp was ok, Vista was trash, Win 7 was ok, Win 8 was trash.. so better wait for next version ...
Setting priority High will not be a permanent solution. In most cases, it gets worse after a while.
Try this for automatic priority: http://www.bitsum.com/
Also - install your graphic card driver from your vendor's website and use a uninstall tool before doing that. They won't conlict with Windows ones and there won't be two drivers running at the same time. That is absurd. If it's really happening, there is a bigger problem with your machine.
Also - try unparking your cores (process lasso can do that). In some systems, it makes wonders.
And yes, never, never disable your virtual ram.
Stages of a new mmo: 1) It's just beta. It still has plenty of time before release. 2) It just launched. Give it time. WoW wasn't built in a day. 3) We don't need you anyway. 4) F2P announced. 5)Huge influx of players. 6) Look how much has changed. 7) Cash shop is the only thing developed lately. 8) It has been a long journey and we thank everyone who was part of it. Shutting down in 3 months. (Courtesy of Robokapp.)
In order to fix the Windows 8.1 freezing, crashing and stopping problem easily and quickly then you can use the automatic method insated of manual method since manual method take longer time. So, for automatic method you will need Reimage Repair tool