Need help please

sputnik1111 · Sep 22, 2019

OS - Windows 10
· 64-bit
· What was the originally installed: Windows 10
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Came with it
· Age of system (hardware) 2 years
· Age of OS installation - have you re-installed the OS? 1.5 years

· CPU: Intel Core i7 7500U CPU @ 2.7GHz 2.9 GHz
· Video Card: NVIDIA Virtual Audio Device
· MotherBoard - (if NOT a laptop)
· Power Supply - brand & wattage (if laptop, skip this one)

· System Manufacturer: ThinkPad
· Exact model number (if laptop, check label on the bottom): PF-10EK5N

· Laptop or Desktop? Laptop

MrPepka · Sep 22, 2019

Update:
Bluetooth driver (propably you found it in Windows Update but if not paste the Bluetooth module ID from the device manager here)

x BlueRobot · Sep 22, 2019

Quick Analysis:

It seems that your Bluetooth driver is potentially the cause here. Please check for a suitable update from here - Qualcomm Product Finder | Qualcomm

Alternatively, you may wish to visit your laptop support page and see if they provide any driver updates.

Code:

0: kd> lmvm btfilter
Browse full module list
start end module name
fffff807`81040000 fffff807`81053000 btfilter T (no symbols)
Loaded symbol image file: btfilter.sys
Image path: btfilter.sys
Image name: btfilter.sys
Browse all global symbols functions data
Timestamp: Thu May 17 03:35:18 2018 (5AFCEA66)
CheckSum: 0001FF81
ImageSize: 00013000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:

Code:

0: kd> !irql
Debugger saved IRQL for processor 0x0 -- 2 (DISPATCH_LEVEL)

Looks like we were processing DPCs, and then crashed because of an illegal page fault. The page fault was caused by referencing an invalid memory address.

Code:

0: kd> knL
# Child-SP RetAddr Call Site
00 fffff807`777ff9c8 fffff807`723d2ee9 nt!KeBugCheckEx
01 fffff807`777ff9d0 fffff807`723cf22b nt!KiBugCheckDispatch+0x69
02 fffff807`777ffb10 fffff807`79073937 nt!KiPageFault+0x46b << We crash here!
03 fffff807`777ffca8 fffff807`79069c08 BthA2dp!A2dpSbcCodec::GetMatchedRemoteSeid+0x7 << Crash started here
04 fffff807`777ffcb0 fffff807`7907c336 BthA2dp!A2DP_Device::AVDT_GetCapabilities_Cfm+0x288
05 fffff807`777ffd40 fffff807`7907e9b4 BthA2dp!Avdtp_impl::HandlePacket_GET_CAPABILITIES+0x356
06 fffff807`777ffdc0 fffff807`7907e3b6 BthA2dp!Avdtp_impl::ProcessCompletedSignallingPacket+0x3fc
07 fffff807`777ffe40 fffff807`790785ce BthA2dp!Avdtp_impl::ProcessReceivedPacket+0x32a
08 fffff807`777ffeb0 fffff807`79075caf BthA2dp!Avdtp_impl::Indication_CallbackImpl+0x102
09 fffff807`777fff60 fffff807`7dc856a4 BthA2dp!Avdtp_impl::Indication_Callback+0x1f
0a fffff807`777fffa0 fffff807`7dc197da bthport!L2CapInt_ProcessReadBip+0x614
0b fffff807`77800160 fffff807`7dc18eec bthport!HCI_ProcessAclReadBip+0x842
0c fffff807`77800260 fffff807`7dc7cb84 bthport!HCI_ProcessAclRead+0x51c
0d fffff807`77800300 fffff807`7dc0863d bthport!HCI_ProcessMpBip+0x28c
0e fffff807`77800410 fffff807`81064961 bthport!BTHPORT_RecvMpBip+0x4d
0f fffff807`77800470 fffff807`8106c53e BTHUSB!BthUsb_ReadTransferComplete+0x1e1
10 fffff807`77800530 fffff807`8106c83b BTHUSB!UsbWrapWorkRoutine+0x1ce
11 fffff807`778005b0 fffff807`72247799 BTHUSB!UsbWrapInterruptReadComplete+0x21b << Bluetooth driver stack
12 fffff807`77800640 fffff807`72247667 nt!IopfCompleteRequest+0x119
13 fffff807`77800750 fffff807`755083fd nt!IofCompleteRequest+0x17
14 (Inline Function) --------`-------- Wdf01000!FxIrp::CompleteRequest+0x13
15 fffff807`77800780 fffff807`75507ecb Wdf01000!FxRequest::CompleteInternal+0x22d
16 (Inline Function) --------`-------- Wdf01000!FxRequest::Complete+0x31
17 fffff807`77800810 fffff807`7ecc7e80 Wdf01000!imp_WdfRequestComplete+0x8b
18 fffff807`77800870 fffff807`7ecc5cf4 USBXHCI!Bulk_Transfer_CompleteCancelable+0x19c
19 fffff807`778008d0 fffff807`7ecc4460 USBXHCI!Bulk_ProcessTransferEventWithED1+0x464
1a fffff807`77800990 fffff807`7ecb98d3 USBXHCI!Bulk_EP_TransferEventHandler+0x10
1b fffff807`778009c0 fffff807`7ecaba4f USBXHCI!TR_TransferEventHandler+0x17
1c fffff807`778009f0 fffff807`7eccc2be USBXHCI!Endpoint_TransferEventHandler+0x167
1d fffff807`77800a70 fffff807`7ecaea3c USBXHCI!UsbDevice_TransferEventHandler+0xa6
1e fffff807`77800ad0 fffff807`7ecaf55c USBXHCI!Interrupter_DeferredWorkProcessor+0x578
1f fffff807`77800bd0 fffff807`755026ad USBXHCI!Interrupter_WdfEvtInterruptDpc+0xc
20 (Inline Function) --------`-------- Wdf01000!FxInterrupt::DpcHandler+0x70
21 fffff807`77800c00 fffff807`7226b065 Wdf01000!FxInterrupt::_InterruptDpcThunk+0x9d
22 fffff807`77800c40 fffff807`7226a6bf nt!KiExecuteAllDpcs+0x305 << Process DPCs waiting on this processor, explains why we're at IRQL level 2
23 fffff807`77800d80 fffff807`723c80e5 nt!KiRetireDpcList+0x1ef
24 fffff807`77800fb0 fffff807`723c7ed0 nt!KxRetireDpcList+0x5
25 ffffd00f`3d632e00 fffff807`723c7785 nt!KiDispatchInterruptContinue
26 ffffd00f`3d632e30 fffff807`723c2c01 nt!KiDpcInterruptBypass+0x25
27 ffffd00f`3d632e40 00007ff8`8229fe00 nt!KiInterruptDispatch+0xb1
28 00000000`0099f390 00000000`00000000 0x00007ff8`8229fe00

Dump the trap frame:

Code:

0: kd> .trap 0xfffff807777ffb10
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffd305cdcfdd80
rdx=00002501a9b0de22 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80779073937 rsp=fffff807777ffca8 rbp=fffff807777ffd10
r8=0000000000000000 r9=0000000000000000 r10=fffff807722a2430
r11=ffffd305cdcf1ebe r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
BthA2dp!A2dpSbcCodec::GetMatchedRemoteSeid+0x7:
fffff807`79073937 8a00 mov al,byte ptr [rax] ds:00000000`00000000=??

This matches the address which we can find in the first parameter.

Code:

0: kd> .bugcheck
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 fffff807`79073937

MrPepka · Sep 22, 2019

Determining the Bluetooth driver was not a problem here, but the problem is determining from which Bluetooth module this driver is because in carrona.org there is not much information on this topic
Driver Reference Table - BthA2DP.sys

x BlueRobot · Sep 22, 2019

Please see the top of my post, I identified a third-party Bluetooth driver.

@sputnik1111 Please find the support page here - laptops and netbooks :: thinkpad edge laptops :: thinkpad e470 :: 20h1 :: 20h1006jpb - US

Looks like there's a driver update for September 2019.

Edit: I've just checked their support page this morning and it seems that the September 2019 driver is for a slightly different device. I'll have a look at your logs again to see if there is a possibility of using that driver update, otherwise I'll have a hunt of the Qualcomm website for you.

x BlueRobot · Sep 23, 2019

There's an update for July 2018, appears to fix at least a security issue with the driver - Qualcomm Atheros Bluetooth Driver for Windows 10 (64-bit) - ThinkPad E470, E570, E475, E575 - US

sputnik1111 · Sep 23, 2019

Qualcomm Atheros QCA9377 Bluetooth

x BlueRobot · Sep 23, 2019

sputnik1111 said:
Qualcomm Atheros QCA9377 Bluetooth

Thanks for confirming, please try the driver update provided in my previous post.

sputnik1111 · Sep 23, 2019

I just reinstalled blootooth driver

x BlueRobot · Sep 23, 2019

I presume that you mean that you installed the updated version of the driver?

sputnik1111 · Sep 23, 2019

Yes I did

x BlueRobot · Sep 23, 2019

Okay thanks, please use the system as you normally would, hopefully the driver update will have resolved your issue.

sputnik1111 · Sep 23, 2019

thank you:)

Search

Search

Need help please

sputnik1111

Member

Attachments

MrPepka

Sysnative Staff, BSOD Kernel Dump Senior Analyst

x BlueRobot

Administrator

MrPepka

Sysnative Staff, BSOD Kernel Dump Senior Analyst

x BlueRobot

Administrator

x BlueRobot

Administrator

sputnik1111

Member

x BlueRobot

Administrator

sputnik1111

Member

x BlueRobot

Administrator

sputnik1111

Member

x BlueRobot

Administrator

sputnik1111

Member