Monster Hunter Wilds

Monster Hunter Wilds

View Stats:
PC restarts itself because of using Controller
capcom You need to solve this problem urgently. Since the new patch, the community has been saying that they can't use the PS5 Controller at all. When I play on PC, the screen goes black and then restarts immediately. I've been stuck here for days and there's no way the team will fix anything
< >
Showing 1-15 of 16 comments
I'm using a Dualsense Edge and I had BSOD after a while of playing. What seems to have fixed it for me was disabling bluetooth on my PC. If you're using Win 11 you just press the volume buttom in the lower right and then press the bluetooth icon so it becomes grey.

Just to be clear, even if it works I don't think this is an acceptable fix. We shouldn't need to disable bluetooth. They need to get their ♥♥♥♥ together and fix their game, including the performance.
Last edited by Citronvand; Mar 17 @ 1:16pm
Fenix Mar 18 @ 11:12am 
My PC doesn't have/support Bluetooth, but it still does this with my Dualsense.
Citronvand Mar 18 @ 12:08pm 
Yeah nevermind, I just had a BSOD again with bluetooth disabled. I did manage to play for several hours, probably over 10, so I thought it fixed it. Guess not.
NiamhNyx Mar 18 @ 12:10pm 
I think it might just be a windows problem. I have 0 issues with my dualsense controller unless windows decides to be a ♥♥♥♥ that day.
Citronvand Mar 18 @ 12:22pm 
Originally posted by NiamhNyx:
I think it might just be a windows problem. I have 0 issues with my dualsense controller unless windows decides to be a ♥♥♥♥ that day.
But I've used my Dualsense edge on probably hundreds of games by now and it is ONLY Monster Hunter Wilds that has caused blue screens. So in my opinion it is the game's fault, not windows.

Going to try out https://www.reddit.com/r/WindowsHelp/comments/1j861m4/bluescreens_with_clock_watchdog_timeout_mostly/
NiamhNyx Mar 18 @ 12:29pm 
Originally posted by Citronvand:
Originally posted by NiamhNyx:
I think it might just be a windows problem. I have 0 issues with my dualsense controller unless windows decides to be a ♥♥♥♥ that day.
But I've used my Dualsense edge on probably hundreds of games by now and it is ONLY Monster Hunter Wilds that has caused blue screens. So in my opinion it is the game's fault, not windows.

Going to try out https://www.reddit.com/r/WindowsHelp/comments/1j861m4/bluescreens_with_clock_watchdog_timeout_mostly/
chances are, if wilds is causing the blue screen its not the controller either. Its either going to be an issue with windows or one of the games bugs that just happens at coincidental times.

I have a dualsense controller that is plugged in to my pc and it works perfectly fine in every game until windows decides to be a ♥♥♥♥.

Also bluetooth and playstation controllers have always had random issues on pc, so i would never recommend using one with out plugging it in on windows.
Wilds with a wireless ps5 controller causes steam to crash. This is confirmed. No fix yet so keep it wired.
Turn off all the overlays you have, steam included.
PS4 dual shock controller user here. Wired USB. I have not had this happen to me yet. I realize the thread is about PS5 controllers, but I just wanted to add my data point in the small chance that it helps somehow.
Originally posted by xavier434:
PS4 dual shock controller user here. Wired USB. I have not had this happen to me yet. I realize the thread is about PS5 controllers, but I just wanted to add my data point in the small chance that it helps somehow.

Noted.
Not Cal Mar 19 @ 3:13am 
I noticed this did not happen until recently so I was able to finish high rank without crashing, basically started since the update for me.

So wiring the controller will stop this from happening ?
I was getting BSOD with clock watchdog timeout starting this weekend after having no issues since launch. I ended up switching from ps5 controller to a switchpro controller and that solved the issue. such an odd problem.
NiamhNyx Mar 19 @ 7:59pm 
Originally posted by Serrassi Effect:
I was getting BSOD with clock watchdog timeout starting this weekend after having no issues since launch. I ended up switching from ps5 controller to a switchpro controller and that solved the issue. such an odd problem.
bluetooth is jank sometimes, its why wired is always the way to go.
Originally posted by Citronvand:
Yeah nevermind, I just had a BSOD again with bluetooth disabled. I did manage to play for several hours, probably over 10, so I thought it fixed it. Guess not.

I've only ever used my dualsense wired and had tons of system-wide crashes. Even when using remote play on my steam deck just having the dualsense plugged in. Since swapping to a switch pro controller, none of the crashes that force me to shut down my pc
Haylel Mar 19 @ 10:28pm 
Originally posted by NiamhNyx:
Originally posted by Serrassi Effect:
I was getting BSOD with clock watchdog timeout starting this weekend after having no issues since launch. I ended up switching from ps5 controller to a switchpro controller and that solved the issue. such an odd problem.
bluetooth is jank sometimes, its why wired is always the way to go.

I have thousands of hours in hundreds of games of bluetooth not being jank.
The only one that has ever caused a problem for me is mhwilds and only since this patch.
< >
Showing 1-15 of 16 comments
Per page: 1530 50

Date Posted: Mar 17 @ 1:05pm
Posts: 16