Gta 3 Definitive Edition Fatal Error
Nguyet Edmondson
So, I start up the game and try to play single player with mods installed, and after making the character and after the cut scene, I get a fatal error, is there any way to fix this so I can play with mods? Servers work just fine though.
In all likelihood, one of the mods you have installed is the cause of your crashes. The first step would be to identify which one. So disable all mods, then start adding them back one by one until you get the fatal error again - the last one you activated is the culprit.
Matt would this be good advice for all with this error. There have just been a ton of users complaining of this issue with no clear idea on what is causing it. Some have claimed that replacement cpus have fixed it. While others say if they regress there Zen 2 processors bios to an older bios this goes away.
I've tried the optimized defaults and it seems stable.
Also tried simply applying DOCP (3600) and FLCK 1800 with good stability.
Also tried enabling PBO with good stability.
I've since updated the bios to 2702 (released Nov.24) and it's running stable so far even with PBO enabled.
Bios 2702 has changed in that if you enable PBO, Max CPU Boost Clock Override is greyed-out. I have a hunch that the 200Mhz value I set here previously was causing me grief, along with the Ryzen Balanced Power Option in Windows (just a guess).
I did have a bit of a scare though, as during the bios update (from BIOS UEFI via USB), it appeared to be a success, the system rebooted itself and went through the final update process after post. At the end of the process where I'd expect another restart, the system powered off. I couldn't power it on again until I turned off/on the PSU (like the problem I mentioned in my first post). The system then started up and all was well.
I'll keep the system running and see how it goes. HOPEFULLY this new bios has fixed it.
If these changes are actually having an impact, I'm hoping a future BIOS update will fix the issues. The target market for 5950 & 3090 is content creators, and a huge part of their workflow is at low/no load. If they lose enough work in progress, you'll have an army of angry creative types, and no marketing department wants to deal with that.
Temps ok? Running at XMP 3600 is fine. CPU clock ratio should work in Auto, kill the PBO and any overvoltage. Try manually setting the IF to 1800 vs. Auto. Auto IF can make things wonky. Best set at half the full RAM clock, no higher than 1800. Still unstable, drop IF to 1600 but you'll lose some performance that you might not notice. Memtest 64 should run for hours without an error, overnight if possible. Lastly if you have 4 RAM slots and 2 sticks they need to go in A2/B2 or the second and fourth slot from the CPU.
I was getting the same errors on mine. Tried many different BIOS settings and still kept getting reboots with the same Cache Heirarchy Error code. Finally got it stable by turning on the Asus TPU II OC setting that keeps my CPU at 4.1ghz speed. It actually runs cooler now and doesn't have crazy temp jumps like before. Haven't had one reboot in the last week.
MOBO: Asus B550 F gaming
CPU: 5950x
GPU: PNY 3090
i'll try troubleshooting and if it becomes a bigger problem i do have a 3900x here as well but would very much like to stick with the 5950x... seems there's still a host of potential issues though which i suppose is to be expected since at this time there aren't any motherboards available that were made specifically for the ryzen 5000 series. maybe by the end of the year..?!?
You can try disabling DF states in the BIOS, not sure where Gigabyte hides it. It seems disabling sleep/hibernation functions in Windows helps. Using an SSD make sure that it's set to never power down. If your RAM is on the QVL, I'd test it with TM5, try running OCCT, try turning XMP off and enter the basic RAM timings/voltage by hand, set the FCLK or IF to 1800 for 3600 RAM. Manually set the SOC to 1.2, that fixes the issue for many. You can run lower SOC but stock is 1.2.
I'm just going to share this here since anyone else reading this using the same apps may be able to verify.
Full specs:
Ryzen 5 3600 4.2ghz All core undervolt 1.125v
DDR4 3600mhz 2x8gb C16,, HCImemtest 200% stable.
Gigabyte RX 6700 XT Slight undervolt, all big titles stable(Days gone, warzone, tarkov etc.).
Rebar enabled according to GPU-Z.
Agesa 1.1.0.0, updated to 1.2.0.2 mid-may in an attempt to fix the Hierarchy Error, seems the Agesa is innocent.
Radeon Driver 21.5.2(this is also suspect as I jumped on 21.5.1 as soon as it released).
I started getting frequent Cache Heirarchy reboots at the start of May, roughly the same time I started using HWinfo(launch at startup) along side MSI afterburner with a undervolted Ryzen 5 3600, now this CPU is ROCK stable in everything I throw at it including long idle periods(I was concerned about the Vcore being too low at first) but now I suspect it may be an issue with Resizable Bar & GPU behaviour + Compute mode COMBINED with CPU trying to 'park' and getting polled for temps too frequently which would obviously be aggravated by multiple sensor programs but Im honestly unsure how the CPU+GPU communicate and if things like Compute mode and Rebar make much difference at all, only a AMD Tech would be able to answer it properly.
So the long story is, I was doing on & off mining, 24hr stable for MONTHS until I started benchmarking games again and set HWinfo to 'launch at startup' to integrate with Afterburner OSD. This is when the Heirarchy crashes began(early May). At first I suspected my undervolt immediately as it's 4.2ghz all core @ 1.125v,, but bumping up to 1.2v made no difference. I did not suspect HWinfo involvement at first, but over 3 weeks of very random and intermittent Heirarchy crashes(mostly at idle) I stumbled across a thread linking it to HWinfo(and other users confirming), so I disabled HWinfo launch at startup from that point, and stopped using all programs except MSI afterburner.
No Heirarchy crashes until 13 days later, when I ran nicehash for all of 5 minutes but changed my mind and shut the PC down. The next day I was greeted with a Heirarchy crash when loading Cyberpunk shortly after boot. And THIS gave me a hint that a combination of not specifically sensor programs, but Mining software enabling 'GPU compute' mode was persisting after reboot and contributing to the Heirarchy crash, after a crash the GPU drivers reset which is why the issue seemed so intermittent. After the crash I loaded up Cyberpunk and tested for hours no problems.
So the TLDR is, Monitoring programs and any Mining software that may be enabling Compute mode are key factors in 'triggering' the Heirarchy issue, and it may be GPU related. I went from about 10 crashes between the first 2 weeks of May, to only one crash after removing HWinfo from my startup programs and avoiding 'compute mode' set by Nicehash. Its frustrating because while Compute mode can be manually enabled via mining software, its not as simple to disable since the switch back to graphics mode was removed from Radeon software.
The main reason for sharing this info is anyone with 'similarities' might have a clue were to start troubleshooting.
I found that I also have the same problem, but the frequency of illness only appears when I watch a movie. Whether you are watching YouTube with a browser or watching a movie with a player, you can just turn on the computer without watching the movie.
After discussing about WHEA error, AMD decided to refund me, instead of send me another 5950x. So, they KNOW the problem they have with PB/Core Performance Boost and PBO, but since AMD is a trash company, they will never admit their mistake.
Its not related to AMD GPU as I have Nvidia. Its not related to HWinfo or monitoring apps as it happened to me and many others without any of that even downloaded yet.
Also not related to F31 or above firmware as some suggested rolling back to F30 since late last year. It happened to me starting with F30. haven't tried F31 through F34 yet. Gigabyte's site is broken I can't even download them they mostly all 404.
Haven't tweaked any settings but found a couple promising workarounds that seem to have worked for people (disabling XMP, CPB, PBO, lowering curve optimizer) but all of those were already disabled and haven't touched any settings yet.
Basically the gigabyte "BIOS" utility was saying it was updating to latest but it wasnt. Also you could not download any/most of the BIOS from Gigabyte's site. Apparently they got hit with ransomware attack and have been slowly recovering for weeks and that's why so many of the utilities/drivers/bios downloads are still 404ing on their site. I know now that I could have grabbed it from Tweaktown but I was attempting other driver updates and fixes before this (thinking BIOS was up to date, and stable). Some people said their F30 was stable so I left it.
I have the same issue with a 5950X. Sometimes the cache Hierarchy error happens directly, sometimes after a few hours. All with default bios settings. I'm using the latest bios version from MSI MEG X570 UNIFY, 7C35vA82. The version before was even worse.
I sorta asked the same question in a few posts. My 3600X has done this since day1, it's intermittent, nothing solves it, ever. I read it was the AMD video driver, can't be, OP is using Nvidia. I ran default settings 72 hours and it would still happen. If I look in Event Viewer now, it's probably there. Doesn't always crash the PC, sometimes just an app or nothing and I find it when it does crash. 2 days ago I got it running OCCT to see why my PC crashes, thinking it's the RX 5600 XT GPU or driver for it. Reinstalled Windows, nope.
I feel bad for the OP but good i didn't go spending more money building with new AMD products. My build is 7 months old and I have 20+ years exp. building PC's for myself and customers, 98% AMD. Had little to no issues with any platform until now. @Matt_AMD Many have similar complaints and tried exactly what you mention. Yields nothing but the same error to the point I'm past returning anything to the vendor. AsRock needs a specific reason to RMA my board. AMD would probably want more than this code to warranty the CPU, if so there's a whole lots more to warranty out there. Guess I can't blame Gigabyte for a faulty RX 5600 XT either. "Processor Core Failure" or "cache hierarchy error", "Processor Core Bus Interconnect error/corrected" all actually do relate to the CPU, not the GPU. Correct? 7 months of getting the wrong info....
4a15465005