Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
It's more than just that. I'll be in combat, and it crashes. I'll be walking around looking for something, it crashes. Hell, loading screens are the only time it won't crash for me. And this is way more frequent than that for me, too. Yesterday, the day I installed the game, I easily had 15 crashes.
Actually another possibility occurred to me. If the crashes are frequent and occurring mostly during active gameplay, it may be a heat issue, likely with your video card, though maybe with your RAM sticks. You might wanna crack open your case and see if you have dust building up in the heatsinks and/or fans, that kind of thing.
I have at least 30 mods installed and I only crash for specific reasons related to my mods.
Which btw is even a rare occurance to begin with.
Vanille should not crash EVER.
Not once had my game crashed without mods.
Well sorry bud, it's pure vanilla. Didn't even know the game had mods. Frankly trying to say something should never happen based purely on your own experience is utterly asinine and insulting.
Well I did hop on the newest driver the moment I found out there were new recording and streaming capabilities. Definitely no issues with heat though. CPU tends to stay at 50-55 celsius, GPU 65-75, and there's no reason for the RAM to get too hot with those temps.
Is there any sort of things you can do to replicate the crash? Specific areas or attacks on certain enemies?
I would recommend a quick verify from Steam to be sure something wasn't corrupted.
Also, if you have two monitors, or any other way to look at it, keep task manager up and keep an eye on your performance.
I'd also recommend cleaning out the dust from your pc anyway (if you haven't done that in a few months)
Oh, what's your PC specs too?
>like everyone else said
Literally only one person said that, and me pointing out that saying something shouldn't happen because you've never experienced it is stupid does not equate to raging. Try harder.
One instance I can replicate is just fighting while using a controller with vibration enabled, but I still crash then, just less frequently without any real predictable pattern. Already verified game cahce, performance is fine, PC isn't dusty. Specs below.
Motherboard: Gigabyte GA-78lmt-s2 rev 1.2
CPU: FX-6300 @3.5 GHz
RAM: 8GB DDR3 @1333 MHz
GPU: Sapphire Dual-X Radeon R9 270
OS: Windows 10 Home 64-bit(upgraded from Windows 7 Home Premium 64-bit)
Diggin' a bit deep here, but I did a quick scan of your hardware and here are some possibilities, though I cannot put any kind of reliable odds on any of these as being "it" in your case:
1. That MB looks solid, except for one tiny thing - it has a Radeon HD 3000 down on the board. That might...theoretically... cause driver hiccups and odd behavior if the driver installation was anything less than perfect, which itself is a known and longstanding trend with ALL Radeon drivers. Not a big red flag, but it would indicate that testing a rollback driver version would be a good idea just to rule it out.
2. The "latest" driver for that video card came out 13 days ago. I am guessing that is the version you are running, namely 16.11.5. If so, there are a couple of things about that which concern me. First, it has some known issues with several games having crashes and other problems when launched while running the Vulkan API. Also, this rev has not yet been platform tested by Sapphire, which is why Sapphire is still pushing the 16.11.4 revision. Sadly, that rev also just came out very recently, so itself hasn't much time for real stability testing.
---Side note: this is part of the problem with Radeon and their lousy track record with drivers. They do great hardware, but can never stay properly on top of their drivers. Rule of thumb: NEVER update a Radeon driver unless there is a specific reason, a NEED, to do so. If your system is running stable, leave the Radeon drivers alone! They are notorious for introducing regression bugs that cause problems with previously working game titles in their efforts to add support for newly emerging game titles. If it ain't broke, don't fix it ... and don't let any automatic driver update utility do it for you! ---
3. Some quick support and review board scanning shows that a rather sizable percentage of people who report problems with that particular Sapphire card were all related to one general problem: overheating the box it is installed in. Apparently the card doesn't have much trouble keeping its own GPU cool enough, or maybe just keeping its temperature sensor cool enough, but I saw several mentions of problems with it pumping excessive amounts of heat into the MB and causing hot spots right under the PCI slot row. Those who reported successful remedies for this generally got there by forcing extra airflow onto that area with strong, side-mounted or side-facing fans blowing right onto the PCI slot row from the motherboard's "UP" direction, which in a tower case would mean from the left side of the case. Some of them even had to remove the side of the case and use a box fan at point blank range! On the flip side, numerous other people reported no such problem at all with the exact same rev of the exact same Sapphire card. This leads me to suspect that it is actually a combination of that card with only some MB designs, probably those which either wire too many caps or with the DIMM slots too near that area. It might also be an alchemy of that card with certain cases. Impossible to say. In any case, it's impossible to diagnosis overall heat issues by just looking at the temperature readings reported by the video utility and the MB's bios. In a perfect world you would whip out your handy-dandy temperature probe and test it by hand. In a less than perfect world you would be to leave the side panel of the case unscrewed. Then the next time the game crashes like this, quickly power down, unplug, pull the side panel you unscrewed, and then quickly probe around with a finger before anything has a real chance to cool off. Check various spots on the MB, neighboring PCI slot and/or PCI card(s), the power cable that feeds your video card, etc. Look for any spots other than heatsinks themselves which are too hot for comfort on the skin of your fingertip (assuming you are not a guitar player with fingertips that have callouses on their callouses). Be careful not to push on slotted cards, DIMMS, etc, as that might mess up their seating in their slots, which is a whole other test for a whole other kind of problem that you aren't having.
3b. Yet another problem I saw with a minor trend on that particular card is the power draw. Apparently one secondary power cable is not really enough in all circumstances, and many other cards by other manufacturers using that GPU and similar specs actually included TWO secondary power sockets, basically feeding that single card as if it were two Crossfire cards. That leads me to wonder if perhaps the power supply in your case may be overtaxed by the draw from this card. Or perhaps the power supply is just slowly degrading in performance. It's a long shot, but not at all outside the realm of possibility that a new power supply, preferably with a larger reserve, i.e. more excess capacity, might be a good idea. Heck, it might be a good idea regardless, as large untapped reserve means you are stressing it less, which results in much greater lifespan and less heat buildup in the case as a whole, which is always good no matter what.
Good luck!
Guessing that brings us back to the original #1 suspect then, i.e. the video driver. The game itself does NOT need administrator privileges, but some element of the new driver and/or its accompanying utility package might want it to have elevated privileges and start causing problems when this or that function is called that expects to see them.
Crossing fingers for you, dude.
I dunno man. All I know is it's working properly now and I'm happy.
I like to know what caused the problem, for the future ability to help others similarly afflicted. That said, I am NOT gonna turn my nose up at a happy ending just because I don't know for sure how it came about!
'Grats, dude.