- Jan 14, 2024
- 165
- 13
- 85
Other components in my signature.
I recently upgraded from an Asus KO RTX3060ti -8GB-OC to an AsRock Phantom Gaming RX 7900 XT.
Things started out quite well, but noticed glitchy audio occasionally and I could not get over 30hz / 30 fps at 4K. Since I have a dual-boot system on separate drives (Mint Cinnamon 2 and Win10) , I tested to try to isolate to a particular OS. After some basic overclock / undervolt settings (1000 min / 2750 max, 5% undervolt, VRAM OC to 2650), I still noticed the same thing. Ultimately, it turns to have been a combination of display input settings (standard vs enhanced), and possibly an older cable. Swapped cable, changed settings and all seemed well, but glitchy audio is still an occasional issue.
However, over the past couple days, I have experienced some crashing and restarts in BeamNG.drive that I cannot seem to home in on the source of. I've disabled DOCP, dropped resolutions, dropped refresh rate, dropped texture quality. Without fail, under Cinnamon or Win10, if BeamNG spawns over 4-5 traffic vehicles, it crashes, and the system restarts itself. American Truck Simulator does not do this.
It would seem to be a memory instability issue, but the DIMMs are on the board's QVL, and no previous issues in a year or so running my old RTX3060ti with the same other components. Does anyone have any ideas here? American Truck Simulator runs PERFECTLY at 4K 60hz with 400% scaling and ultra settings.
On a few of these restarts, the machine has reported some errors, I presume related to the crash, indicating an issue with various CPU cores. Images of these error messages are linked below. A few others I didn't catch on camera indicated CPU 10 and CPU 11. They are not necessarily consecutive, but random out of the last 6-7 crashes / restarts.
First restart error - CPU 23 - Processor 2
Second restart error - CPU 11 - Processor 2
Third restart error - CPU 23 - Processor 2
Since the core number is never the same, I am starting to think it is either the way the game is trying to adress the cores (meaning an issue with a recent update), or perhaps I have a flaky CPU, and the RTX3060ti never loaded it enough to cause this? Perhaps ATS is not loading it enough to do this either? Or is there a pattern of BeamNG misbehaving with AMD cards?
I recently upgraded from an Asus KO RTX3060ti -8GB-OC to an AsRock Phantom Gaming RX 7900 XT.
Things started out quite well, but noticed glitchy audio occasionally and I could not get over 30hz / 30 fps at 4K. Since I have a dual-boot system on separate drives (Mint Cinnamon 2 and Win10) , I tested to try to isolate to a particular OS. After some basic overclock / undervolt settings (1000 min / 2750 max, 5% undervolt, VRAM OC to 2650), I still noticed the same thing. Ultimately, it turns to have been a combination of display input settings (standard vs enhanced), and possibly an older cable. Swapped cable, changed settings and all seemed well, but glitchy audio is still an occasional issue.
However, over the past couple days, I have experienced some crashing and restarts in BeamNG.drive that I cannot seem to home in on the source of. I've disabled DOCP, dropped resolutions, dropped refresh rate, dropped texture quality. Without fail, under Cinnamon or Win10, if BeamNG spawns over 4-5 traffic vehicles, it crashes, and the system restarts itself. American Truck Simulator does not do this.
It would seem to be a memory instability issue, but the DIMMs are on the board's QVL, and no previous issues in a year or so running my old RTX3060ti with the same other components. Does anyone have any ideas here? American Truck Simulator runs PERFECTLY at 4K 60hz with 400% scaling and ultra settings.
On a few of these restarts, the machine has reported some errors, I presume related to the crash, indicating an issue with various CPU cores. Images of these error messages are linked below. A few others I didn't catch on camera indicated CPU 10 and CPU 11. They are not necessarily consecutive, but random out of the last 6-7 crashes / restarts.
First restart error - CPU 23 - Processor 2
Second restart error - CPU 11 - Processor 2
Third restart error - CPU 23 - Processor 2
Since the core number is never the same, I am starting to think it is either the way the game is trying to adress the cores (meaning an issue with a recent update), or perhaps I have a flaky CPU, and the RTX3060ti never loaded it enough to cause this? Perhaps ATS is not loading it enough to do this either? Or is there a pattern of BeamNG misbehaving with AMD cards?
Facebook
Twitter
Instagram