Emulator Issues #12444
Mayflash GameCube Controller Adapter crashes PC to BSOD when using Dolphin 5.0-13817
Game ID? (right click the game in the game list, Properties, Info tab)
MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)
What's the problem? Describe what went wrong.
When plugging in (or having it already plugged in and set to Wii U/NS mode) the Mayflash 4-Port GameCube Controller Adapter into my laptop and then starting up Dolphin, it crashes to the BSOD with the error "KMOD_EXCEPTION_NOT_HANDLED". It did not have any indicator of what specifically is the issue as there were no other information that popped up. Running the stable 5.0 version of Dolphin causes no issues and I can use the adapter just fine. I also use an original GameCube controller. A crash does not happen when the switch on the back of the adapter is in "PC" mode and I can open Dolphin.
The specific adapter I am using for visual reference is on Amazon at this link: amazon.com/gp/product/B00RSXRLUE
What steps will reproduce the problem?
- Plug in the Mayflash 4-Port GC Adapter via USB cable and the switch on the back set to "Wii U/NS"
- Open Dolphin 5.0-13817.
- Crashes straight to BSOD.
- Start up Dolphin 5.0-13817
- Plug in the Mayflash adapter with "Wii U/NS" for the switch on the back.
- In Dolphin, if the GameCube controller Port 1 option was already set to "GameCube Adapter for Wii U", it will crash to BSOD.
- If set to "Standard Controller" beforehand, the BSOD will happen when I switch the option to "GameCube Adapter for Wii U".
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
Yes, 5.0-13817 and currently using it.
Is the issue present in the latest stable version?
No, not in 5.0.
If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)
N/A, but I do remember everything working well when I was testing the adapter the day I got it delivered back in late August 2020. I had always used the latest development versions, so it was somewhere between version 5.0-12481 and 5.0-12530, about 6 months and a week ago of writing this. Since then, I don't remember if I really used it much after so it'd be hard to pinpoint when it stopped working.
If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer
What are your PC specifications? (CPU, GPU, Operating System, more)
CPU: Intel Core i7-6700HQ @ 2.60GHz
RAM: 8 GB DDR3L SDRAM 2133 MHz
GPU: NVIDIA GeForce GTX 960M 4GB
OS: Windows 10 Home Version 2004 64-bit (OS Build 19041.804)
Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)
This can just happen with only plugging in the main black USB cable and not the grey cable. I went and see if disabling rumble in the configure window of Dolphin did much but the issue still persists.
I already had installed the correct driver before using Zadig and following the guide on using the adapter for Dolphin. I also reinstalled the driver for the adapter just in case anything was wrong but the problem was still there.
The only other thing I can think of is when I used the adapter on a Nintendo Switch the day before to play with some of my friends using GameCube controllers, but I don't think anything can be because of that.
There's no guarantee that this is actually Dolphin causing the issue. There may be another program also listening to libusb devices on your computer causing a conflict/bluescreen. If you do believe that this is a direct fault in Dolphin, please try to bisect down to an exact change. I know it is a pain in the ass since the manifestation of the bug is a bluescreen, but without being able to reproduce it myself it's the best change toward us figuring out what's going on.
- File 030821-11062-01.dmp 030821-11062-01.dmp added
- File 030821-10890-01.dmp 030821-10890-01.dmp added
- File 030821-10765-01.dmp 030821-10765-01.dmp added
- File 030821-10718-01.dmp 030821-10718-01.dmp added
- File 030821-10593-01.dmp 030821-10593-01.dmp added
- File 030821-10546-01.dmp 030821-10546-01.dmp added
You should be able to use a tool like WhoCrashed to see which driver triggered the exception.
So I downloaded it and this is the info that it gives me for the crashes.
On Mon 3/8/2021 2:49:08 PM your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\030821-10546-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8046BBEBC02, 0x0, 0x18) Error: KMODE_EXCEPTION_NOT_HANDLED file path: C:\WINDOWS\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Since I was doing it multiple times yesterday, the main differences in the other crashes is different bugcheck codes. I uploaded the dump files if anyone wants to look at them and if it helps at all.
There may be another program also listening to libusb devices on your computer causing a conflict/bluescreen. If you do believe that this is a direct fault in Dolphin, please try to bisect down to an exact change.
So after some testing, I actually found out that Logitech G Hub is the problem, although I'm not sure what or if Dolphin can do about it. I got my new mouse a while back to use with G Hub and during that period until now, I didn't use Dolphin. I took the time and did some more testing with this in mind.
Within Logitech G Hub, it's already set to auto startup when I login to Windows. When I open Dolphin and plug my GameCube adapter in and select the adapter in the controller config, BSOD.
If I close G Hub after starting up Windows, then go through Dolphin, it all works fine and no BSOD.
If I open G Hub after having Dolphin open with the adapter plugged in and in use, it disconnects and prioritizes G Hub. This even happens when I don't have my Logitech mouse plugged in. Closing G Hub, then closing and reopening Dolphin, and reconnecting the GameCube adapter starts working again. No BSOD.
I did notice when I open G Hub with Dolphin already opened, I get the Windows device disconnect sound that disconnects the GameCube adapter.
I updated my Logitech G Hub program to see if they did any change on their end, but their latest version still caused the issue. All in all, their G Hub conflicts with the Mayflash GameCube adapter it seems, since I didn't really had a problem with other devices.
I'm not sure where to take this issue from here, but I'm glad I found out what the problem was.
Hmm, ntoskrnl.exe is rather non-specific so that doesn't really help to narrow down the actual problem. I have a friend using Logitech G Hub and the Mayflash GC Adapter without any BSOD occurring, so it still seems like there's something screwed up about your particular system, though I don't have any clue as to what.