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
What I figured out - BSOD only occurs in Hunt, when I have USB microphone plugged, I repeat - only in HUNT it causes the problem, any other game or communication program works fine.
I think they introduced something on the server side since I was able to play normally with 1.4.9 for pretty long, whatever was introduced recently, less than 1 month ago - a check or a telemetry or a system call or whatever is causing absolutely random BSOD. Which points to different system errors, KERNEL exceptions, Memory non paged AREA, random driver.sys, priveledge escalation, IRQL not less or equal, or whatever, seen all of them. Drivers that showed up were everything from network, sound, xbox controller, HID device, system drivers, windows drivers, nvidia drivers etc.
Sometimes it causes BSOD upon joining server, sometimes 2 minutes later, sometimes 12-15 minutes later, the longest one I was able to play was 35 minutes.
OFC drivers and windows are all latest version and there is NO overclocking on my system.
Ditched playing Hunt after that. Bad coders to blame I guess.
Notice the cause:
Hunt is not there. :) Games are not there. Any client software is not there. Only kernel side software (such as the operating system itself and drivers).
If you want this to be fixed, you have to look into your PC. Load the BIOS defaults. Update your drivers.
Update: if the anti-cheat software has kernel-level integration, it may cause the problem as well. However, the majority of the time is incorrect overclocking settings. Just load the BIOS defaults and the problem should be fixed.
BLAH BLAH BLAH, It Is YeR CoMpUtEr HeNt Is PeRfiCt No FlAwS. Thanks captain obvious, next time when you copy/paste wiki please be sure to read it yourself. The EAC is also in the list of BSODs and it is part of Hunt "package".
GG :D
Simply running a test on your RAM won't necessarily expose where the issue is. Google the error code, and keep your memory dumps so that they can be analysed by someone who can make sense of them.
Attitudes like this get you nowhere. It's not up to the devs to fix your computer. Having experienced BSODs in Hunt (and only in Hunt) like Shakaron says, I've addressed where the issue was and fixed it. Guess what, no more BSOD's in Hunt since.
Whine all you like, but I absolutely guarantee you, the BSOD problem is not with the game (or any game for the matter). It's 100% to do with something in your software
or hardware setup.
Which your pc can not handle ( at times). Do you overclock? When I use to max out my overclock on my old pc, I use to run into that problem. I kicked it down ( both GPU & CPU)
and BSOD stopped.
There could be other factors causing this too. How many programs running in background while your playing?
A few times my new rig just shut down while playing. Which was very disturbing!
After some digging in to as why, I isolated the reason to windows update. I had it scheduled to install, etc.
I had forgotten about that and have since turned that off. No more issues.
Something is causing your rig to shut. It could be as simple as your spyware or your antivirus.
Don't panic. Just take the time to go through all your programs.
I always say, go to task manager. Start up. Turn off all but microsoft. You have an option to hide those. Then reboot. Play the game. If no crashes, go back to TM and enable 1st program to start.
Re boot and play. No problems go do the steps again. Keep repeating untill you find what program is causing the issue.
Hope this helps.
🤠
Hunt is very very clunky even on fully optimized machines like mine. To tell someone who seems to have realy checked his system bevore opening this thread "it´s not Hunt. It´s your PC - Hunt is not there... Hunt is fine" is just wrong.
My System is overclocked like hell - but tested. Everything runs fine. Karhu 15000%+ no problem, all other games / benchmarks and even full-load-software like occt / prime95 etc. are running forever if i want to.
But with the new Update-Release my System is crashing randomly about 1-3 Times / hour when i play Hunt. So ... you tell me it is not Hunt, it is my computer? If yes, mkay - you got no clue what youre talking. Hunt is just a bad bunch of code :)
I identyfied the RAM oc as problem. if i am pushing the ram down a bit, the crashes are stopping. But that setting could do Karhu forever - if you know that software, you will maybe know that RAM witch are testet with it, are stable - ROCKSTABLE if you get above 15k%+
But Hunt manages to crash the RAM :D nono.... it´s not the setting mate, it´s the ♥♥♥♥♥♥♥ Game.
Very good game, i love it - but it´s clunky and it is crashing systems becouse of bugs, not becouse systems are badly configurated.
your BSOD when playing?
I start to hear the sound from the speakers: Brrrrrrr, and then a blue screen appears and restarts in the BIOS. I really can't figure out what is the reason for the blue screen. The most interesting thing is that the blue screen only appears during the game Hunt: Showdown. In other games, there are no problems like that.
This can happen at any time during the game.
0x0000000000000010
0xFFFFA68E517C6028
0XFFFFA68E45D25B5c
0xFFFFA68E45E7B1A0