Things work ok, but out of interest what are these...

[Bhuna50]

I have recently been giving someone advice on ensuring they had no yellow warning triangles etc in Device manager, along with some mini question marks. So, I thought I would take a look at mine and found this:

Now, my wifi/bluetooth card is an AX200 (my spec is posted later).

The Device IDs for these three items are here:

MAP MAS-iOS:
BTHENUM\{00001132-0000-1000-8000-00805f9b34fb}_VID&0001004c_PID&710c
BTHENUM\{00001132-0000-1000-8000-00805f9b34fb}_LOCALMFG&0002

Wireless IAP:
BTHENUM\{00000000-deca-fade-deca-deafdecacafe}_VID&0001004c_PID&710c
BTHENUM\{00000000-deca-fade-deca-deafdecacafe}_LOCALMFG&0002

Wireless IAP v2:
BTHENUM\{02030302-1d19-415f-86f2-22a2106a0a77}_VID&0001004c_PID&710c
BTHENUM\{02030302-1d19-415f-86f2-22a2106a0a77}_LOCALMFG&0002


Now when googling, it seems to imply Bluetooth (presumably the reason for the BT at the start) but also I see the one mentioned iOS - yet I dont even think I have connected my iPhone to this laptop at all yet.

The other 2 wireless items - do these relate to my AX200 - it seems to be working fine so do I need to worry about addressing these or just leave as is?

I have done a search on these and seem to get pointed to HP or Dell website for their specific drivers.

Now I know about clean installing windows etc and windows update has been completely run and exhausted, but must admit I am inclined not to follow this route as absolutely everything else seems to be working ok. I have only ever had one shut down - the memory dump file for that is dated November and have no mini dumps so dont think I have any other issues - im just extremely curious (and always want to learn) as to what these three are referring to and if I can just install / check a driver update for these.

So opening up to the experts please (and thanks in advance).

My spec:

Chassis & Display
Optimus Series: 17.3" Matte Full HD 144Hz 72% NTSC LED Widescreen (1920x1080)
Processor (CPU)
AMD Ryzen™ 7 Eight Core Processor 4800H (2.9GHz, 4.2GHz Turbo)
Memory (RAM)
64GB Corsair 2666MHz SODIMM DDR4 (2 x 32GB)
Graphics Card
NVIDIA® GeForce® RTX 2060 - 6.0GB GDDR6 Video RAM - DirectX® 12.1
1st M.2 SSD Drive
1TB SAMSUNG 970 EVO PLUS M.2, PCIe NVMe (up to 3500MB/R, 3300MB/W)
1st M.2 SSD Drive
1TB PCS PCIe M.2 SSD (2000 MB/R, 1100 MB/W)
Memory Card Reader
Integrated 3 in 1 Card Reader (Full Size SD / SDHC / SDXC)
AC Adaptor
2 x 180W AC Adaptor
Power Cable
2 x 1 Metre Cloverleaf UK Power Cable
Battery
Optimus Series Integrated 46WH Lithium Ion Battery
Thermal Paste
STANDARD THERMAL PASTE FOR SUFFICIENT COOLING
Sound Card
2 Channel High Definition Audio + MIC/Headphone Jack
Wireless Network Card
GIGABIT LAN & WIRELESS INTEL® Wi-Fi 6 AX200 (2.4 Gbps) + BT 5.0
USB/Thunderbolt Options
1 x USB 3.1 PORT (Type C) + 2 x USB 3.1 PORTS + 1 x USB 2.0 PORT
Keyboard Language
OPTIMUS SERIES RGB BACKLIT UK KEYBOARD
Operating System
Windows 10 Home 64 Bit - inc. Single Licence [KUK-00001]
Operating System Language
United Kingdom - English Language
Anti-Virus
NO ANTI-VIRUS SOFTWARE
Browser
Microsoft® Edge (Windows 10 Only)
Keyboard & Mouse
INTEGRATED 2 BUTTON TOUCHPAD MOUSE
Webcam
INTEGRATED 1MP HD WEBCAM
Warranty
3 Year Gold Warranty (2 Year Collect & Return, 2 Year Parts, 3 Year Labour)
Dead Pixel Guarantee
1 Year Dead Pixel Guarantee Inc. Labour & Carriage Costs

 

[NoddyPirate]

I have the same on my PC:

The '?' s are realted to my Sony Noice Cancelling Headset which I paired with my PC over Bluetooth earlier. When it is connected the question mark symbol remains but it all works fine.

BTHENUM is Bluetooth Emulator - apparently (according to Google at least!) - that is a driver that allows communications with other devices - so if you have ever paired your computer with anything else I expect that is what they relate to.

If everything is behaving I wouldn't worry too much??

 

[Bhuna50]

Thanks,

Its paired with my Logitech MX Anywhere 2S Mouse - but thats on.

My headset is a USB one, but I have used a Plantronics briefly, so wonder if it relates to them?

I cant think of anything else I have paired with.

 

[Bhuna50]

Just for @ubuysa - www.aj1.co.uk/MEMORY.DMP

Although, only if you get a spare few mins and want something to do - cant say I have experienced anything since November so absolutely no need to look at if you think its a waste of time to do so.

 

[NoddyPirate]

Its paired with my Mouse - but thats on.

My headset is a USB one, but I have used a Plantronics briefly, so wonder if it relates to them?

I cant think of anything else I have paired with.

Check your list of devices in Settings - Devices - Bluetooth and Other Devices. You'll see a list of everything that has ever been paired with your computer.....

As I say my questions marks remain even if my headset is connected - so I imagine that Windows just can't figure out exactly what it's communicating to - hence the ?'s.....

 

[Bhuna50]

Cheers - just the mouse - never connected to any of the other devices yet

 

[NoddyPirate]

Cheers:

View attachment 22673

Typo earlier - BTHENUM is an enumerator - bloody auto-correct. Anyway I dont' even know what that means whatever it says!!

When I look at the driver settings for my connected devices - I can see I have an Enumerator Driver thingy installed just this evening at exactly the time I connected my Sony headset for the first time. So I'd be fairly confident that's it and that all is well.....

 

[Bhuna50]

OK thanks @NoddyPilot - much appreciate your time.

 

[NoddyPirate]

Sorry I’ll leave you alone after this! 😀

just the mouse would be enough on its own. The AP in your Wireless AP means Access Point.

And Google Darling says:

I’ll tells ya I is learnin’ more than anyone around here! 🙂🙂

 

[Bhuna50]

Thanks.

Hey if you find anything out I’d love to know as learning too lol.

Have come of laptop now though so on iPhone. [emoji3]


Sent from my iPhone using Tapatalk

 

[SpyderTracks]

Seems to be related to Apple Airpods possibly, definitely an Apple bit of hardware, is the phone paired with the computer?:

AAP server and wireless iAP missing drivers

Hello, I have AAP server and wireless iAP missing drivers and I don't have a clue what they are, anyone can help please?

h30434.www3.hp.com

 

[ubuysa]

'Enumerate' means to count. Enumeration is the process of counting things, so a Bluetooth Enumerator basically counts (and queries) the Bluetooth devices it can detect in range. It's the Bluetooth component that figures out what devices you're able to pair with. [emoji6]

Now back you your dump. [emoji16]

 

[ubuysa]

Now this is an interesting dump! I've not seen this stop code in a dump before, it's a THREAD_STUCK_IN_DEVICE_DRIVER and as the name implies it's caused by a thread in a device driver looping or spinning waiting for a spinlock to come free. Looking at the locks held by the active thread there are no exclusive locks held, so the thread must be looping. This is thus a driver error and the code is looping - waiting for some hardware response possibly. That might indicate a hardware issue - possibly.

The process in control at the time of the error was aida64.exe, the AIDA64 benchmarking tool, so this may well be why you've not seen the problem since running it

The stack trace for the stuck thread shows the DirectX kernel driver (dxgkrnl.sys) communicating with the DirectX component in the graphics card (dxgkrnl!DXGADAPTER:diEscape+0xfa). This is followed by a repeated series of calls to amdkmdag.sys - this is the ATI Radeon Kernel Mode Driver and that's curious because you don't have a Radeon graphics card but an Nvidia one. I don't know whether amdkmdag.sys is a standard component of AMD chipsets even if you don't have a Radeon card? It might well be involved in communication between the AMD chipset and the Nvidia graphics card.

Immediately after the series of amdkmdag.sys calls are two more calls to dxgkrnl.sys. The first of these calls (to dxgkrnl!TdrTimedOperationDelay+0xce) is clearly related to detecting the TDR delay (TDR is Timeout Detection and Recovery), the second call (to dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45) is the delay timer popping and triggering the bug check. Immediately following this is the bug check call itself (to nt!KeBugCheckEx).

It thus seems to me that the fault is in amdkmdag.sys, that's the driver that's stuck in a loop, and that dxgkrnl.sys was only involved in starting the action and detecting the TDR timeout after amdkmdag.sys had been called a number of times (16 in fact). These repeated calls to amdkmdag.sys would suggest that the graphics adapter didn't respond and that this may be a graphics card problem. However, since the process in control is a benchmarking and diagnosis tool it's also possible that the graphics card was asked to do something it wasn't able to do? Since you've not experienced any other issues I would suggest we can put this down to overstressing by AIDA64.

Thank you for that. This is the most fun I've had so far today.

 

[Bhuna50]

Thanks for that ubuysa

Would Aida64 be part of 3D Mark benchmarking as that froze my machine before. Or you mention stress testing, I need to look at the date of the dump file again as I received the machine 20 November so wonder if it was the two stress tests I ran or maybe one run by PCS in testing.

Re graphics, it has in built AMD graphics and then the dGPU.

When I load up machine later I’ll find the name of the two stress tests I ran (it was from a post on here somewhere lol).

Also thanks Spydertracks - I don’t have AirPods but I think someone in the house may have bluetoothed their Iphone to my machine to get a picture to print out for a present and then removed the phone to avoid questions LOL.

I guess all can be put in the nothing to worry about draw.


Sent from my iPhone using Tapatalk

 

[NoddyPirate]

Now this is an interesting dump! I've not seen this stop code in a dump before, it's a THREAD_STUCK_IN_DEVICE_DRIVER and as the name implies it's caused by a thread in a device driver looping or spinning waiting for a spinlock to come free. Looking at the locks held by the active thread there are no exclusive locks held, so the thread must be looping. This is thus a driver error and the code is looping - waiting for some hardware response possibly. That might indicate a hardware issue - possibly.

The process in control at the time of the error was aida64.exe, the AIDA64 benchmarking tool, so this may well be why you've not seen the problem since running it

The stack trace for the stuck thread shows the DirectX kernel driver (dxgkrnl.sys) communicating with the DirectX component in the graphics card (dxgkrnl!DXGADAPTER:diEscape+0xfa). This is followed by a repeated series of calls to amdkmdag.sys - this is the ATI Radeon Kernel Mode Driver and that's curious because you don't have a Radeon graphics card but an Nvidia one. I don't know whether amdkmdag.sys is a standard component of AMD chipsets even if you don't have a Radeon card? It might well be involved in communication between the AMD chipset and the Nvidia graphics card.

Immediately after the series of amdkmdag.sys calls are two more calls to dxgkrnl.sys. The first of these calls (to dxgkrnl!TdrTimedOperationDelay+0xce) is clearly related to detecting the TDR delay (TDR is Timeout Detection and Recovery), the second call (to dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45) is the delay timer popping and triggering the bug check. Immediately following this is the bug check call itself (to nt!KeBugCheckEx).

It thus seems to me that the fault is in amdkmdag.sys, that's the driver that's stuck in a loop, and that dxgkrnl.sys was only involved in starting the action and detecting the TDR timeout after amdkmdag.sys had been called a number of times (16 in fact). These repeated calls to amdkmdag.sys would suggest that the graphics adapter didn't respond and that this may be a graphics card problem. However, since the process in control is a benchmarking and diagnosis tool it's also possible that the graphics card was asked to do something it wasn't able to do? Since you've not experienced any other issues I would suggest we can put this down to overstressing by AIDA64.

Thank you for that. This is the most fun I've had so far today.

Interesting @ubuysa! You scare me sometimes though I must say...... 😍

Are those issues you’ve found related to the OPs Device Manager ‘?’ indications or have you found a different problem? Just wondering as I have a similar indication - but mine seem to be more directly traceable to my wireless peripherals....

 

[Bhuna50]

Interesting @ubuysa! You scare me sometimes though I must say...... [emoji7]

Are those issues you’ve found related to the OPs Device Manager ‘?’ indications or have you found a different problem? Just wondering as I have a similar indication - but mine seem to be more directly traceable to my wireless peripherals....

From what I understand, it’s driver related but nothing directly related to the question marks I highlighted.


Sent from my iPhone using Tapatalk

 

[ubuysa]

Interesting @ubuysa! You scare me sometimes though I must say...... 😍

Are those issues you’ve found related to the OPs Device Manager ‘?’ indications or have you found a different problem? Just wondering as I have a similar indication - but mine seem to be more directly traceable to my wireless peripherals....

I don't think the dump issue is at all related to the Device Manager '?' indications.

FWIW the '?' in Device Manager means only that the device-specific driver is not installed but a compatible driver is being used. The only time this would be an issue would be if the device was misbehaving, then you'd need to locate the specific driver.

 

[NoddyPirate]

I don't think the dump issue is at all related to the Device Manager '?' indications.

FWIW the '?' in Device Manager means only that the device-specific driver is not installed but a compatible driver is being used. The only time this would be an issue would be if the device was misbehaving, then you'd need to locate the specific driver.

Brillo. Thanks so much. Makes sense and more or less what we thought.... 👍

 

[Bhuna50]

I just looked @ubuysa and that MEMORY.DMP file was on the machine when I received it LOL - sorry - doesnt seem to relate to me running benchmark / stress tests at all - as I didnt receive the machine until 21 November, so the 19 November must have been a PCS test caused it but then found to all be ok.

I did also run Aida64 actually - as its in the https://www.pcspecialist.co.uk/foru...nd-tools-for-troubleshooting-new-build.71577/ thread I looked at for testing my machine when I first got it - but never had any problems (obviously as the memory.dmp file is before I ran it).

Dmp file now deleted (freeing up 3gb space - as I had a copy of it too) ready for the next time one creates

Thanks for your time everyone, I can put this thread to bed now

 

[ubuysa]

I just looked @ubuysa and that MEMORY.DMP file was on the machine when I received it LOL - sorry - doesnt seem to relate to me running benchmark / stress tests at all - as I didnt receive the machine until 21 November, so the 19 November must have been a PCS test caused it but then found to all be ok.

I did also run Aida64 actually - as its in the https://www.pcspecialist.co.uk/foru...nd-tools-for-troubleshooting-new-build.71577/ thread I looked at for testing my machine when I first got it - but never had any problems (obviously as the memory.dmp file is before I ran it).

Dmp file now deleted (freeing up 3gb space - as I had a copy of it too) ready for the next time one creates

Thanks for your time everyone, I can put this thread to bed now

TBH I don't care. It was a learning experience and great fun to be able to pinpoint the problem - that happens far less often with a memory dump than you might imagine!