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
I love this game a lot...but it's still riddled with bugs and crashes.
Yes. I havent used version 2 yet but 1 will work just fine.
https://www.geeks3d.com/furmark/
Also, please list your PC specs.
Include any crash logs if generated.
Open event viewer. Go to windows logs> application and see if a report has been generated at date and time of event. Than look for a general tab towards the bottom. It should list faulting module name and path. It should help give an idea what is causing the crashes. If a report was made that is.
Windows 11
RTX 4090
13th Gen Intel(R) Core(TM) i9-13900K 3.00 GHz
Did you open event viewer?
Here are some suggestions to try.
Make sure your motherboard's BIOS is up to date. Especially since you have a 13900K, it is highly recommended you update your BIOS. As intel has released 3 microcode updates to fix game crashes. The last one being 0x12B.
If you are on older BIOS version, make sure to default the settings before applying the update. Once update is successful apply the correct XMP profile supported by the RAM.
Here is more info on that:
https://wccftech.com/intel-14th-13th-gen-cpu-instability-issues-solved-confirms-0x12b-as-final-mitigation/
Download latest display driver from NVIDIA. Before you install, run DDU to remove old driver first. Than install new one.
Here is link for DDU. Make sure to read/follow guide. Its in the link. https://www.wagnardsoft.com/forums/viewtopic.php?t=5070
Running DDU will remove previous driver/s completely and ensure a clean install. Like its being done for the first time on a newly installed OS. Just note that all NVIDIA control panel (app)/monitor settings will be reset and whenever you update the display driver the shaders will recompile.
Try a clean boot. A clean boot will remove any potential conflicts with other software running in background. So disable all non essential services, programs and tasks from starting with PC. So use services (services app or system configuration app), tasks (task scheduler app, select task scheduler library), and startup items (task manager) to disable them.
Check all 3 areas. If anyone is enabled that software will run and could be causing conflicts with the game. This will also help free up system resources in general.
If you got a Windows update. Make sure it is on latest public build. No insider, preview, or optional updates.
Disable windows game mode, game bar, and game captures.
If you use an anti-virus, windows security, or data protection. Make exceptions to your game folders. This way it disables the scans and doesnt conflict with your games and take away system resources as you are playing. Which may be causing the crashes.
You can also do an SFC (system file checker) scan. Open command prompt and type this:
sfc /scannow
It will scan and repair system files. Run it twice.
If those suggestions do not help fix the crashes. I will offer more.
RMA your CPU!!! Seriously, this is ALL OVER the news for months and months now.
You might even get a 14th generation chip in return (it will be a new one).
UPDATE YOUR BIOS! USE NEW 0x12B VERSION! REQ'D (you may wish to try this first). Go to your system builder's website, or if you built your system you must go to the motherboard manufacturer's website, and then download the appropriate BIOS to an empty USB stick. Then put the stick into the correct port on the back of the board (yes it matters!) and the file MUST be named correctly so the board BIOS will find it. You then either do one of the following:
PLEASE READ THIS IN IT'S ENTIRETY BEFORE PROCEEDING! STEAM, NAUGHTY-DOG, AND MYSELF ARE NOT RESPONSIBLE IF YOU BLOW UP OR DAMAGE YOUR COMPUTER / THE HOUSE / YOUR STUFF / YOUR MOTHER-IN-LAW / THE EARTH, BY DOING WHAT IS STATED, BUT YOU WILL LIKELY BE FINE AND YOUR CPU SHOULD BE RMA'ED IF IT IS CRASHING ALREADY! JUST FOLLOW INSTRUCTIONS CAREFULLY AND BE PATIENT!
---------------FIRST WAY TO DO IT, HIGH-END CUSTOM GAMING DESKTOPS!
1.) Shut the computer OFF entirely (not sleep, not power-saving this or that, OFF)
Make sure the USB stick is in the CORRECT port with the file on it CORRECTLY NAMED, and push the BIOS FLASH button on the back of the motherboard right next to the USB port for flashing BIOS, consult your manual as you may need to hold the button a few seconds. Walk away from your computer for 15 minutes, and see if it's still blinking the light that it blinks when it flashes BIOS updates onto the board. If it is complete, you can then proceed to use your computer again after entering BIOS and setting the date, time, configuration settings etc. This "BIOS FLASHBACK" type update feature on some models (Asus, Gigabye, top-end MSI boards) might not even require a CPU being in place on the board (installed to the board) to do such process, as it is to expedite later purchasers of boards who have newer processors than were out when the board was manufactured.
-------------------OTHER WAY TO DO IT, MOST CUSTOM DESKTOPS!
2.) Put the file onto the USB stick and make sure the name is correct. Place this into a dedicated BIOS FLASH / UPDATE port. If you do not have the button on the back for BIOS FLASH function, you will have to do it this way. Enter your BIOS after restarting your computer, then proceed to go to ADVANCED mode (if you have a modern UEFI gamer-board type BIOS that all major brands use now) if it has defaulted to simple/overview screen, then in advanced you should be able to click through some screens to the right and eventually find an option for updating your motherboard BIOS version (flash a new bios version, or BIOS update tool) with a file from a USB stick. You should be able to tell the computer BIOS which file to flash, or it may pick it up automatically if you named it correctly (or not proceed if you failed to name it right!). Again, like the above, wait a good 10~15 minutes (20~25 minutes max), and make sure that it's correctly finished through all the different screens (it may have to update multiple modules after the initial BIOS flash, so be patient if it starts switching screens, and some systems may have increase power-on time or restart time for the first restart, due to retraining system memory / speed adjustments).
For either:
If you have an issue, make sure the file has been extracted (it should be a .bin file), and placed on a FAT-formatted USB stick that's not using encryption or bit-locker (etc) type of file encoding. Make sure it's the only file on there, just that one, nothing else will be needed and the presence of other files may confuse the computer, break the computer, or do other stupid things you don't want.
If you have issues with the secondary / tertiary updates (after the first bios update, the screen may go to another boot screen to update other things like networking or drive controller support and even remote-management if you have an ASPEED chip in there), make sure to absolutely positively have disconnected any extraneous cables from your computer. You only need a keyboard, monitor, and power plugged in when you do this. You won't need a mouse plugged in but this should not hurt, and will make it easier to navigate BIOS.
NOTE: For DELL, LENOVO, GATEWAY, PACKARD BELL, or HP/COMPAQ system users:
LASTLY, if you have a major-brand machine, go to the manufacturer's website, and read up on how to update those machines best. They likely have their own special way of doing it now (it's been many years since I worked with a Dell or HP that wasn't already completely broken once I got to it), that differs from the main built-it-yourself and boutique-high-end system builders that use top-shelf parts like custom/purpose-built gaming system builders do. (for US folks, yes Gateway and Packard Bell is still sold in other countries)
IF YOU INTERRUPT YOUR COMPUTER WHILE BIOS IS UPDATING, OR IF THE POWER GOES OUT, IT MIGHT BRICK THE COMPUTER (except those with the BIOS FLASHBACK button). NEVER INTERRUPT, TURN OFF, RESTART, OR OTHERWISE ANNOY A COMPUTER WHILE IT IS UPDATING BIOS, OR YOU WILL LIVE TO REGRET YOUR DECISION.
If this post intimidates you more than it should, and you do not know anyone who is computer savvy, and do not feel comfortable updating your BIOS no matter how much info you read on about how it's done on your computer and info from this post, DO NOT proceed. Have a tech-savvy friend or an independent computer shop do it. Still, if you're on 13th/14th gen intel and you're having crashes (any K-model, or KS/KF models 65w and above, including all i7/i9 K/KF/KS and some i5 K/KF models), you still need to RMA your CPU, but you should update BIOS immediately before or after you do so to prevent the system from over-volting the processor and damaging it over time.
Some chips make it 12~18 months without damage, others go belly-up in 2~3 months. It all depends how often you run it full throttle and how hot it gets (your airflow / ambient temps + cpu cooler & case cooling capacity) and how often it's that hot and for how long. Some motherboards are a little more lenient than others, but it's not a motherboard fault (and this point is NOT to be argued here!) as even SuperMicro server/workstation boards were blowing up chips.
Performance degradation of 2~8% in some cases, in others none; but any is better than the processor blowing itself up. It might even run better and turbo faster for longer with less voltage on the newer BIOS updates as it won't get so hot so quick.
"Mom I want a new Intel computer now!" --No, you don't. Just get your CPU replaced. Intel added an additional few years of warranty to retail CPUs and your system vendor (if you bought a pre-built) might warranty your CPU if you ask nicely enough for minimal or no cost, depending if they work directly with intel or not. You can still email or call intel and ask about it if you have a tray/OEM CPU as I have heard conflicting reports. The new intel ARROW LAKE chips aren't really much of any faster than the current CPUs that blow themselves up (and are sometimes slower by a few %), except Arrow Lake chips supposedly won't blow themselves up automatically from the factory. Arrow Lake chips are coming out within the next few weeks sometime, you can look to the tech news for answers on this, but also to the same extent, the 9800x3D / 9600x3D are due out in November (? Before year's end purportedly) so there will be plenty of choice on the CPU market when you're next buying - if you can wait a month or two. 9900x3D 12-core and 9950x3D 16-core are supposedly coming in Q1 2025, and may even have dual-V-cache dies (both core complexes with V-cache) but this is a rumor outside of the more reliable date given.
AMD or AM4/AM5 system users: This post should be ignored by AMD users and does not apply, since this only affects INTEL microcode in BIOS that all BIOSes for LGA1700 were built upon for 13th and 14th gen CPUs regardless of who made the system/motherboard.
This does NOT affect 12th or older generation intel chips, or low power U/T-models.
It may however affect a select few super-high-end laptop chips of 13th or 14th generation but this is much more rare since those don't get the higher power limits needed. If you have an affected crash-tastic laptop, contact one of the Youtube tech guys (Steve from Gamer's Nexus) as they might buy your non-working or happily-crashing-but-otherwise-works sample off you as part of their study. Seriously.
i3's and pentium-class 13th/14th gen models are obviously too low power and not affected, also.
If you're still totally not sure, write your system builder an email (or whoever sold it to you) and inquire about your crashing / faulty processor and needing CPU RMA and a BIOS update to prevent future processors from going BUST.
YOU MUST UPDATE YOUR BIOS EVEN IF YOUR INTEL CHIP IS NOT CRASHING YET, IF YOU HAVE A 13TH OR 14TH GENERATION INTEL PROCESSOR, OR YOUR CHIP COULD BECOME UNSTABLE OR STOP FUNCTIONING COMPLETELY WITHOUT WARNING.
There were four BIOS updates, the most recent one should do (if it does not, you will have to do them all, one by one, one file on the USB stick and reboot/flash one at a time. Most recent update is the 12B update, though your system vendor will number versions differently there should still be a note that it includes the 12B updates, which comes some two to four weeks after a 0x129 update that fixed 3 of the 4 issues with the chips going nuclear and damaging themselves.
Intel has really made a mess this time, hopefully their next round is more reliable / longer lasting.
The heat & power use was one of the reasons (besides only supporting 2~3 generations of chip per socket) that I didn't go with intel, turns out that reason was very valid. So I will sit this out and be able to help others with the issue. Please tell your friends and share this post if they have the same issue as you, it does not earn me even a cent, but it will help your friends. ...and to think I just didn't want to BBQ myself any more than the last computer BBQ'ed me.
--Good luck people!
You have done all of the troubleshooting steps I suggested above? Yet have provided no other info or crash logs. Seems like you didnt do a thing to me with that very small response.
If your CPU and GPU you were fine. Than you wouldnt of needed to make this thread and say you are crashing with higher temps. Even though those temps are normal and wont have a negative effect on performance/hardware.
Its either a software conflict, bad driver, bad OS , or faulting/defective hardware.
What CPU cooler do you have?
What is your PSU?
How much RAM and what speed?
What is your Case and how many fans? What directions are they flowing?
Lastly, since none of my questions were answered that I asked above besides listing some of your specs. If you arent going to bother troubleshooting your PC or try to answer questions. Which is very much going against the grain when others are trying to help. Let us know and I will stop offering suggestions and leave you to it.
Don't really understand the hostility. I have no crash logs since it hasn't crashed since (yet) and the only information was GPU ERROR. It hasn't happened in other games
No hostility. Just seems you arent bothering answering anyone that is helping you.
If we ask questions and you dont answer. It makes it more difficult to get the issue fixed.
So you say it hasnt crashed since? So you are saying the issue has corrected itself? Or you did something that fixed it?
Did you look at Even Viewer for this GPU error? How do you know it was GPU error? If it was GPU than it was either a bad driver, fault from OC, or it overheated.