Emulator

Game Name?

N/A

Game ID? (right click the game in the game list, Properties, Info tab)

N/A

MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)

N/A

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?

1. Plug in the Mayflash 4-Port GC Adapter via USB cable and the switch on the back set to "Wii U/NS"
2. Open Dolphin 5.0-13817.
3. Crashes straight to BSOD.

OR

1. Start up Dolphin 5.0-13817
2. Plug in the Mayflash adapter with "Wii U/NS" for the switch on the back.
3. In Dolphin, if the GameCube controller Port 1 option was already set to "GameCube Adapter for Wii U", it will crash to BSOD.
4. 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

N/A

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.