BSOD (KERNEL_MODE_HEAP_CORRUPTION) When using Qbittorrent.

[SouljaVR]

trafficstars

qBittorrent & operating system versions

qBittorrent 4.6.7, Windows 11 23H2

What is the problem?

For some reason I keep on getting a consistent BSOD when I open a magnet link with qBittorrent. It only started happening recently, but I can reliably BSOD my computer by opening any magnet link with it. Happens every time. Why could such a thing be happening? Besides this, my machine is completely stable, and I have never had BSOD issues like this until now. I am aware that it is most likely something wrong with my machine, but I need help to identify the issue. I'm asking here since it is qBittorrent loading a magnet link that triggers this BSOD to happen. Just to be very clear it reliably causes a blue screen every time I open a magnet link, its that simple. I cannot find any way around it. Any ideas? Thank you.

Steps to reproduce

Open a magnet link with qBittorrent Link loads and then BSOD happens instantly, every time Happens with any link, ones I can confirm are fine on other machines.

Additional context

No response

Log(s) & preferences file(s)

No response

[xavier2k6]

@SouljaVR any *.dmp files??

[stalkerok]

Happens with any link, ones I can confirm are fine on other machines.

The problem is the OS.

[xavier2k6]

The problem is the OS.

Look that way!

[Darklocq]

I get this as well (Win 11 23H2) with the last several versions of qBittorrent. I don't recall if it was exactly "KERNEL_MODE_HEAP_CORRUPTION", though, just that it was a Blue Screen of Death. Since it was tripping me up on a daily basis, I just removed every vestige of the "magnet:" URL scheme from the registry with RegEdit (Windows now thinks it has no app capable of handling it). The problem was not happening with any other URL scheme and its handlers. I tried re-adding this URL scheme, with qBittorrent as handler, and the BSoDs returned. I don't have another BT app around to try instead.

I guess I could re-do that and put up with some BSoDs if further debugging information like a new dmp file is needed.

If the qBittorrent devs are certain this is an OS problem not a qBittorrent problem, then I'm open to ideas on how to resolve it, since having to manually copy-paste magnet URLs into the app is a hassle. Though way less of a hassle than the BSoDs.

The C:\DumpStack.log includes:

Dump stack initialized at UTC: 2025/02/25 06:39:51, local time: 2025/02/24 22:39:51.
#BugCheckCode 0x000000000000003B
#BugCheckP1 0x00000000C0000005
#BugCheckP2 0xFFFFF80762E954C9
#BugCheckP3 0xFFFFF8075FC6E900
#BugCheckP4 0x0000000000000000
Progress 0x00000042
Elapsed BugCheck duration 00002904ms
Starting get secondary dump callbacks size.
Progress 0x00000052
Finish get secondary dump callbacks size.
Dump Type: 6, Total Dump Size: 3597537661, Secondary Dump Size: 3395965.
Starting write of dump header.
Finish write of dump header.
Starting write of kernel bitmap dump header.
Finish write of bitmap dump header.
Starting write of memory dump data.
Elapsed BugCheck duration 00003158ms
Dumping physical memory to disk:  0%
[...]

I did have the latest MEMORY.DMP around, but WinDbg choked on it, and I don't know enough about Windows-architecture debugging to proceed any further with this at this point.

[xavier2k6]

@Darklocq this is more than likely an OS issue or system/user issue.

• Run sfc /scannow in an elevated command prompt for any corrupt OS files
• Update to 24H2/ensure all drivers & firmware/BIOS etc are up-to-date
• Run a memtest
• Run a Drive test
• Double check all cable seating