This is the reason why the CPU becomes unstable at some conditions and crashes. Many motherboard makers depending on the model and bios revision use negative offsets by default so they can cheat in benchmarks! Much like the "Power Reporting Deviation" uncovered not that long ago the smarties at motherboard makers decided that setting CPU voltage default to anything else than normal just because their test CPU passed some in-house test it's fine!īut no it's not! CPU Vcore voltage is usually set to AUTO. But the motherboard can lie and here's the catch. These CPU's expect telemetry from the motherboard to know what they are doing. There is a myriad of factors affecting stability, and this curve should be thought off as a suggestion of what the CPU thinks it should be OK. It's the CPU cores getting too low of a voltage in a specific boost condition.īut you ask WHY?! Aren't Zen 2 cpu's follow a fixed FIT curve? Yes and no. And because this crash is impossible to reproduce on demand placebo kicks in and they think they've fixed it. Everyone just assumes it's either the gpu drivers or bad cpu or something else. There are a lot of threads discussing this error but no actual solution. This gave me a valuable lead to get to the cause of the issue. In older versions i never had a logged error during this type of crash and i didn't even had the famous "WHEA Uncorrectable Error" Starting with W10 2H10 (and possibly because of new AGESA) a new type of event has been added to the event log for Zen processors: This became a little annoying so i decided to find the issue and fix it once and for all. However 2 weeks ago i started playing Cyberpunk and these crashes were far more frequent and also behaved a little weirder (example the game would freeze but crash in 1 minute later, but if i relaunched the game without restarting it was guaranteed to get a crash withing 5-10 minutes) I had this issue specifically when only playing PUBG for a long time but it was not that frequent so i thought it was because it's a bad written game since everything checked out CPU burn tests, RAM tests, etc. It's totally random and impossible to predict. You play a game and randomly you will get a black screen crash for no apparent reason, and the PC restarts and you get back into the game, only not to have none, or another crash in 5 minutes or 4 hours later into the game. I hear you can resolve the issue using GeDoSaTo, but i never tried it myself.So quite a bunch of people have experienced this type of random black screen crash on Zen 2 and even Zen 3 systems. If you run the game at a resolution higher than 1280x1024, the text describing some the hints for each monster in bestiary becomes invisible. I've played through FF13 and 100% it, and the only issue i noted was minor one at best, it doesn't affect the game play in of itself, but can be annoying nonetheless. Hopefully the mongoloids in charge of porting to PC at Square Enix figure it out by the time FF15 comes out on Steam. Hopefully FF13 isn't as bad as this since I'm planning to get that game next (weird order I know but I want more FF13 goodness and never played the first). Oh boy I better finish this ♥♥♥♥ before another damn bug shows up then. Originally posted by Shadownight Dragoon:LAA may just be a bandaid solution to the pisspoor port job the SE did with FFXIII-2, but seeing as it more and more unlikely they do some kind of optimization patch, I found it addressed the constant crashing/freezing issues I had, frame rate seem to be steadier than before, probably nowhere near a constant 60fps, but definitely not stuttering and lagging as before. Running as admin does nothing and running in compatibility mode for any other windows version just makes it so I can't get past the Square Enix logo, another problem I discovered lmao. Windowed or fullscreen don't do anything and lowering settings doesn't do anything as well. I have tried messing around with v-sync and AA and other settings over in the AMD control center but nothing seems to work. When I got the problem I had not updated my drivers or installed any mods, although I have updated since today and I tried rolling back to older drivers as well but to no avail. The problem can be recreated with precision and the outcome is always the same, a frozen game. In 300 AF when when I'm mid-swing on a vine the game stops completely as well, this happens on any vine. For example, in 05 AF when I'm about to turn the corner to get into the town the game stops, audio and everthing, completely frozen. I can't alt-tab, f4, or taskmanger myself out of this predicament and I either have to ctrl-alt-delete to sign out and back into my account or restart my computer completely. Now I've gotten all the way to the Coliseum since then and out of seemingly nowhere the game freezes after I hit a set point in most places and stays completely frozen.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |