Monster Hunter Wilds

Monster Hunter Wilds

View Stats:
CLOCK_WATCHDOG_TIMEOUT
I was wondering if anyone else has been getting PC crashes with this game with this game with CLOCK_WATCHDOG_TIMEOUT as a response?

I have:
12th Gen Intel(R) Core(TM) i9-12900KF
NVIDIA GeForce RTX 4070

I can run modern games just fine. I have been playing Marvel Rivals and Pirate Yakuza without any PC crashes, its just Monster Hunter. Viewing the threads and it feels like this one hasnt been documented
Originally posted by Nana998:
For those who encountered this, are you guys using a dualsense/dualshock controller? If so, try using a different controller or mnk. There are reports of BSOD after the update when using DS controller, many have resolved this issue once they swapped out DS controller.
< >
Showing 1-15 of 120 comments
https://steamcommunity.com/sharedfiles/filedetails/?id=3441180997

Were you in suja? Because this strange location with nothing happening brings cpu to constant 95-100%, while desert hub is 50% after loading
Yep, I only started getting it at the black flame fight. I fight it for a good 5ish mins then it crashes and I get blue screen with same error. Tried suggested fixes but still crashes.
Originally posted by ❤️ニューハーフ:
https://steamcommunity.com/sharedfiles/filedetails/?id=3441180997

Were you in suja? Because this strange location with nothing happening brings cpu to constant 95-100%, while desert hub is 50% after loading

This has been happening constantly throughout multiple points in the game. When I was refighting Quematrice for armor, when I was trying to get to the forest, and most recently (right before I made this thread) on the cutscene right before the lala barina fight
This PC Mar 9 @ 8:55pm 
update chipset drivers
I think I used to get this specific bluescreen with unstable CPU overclocks. After bringing things down a bit it stopped happening on my system.
Originally posted by This PC:
update chipset drivers
I wish these forums added captcha so capcom bots won't post nonsense here

Originally posted by LexoRavi:
Originally posted by ❤️ニューハーフ:
https://steamcommunity.com/sharedfiles/filedetails/?id=3441180997

Were you in suja? Because this strange location with nothing happening brings cpu to constant 95-100%, while desert hub is 50% after loading

This has been happening constantly throughout multiple points in the game. When I was refighting Quematrice for armor, when I was trying to get to the forest, and most recently (right before I made this thread) on the cutscene right before the lala barina fight


This is the only place so far i got bsod message pop up instead of completely freezing pc

Originally posted by MeteoImpact:
I think I used to get this specific bluescreen with unstable CPU overclocks. After bringing things down a bit it stopped happening on my system.

another bot, i did not touch anything related to CPU
Last edited by ❤️ニューハーフ; Mar 9 @ 8:59pm
This PC Mar 9 @ 8:58pm 
Originally posted by MeteoImpact:
I think I used to get this specific bluescreen with unstable CPU overclocks. After bringing things down a bit it stopped happening on my system.

Yeah this error is related to hardware struggling to communicate with CPU, very simply put. This can be caused by overheating CPU and overclocks. Temp monitoring might help~ ^^''
Last edited by This PC; Mar 9 @ 8:59pm
Originally posted by This PC:
Originally posted by MeteoImpact:
I think I used to get this specific bluescreen with unstable CPU overclocks. After bringing things down a bit it stopped happening on my system.

Yeah this error is related to hardware struggling to communicate with CPU, very simply put. This can be caused by overheating CPU and overclocks. Temp monitoring might help~ ^^''
not being capcom sheep might help^^
This PC Mar 9 @ 8:59pm 
Originally posted by ❤️ニューハーフ:
I wish these forums added captcha so capcom bots won't post nonsense here

Sorry for actually trying to help instead of blaming game. ;p
This PC Mar 9 @ 9:01pm 
Originally posted by ❤️ニューハーフ:
not being capcom sheep might help^^

I mean, you have an issue, I don't, I'm trying to give you solutions. I enjoy the game, you don't, I guess you can keep suffering your blue screens, I'll keep enjoying the game.
Needing to construct a fantasy of me in your head so you can deconstruct it to maintain your biases says a lot about you. Enjoy your echo chamber and your IT problems. <3
Last edited by This PC; Mar 9 @ 9:02pm
Originally posted by MeteoImpact:
I think I used to get this specific bluescreen with unstable CPU overclocks. After bringing things down a bit it stopped happening on my system.

I have not overclocked my CPU, do you happen to have any other suggestions?
Last edited by LexoRavi; Mar 9 @ 9:04pm
Originally posted by This PC:
update chipset drivers
My apologies I think I skimmed this while scrolling past the argument. Ill try that now
CLOCK_WATCHDOG_TIMEOUT
Is caused by a a driver incompatibility or corruption. Trying DDUing your gpu drivers.
This PC Mar 9 @ 9:11pm 
Originally posted by LexoRavi:
Originally posted by This PC:
update chipset drivers
My apologies I think I skimmed this while scrolling past the argument. Ill try that now

I understand lol ._.
I have some other solutions, but we'll start there, I'll check thread when I get up to help some more if it hasn't solved it. >//<
Originally posted by ❤️ニューハーフ:
Originally posted by MeteoImpact:
I think I used to get this specific bluescreen with unstable CPU overclocks. After bringing things down a bit it stopped happening on my system.

another bot, i did not touch anything related to CPU
Uhh, I was responding to the specific error that OP brought up? I used to get this crash sometimes when playing PSO2:NGS, but it wasn't specifically the game causing it, just that my overclocks were actually unstable if the CPU was under load in some way that somehow wasn't getting caught in testing. Wilds may run like ♥♥♥♥♥♥♥, but that doesn't mean it's necessarily the root cause of the system crash being observed.

EDIT: And immediately calling me out as a Capcom shill is pretty amusing when my review for the game fell on the side of "not recommended".
Last edited by MeteoImpact; Mar 9 @ 9:15pm
< >
Showing 1-15 of 120 comments
Per page: 1530 50

Date Posted: Mar 9 @ 8:38pm
Posts: 120