BugCheck 0x65 during Phone Link PAN pairing (AX200, IBTHFP.SYS)

This is a repost due to access authorization issues encountered after receiving in my email a notification about a reply from a forum member.
Unfortunately, the original thread is no longer accessible — I get a "Opss... You do not have permission to view this page" error.

The issue:
System reproducibly crashes with BugCheck 0x65 when pairing Phone Link with PAN active.
Driver involved: IBTHFP.SYS (Intel Bluetooth Hands-Free Profile).
Device: Beelink Mini PC with AX200.

Dump and analysis:
- GitHub: GitHub - FrancoTrone64/AX200-HFP-PhoneLink: Documentazione tecnica sul mancato binding HFP su Intel AX200 con Phone Link
- Mirror: This post is not an isolated complaint. It is part of a coordinated escalatio - Pastebin.com

Looking for confirmation, workaround, or escalation path.
Thanks in advance.

escalation path?
This is not a support site you know.
Better off trying Beelink support for escalation.
support-pc@bee-link.com

Attention: Franco64
Before posting a BSOD thread, please read the instructions here: Blue/Black Screen of Death (BSOD) Posting Instructions
If you need to add new information, please make a new post in your initial BSOD thread. Please do not make an extra new thread.

Please do not post anything other than Windows 11 Blue/Black Screen Of Death problems in this section.

Hello Zbook,
Let me first apologize for not strictly adhering to the BSOD posting guidelines, which I had read before submitting the post. Thank you as well for your reply, which aimed to address the scenario using a different approach.

You're absolutely right that BSOD threads should focus strictly on crash diagnostics. I acknowledge that my initial post may have unintentionally blurred two distinct layers — the BSOD event itself and the broader systemic incompatibility involving the **IBtHFP.SYS** driver.

However, I’d like to clarify that while these are two separate analytical planes, they are deeply interconnected:

- The BSOD (`0x00000065`) is triggered by the **IBtHFP.SYS** driver under specific Bluetooth conditions.
- The same driver fails to initialize the **HFP channel** correctly, breaking the Bluetooth stack and preventing **Phone Link** from completing its configuration.
- This leads to a loop of failed memory allocations and unstable Bluetooth behavior, which — under certain configurations — culminates in the crash.

In short, the crash is not an isolated event but the final symptom of a deeper incompatibility between the driver and the system's Bluetooth architecture.

---

## Crash details

- **Stop code**: `MEMORY_MANAGEMENT (0x00000065)`
- **Driver involved**: `IBtHFP.SYS`
- **Conditions**: Bluetooth active, Phone Link configured, AX200 chipset
- **Symptoms**: Sudden BSOD, failed memory allocation, BT stack instability

---

## Dump and documentation

- Minidump file attached below
- Full technical analysis and supporting files available on GitHub:
[https://github.com/Franco64/AX200-B...://github.com/Franco64/AX200-BSOD-escalation)

---

In comliance with the forum’s structure, I’ve now reframed this post strictly around the crash event. I will open a second, separate thread to address the broader driver incompatibility and its impact on Bluetooth stability and Windows components like Phone Link.

Thanks again for your feedback — I hope this clarification helps distinguish the two layers while preserving their technical interdependence.

When available please post a V2 share link into the newest post.
(third request in addition to the posting instructions)