nefarius / bthps3 Goto Github PK

View Code? Open in Web Editor NEW

563.0 18.0 26.0 19.45 MB

Windows kernel-mode Bluetooth Profile & Filter Drivers for PS3 peripherals

Home Page: https://docs.nefarius.at/projects/BthPS3/

License: BSD 3-Clause "New" or "Revised" License

C 21.40% C++ 4.91% C# 1.30% Batchfile 0.08% PowerShell 0.60% Roff 0.97% Shell 0.15% HTML 70.58%

playstation dualshock3 bluetooth windows driver

bthps3's Introduction

About ✨ Nefarius ✨

Hello there 👋 welcome to my GitHub profile!

I'm a Software Developer from Austria 🇦🇹 (not Australia 🦘)!

I've started tinkering with code in my late teens, trying to automate some tasks and generally try to understand how programs work. Later in life when beginning my professional career I turned my back on coding and focussed on project management and infrastructure design, support and maintenance of common Microsoft products (Windows, Active Directory, SQL Server, ...) and DevOps topics. Around 2014 I started to get back into programming by taking over a rather large and successful community project and extended my roster of open-source solutions ever since.

Nowadays I am consulting on, designing and developing Windows kernel (and user-mode) drivers for gaming peripherals and other low-level challenges. With every new project I extend my portfolio and toolbox, I primarily develop in - but am not limited to - C and C#. Besides driver shenanigans I also create and maintain backend services and middleware based on .NET Core and ASP.NET Core and I have authored the occasional web application. I am versed in reverse engineering and have a deep understanding of common communication protocols like USB, Bluetooth, HID and RS-232 emulation. When necessary I'll also dust off the soldering iron to fix some PCBs!

Sounds interesting? You can book my services! Head over to my website for more information!

🛠️ Languages and Tools

🔥 Statistics

🏆 Awards

bthps3's People

Contributors

Stargazers

Watchers

bthps3's Issues

Conflict with Dualshock 4 on Bluetooth (connection error)

I have searched open and closed issues for duplicates
I am submitting a bug report for existing functionality that does not work as intended
I have read https://vigem.org/Community-Support/
This isn't a feature request or a discussion topic

Bug description

When installing BthPS3, the dualshok4 bluetooth connection stopped working (I need to use dualshok3 and dualshok4 at the same time). Windows says that the gamepad is connected, but after a second the connection disappears. dualshok4 itself continues to blink while waiting for connection.

There is a funny situation that dualshok4 connects via Bluetooth and everything works, but only as a new device (if it has never been connected before or it has been deleted in Bluetooth devices). But with subsequent automatic connections, the failure described above occurs.

Before installing BthPS3, I could automatically connect dualshock 4 via bluetooth. And also I could use dualshock 3 via USB after installing DsHidMini. I use DS4Windows and all gamepads were displayed correctly there.

Steps to reproduce

Installed BthPS3
Installed DsHidMini
Launched DsHidMini
Connected dualshock3 via USB (the error is reproduced without this action)
A connection was established with dualshock3 (the error is reproduced without this action)
Disconnected dualshock3 from USB (the error is reproduced without this action)
Connected dualshock3 via Bluetooth (the error is reproduced without this action)
Turning on dualshock 4
I search for devices in the windows bluetooth settings
Connecting dualshock 4 (windows remembers the device)
To check, I disable dualshock 4
Turning on dualshock 4 again
There is an automatic connection (an error occurs here)

Actual result:
Windows writes that dualshock 4 is connected, but after a second the connection is disconnected. And dualshock 4 continues to flash the indicator while waiting for connection.
Expected result:
DualShock 4 automatically connects to a PC via bluetooth

Screenshots

I can take screenshots (if necessary), but they won't be able to convey much information. I tried to write the error in some detail.

Machine info

CPU-Architecture: x64
Windows version: Windows 10 Pro 22H2
Software/driver version(s): v2.6.174

Any other helpful information

DS4Windows version(s): v3.2.10
DsHidMini Driver: v2.2.282

I have an assumption that BthPS3 perceives dualshock4 as dualshock3 and tries to transmit connection information to it (although I connect via the standard bluetooth settings tools in windows). As I read, the driver intercepts bluetooth traffic and splits it to connect dualshock3. But dualshock4 does not expect this and the connection fails.

BthPS3.sys DRIVER_POWER_STATE_FAILURE restoring from hibernate - Windows 10/11

BthPS3 version v2.0.144
Windows 11 version 22000.100
Had a DRIVER_POWER_STATE_FAILURE after restoring from Hibernate

WinDBG log as follows:

Microsoft (R) Windows Debugger Version 10.0.21349.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\072521-27953-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*C:\Symbols*https://msdl.microsoft.com/download/symbols
Symbol search path is: srv*C:\Symbols*https://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 10 Kernel Version 22000 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff806`7da00000 PsLoadedModuleList = 0xfffff806`7e629600
Debug session time: Sat Jul 24 21:13:06.253 2021 (UTC - 4:00)
System Uptime: 0 days 2:58:38.079
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
........................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`7de129b0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffb70f`58a8f6a0=000000000000009f
7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an IRP for too long a time
Arg2: ffffb88a95fe5a70, Physical Device Object of the stack
Arg3: ffffb70f58a8f6d0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffb88abb075010, The blocked IRP

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for BthPS3.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3999

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 14693

    Key  : Analysis.Init.CPU.mSec
    Value: 983

    Key  : Analysis.Init.Elapsed.mSec
    Value: 603378

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 90

    Key  : WER.OS.Branch
    Value: co_release

    Key  : WER.OS.Timestamp
    Value: 2021-06-04T16:28:00Z

    Key  : WER.OS.Version
    Value: 10.0.22000.1


TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


BUGCHECK_CODE:  9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffb88a95fe5a70

BUGCHECK_P3: ffffb70f58a8f6d0

BUGCHECK_P4: ffffb88abb075010

DRVPOWERSTATE_SUBCODE:  3

DRIVER_OBJECT: ffffb88a80632e10

IMAGE_NAME:  BthPS3.sys

MODULE_NAME: BthPS3

FAULTING_MODULE: fffff8069a6f0000 BthPS3

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffb70f`58a8f698 fffff806`7dfc2ca7     : 00000000`0000009f 00000000`00000003 ffffb88a`95fe5a70 ffffb70f`58a8f6d0 : nt!KeBugCheckEx
ffffb70f`58a8f6a0 fffff806`7dfc2bc1     : ffffb88a`89eac208 00000000`00000080 ffffb70f`58a8f9f8 ffffb70f`58a8f9f0 : nt!PopIrpWatchdogBugcheck+0xdf
ffffb70f`58a8f710 fffff806`7dc12824     : 00000000`00000000 ffffb88a`00000001 ffffb70f`00000000 ffffb88a`00000002 : nt!PopIrpWatchdog+0x31
ffffb70f`58a8f760 fffff806`7dc10e14     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff806`7aa52648 : nt!KiProcessExpiredTimerList+0x204
ffffb70f`58a8f890 fffff806`7de168fe     : 00000000`00000000 ffff8101`9fdd6180 ffff8101`9fde2240 ffffb88a`86bbd080 : nt!KiRetireDpcList+0x714
ffffb70f`58a8fb40 00000000`00000000     : ffffb70f`58a90000 ffffb70f`58a89000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x9F_3_IMAGE_BthPS3.sys

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {328a30da-bacc-a428-20ed-22a427c03a3c}

Followup:     MachineOwner
---------

BthPS3 installer breaks/uninstall ViGEmBus

Tested on v2.1.153

This issue is currently a draft

Installing or uninstalling BthPS3 (can't remember right now) causes ViGEmBus to not be detected anymore by applications looking for it. I'm not sure if the driver itself does not get loaded anymore by Windows or if it's loaded but applications can't find it.

Regardless, it's possible to just re-install the ViGEmBus without major problems.

To-do

Reproduce the issue again to check if the ViGEmBus still appears as installed on windows' Apps and Features list or is present in the Device Manager

RUMBLE NOT WORKING PANHAI CONTROLLER

The controller worked with SCP for a bit (latest version) and then it stopped i tried old SCP wtih DLL fix by some guy it worked but i got lazy since it's annoying to turn on again via bluetooth and also no vibration
with Latest SCP ver i can get rumble via USB but controller doesn't work with bluetooth like i said
i tried BthPS3 and the controller works automatically with bluetooth but there is no rumble should i give up? xD

DS3 Bluetooth Connecting to slot 4

My genuine 409B-CECHZC2U controller is working fine on USB, but whenever I try to use Bluetooth it connects to Slot 4. I cannot find a way to change this behavior. I'm sorry if this is explained somewhere, I have tried looking and failed.

USB\VID_0A12&PID_0001 Issue (USB BT Adapter)

Hi it's me again, so I ended up ordering another Bluetooth adapter from Amazon that I was sure would work with this.
Unsurprisingly with my luck, it did not end up working. (Code 10, same old stuff)

I feel like its due to the fact that I have two BT adapters now, my built in one and this usb one I got, but I don't know how to confirm that theory.

I attached the ETL file below, hope it helps.

BthPS3.zip

Driver Picking up Stray Controllers

[ x] I have searched open and closed issues for duplicates
[ x] I am submitting a bug report for existing functionality that does not work as intended
[ x] I have read https://vigem.org/Community-Support/
[ x] This isn't a feature request or a discussion topic

Bug description

Driver software is picking up other DS3 controllers that aren't mine.

Steps to reproduce

Start any unpaired DS3 near computer.

Actual result: Other family member's controller connecting to my pc.
Expected result: Only my controller should connect.

Machine info

CPU-Architecture: x64
Windows version: Windows 10 10.0.19042
Software/driver version(s): Unsure

Other Info

We found this out entirely by mistake. I only ever use my controller with my pc. I went to my family member's room, who was trying to connect their controller to their pc, and heard noise from mine as if something connected. Found out both controllers are able to connect with my pc, but I've never done anything with the other controller to connect it with this machine.

Add new supported SIXAXIS names

The name PLAYSTATION(R)3Controller-ghic (without the spelling mistake) is also out there in the wild and works, add to INF in next update.
Add Sony PLAYSTATION(R)3 Controller (reported by Bilious on Discord).

problem trying to install bthps3 on windows 7 64 bit

My problem is that I was trying to install BTHPS3 on a PC with Windows 7 64 bits because on my PC with Windows 11 it didn't work and the installer said the following:
Nefariurs BTHPS3 Bluetooth Drivers Setup Wizard ended Prematurely

Attached install log file
install.txt

Fake ps3 controller connection issue

I have searched open and closed issues for duplicates
I am submitting a bug report for existing functionality that does not work as intended
I have read https://vigem.org/Community-Support/
This isn't a feature request or a discussion topic

Bug description

While it works using usb cable, my ps3 fake controller can't connect over bluetooth to my pc. Walked over discussions and wasn't able to find a way to debug this issue, if it's possible can you please share instructions on how to debug bluetooth connectivity issue or check if this ps3 fake controller is already compatible with BthPS3 🙏

Actual result: I remember when testing with scpToolkit I see in the monitor that the controller is connected during couple of seconds then disconnected, logs show a connect request ... then a disconnect request (not sure if it's related but I remember reading somewhere that this might be related to the fake ps3 controller not being able to connect securily over bluetooth when using win 10)

Machine info

CPU-Architecture: x64
Windows version: Windows 10 21H2
PS3 controller hardware id: HID\VID_054C&PID_0268&REV_0100 (what is written in the controller back: model no CECHZC2U)
Bluetooth hardware: Dell Wireless 365 Bluetooth Module Driver (driver version 10.0.19041.1682)

Many thanks for this great project ❤️

DS3 connects via bluetooth only for few seconds

I have searched open and closed issues for duplicates
I am submitting a bug report for existing functionality that does not work as intended
I have read https://vigem.org/Community-Support/
This isn't a feature request or a discussion topic

Bug description

I tried it both on desktop and laptop with Bluetooth. Both same result (soon will test if it couldn't be a dead battery in my newly bought DS3).

Steps to reproduce

I check my UAC settings
Install Bluetooth driver + restart
Install ds hid mini driver
Connect controller via USB => there my controller shows and works via USB
Disconnect controller => for a second or two a Bluetooth connection with DS3 pops up. Here I managed to click and screenshot it while it opens for 1s:

Expected result: I believe it should pair when I connect it, and connect to Bluetooth when I disconnect it

Machine info

CPU-Architecture: Both intel i7 and AMD Ryzen 9 tested
Windows version: Windows 10 Pro 19045 build / The laptop with i7 is Windows 10 Home not sure which version
Software/driver version(s):

how to conect to bluethooth with windows 11

how do i connect to bluetheeth with windows 11 it keeps asking for a pin its not 0000 its not 1234 what is the stupid pin this has to be a bug right ?

"Enable PSM patching" re-enables itself on reboot

I have searched open and closed issues for duplicates
I am submitting a bug report for existing functionality that does not work as intended
I have read https://vigem.org/Community-Support/
This isn't a feature request or a discussion topic

Bug description

After having disabled the PSM patching, by unticking the checkbox for it, and restarting the computer, the checkbox has automatically ticked itself again. It doesn't seem like the setting is stored anywhere. I think it's supposed to be stored in the registry on a value called "IsPSMPatchEnabled", but this doesn't seem to get written anywhere.

I've uninstalled and reinstalled the utility, but the problem remains.

Note that disabling the filter does work as intended while keeping the computer running. It's just that it re-enables itself on reboot.

Steps to reproduce

Install BthPS3.
Start the utility.
Click yes in the elevation prompt.
Go to tab "Filter Driver Settings".
Untick "Enable PSM patching.
Close the utility and restart the computer.
Open the utility again.

Actual result: The checkbox is ticked again. And the filter is active.
Expected result: The checkbox should remain unticked and the filter should remain inactive.

Screenshots

Machine info

CPU-Architecture: x64
Windows version: Windows 10 Enterprise 22H2
Software/driver version(s): v2.6.174

Any other helpful information

Here is a discussion of the problem in Discord:
https://discord.com/channels/346756263763378176/1025174973498789918/1099328923738837013

Problem during installation of BthPS3 on Windows 11

Hello, I have this issue, I can't install :(
ScpToolkit work a charm but the wireless randomly no longer works after computer reboot with my Dualshock 3

error

BSOD on disconnect

DRIVER_IRQL_NOT_LESS_OR_EQUAL

Technically a BthPS3 bug but appeared in combination with DsHidMini. Occurred on disconnect. Currently not reliably reproducible. Under investigation.

Bugcheck

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000084f20, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8007b244f0d, address which referenced memory

Call stack

3: kd> kc
 # Call Site
00 nt!KeBugCheckEx
01 nt!KiBugCheckDispatch
02 nt!KiPageFault
03 BthPS3!WdfObjectGetTypedContextWorker
04 BthPS3!GetServerDeviceContext
05 BthPS3!L2CAP_PS3_ConnectionIndicationCallback
06 BTHport!L2CapCon_CallClientCallbackForRemoteDisconnect
07 BTHport!L2CapCon_HciConnectCallback
08 BTHport!HCI_CxnCallClientCallback
09 BTHport!HCI_CxnDrainMoveList
0a BTHport!HCI_HandleDisconnectionComplete
0b BTHport!Fn_EVENT_DisconnectionComplete
0c BTHport!HCI_DoCmdCompletion
0d BTHport!HCI_ProcessAsynchronousEvent
0e BTHport!HCI_ProcessEventAtDPC
0f BTHport!HCI_ProcessMpBip
10 BTHport!imp_BthLegacyRecvMpBip
11 BTHUSB!BthUsb_EventTransferComplete
12 BTHUSB!UsbWrapWorkRoutine
13 BTHUSB!UsbWrapInterruptReadComplete
14 nt!IopfCompleteRequest
15 nt!IofCompleteRequest
16 Wdf01000!FxIrp::CompleteRequest
17 Wdf01000!FxRequest::CompleteInternal
18 Wdf01000!FxRequest::Complete
19 Wdf01000!FxRequest::CompleteWithInformation
1a Wdf01000!imp_WdfRequestCompleteWithInformation
1b RtkBtfilter
1c RtkBtfilter
1d RtkBtfilter
1e nt!PspSystemThreadStartup
1f nt!KiStartSystemThread

Driver logs

3: kd> !wdfkd.wdflogdump BthPS3 -d
Trace searchpath is: 

Trace format prefix is: %7!u!: %!FUNC! - 
Trying to extract TMF information from - C:\ProgramData\Dbg\sym\BthPS3.pdb\19E0668804F04B958FCA38E819AFF14C1\BthPS3.pdb
--- start of log ---
1: BthPS3_RetrieveLocalInfo -  [BthPS3_RetrieveLocalInfo]Host radio HCI major version 10
2: BthPS3_RegisterPSM -  [BthPS3_RegisterPSM]Trying to register PSM 0x5053
3: BthPS3_RegisterPSM -  [BthPS3_RegisterPSM]Got PSM 0x5053
4: BthPS3_RegisterPSM -  [BthPS3_RegisterPSM]Trying to register PSM 0x5055
5: BthPS3_RegisterPSM -  [BthPS3_RegisterPSM]Got PSM 0x5055
6: BthPS3_IndicationCallback -  [BthPS3_IndicationCallback]New connection for PSM 0x5053 from 04367E4C6325 arrived
7: L2CAP_PS3_HandleRemoteConnect -  [L2CAP_PS3_HandleRemoteConnect] ERROR:BTHPS3_GET_DEVICE_NAME failed with status 0xc000000d(STATUS_INVALID_PARAMETER), dropping connection
8: BthPS3_IndicationCallback -  [BthPS3_IndicationCallback]New connection for PSM 0x5053 from 04367E4C6325 arrived
9: L2CAP_PS3_HandleRemoteConnect -  [L2CAP_PS3_HandleRemoteConnect]Device 04367E4C6325 name: PLAYSTATION(R)3Conteroller-PANHAI
10: L2CAP_PS3_HandleRemoteConnect -  [L2CAP_PS3_HandleRemoteConnect]Device 04367E4C6325 identified as SIXAXIS compatible
11: L2CAP_PS3_ControlConnectResponseCompleted -  [L2CAP_PS3_ControlConnectResponseCompleted]HID Control Channel connection established
12: BthPS3_IndicationCallback -  [BthPS3_IndicationCallback]New connection for PSM 0x5055 from 04367E4C6325 arrived
13: L2CAP_PS3_InterruptConnectResponseCompleted -  [L2CAP_PS3_InterruptConnectResponseCompleted]HID Interrupt Channel connection established
14: BthPS3_PDO_EvtWdfDeviceD0Exit -  [BthPS3_PDO_EvtWdfDeviceD0Exit]Requesting device disconnect
15: BthPS3_IndicationCallback -  [BthPS3_IndicationCallback]New connection for PSM 0x5053 from 04367E4C6325 arrived
16: L2CAP_PS3_HandleRemoteConnect -  [L2CAP_PS3_HandleRemoteConnect]Device 04367E4C6325 name: PLAYSTATION(R)3Conteroller-PANHAI
17: L2CAP_PS3_HandleRemoteConnect -  [L2CAP_PS3_HandleRemoteConnect]Device 04367E4C6325 identified as SIXAXIS compatible
18: L2CAP_PS3_ControlConnectResponseCompleted -  [L2CAP_PS3_ControlConnectResponseCompleted]HID Control Channel connection established
19: BthPS3_IndicationCallback -  [BthPS3_IndicationCallback]New connection for PSM 0x5055 from 04367E4C6325 arrived
20: L2CAP_PS3_InterruptConnectResponseCompleted -  [L2CAP_PS3_InterruptConnectResponseCompleted]HID Interrupt Channel connection established
21: BthPS3_PDO_EvtWdfDeviceD0Exit -  [BthPS3_PDO_EvtWdfDeviceD0Exit]Requesting device disconnect
22: BthPS3_PDO_EvtWdfDeviceD0Exit -  [BthPS3_PDO_EvtWdfDeviceD0Exit]Requesting device disconnect
23: BthPS3_IndicationCallback -  [BthPS3_IndicationCallback]New connection for PSM 0x5053 from 04367E4C6325 arrived
24: L2CAP_PS3_HandleRemoteConnect -  [L2CAP_PS3_HandleRemoteConnect]Device 04367E4C6325 name: PLAYSTATION(R)3Conteroller-PANHAI
25: L2CAP_PS3_HandleRemoteConnect -  [L2CAP_PS3_HandleRemoteConnect]Device 04367E4C6325 identified as SIXAXIS compatible
26: L2CAP_PS3_ControlConnectResponseCompleted -  [L2CAP_PS3_ControlConnectResponseCompleted]HID Control Channel connection established
27: BthPS3_IndicationCallback -  [BthPS3_IndicationCallback]New connection for PSM 0x5055 from 04367E4C6325 arrived
28: L2CAP_PS3_InterruptConnectResponseCompleted -  [L2CAP_PS3_InterruptConnectResponseCompleted]HID Interrupt Channel connection established
29: BthPS3_PDO_EvtWdfDeviceD0Exit -  [BthPS3_PDO_EvtWdfDeviceD0Exit]Requesting device disconnect
30: BthPS3_PDO_EvtWdfDeviceD0Exit -  [BthPS3_PDO_EvtWdfDeviceD0Exit]Requesting device disconnect
31: BthPS3_IndicationCallback -  [BthPS3_IndicationCallback]New connection for PSM 0x5053 from 04367E4C6325 arrived
32: L2CAP_PS3_HandleRemoteConnect -  [L2CAP_PS3_HandleRemoteConnect]Device 04367E4C6325 name: PLAYSTATION(R)3Conteroller-PANHAI
33: L2CAP_PS3_HandleRemoteConnect -  [L2CAP_PS3_HandleRemoteConnect]Device 04367E4C6325 identified as SIXAXIS compatible
34: L2CAP_PS3_ControlConnectResponseCompleted -  [L2CAP_PS3_ControlConnectResponseCompleted]HID Control Channel connection established
35: BthPS3_IndicationCallback -  [BthPS3_IndicationCallback]New connection for PSM 0x5055 from 04367E4C6325 arrived
36: L2CAP_PS3_InterruptConnectResponseCompleted -  [L2CAP_PS3_InterruptConnectResponseCompleted]HID Interrupt Channel connection established
37: BthPS3_PDO_EvtWdfDeviceD0Exit -  [BthPS3_PDO_EvtWdfDeviceD0Exit]Requesting device disconnect
38: BthPS3_IndicationCallback -  [BthPS3_IndicationCallback]New connection for PSM 0x5053 from 04367E4C6325 arrived
39: L2CAP_PS3_HandleRemoteConnect -  [L2CAP_PS3_HandleRemoteConnect]Device 04367E4C6325 name: PLAYSTATION(R)3Conteroller-PANHAI
40: L2CAP_PS3_HandleRemoteConnect -  [L2CAP_PS3_HandleRemoteConnect]Device 04367E4C6325 identified as SIXAXIS compatible
41: L2CAP_PS3_ControlConnectResponseCompleted -  [L2CAP_PS3_ControlConnectResponseCompleted]HID Control Channel connection established
42: BthPS3_IndicationCallback -  [BthPS3_IndicationCallback]New connection for PSM 0x5055 from 04367E4C6325 arrived
43: L2CAP_PS3_InterruptConnectResponseCompleted -  [L2CAP_PS3_InterruptConnectResponseCompleted]HID Interrupt Channel connection established
44: BthPS3_PDO_EvtWdfDeviceD0Exit -  [BthPS3_PDO_EvtWdfDeviceD0Exit]Requesting device disconnect
45: BthPS3_IndicationCallback -  [BthPS3_IndicationCallback]New connection for PSM 0x5053 from 04367E4C6325 arrived
46: L2CAP_PS3_HandleRemoteConnect -  [L2CAP_PS3_HandleRemoteConnect]Device 04367E4C6325 name: PLAYSTATION(R)3Conteroller-PANHAI
47: L2CAP_PS3_HandleRemoteConnect -  [L2CAP_PS3_HandleRemoteConnect]Device 04367E4C6325 identified as SIXAXIS compatible
48: L2CAP_PS3_ControlConnectResponseCompleted -  [L2CAP_PS3_ControlConnectResponseCompleted]HID Control Channel connection established
49: BthPS3_IndicationCallback -  [BthPS3_IndicationCallback]New connection for PSM 0x5055 from 04367E4C6325 arrived
50: L2CAP_PS3_InterruptConnectResponseCompleted -  [L2CAP_PS3_InterruptConnectResponseCompleted]HID Interrupt Channel connection established
51: BthPS3_PDO_EvtWdfDeviceD0Exit -  [BthPS3_PDO_EvtWdfDeviceD0Exit]Requesting device disconnect
52: BthPS3_IndicationCallback -  [BthPS3_IndicationCallback]New connection for PSM 0x5053 from 04367E4C6325 arrived
53: L2CAP_PS3_HandleRemoteConnect -  [L2CAP_PS3_HandleRemoteConnect]Device 04367E4C6325 name: PLAYSTATION(R)3Conteroller-PANHAI
54: L2CAP_PS3_HandleRemoteConnect -  [L2CAP_PS3_HandleRemoteConnect]Device 04367E4C6325 identified as SIXAXIS compatible
55: L2CAP_PS3_ControlConnectResponseCompleted -  [L2CAP_PS3_ControlConnectResponseCompleted]HID Control Channel connection established
56: BthPS3_IndicationCallback -  [BthPS3_IndicationCallback]New connection for PSM 0x5055 from 04367E4C6325 arrived
57: L2CAP_PS3_InterruptConnectResponseCompleted -  [L2CAP_PS3_InterruptConnectResponseCompleted]HID Interrupt Channel connection established
58: BthPS3_PDO_EvtWdfDeviceD0Exit -  [BthPS3_PDO_EvtWdfDeviceD0Exit]Requesting device disconnect
59: BthPS3_IndicationCallback -  [BthPS3_IndicationCallback]New connection for PSM 0x5053 from 04367E4C6325 arrived
60: L2CAP_PS3_HandleRemoteConnect -  [L2CAP_PS3_HandleRemoteConnect]Device 04367E4C6325 name: PLAYSTATION(R)3Conteroller-PANHAI
61: L2CAP_PS3_HandleRemoteConnect -  [L2CAP_PS3_HandleRemoteConnect]Device 04367E4C6325 identified as SIXAXIS compatible
62: L2CAP_PS3_ControlConnectResponseCompleted -  [L2CAP_PS3_ControlConnectResponseCompleted]HID Control Channel connection established
63: BthPS3_IndicationCallback -  [BthPS3_IndicationCallback]New connection for PSM 0x5055 from 04367E4C6325 arrived
64: L2CAP_PS3_InterruptConnectResponseCompleted -  [L2CAP_PS3_InterruptConnectResponseCompleted]HID Interrupt Channel connection established
65: BthPS3_PDO_EvtWdfDeviceD0Exit -  [BthPS3_PDO_EvtWdfDeviceD0Exit]Requesting device disconnect
66: BthPS3_IndicationCallback -  [BthPS3_IndicationCallback]New connection for PSM 0x5053 from 04367E4C6325 arrived
67: L2CAP_PS3_HandleRemoteConnect -  [L2CAP_PS3_HandleRemoteConnect]Device 04367E4C6325 name: PLAYSTATION(R)3Conteroller-PANHAI
68: L2CAP_PS3_HandleRemoteConnect -  [L2CAP_PS3_HandleRemoteConnect]Device 04367E4C6325 identified as SIXAXIS compatible
69: L2CAP_PS3_ControlConnectResponseCompleted -  [L2CAP_PS3_ControlConnectResponseCompleted]HID Control Channel connection established
70: BthPS3_IndicationCallback -  [BthPS3_IndicationCallback]New connection for PSM 0x5055 from 04367E4C6325 arrived
71: L2CAP_PS3_InterruptConnectResponseCompleted -  [L2CAP_PS3_InterruptConnectResponseCompleted] ERROR:Connection failed with status 0xc00000b5(STATUS_IO_TIMEOUT)
---- end of log ----

Framework log

3: kd> !wdfkd.wdflogdump BthPS3 -f
Trace searchpath is: 

Trace format prefix is: %7!u!: %!FUNC! - 
Trying to extract TMF information from - C:\ProgramData\Dbg\sym\Wdf01000.pdb\6D6E9C327875C47856AC7DA750AB1C5E1\Wdf01000.pdb
Gather log: Please wait, this may take a moment (reading 4024 bytes).
% read so far ... 10, 20, 30, 40, 50, 60, 70, 80, 90, 100
There are 75 log entries
--- start of log ---
1269: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleTimerRunning from FxIdleStartTimer
1270: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleCancelTimer from FxIdleTimerRunning
1271: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleCheckIoCount from FxIdleCancelTimer
1272: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleBusy from FxIdleCheckIoCount
1273: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleDecrementIo from FxIdleBusy
1274: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleStartTimer from FxIdleDecrementIo
1275: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleTimerRunning from FxIdleStartTimer
1276: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleCancelTimer from FxIdleTimerRunning
1277: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleCheckIoCount from FxIdleCancelTimer
1278: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleBusy from FxIdleCheckIoCount
1279: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleDecrementIo from FxIdleBusy
1280: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleStartTimer from FxIdleDecrementIo
1281: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleTimerRunning from FxIdleStartTimer
1282: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleCancelTimer from FxIdleTimerRunning
1283: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleCheckIoCount from FxIdleCancelTimer
1284: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleBusy from FxIdleCheckIoCount
1285: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleDecrementIo from FxIdleBusy
1286: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleStartTimer from FxIdleDecrementIo
1287: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleTimerRunning from FxIdleStartTimer
1288: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleCancelTimer from FxIdleTimerRunning
1289: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleCheckIoCount from FxIdleCancelTimer
1290: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleBusy from FxIdleCheckIoCount
1291: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleDecrementIo from FxIdleBusy
1292: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleStartTimer from FxIdleDecrementIo
1293: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleTimerRunning from FxIdleStartTimer
1294: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleCancelTimer from FxIdleTimerRunning
1295: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleCheckIoCount from FxIdleCancelTimer
1296: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleBusy from FxIdleCheckIoCount
1297: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleDecrementIo from FxIdleBusy
1298: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleStartTimer from FxIdleDecrementIo
1299: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleTimerRunning from FxIdleStartTimer
1300: FxPkgPnp::Dispatch - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0, IRP_MJ_PNP, 0x00000017(IRP_MN_SURPRISE_REMOVAL) IRP 0xFFFFE788E90D9010
1301: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering PnP State WdfDevStatePnpSurpriseRemoveIoStarted from WdfDevStatePnpStarted
1302: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering PnP State WdfDevStatePnpFailedIoStarting from WdfDevStatePnpSurpriseRemoveIoStarted
1303: FxPkgPnp::PowerPolicyEnterNewState - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power policy state WdfDevStatePwrPolStoppingCancelTimer from WdfDevStatePwrPolStartedIdleCapable
1304: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleDisabling from FxIdleTimerRunning
1305: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleDisabled from FxIdleDisabling
1306: FxPkgPnp::PowerPolicyEnterNewState - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power policy state WdfDevStatePwrPolStopping from WdfDevStatePwrPolStoppingCancelTimer
1307: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering Power State WdfDevStatePowerGotoD3Stopped from WdfDevStatePowerD0BusWakeOwner
1308: FxSelfManagedIoMachine::ProcessEvent - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering self managed io state FxSelfManagedIoSuspending from FxSelfManagedIoStarted
1309: FxSelfManagedIoMachine::ProcessEvent - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering self managed io state FxSelfManagedIoStopped from FxSelfManagedIoSuspending
1310: FxPkgIo::StopProcessingForPower - Perform FxIoStopProcessingForPowerHold for all queues of WDFDEVICE 0x0000187710D0E5F8
1311: FxPnpDeviceD0Exit::InvokeClient - EvtDeviceD0Exit WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0, new state WdfPowerDeviceD3Final failed, 0xc000009d(STATUS_DEVICE_NOT_CONNECTED)
1312: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering Power State WdfDevStatePowerFinalPowerDownFailed from WdfDevStatePowerGotoD3Stopped
1313: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering Power State WdfDevStatePowerStopped from WdfDevStatePowerFinalPowerDownFailed
1314: FxPkgPnp::PowerPolicyEnterNewState - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power policy state WdfDevStatePwrPolStoppingFailed from WdfDevStatePwrPolStopping
1315: FxPkgPnp::PowerPolicyEnterNewState - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power policy state WdfDevStatePwrPolStoppingSendStatus from WdfDevStatePwrPolStoppingFailed
1316: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power idle state FxIdleStopped from FxIdleDisabled
1317: FxPkgPnp::PowerPolicyEnterNewState - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power policy state WdfDevStatePwrPolStopped from WdfDevStatePwrPolStoppingSendStatus
1318: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering PnP State WdfDevStatePnpFailedOwnHardware from WdfDevStatePnpFailedIoStarting
1319: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering PnP State WdfDevStatePnpFailed from WdfDevStatePnpFailedOwnHardware
1320: FxPkgIo::StopProcessingForPower - Perform FxIoStopProcessingForPowerPurgeManaged for all queues of WDFDEVICE 0x0000187710D0E5F8
1321: FxSelfManagedIoMachine::ProcessEvent - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering self managed io state FxSelfManagedIoFlushing from FxSelfManagedIoStopped
1322: FxSelfManagedIoMachine::ProcessEvent - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering self managed io state FxSelfManagedIoFlushed from FxSelfManagedIoFlushing
1323: FxPkgPnp::PowerPolicyEnterNewState - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power policy state WdfDevStatePwrPolStoppedRemoving from WdfDevStatePwrPolStopped
1324: FxPkgPnp::PowerPolicyEnterNewState - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering power policy state WdfDevStatePwrPolRemoved from WdfDevStatePwrPolStoppedRemoving
1325: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering PnP State WdfDevStatePnpFailedPowerPolicyRemoved from WdfDevStatePnpFailed
1326: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering PnP State WdfDevStatePnpFailedWaitForRemove from WdfDevStatePnpFailedPowerPolicyRemoved
1327: FxPkgPnp::Dispatch - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0, IRP_MJ_PNP, 0x00000002(IRP_MN_REMOVE_DEVICE) IRP 0xFFFFE788E90D9010
1328: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering PnP State WdfDevStatePnpRemoved from WdfDevStatePnpFailedWaitForRemove
1329: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering PnP State WdfDevStatePnpRemovedChildrenRemoved from WdfDevStatePnpRemoved
1330: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering PnP State WdfDevStatePnpCheckForDevicePresence from WdfDevStatePnpRemovedChildrenRemoved
1331: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering PnP State WdfDevStatePnpPdoRemoved from WdfDevStatePnpCheckForDevicePresence
1332: FxPkgIo::StopProcessingForPower - Perform FxIoStopProcessingForPowerPurgeNonManaged for all queues of WDFDEVICE 0x0000187710D0E5F8
1333: FxSelfManagedIoMachine::ProcessEvent - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering self managed io state FxSelfManagedIoCleanup from FxSelfManagedIoFlushed
1334: FxSelfManagedIoMachine::ProcessEvent - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering self managed io state FxSelfManagedIoFinal from FxSelfManagedIoCleanup
1335: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x0000187710D0E5F8 !devobj 0xFFFFE788EC5242D0 entering PnP State WdfDevStatePnpFinal from WdfDevStatePnpPdoRemoved
1336: FxPkgPnp::_PnpRemoveDevice - WDFDEVICE 0000187710D0E5F8, !devobj FFFFE788EC5242D0 waiting for remove event to finish processing
1337: FxDevice::Destroy - Deleting !devobj FFFFE788EC5242D0, WDFDEVICE 0000187710D0E5F8, attached to !devobj 0000000000000000
1338: FxPkgPnp::Dispatch - WDFDEVICE 0x000018771D7CDFD8 !devobj 0xFFFFE788E09A3DE0, IRP_MJ_PNP, 0x00000007(IRP_MN_QUERY_DEVICE_RELATIONS) type BusRelations IRP 0xFFFFE788EE1E23F0
1339: FxPkgPnp::Dispatch - WDFDEVICE 0x000018771D7CDFD8 !devobj 0xFFFFE788E09A3DE0, IRP_MJ_PNP, 0x00000007(IRP_MN_QUERY_DEVICE_RELATIONS) type BusRelations IRP 0xFFFFE788F0B63010
1340: FxPkgPnp::Dispatch - WDFDEVICE 0x000018771D7CDFD8 !devobj 0xFFFFE788E09A3DE0, IRP_MJ_PNP, 0x00000007(IRP_MN_QUERY_DEVICE_RELATIONS) type BusRelations IRP 0xFFFFE788EE1E23F0
1341: FxPkgPnp::Dispatch - WDFDEVICE 0x000018771D7CDFD8 !devobj 0xFFFFE788E09A3DE0, IRP_MJ_PNP, 0x00000007(IRP_MN_QUERY_DEVICE_RELATIONS) type BusRelations IRP 0xFFFFE788EE1E23F0
1342: FxPkgPnp::Dispatch - WDFDEVICE 0x000018771D7CDFD8 !devobj 0xFFFFE788E09A3DE0, IRP_MJ_PNP, 0x00000007(IRP_MN_QUERY_DEVICE_RELATIONS) type BusRelations IRP 0xFFFFE788EE1E23F0
1343: FxPkgPnp::Dispatch - WDFDEVICE 0x000018771D7CDFD8 !devobj 0xFFFFE788E09A3DE0, IRP_MJ_PNP, 0x00000007(IRP_MN_QUERY_DEVICE_RELATIONS) type BusRelations IRP 0xFFFFE788EE1E23F0
---- end of log ----

Buttons 11 (L1) and 12 (L2) won't work (PS3 controller, Windows 11)

I have searched open and closed issues for duplicates
I am submitting a bug report for existing functionality that does not work as intended
I have read https://vigem.org/Community-Support/
This isn't a feature request or a discussion topic

Bug description

Everything else worked fine, except for buttons 11 and 12, respectivelly L1 and L2 in my Sony PS3 joystick.

Steps to reproduce

Open any game
Go to joystick mapping
Try to press buttons 11 or 12 for an action
They don't work, but all other buttons work fine

Actual result: Nothing happens
Expected result: The game should recognize the button I pressed

Machine info

CPU-Architecture: x64
Windows version: Windows 11 22H2
Software/driver version(s): 2.6.174

Any other helpful information

The buttons are working at the joystick native software from windows, but not in games. They both control "Z axis". If I press L1, the bar goes left, and with L2, wthe bar goes right.

Problem Navigation and Motion controls

my Navigation controls are being recognized as dualshock 3 and the motion controls do not connect with the bthps3 driver

Upgrade to Visual Studio 2022

A reminder so all projects (especially modern .NET UI components) can be built and edited under one IDE it should be fairly frictionless to upgrade from 2019 to 2022.

Universal Windows Platform build setting breaks on older OS builds

Switching the target platform from Desktop to Universal causes problems with driver loading on older Windows 10 builds, experiment if we can downgrade and make it work again.

Add ETW to filter driver

Instrument BthPS3PSM with ETW as well so errors like these are easier to diagnose on users machines:

Should vibration work?

Hello. I installed this driver for the PS3 joystick, went into the game and the vibration does not work for me. Is such a function implemented? Or do I have some problems?

Auto-pairing in other paired devices doesn't work (CSR USB dongle)

Since I installed BthPS3, I need to re-pairing my 8bitdo controller to the CSR USB Bluetooth dongle (I need to do all process in the Windows Device Configuration panel every time after disconnect the controller). I don't know if this is an issue with my CSR dongle or is an issue in BthPS3.

Thanks!!

Uninstall/Install Issue

I'm getting the error that because of a previous installation, install ended prematurely.

I tried the msi switch .\BthPS3Setup_x64.msi FILTERNOTFOUND="1" and at least i could bypass that error but still installation always rolls back and fails prematurely.

Thing is i had messed with Bluetooth registry keys and used revo uninstaller to remove bthps3 (completely) than still to no avail my Bluetooth wouldn't turn on , yellow exclamation point in device manager, so i did an inplace upgrade Widows 11 22H2 (already had this before things went south).

Now Bluetooth works correctly but still Bthps3 thinks another installation already exists, control panel, registry I've removed everything related to Bthps3 but still issue persists.

Any Ideas?

Driver not retained when migrating from Windows 11 22000 to 22449 and likely all build upgrades

I have searched open and closed issues for duplicates
I am submitting a bug report for existing functionality that does not work as intended
I have read https://vigem.org/Community-Support/
This isn't a feature request or a discussion topic

Bug description

Driver for BthDS3 is lost when upgrading from Windows 11 build 22000 to 22449.

Steps to reproduce

Install Windows 11 from ISO
Install DsHidMini and BthPS3
Enroll in the Dev channel and install the new build

Actual result: Controller no longer connects, Nefarius Bluetooth PS Enumerator is no longer present in Device Manager.
Expected result: Driver should be still installed.

Machine info

CPU-Architecture: x64
Windows version: Windows 11 builds 22000 and 22449
Software/driver version(s): 2.1.153

Any other helpful information

The MSI "Repair" option is not available to reinstall the drivers in one step; have to uninstall, reboot, and install again to get the drivers back.

Qualcomm Atheros AR3012 Not working (Integrated laptop BT adapter)

I just installed this to try and get BT working with my controller, but I'm getting this error. Is it just not compatible and I'm out of luck or is there something I can do?

This device cannot start. (Code 10)

STATUS_DEVICE_POWER_FAILURE

Bug in Instance ID creation causes multiple device node creation for same device

TL;DR: this is wrong 😛

The device ID is already unique because it contains the remote MAC address, adding another incrementing slot causes the same unique device being recreated into a new unique node causing issues with function drivers.

Installation causes interference with other adapters even when host adapter is not connected

When the host Bluetooth device is unplugged and i use an alternative bluetooth dongle I cannot remove any previously connected bluetooth devices through registry or device manager or connect to these devices, it seems the handler causes permanent conflicts when installed. This renders all previously connected devices unusable and creates a huge log of bluetooth "devices" that cannot be removed to build up in Device Manager. Wiping my entire Bluetooth registry worked before I reinstalled the drivers. Is it possible to disable the service temporarily to allow alternate dongles to continue traditional capability? Any sort of workaround would be fantastic

Blocking call in bus child D0 Exit triggers BSOD

Original issue.

Replace synchronous call to radio disconnect with async variant or apply timeout for request cancellation here.

Improve device serial number consistency

Currently the hex-encoded MAC address of the remote device is spliced into the Device ID string to enforce uniqueness and consistency. This behaviour changed slightly with the introduction of the DMF_Pdo module. Suggested new design:

Check the drivers Parameters registry key if a sub-key with the hex-encoded device MAC address exists.
- If it exists, attempt to read the DWORD value SerialNo and assign it to the PDO
- If it doesn't exist, find the next free serial, create the key and store the serial in the DWORD value SerialNo
Once the device is reconnected, it is ensured to end up in the same slot again by using the registry-cached information.
Save and restore the slots value as a REG_BINARY in the registry as well to avoid duplicate assignments

Trouble uninstalling

Hey I installed the software without running into any error messages and after restarting my computer as requested by the installer my bluetooth dongle wasn't working.

Now I wanted to reinstall the software to see if it fixes but when I hit uninstall I get a error message saying "Bluetooth Host Radio not found. A working Bluetooth stack is required for driver installation or removal."

Is there another way to uninstall this program?

Vibration/Rumble bug

I experience this bug when using DualShock 3 in bluetooth mode, in native PC games and in RPCS3 as well.
Basicly what is happeing is that when a vibration need to happen it does but the controller doesnt stop vibrating until i perform an action again which triggers a vibration.

I am using a USB Bluetooth dongle, and this "bug" doesnt happen when using a cable to play with DualShock 3

KERNEL AUTO BOOST LOCK ACQUISITION WITH RAISED IRQL [BSOD]

BSOD after stopped Shibari, this is my second time appear BSOD after stopping Shibari service.
Any driver information/version should I attach? Thank you in advance

Raised IRQL.zip

NB : In the first BSOD, the stop code is IRQL NOT LESS OR EQUAL, I can't find the log.

Random Disconnects

Checking the warnings on Windows Event Viewer shows the bth adapter stops responding, no error messages and refuses to connect unless I do a full restart.

No amount output rate control fixes the issue. These issues werent present when I previously used SCP Toolkit (Same controller and BT dongle.

)

Bluetooth connection suddenly stopped working

[X ] I have searched open and closed issues for duplicates
[ X] I am submitting a bug report for existing functionality that does not work as intended
[X ] I have read https://vigem.org/Community-Support/
[X ] This isn't a feature request or a discussion topic

Bug description

Bluetooth connection suddenly stopped working, was working fine last night turned off the pc(Normal shutdown), and this afternoon when i started the PC again the bluetooth connection did not work on both my controllers

-I pressed the reset on both controllers( both original dualshock 3)

removed and reinstalled all drivers pertaining to VIGEM/BthPS3/Dshdmini
I get the checkmark in DSHIDMINI next to Host and Device addresses
according to Device manager everything seems to be working

Steps to reproduce

I dont think this is possible to reproduce actually so that is a huge issue I know
But what i do is press the ps button on controller like usual and nothing happens,
in DShdMini

Actual result: Describe here what happens after you run the steps above (i.e. the buggy behaviour)
Expected result: Describe here what should happen after you run the steps above (i.e. what would be the correct behaviour)

Screenshots

nd drop images below -->

Machine info

CPU-Architecture: x64 Ryzen 5 3600
Windows version: Windows 10 20H2
Software/driver version(s): dshidmini_v2.2.282.0, BthPS3 Bluetooth Drivers v2.1.153

mac support?

mac ver pls

Save the time stamp of the last connection request and the associated device's Name and MAC Address as properties/keys

90% of the time that a controller can't connect to the BT Adapter running with BthPS3 it's because either the controller is using an unsupported name, it's a known name for an unsupported controller or the connection request is not even reaching the adapter.

Currently, investigating these cases require a full driver tracing. By adding the last device's Name, Mac Address and time stamp of the connection as properties/registry keys so they can be displayed on the BthPS3 Config App would greatly facilitate troubleshooting BT related connection issues.

Unable to install BthPS3

Hello, I wanted to do an uninstallation and reinstallation but impossible

Yet everything is well deleted in my drivers

So I'm completely stuck :(

Broke "DS4Windows" mode in DsHidMini

Regression reported by @Kanuan that wireless DS4Windows mode on DsHidMini broke wit the refactoring changes.

Add Event Tracing for Windows (ETW) to drivers

Add Event Tracing for Windows (ETW) for relevant diagnostics so users can just use the Event Viewer for common issues instead of having to make a trace log.

BSOD on disconnect/driver unload (L2CAP_PS3_ConnectionIndicationCallback)

@Kanuan discovered a crash caused by context memory being freed while a disconnect request is still in progress. Either use KEVENT or increase reference count to avoid unloading the PDO device object while the disconnect logic is pending.

WinDbg

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80043467a27, address which referenced memory

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5811

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 5878

    Key  : Analysis.Init.CPU.mSec
    Value: 749

    Key  : Analysis.Init.Elapsed.mSec
    Value: 5062

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 110

    Key  : Bugcheck.Code.DumpHeader
    Value: 0xd1

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0xd1

    Key  : Bugcheck.Code.Register
    Value: 0xa

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


FILE_IN_CAB:  MEMORY.DMP

BUGCHECK_CODE:  d1

BUGCHECK_P1: 0

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80043467a27

READ_ADDRESS:  0000000000000000 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  svchost.exe

DPC_STACK_BASE:  FFFFF8003A675FB0

TRAP_FRAME:  fffff8003a674890 -- (.trap 0xfffff8003a674890)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffdf8713be0f20
rdx=0000000000000007 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80043467a27 rsp=fffff8003a674a20 rbp=fffff8003a674a79
 r8=fffff8004347f198  r9=0000000000000000 r10=fffff80034d22bc0
r11=fffff8003a674cb0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
BthPS3!L2CAP_PS3_ConnectionIndicationCallback+0x117:
fffff800`43467a27 488b10          mov     rdx,qword ptr [rax] ds:00000000`00000000=????????????????
Resetting default scope

LOCK_ADDRESS:  fffff80035644ae0 -- (!locks fffff80035644ae0)

Resource @ nt!PiEngineLock (0xfffff80035644ae0)    Available
    Contention Count = 22
1 total locks

PNP_TRIAGE_DATA: 
	Lock address  : 0xfffff80035644ae0
	Thread Count  : 0
	Thread address: 0x0000000000000000
	Thread wait   : 0x0

STACK_TEXT:  
fffff800`3a674748 fffff800`34e09269     : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`3a674750 fffff800`34e05569     : 00000000`000000ff fffff800`34d42af8 ffffdf87`096610f0 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`3a674890 fffff800`43467a27     : ffff45a1`079ec7a8 00000000`12582eff 00000001`ffffffff 00000000`00000000 : nt!KiPageFault+0x469
fffff800`3a674a20 fffff800`43033479     : 00000000`00000000 ffffdf87`1a1ae010 ffffdf87`1a1ae001 fffff800`4309b3a4 : BthPS3!L2CAP_PS3_ConnectionIndicationCallback+0x117 [C:\projects\bthps3\BthPS3\L2CAP.Disconnect.c @ 168] 
fffff800`3a674ae0 fffff800`4303c19b     : 00000000`00000001 ffffdf87`1a1ae010 00000000`00000001 ffffdf87`1a1ae010 : BTHport!L2CapCon_CallClientCallbackForRemoteDisconnect+0xc9
fffff800`3a674cc0 fffff800`42fc8d71     : ffffdf87`1a1ae028 ffffdf87`17df3ad0 00000000`c000009d 00000000`00000016 : BTHport!L2CapCon_HciConnectCallback+0x46b
fffff800`3a674d90 fffff800`42fc9a2a     : ffffdf87`1a1ae028 fffff800`3a674f00 fffff800`3a675200 fffff800`42fbcb5e : BTHport!HCI_CxnCallClientCallback+0xe1
fffff800`3a674e20 fffff800`42fd3e8a     : ffffdf87`17df3f70 fffff800`3a674f70 ffffdf87`17df3a20 fffff800`3a675200 : BTHport!HCI_CxnDrainMoveList+0x7a
fffff800`3a674e70 fffff800`42fd406f     : ffffdf87`1b998205 00000000`00000004 ffffdf87`165bd720 ffffdf87`17df3a20 : BTHport!HCI_HandleDisconnectionComplete+0xb8a
fffff800`3a675070 fffff800`42fc0765     : ffffdf87`1d0da6f0 fffff800`3a675211 fffff800`3a675211 ffffdf87`165bd720 : BTHport!Fn_EVENT_DisconnectionComplete+0xaf
fffff800`3a675130 fffff800`42ff45b5     : ffffdf87`1350a000 ffffdf87`09002005 00000000`00000202 00000000`00000000 : BTHport!HCI_DoCmdCompletion+0x469
fffff800`3a675270 fffff800`430279fb     : ffffdf87`1b99bc30 fffff800`3a6753d9 00000000`00000000 00000000`00000002 : BTHport!HCI_ProcessAsynchronousEvent+0x99
fffff800`3a6752c0 fffff800`43027dec     : ffffdf87`1b99bc30 fffff800`3a6753d9 00000000`00000000 ffffdf87`1350a000 : BTHport!HCI_ProcessEventAtDPC+0x1fb
fffff800`3a675330 fffff800`43086ba7     : 00000000`00000000 fffff800`42f7c882 00000000`00000000 00000000`00000000 : BTHport!HCI_ProcessMpBip+0x3a0
fffff800`3a675440 fffff800`42f7461b     : ffffdf87`1b99bc30 00000000`00000000 00000000`00000000 fffff800`3a6755b0 : BTHport!imp_BthLegacyRecvMpBip+0x47
fffff800`3a6754a0 fffff800`42f7de99     : fffff800`3a675620 ffffdf87`134f2ab0 ffffdf87`134f2ab0 ffffdf87`12b95560 : BTHUSB!BthUsb_EventTransferComplete+0x1bb
fffff800`3a675560 fffff800`42f7e185     : 00000000`00000003 fffff800`3a675620 00000000`00000000 ffffdf87`00000006 : BTHUSB!UsbWrapWorkRoutine+0x1c9
fffff800`3a6755e0 fffff800`34c84ffe     : ffffdf87`12b95560 fffff800`3a6756f9 ffffdf87`09002340 00000000`00000000 : BTHUSB!UsbWrapInterruptReadComplete+0x205
fffff800`3a675670 fffff800`34c84ec7     : ffffdf87`00000000 fffff800`319d8100 ffffdf87`10ea6050 01000000`00100000 : nt!IopfCompleteRequest+0x11e
fffff800`3a675760 fffff800`44ae2c17     : ffffdf87`1ee28b40 ffffdf87`122515ec ffffdf87`10ea70e8 ffffffff`ffffffff : nt!IofCompleteRequest+0x17
fffff800`3a675790 fffff800`44ae22ae     : ffffdf87`10ea61a0 ffffdf87`122515ec ffffdf87`10ea61a0 00000000`00000000 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x867
fffff800`3a675a60 fffff800`44adf98d     : ffffdf87`12251724 ffffdf87`10ea7180 ffffdf87`10ea61a0 ffffdf87`096ad040 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x22e
fffff800`3a675ac0 fffff800`44ae781c     : ffffdf87`10ea70e8 ffffdf87`10ea6050 ffffdf87`098fea02 ffffdf87`096ad040 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0x24d
fffff800`3a675b30 fffff800`34c9a38e     : fffff800`3a675cb0 ffffdf87`0980f000 fffff800`3a675ea0 fffff800`319d8180 : USBPORT!USBPORT_Xdpc_Worker_IocDpc+0x18c
fffff800`3a675bb0 fffff800`34c99674     : fffff800`319d8180 00000000`00000000 00000000`00000008 00000000`000047da : nt!KiExecuteAllDpcs+0x30e
fffff800`3a675d20 fffff800`34dfe325     : 00000000`00000000 fffff800`319d8180 ffffbc01`9b966a00 ffffdf87`165b8380 : nt!KiRetireDpcList+0x1f4
fffff800`3a675fb0 fffff800`34dfe110     : 0001d3c5`1de8ffff fffff800`34d25f5a 00000000`ffffffff 00000000`00000000 : nt!KxRetireDpcList+0x5
ffffcc08`113db5b0 fffff800`34dfd9c5     : ffffdf87`165b8380 fffff800`34df8631 00000000`00000000 ffffdf87`00000005 : nt!KiDispatchInterruptContinue
ffffcc08`113db5e0 fffff800`34df8631     : 00000000`00000000 ffffdf87`00000005 00000000`00000000 ffffdf87`00000000 : nt!KiDpcInterruptBypass+0x25
ffffcc08`113db5f0 fffff800`34fd13f7     : fffff800`34fd2297 ffffdf87`00000001 ffffcc08`113db9c0 ffffdf87`165b9368 : nt!KiChainedDispatch+0xb1
ffffcc08`113db788 fffff800`34fd2297     : ffffdf87`00000001 ffffcc08`113db9c0 ffffdf87`165b9368 00000000`000000c0 : nt!PiDqIrpQueryGetResult+0x3
ffffcc08`113db790 fffff800`350eeddd     : ffffdf87`165b8380 ffffdf87`0971fd80 fffff800`34a06590 00000000`00000000 : nt!PiDqDispatch+0x1c7
ffffcc08`113db7d0 fffff800`34c8f825     : ffffdf87`165b8380 00000000`00000002 00000000`00000000 00000000`00000000 : nt!PiDaDispatch+0x4d
ffffcc08`113db800 fffff800`35075b58     : ffffdf87`165b8380 00000000`00000000 ffffdf87`165b8380 00000000`00000000 : nt!IofCallDriver+0x55
ffffcc08`113db840 fffff800`35075957     : 00000000`00000000 ffffcc08`113dbb80 00000000`00000005 ffffcc08`113dbb80 : nt!IopSynchronousServiceTail+0x1a8
ffffcc08`113db8e0 fffff800`35074cd6     : 00000000`00000000 00000000`00000000 00000000`00000000 000001ff`692639c8 : nt!IopXxxControlFile+0xc67
ffffcc08`113dba20 fffff800`34e08cb5     : ffffdf87`17403080 00000000`00000000 00000000`00000000 000001ff`67602458 : nt!NtDeviceIoControlFile+0x56
ffffcc08`113dba90 00007ffe`2bf8ce54     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
0000008d`5aa7f788 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`2bf8ce54


FAULTING_SOURCE_LINE:  C:\projects\bthps3\BthPS3\L2CAP.Disconnect.c

FAULTING_SOURCE_FILE:  C:\projects\bthps3\BthPS3\L2CAP.Disconnect.c

FAULTING_SOURCE_LINE_NUMBER:  168

FAULTING_SOURCE_CODE:  
No source found for 'C:\projects\bthps3\BthPS3\L2CAP.Disconnect.c'


SYMBOL_NAME:  BthPS3!L2CAP_PS3_ConnectionIndicationCallback+117

MODULE_NAME: BthPS3

IMAGE_NAME:  BthPS3.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  117

FAILURE_BUCKET_ID:  AV_BthPS3!L2CAP_PS3_ConnectionIndicationCallback

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {402dc05b-0c19-2f3a-d858-59fa43906eb6}

Followup:     MachineOwner
---------

0: kd> kc
 # Call Site
00 nt!KeBugCheckEx
01 nt!KiBugCheckDispatch
02 nt!KiPageFault
03 BthPS3!WdfObjectGetTypedContextWorker
04 BthPS3!GetServerDeviceContext
05 BthPS3!L2CAP_PS3_ConnectionIndicationCallback
06 BTHport!L2CapCon_CallClientCallbackForRemoteDisconnect
07 BTHport!L2CapCon_HciConnectCallback
08 BTHport!HCI_CxnCallClientCallback
09 BTHport!HCI_CxnDrainMoveList
0a BTHport!HCI_HandleDisconnectionComplete
0b BTHport!Fn_EVENT_DisconnectionComplete
0c BTHport!HCI_DoCmdCompletion
0d BTHport!HCI_ProcessAsynchronousEvent
0e BTHport!HCI_ProcessEventAtDPC
0f BTHport!HCI_ProcessMpBip
10 BTHport!imp_BthLegacyRecvMpBip
11 BTHUSB!BthUsb_EventTransferComplete
12 BTHUSB!UsbWrapWorkRoutine
13 BTHUSB!UsbWrapInterruptReadComplete
14 nt!IopfCompleteRequest
15 nt!IofCompleteRequest
16 USBPORT!USBPORT_Core_iCompleteDoneTransfer
17 USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer
18 USBPORT!USBPORT_Core_UsbIocDpc_Worker
19 USBPORT!USBPORT_Xdpc_Worker_IocDpc
1a nt!KiExecuteAllDpcs
1b nt!KiRetireDpcList
1c nt!KxRetireDpcList
1d nt!KiDispatchInterruptContinue
1e nt!KiDpcInterruptBypass
1f nt!KiChainedDispatch
20 nt!PiDqIrpQueryGetResult
21 nt!PiDqDispatch
22 nt!PiDaDispatch
23 nt!IofCallDriver
24 nt!IopSynchronousServiceTail
25 nt!IopXxxControlFile
26 nt!NtDeviceIoControlFile
27 nt!KiSystemServiceCopyEnd
28 0x0

Have you been thinking of making a version of this for Android?

While Android 8.0 (and above) Phones have Out-Of-The-Box support for DS3/Sixaxis controllers, you can only pair them by wire (or maybe even a dongle, but I never heard of anyone trying it).

The only way to do it on Androids is to root your device first, and then getting the Master Key in order to pair it wirelessly to the device using a very shady app from Google Play.

But that's just a suggestion, I just think it would be nice to be able to do that without a root.

BugCheck (DRIVER_POWER_STATE_FAILURE)

Can't provide more as the mem dump is 1.2GB

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an IRP for too long a time
Arg2: ffffaa06b8bab840, Physical Device Object of the stack
Arg3: fffff8055a272750, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffaa06afb99560, The blocked IRP

Debugging Details:
------------------

Unable to load image \SystemRoot\System32\drivers\BthPS3.sys, Win32 error 0n2

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2967

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 4005

    Key  : Analysis.Init.CPU.mSec
    Value: 765

    Key  : Analysis.Init.Elapsed.mSec
    Value: 48473

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 95

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


FILE_IN_CAB:  MEMORY.DMP

BUGCHECK_CODE:  9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffaa06b8bab840

BUGCHECK_P3: fffff8055a272750

BUGCHECK_P4: ffffaa06afb99560

DRVPOWERSTATE_SUBCODE:  3

DRIVER_OBJECT: ffffaa06ac72be40

IMAGE_NAME:  BthPS3.sys

MODULE_NAME: BthPS3

FAULTING_MODULE: fffff8055c1f0000 BthPS3

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

STACK_TEXT:  
fffff805`5a272718 fffff805`56b60157     : 00000000`0000009f 00000000`00000003 ffffaa06`b8bab840 fffff805`5a272750 : nt!KeBugCheckEx
fffff805`5a272720 fffff805`56b60071     : ffffaa06`b8687438 00000000`00000000 ffffaa06`b2ab7600 00000000`00000000 : nt!PopIrpWatchdogBugcheck+0xdf
fffff805`5a272790 fffff805`56881702     : ffffaa06`b8687470 fffff805`51977180 fffff805`51977180 00000000`00000002 : nt!PopIrpWatchdog+0x31
fffff805`5a2727e0 fffff805`56899add     : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`003d1e14 : nt!KiProcessExpiredTimerList+0x172
fffff805`5a2728d0 fffff805`569fb18e     : 00000000`00000000 fffff805`51977180 fffff805`57326a00 ffffaa06`c32c50c0 : nt!KiRetireDpcList+0x5dd
fffff805`5a272b60 00000000`00000000     : fffff805`5a273000 fffff805`5a26c000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x9F_3_IMAGE_BthPS3.sys

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {328a30da-bacc-a428-20ed-22a427c03a3c}

Followup:     MachineOwner
---------

IRQL NOT LESS OR EQUAL

Hopefully this information helps, if not I can dig around and find what your after or reproduce the issue. The bluetooth adapter is a BCM20702A0 with driver V12.0.1.921
logs.zip

Migrate Setup to WixSharp

Should be possible nowadays to pull off all the setup tasks in C# and reduce the amount of code and helper projects required to maintain. Consider switching to WixSharp. Already did some prototyping and I really like it!

Convert the profile driver into a DMF module

Now this certainly is a huge undertaking but the results would be awesome for code reusability. Besides sample drivers and this project there is very little reusable code out there on how to fire up a custom Bluetooth profile driver, so DMFs modular approach could be used to turn big chunks of the profile driver state machine into one or more DMF modules.

Cannot get working with windows 10 release 1507

Hey there, love the functionality with this new software however I cannot seem to get working on a laptop which I have on windows 10 1507. If i update to newer windows it installs however if not I get an error stating that there was an error with the windows installer package. Any ideas? I also run into issues with ViGEmBusSetup_x64 where the device is not recognised after installation. Any help would be much appreciated as I need to stay on this build of windows for driver compatibility reasons. Thanks!

BthPS3 Causing Bsod

                   Bugcheck Analysis                                    *

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an IRP for too long a time
Arg2: ffffcd0990d7ade0, Physical Device Object of the stack
Arg3: fffff80058091850, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffcd0990b93010, The blocked IRP

Debugging Details:

*** WARNING: Unable to verify timestamp for BthPS3.sys

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 6703

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 42890

Key  : Analysis.Init.CPU.mSec
Value: 812

Key  : Analysis.Init.Elapsed.mSec
Value: 147156

Key  : Analysis.Memory.CommitPeak.Mb
Value: 89

FILE_IN_CAB: 050122-10500-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffcd0990d7ade0

BUGCHECK_P3: fffff80058091850

BUGCHECK_P4: ffffcd0990b93010

DRVPOWERSTATE_SUBCODE: 3

DRIVER_OBJECT: ffffcd099018d800

IMAGE_NAME: BthPS3.sys

MODULE_NAME: BthPS3

FAULTING_MODULE: fffff80065bb0000 BthPS3

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

This happens randomly.
Windows 10 build 19044

Nefarius Bluetooth PS Enumerator device - Code 31

I have installed BthPS3 v2.1.153 and had difficulties where my Bluetooth device (listed as Generic Bluetooth Radio) would have a Code 10 error with an exclamation mark. I have fixed this as per this link that recommended deleting the "LowerFilters" item at "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class{e0cbf06c-cd8b-4647-bb8a-263b43f0f974}" in the registry.

I am now facing a new issue where the Nefarius Bluetooth PS Enumerator device has an exclamation mark in Device Manager with the below error description:

This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)

Object Name not found.

I am on Windows 10 Version 10.0.19043 Build 19043

Windows on ARM, Support?

Please let us know when can we have an ARM64 version for Windows on ARM OS.

BthPS3 Code 31

I have searched open and closed issues for duplicates
I am submitting a bug report for existing functionality that does not work as intended
I have read https://vigem.org/Community-Support/
This isn't a feature request or a discussion topic

Bug description

Like many other people, im getting the Code 31 error message even after running the powershell command in the website. And DsHidMini isn't detecting BthPS3 at all.

Steps to reproduce

Install DsHidMini
Install BthPS3
Run the powershell command

Actual result: No bluetooth detected, Not detected in DsHidMini before running the command. After running the command, Code 31, normal bluetooth works fine (Not BthPS3 tho), still not detected in DsHidMini. And also BthPS3 Config Tool wont launch if Bluetooth is on.

Expected result: Without any command or registery edits, Bluetooth and BthPS3 both work fine, and is detected by DsHidMini,

Screenshots

Machine info

CPU-Architecture: x64
Windows version: Phoenix LiteOS 11 Pro Plus (based on Windows 11 Pro 22H2)
Software/driver version(s): Latest

Any other helpful information

This also happened with other people, I have no clue what's going on and I've been trying to fix it for weeks. Thanks in advance.

nefarius / bthps3 Goto Github PK

bthps3's Introduction

About ✨ Nefarius ✨

🛠️ Languages and Tools

🔥 Statistics

🏆 Awards

bthps3's People

Contributors

Stargazers

Watchers

Forkers

bthps3's Issues

Bug description

Steps to reproduce

Screenshots

Machine info

Any other helpful information

This issue is currently a draft

To-do

Bug description

Steps to reproduce

Machine info

Other Info

Bug description

Machine info

Bug description

Steps to reproduce

Machine info

Bug description

Steps to reproduce

Screenshots

Machine info

Any other helpful information

DRIVER_IRQL_NOT_LESS_OR_EQUAL

Bugcheck

Call stack

Driver logs

Framework log

Bug description

Steps to reproduce

Machine info

Any other helpful information

Bug description

Steps to reproduce

Machine info

Any other helpful information

Bug description

Steps to reproduce

Screenshots

Machine info

WinDbg

Can't provide more as the mem dump is 1.2GB

Debugging Details:

Bug description

Steps to reproduce

Screenshots

Machine info

Any other helpful information

Recommend Projects

Recommend Topics

Recommend Org