Project

General

Profile

Actions

Emulator Issues #11986

open

KMode Exception Not Handled in Bluetooth Passthrough mode past Dolphin 5.0-2341 Windows

Added by Dolphinish almost 5 years ago. Updated over 3 years ago.

Status:
Questionable
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
Windows
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

Game Name?

Every Wii game

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

Does not apply

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

Does not apply

What's the problem? Describe what went wrong.

I have an original Bluetooth Module soldered to a usb cable and using Bluetooth passthrough. The libusbK Driver is installed for the module and it was working fine up until Dolphin 5.0-2341. I downloaded version 5.0-11309 around beginning of December and starting from this version, launching a game with Bluetooth Passthrough enabled causes a bluescreen of death: KMode Exception Not Handled. I have not tested every version in between 2341 and 11309, so all I can say it worked. I am still forced to use this version when using bluetooth passthrough.
I have two Bluetooth modules and they are both causing the BSoD.

What steps will reproduce the problem?

Launching any game with Bluetooth Passthrough enabled on versions greater than 5.0-2341 - but I have not verified on what version the problem started emerging.

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, still present in 5.0-11669

Is the issue present in the latest stable version?

No, because the feature didn't exist yet.

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.)

Every broken build to test takes 2 minutes because of the bluescreen and the reboot, so I cannot verify it.

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

[Attach any fifologs if possible, write a description of fifologs and screenshots here to assist people unfamiliar with the game.]

What are your PC specifications? (CPU, GPU, Operating System, more)

Intel Core i7 9700K, RTX 2080Ti, Windows 10 1909, Bluetooth passthrough, Original Wii Bluetooth module.

Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)

[Anything else here]

This is what I thought might be interesting from the Event Viewer.

BTHUSB
**The local adapter does not support an important Low Energy controller state to support peripheral mode. The minimum required supported state mask is 0x2491f7fffff, got 0x1fffffff. Low Energy peripheral role functionality will not be available.
**
If I should post additional infos from the event viewer, please let me know.

Actions #1

Updated by JosJuice almost 5 years ago

For the reference, the version after 5.0-2341 would be 5.0-2352 "IOS: USB support (OH0, USB_VEN, USB_HID)".

Actions #2

Updated by Dolphinish almost 5 years ago

I have downloaded version 5.0-2352 and it is in fact the version that causes the BSoD with Bluetooth Passthrough. I must have kept version 5.0-2341 for that reason in my backup folder.

So starting from version 5.0-2352 - 5.0-11669 - bluetooth passthrough causes a BSoD

Actions #3

Updated by leoetlino over 3 years ago

  • Operating system Windows added
  • Operating system deleted (N/A)

Unfortunately I'm not sure there's much we can do -- this sounds like a libusb (libusbK driver?) issue because nothing Dolphin does should be able to BSOD the entire system. And updating libusb was required to fix other USB related issues so downgrading is not an option. :/

We could try to update again (to 1.0.24; I think we're currently on 1.0.23-rc1) but I'm not confident that will fix the issue.

Actions #4

Updated by JMC4789 over 3 years ago

  • Status changed from New to Questionable

If this isn't Dolphin's problem then I'm not sure if there's a reason to keep this open.

Actions

Also available in: Atom PDF