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
0 
Report this post
That being said, usually when my PC gets hot due to graphics use, I will see "waves" on the screen. There is no visual warning. The game sounds make a very light buzz noise just before going full freeze and very LOUD buzz.
I'm sick to death of it being my PCs fault that a game can't run properly, especially considering my setup is more than the recommended.
Im not trying to aggravate you, this game is exaggerating or exacerbating whatever "it" is, but it does sound like you do have a PC fault though, whether it be hardware, drivers or software. This fault though could be something as simple as a blocked fan, too close to the wall, etc, to something like the GPU is loose, to something near failure. Waves on the screen and buzzing, would worry me very much. Sounds like a hardware issue the heat is creating, but i could be completely wrong without seeing it. Also saying, "More than the recommended" is like calling me a man and you a woman. There is much more specifics, differences, flaws and faults to us and PCs. I could have exactly the same PC and it works is what i mean. If its only presenting itself in this game though, its not the end of the world.
Can you check the temps for me? Laptop or PC? Integrated graphics or GPU? I will try to help you, if you want me to.
All drivers are up to date and in fact, just updated the graphics driver last week.
Again, this DOES NOT happen on single player mode... so it's my PCs fault it can't handle how the game was designed for multiplayer. Shame on you, PC.
I do appreciate that you have put considerable effort into trying to help, but you sound like Blizzard and so many other companies when there's an issue. "Did you delete your cache and WTF folders?" "Are your drivers up to date?" etc. Been PC gaming for 10+ years and have had low end GPUs that I had to watch the temp of when playing more modern games. But this time, it's not the PC. I promise you.
Seriously though, search the internet for buzzing crashes and you will get, "It was my PSU", "It was my graphics drivers", "It was my motherboard", "It was my Ram", "I reseated my GPU and it works now", "It was my overclocking", "I reinstalled Windows and it never happened again", etc etc. Its just this one game (whilst multiplayer) brings out your issue, thats all, whatever it is. Im not calling you computer illiterate or anything of the sort, as you say, im being the Blizzard support type. Pointing out the obvious to people who dont know, but i didnt know how much experience you have. Personally ive been in gaming and making 15+ PCs for over 20 years. First PC i ever used was an IBM386 and the birth of the Internet using a 32k Modem lol. ;)
I have had the exact same issue on and off for the last few years. Unsure as to why it happens. When it does i generally have to verify game files as it starts a crash loop that even starting the game causes BSOD.
I have tested many things over the years including a PC rebuild over the last year, win 7 and win 10. I ruled out most of the part issues over time as initially i feared my GPU or RAM were dying. Most of it was not a direct test but, the issue persisted throughout the evolution of my rig.
I run a custom rig as previously mentioned and i am WELL above spec as well. My case is so well ventilated that my GPU rarely gets over 55C and never over 60C with fan speed at 35% (I have WAY more 120mm case fans than any man should reasonably want).
I have tried every combination of stock and OC for GPU and CPU. I have also tried using an SSD vs harddrive for it to see if it was the SSD's firmware.
The issue is VERY odd and a crash can corrupt the game itself in such a way that causes repeat crashes each time the game is even launched. These repeat crashes usually happen within 10 seconds of hitting start and unless you skip the intro you wont make it to the menu. if you skip the intro it freezes within a second of hitting the menu. verifying files usually fixes the current instance of the issue. on occasion a reinstall is required. In all cases the game save itself seems to be fine.
I have alternated from out of date saves, current saves, and starting a new game. Once the issue begins it persists in all with an equal frequency that i can tell further ruling out save corruption.
I have found NO way to effectively prevent the crashes however. sometimes i just get lucky and have dry spells. other times like the past 2 days i have had over 20 crashes (about 12 of which were pre-menu crashes).
I checked logs as you recommended and oddly enough no errors or warnings except the power event failure which as you stated pretty much says whatever it was could not be recorded by the system. I am wondering if the game is dipping voltage or something odd that might cause these sudden hardware hiccups.
Try to take it easy on him. you never listed what you had done therefore, he will pretty much go down a list of what could cause the issue from easiest to hardest to test/try as any support tech will do. Many times the issue is one of these. Unfortunately, in my experience, this game has some jacked up optimization. This game has something weird going on. No clue as to what it is yet. if i ever find a magic fix ill let you know.
My game is vanilla. It is probably a good time to revert any mods you have if you are using them.
So as you say, something about this game brings out the issue. Some of the ones i was reading were DOTA only, GTA only, etc etc. Some are just that unlucky, one game makes it happen. Either way, to find a magic fix i think is gonna take a lot of time i dont think she wants to spend and I probably wouldnt either, just for 1 game, unless i really, really, liked it.
I did some research and it appears the issue is not actually the game but the engine itself. Unity seems to have a bigger problem in the gaming community in the sense that many tried and well running rigs run into BSOD often when running unity specifically. A simple google search revealed DOZENS of threads from both devs and players on every site from stackoverflow to reddit.
Knowing this i think ill give the game a bit more of a break considering the version of the engine the game was coded on may just be jacked up.
While there a google search does show the issue is common most of the complaints stem from development that happened 5 years or more ago. It seemed to be at its worst in 2009 and it becomes very hard to find a BSOD issue after 2015 (this game started development around this time and obviously updating the engine will screw the game and require a LOT of fixing making this option not viable for a dev this invested on a bugged version).
I am willing to bet that this version of unity's hardware management is bugged and is causing voltage dips on assorted hardware sets. This explains why tested and functional hardware would have issues exclusively with The Forest or other titles using Unity. The bug also seems more likely to occur with 3D games pointing toward GPU usage though, there were a few 2D games that suffered from the issue as well.
https://answers.unity.com/questions/842831/build-problem-build-gives-me-a-blue-screen-not-bso.html
The newest instance i found of the issue was covered by tomshardware. Honestly dont know if they are covering old issues or if the issue is still alive in unity but, this shows the problem generated a lot of heat at some point for a computer magazine/news site to cover it.
https://forums.tomshardware.com/threads/unity-3d-crashes-windows-with-bsod.3200884/
Yet another complaint by what appears to be a dev who has done a significant number of fixes to the point that someone recommended him to Unity devs for a new version. Again, tried and tested rig has issues exclusively when in use with unity.
https://answers.microsoft.com/en-us/windows/forum/all/bsod-when-trying-to-create-a-new-3d-unity-project/9e8fcb3d-8d37-40e2-b32e-5849ee5bbfcd
These are the more useful examples. I tried to cut out the ones that had poor answers and did not dig deep enough to make a solid point.
At this point in my research i am worried that a fix at consumer level is impossible as it may very well be unity is mismanaging hardware power. Some hardware is more resilient to voltage dips than others explaining why some desktops evade the issue. It also directly explains why altering power management could help. More power essentially counter balances the dips so you are less likely to dip below the BSOD threshold. From this point i am at a loss as to what could be done except raising voltages too offset a dip but, this in itself poses too much risk to hardware to even try except as maybe a temporary test as a proof of concept. However, if raising voltage worked it would prove Unity is the culprit.
Op, at this point i am digging REALLY deep and taking shots in the dark. if for whatever reason i turn out to be right it means it is unlikely we can find a fix in the forest itself depending on what the exact issue is.
"The GPU tweaking driver "iomap64.sys" was found on your system. Remove all overclocks."
"The Whea_uncorrectable_error usually occurs if the there's a hardware error."
"Update: it appears changing the quality to anything other than Fantastic makes everything work fine... Apart from the bit where I'd like to be able to run it on fantastic"
Could it be their lack of "optimisation" SURE, more than likely. It could be calling on so much GPU and CPU usage that some PSUs dip when it takes the first hit, especially the cheaper Bronze type. The higher you get to max Watts, the drop in efficiency and output, similarly a sudden max draw just wont supply whats needed fast enough. A minor drop in voltage, a blue screen or similar might occur.
I think they took on too much, making the game work for 32/64bit, VR and PS4. They added multiplayer they didnt plan to add in the first place and on top made shoddy Dedicated servers. Coop however was one of the best additions i think personally. Then adding all the extra content wasnt a mistake, but after that, they should have definitely used more time to "bug fix" BEFORE they moved to the next game. "Optimisation" would have been lovely to polish it too for a finish product. However my feeling is that they were under pressure by someone to push on, whether it by Sony or the investors, idk.
probably both tbh. Not much money to be made in a game that is 'finished' enough to be sold already and has been sold for a while already. If either or both thought that the selling potential of the game had expired they would hastily push to move onward. devs attempt to keep it selling was probably the multiplayer, coop, more stuff to buy just a bit more development time.
The upside is they may have learned lessons from this title hopefully and carry that forward to an overall less buggy experience on the next title. They might not but, only one way to know for sure.
As far as the rest you make solid points. I just cannot figure it out and the bug is so on and off. Sometimes it can be severe. sometimes it barely exists. It effects countless reliable machines that have been tested which is what makes it particularly tough to diagnose and fix. When i first encountered the bug i thought my machine was dying and i went through a whole A+ book just to make sure there was not something i was forgetting and still nothing. Everything turned out fine. The only common denominator is the game.I feel like as many people have dug into this game somebody would have tried something and made a community patch (maybe there is and i am unaware. If this was the case you probably would have recommended it though).
Its odd. You might be right. maybe this game or the engine is able to find the slightest flaw in any reliable system and BSOD it.
As for the next game, yeah i hope they do learn and slow down. You know like, dont push so much content before you fix more issues, even if they are minor. I like the dev teams i see in other games, using a bug table/board for everyone to see. Fixed, in progress, need more info and not a bug. Something players can view and "Oh, they know about/fixed that one for the next patch, good" or "They need more info? Ok i have some". They could do what others do too, give out keys to a separate test branch, one ahead of the Public patch and get a hundred players to report anything they find to you. They were far too secretive and quiet in the making of this game. Indie dev teams arent usually so silent, except their news and patches. As much excitement as their was from players, the return was FAQs in the first years, then basically nothing. They are missing out on so much of the "Hype factor" to players clamouring excitedly for more info. Going off topic of the bugs now, but you know what i mean lol.