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
https://rog.asus.com/support/
Some BIOS updates are rated by ASUS as critical. It's very important to install such updates ASAP. Some older BIOSes were applying too high voltage making the system unstable and even degrading the CPU permanently.
All the automatic update helpers say as much.
Checking manually, my system info says I have BIOS version 331, which is also the version ASUS has on their site as critical.
Are there any other known potential causes for these crashes?
Once it has happened it's already too late though. When this happens the CPU is too damaged to be used with Unreal Engine 5 games.
Unreal Engine 5 tends to give you an error message, refering to issues with "shaders", in many CPU-related crashes.
The safer but not as reliable options that come to mind for me are those:
- Intel Processor Diagnostics Tool: it can be downloaded directly from Intels homepage. It runs a few tests and tells you if your CPU passed these tests. If your CPU is alright it should pass every last one of them. If it fails a test, then there might be an issue..
- 3D Mark: not free, but it does offer a CPU stress test that takes around 20 minutes or so to complete. It's mostly performance related but after the test it gives you the option to compare your results to other peoples results. Should there be a huge difference between your CPU's performance and other peoples performances with the same CPU, then there might be something.. or when 3D Mark itself runs into an error
- Prime95: This is as far as I am aware one of the better free tools to check if a CPU is doing alright. However, it is also a tool that comes with a certain risk. This tool comes with a stress test that can damage undamaged CPU's if for example the cooling unit can't keep up with the stress test. So this tool should be used with caution and better while also using HWiNFO64 to keep an eye on temperatures. I would say the test should be aborded if HWiNFO64 shows CPU temperatures 90°C or above to not cause damage while checking for damages.
But maybe there are people who have some better ideas on how to check for these issues. Those were the tools I used to learn that my CPU was damaged last week. It was an i9 14900K that was only 13 months in use.
Before you start any of these stress tests do make backups of your important files though :) You never know what happens if you use a stress test on a damaged CPU. In most cases the tool will probably just tell you that something is wrong, but I believe there is always the risk that a damaged CPU can be completely broken by a stress test.
The 566.36 is one of the drivers I had already tried.
My CPU failing doesn't make a lot of sense to me, since I'm having zero issues running other supposedly CPU-intensive games like Monster Hunter Wilds.
I don't think I'm going to be kicking apart that ant's nest by running a stress test, especially if it wouldn't actually solve anything even if my CPU was the problem.
I guess I'll get a refund and hope the game comes to Switch 2 eventually. Bummer, but I'll live.
That was incredibly helpful, many thanks!
It seemed to be my overclocking caused game crashing, I just lower my oc settings see how's going.
Came back with no issue.
On the downside, I still don't know why the game keeps crashing
On the upside, my CPU's not busted, so that's something
Depending how bad or not so bad the degradation is, it may not be very easy to intentionally trigger the problem.
https://youtu.be/P7Eyv5d2Rq8?si=ljj5QYA9vngcLPxM