BSOD when trying to pair bluetooth (cricut) device

Nor Nor 0 Reputation points
2023-05-23T01:41:33.6866667+00:00

When trying to pair my cricut I am getting BSOD. Windows is fully updated. Dump file below

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

PNP_DETECTED_FATAL_ERROR (ca)
PnP encountered a severe error, either as a result of a problem in a driver or
a problem in PnP itself.  The first argument describes the nature of the
problem, the second argument is the address of the PDO.  The other arguments
vary depending on argument 1.
Arguments:
Arg1: 0000000000000001, Duplicate PDO
	A specific instance of a driver has enumerated multiple PDOs with
	identical device id and unique ids.
Arg2: ffffba89ca979080, Newly reported PDO.
Arg3: ffffba89c17440a0, PDO of which it is a duplicate.
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5546

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 10572

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 0

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0xca

    Key  : Bugcheck.Code.Register
    Value: 0xca

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Timestamp
    Value: 2022-05-06T12:50:00Z

    Key  : WER.OS.Version
    Value: 10.0.22621.1


FILE_IN_CAB:  052223-14734-01.dmp

BUGCHECK_CODE:  ca

BUGCHECK_P1: 1

BUGCHECK_P2: ffffba89ca979080

BUGCHECK_P3: ffffba89c17440a0

BUGCHECK_P4: 0

DEVICE_OBJECT: ffffba89ca979080

DRIVER_OBJECT: ffffba89c0b65e30

IMAGE_NAME:  BthEnum.sys

MODULE_NAME: BthEnum

FAULTING_MODULE: fffff8043afb0000 BthEnum

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

LOCK_ADDRESS:  fffff80417c5c660 -- (!locks fffff80417c5c660)
Cannot get _ERESOURCE type

Resource @ nt!PiEngineLock (0xfffff80417c5c660)    Available
1 total locks

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

STACK_TEXT:  
fffffb06`b60c7518 fffff804`178e0ad7     : 00000000`000000ca 00000000`00000001 ffffba89`ca979080 ffffba89`c17440a0 : nt!KeBugCheckEx
fffffb06`b60c7520 fffff804`17804356     : 00000000`00000001 ffffba89`cc1baaa0 ffffba89`cc1baaa0 00000000`00000001 : nt!PiProcessNewDeviceNode+0x188a33
fffffb06`b60c7700 fffff804`176ec672     : ffffba89`cc1baaa0 fffffb06`b60c77a8 ffffba89`baf71aa0 00000000`00000001 : nt!PiProcessNewDeviceNodeAsync+0x42
fffffb06`b60c7730 fffff804`1776b092     : ffffba89`c09b7300 fffff804`17239700 fffffb06`b60c7840 fffffb06`00000002 : nt!PipProcessDevNodeTree+0x3ba
fffffb06`b60c77f0 fffff804`1731e1f9     : 00000001`00000003 ffffba89`c1323be0 ffffba89`c09b7380 00000000`00000000 : nt!PiProcessReenumeration+0x92
fffffb06`b60c7840 fffff804`172162c5     : ffffba89`c86dc040 ffffba89`baecfce0 fffff804`17d49ac0 fffff804`00000000 : nt!PnpDeviceActionWorker+0x339
fffffb06`b60c7900 fffff804`1720dc67     : ffffba89`c86dc040 00000000`00000542 ffffba89`c86dc040 fffff804`17216170 : nt!ExpWorkerThread+0x155
fffffb06`b60c7af0 fffff804`17430854     : ffff9900`d0458180 ffffba89`c86dc040 fffff804`1720dc10 00000174`80e02ec1 : nt!PspSystemThreadStartup+0x57
fffffb06`b60c7b40 00000000`00000000     : fffffb06`b60c8000 fffffb06`b60c1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


IMAGE_VERSION:  10.0.22621.1626

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0xCA_1_IMAGE_BthEnum.sys

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {de19fb8a-9ab3-2b37-5af6-f0134ebfbf7e}

Followup:     MachineOwner
Windows for business | Windows Client for IT Pros | User experience | Other
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Limitless Technology 44,776 Reputation points
    2023-05-23T09:39:49.39+00:00

    Hi, thanks for coming into the forums. I'm also a user like you and I'll be more than happy to help you to the best of my knowledge.

    Please try the steps below.

    1. Run the SFC scan & update all pending updates for your Window, below is the link for the complete guide.

    https://support.microsoft.com/windows/365e0031-36b1-6031-f804-8fd86e0ef4ca

    1. Update your Bluetooth driver. Right-click the Windows start > select Device Manager > Find the Bluetooth and expand it > Right-click the driver and select update. If that doesn't work, follow the same steps but instead of updating, right-click and select uninstall. Restart your computer.
    2. If the issue started after you made changes, you can perform a system restore. On your keyboard, press the Windows key + R then type rstrui then press enter > select Next > Select the restore point/Date that you want to use on your computer click > Next > click Finish.
    3. Reset your PC https://support.microsoft.com/windows/0ef73740-b927-549b-b7c9-e6f2b48d275e

    If the reply is helpful, please Upvote and Accept it as an answer.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.