Question Could anyone help with this BSOD on my Windows 11 PC ?

[pinapple198]

We have a PC that is running 24/7, as it runs overnight tests, and it keeps having BSOD randomly. I have looked at the Minidump files that it generates but it means absolutely nothing to me. I have tried searching around for answers but I have had no luck. Any help and advice would be appreciated (I don't know what I'm doing).

Spoiler: Debugger log file

KERNEL_MODE_HEAP_CORRUPTION (13a)
The kernel mode heap manager has detected corruption in a heap.
Arguments:
Arg1: 0000000000000011, Type of corruption detected
Arg2: ffffd58c2a010140, Address of the heap that reported the corruption
Arg3: ffffd58c6acdeea0, Address at which the corruption was detected
Arg4: 0000000000000000

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

fffff8061671c470: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
HeapDbgInitExtension Failed

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4905

Key : Analysis.Elapsed.mSec
Value: 5734

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: 499

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x13a

Key : Dump.Attributes.AsUlong
Value: 1808

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0

Key : Failure.Bucket
Value: 0x13a_11_SsKi_BbNBus41!unknown_function

Key : Failure.Hash
Value: {546fedcc-0033-4505-ccc7-4195f1745991}

Key : Hypervisor.Enlightenments.ValueHex
Value: 1417df84

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1

Key : Hypervisor.Flags.ApicEnlightened
Value: 0

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 1

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 1

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1

Key : Hypervisor.Flags.Phase0InitDone
Value: 1

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 1

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 21631230

Key : Hypervisor.Flags.ValueHex
Value: 14a10fe

Key : Hypervisor.Flags.VpAssistPage
Value: 1

Key : Hypervisor.Flags.VsmAvailable
Value: 1

Key : Hypervisor.RootFlags.AccessStats
Value: 1

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 1

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1

Key : Hypervisor.RootFlags.MceEnlightened
Value: 1

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1

Key : Hypervisor.RootFlags.Value
Value: 1015

Key : Hypervisor.RootFlags.ValueHex
Value: 3f7


BUGCHECK_CODE: 13a

BUGCHECK_P1: 11

BUGCHECK_P2: ffffd58c2a010140

BUGCHECK_P3: ffffd58c6acdeea0

BUGCHECK_P4: 0

FILE_IN_CAB: 022824-10921-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x1808
Kernel Generated Triage Dump

POOL_ADDRESS: Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
ffffd58c6acdeea0

FREED_POOL_TAG: SsKi

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff8389`a7ca7728 fffff806`15fb2954 : 00000000`0000013a 00000000`00000011 ffffd58c`2a010140 ffffd58c`6acdeea0 : nt!KeBugCheckEx
ffff8389`a7ca7730 fffff806`15fb29b4 : 00000000`00000011 00000000`00000000 ffffd58c`2a010140 fffff806`15a00000 : nt!RtlpHeapHandleError+0x40
ffff8389`a7ca7770 fffff806`15fb25d1 : 00000000`012000c0 ffffffff`ffffffff 00000000`00000001 00000000`00000000 : nt!RtlpHpHeapHandleError+0x58
ffff8389`a7ca77a0 fffff806`15ead59e : 00000000`0000011b ffffd58c`6c9e61e0 00000000`00000000 ffff8389`a7ca7880 : nt!RtlpLogHeapFailure+0x45
ffff8389`a7ca77d0 fffff806`15d217ff : ffffd58c`2a010380 ffffa301`936e70ff ffffd58c`2dea6040 00000000`00000000 : nt!RtlpHpLfhSubsegmentFreeBlock+0x1b31ce
ffff8389`a7ca7860 fffff806`164acce5 : ffff857f`694b7353 fffff806`00000002 01000000`00000000 00000000`000000c0 : nt!ExFreeHeapPool+0x2ef
ffff8389`a7ca7910 fffff806`441b8e9c : ffffd58c`6acdeeb0 ffffd58c`5cb640e0 ffffd58c`5cb5ff90 ffffd58c`2dea6040 : nt!ExFreePool+0x25
ffff8389`a7ca7950 ffffd58c`6acdeeb0 : ffffd58c`5cb640e0 ffffd58c`5cb5ff90 ffffd58c`2dea6040 ffffd58c`5cb5ef10 : BbNBus41+0x18e9c
ffff8389`a7ca7958 ffffd58c`5cb640e0 : ffffd58c`5cb5ff90 ffffd58c`2dea6040 ffffd58c`5cb5ef10 fffff806`441bb5f6 : 0xffffd58c`6acdeeb0
ffff8389`a7ca7960 ffffd58c`5cb5ff90 : ffffd58c`2dea6040 ffffd58c`5cb5ef10 fffff806`441bb5f6 ffffd58c`5cb5ef10 : 0xffffd58c`5cb640e0
ffff8389`a7ca7968 ffffd58c`2dea6040 : ffffd58c`5cb5ef10 fffff806`441bb5f6 ffffd58c`5cb5ef10 ffffd58c`6acdeeb0 : 0xffffd58c`5cb5ff90
ffff8389`a7ca7970 ffffd58c`5cb5ef10 : fffff806`441bb5f6 ffffd58c`5cb5ef10 ffffd58c`6acdeeb0 00000000`0000011b : 0xffffd58c`2dea6040
ffff8389`a7ca7978 fffff806`441bb5f6 : ffffd58c`5cb5ef10 ffffd58c`6acdeeb0 00000000`0000011b ffffd58c`72718000 : 0xffffd58c`5cb5ef10
ffff8389`a7ca7980 ffffd58c`5cb5ef10 : ffffd58c`6acdeeb0 00000000`0000011b ffffd58c`72718000 ffffd58c`5cb5d308 : BbNBus41+0x1b5f6
ffff8389`a7ca7988 ffffd58c`6acdeeb0 : 00000000`0000011b ffffd58c`72718000 ffffd58c`5cb5d308 fffff806`441aad2f : 0xffffd58c`5cb5ef10
ffff8389`a7ca7990 00000000`0000011b : ffffd58c`72718000 ffffd58c`5cb5d308 fffff806`441aad2f ffffd58c`5cb59000 : 0xffffd58c`6acdeeb0
ffff8389`a7ca7998 ffffd58c`72718000 : ffffd58c`5cb5d308 fffff806`441aad2f ffffd58c`5cb59000 ffffd58c`5cb5ff90 : 0x11b
ffff8389`a7ca79a0 ffffd58c`5cb5d308 : fffff806`441aad2f ffffd58c`5cb59000 ffffd58c`5cb5ff90 ffffd58c`5cb64cf0 : 0xffffd58c`72718000
ffff8389`a7ca79a8 fffff806`441aad2f : ffffd58c`5cb59000 ffffd58c`5cb5ff90 ffffd58c`5cb64cf0 ffffd58c`659f5bf0 : 0xffffd58c`5cb5d308
ffff8389`a7ca79b0 ffffd58c`5cb59000 : ffffd58c`5cb5ff90 ffffd58c`5cb64cf0 ffffd58c`659f5bf0 ffffd58c`5cb5d308 : BbNBus41+0xad2f
ffff8389`a7ca79b8 ffffd58c`5cb5ff90 : ffffd58c`5cb64cf0 ffffd58c`659f5bf0 ffffd58c`5cb5d308 fffff806`441adbfc : 0xffffd58c`5cb59000
ffff8389`a7ca79c0 ffffd58c`5cb64cf0 : ffffd58c`659f5bf0 ffffd58c`5cb5d308 fffff806`441adbfc ffffd58c`5cb59000 : 0xffffd58c`5cb5ff90
ffff8389`a7ca79c8 ffffd58c`659f5bf0 : ffffd58c`5cb5d308 fffff806`441adbfc ffffd58c`5cb59000 fffff806`441b2ffa : 0xffffd58c`5cb64cf0
ffff8389`a7ca79d0 ffffd58c`5cb5d308 : fffff806`441adbfc ffffd58c`5cb59000 fffff806`441b2ffa 00000000`00000003 : 0xffffd58c`659f5bf0
ffff8389`a7ca79d8 fffff806`441adbfc : ffffd58c`5cb59000 fffff806`441b2ffa 00000000`00000003 ffffd58c`659f5bf0 : 0xffffd58c`5cb5d308
ffff8389`a7ca79e0 ffffd58c`5cb59000 : fffff806`441b2ffa 00000000`00000003 ffffd58c`659f5bf0 ffffa301`936e7000 : BbNBus41+0xdbfc
ffff8389`a7ca79e8 fffff806`441b2ffa : 00000000`00000003 ffffd58c`659f5bf0 ffffa301`936e7000 00000000`00000012 : 0xffffd58c`5cb59000
ffff8389`a7ca79f0 00000000`00000003 : ffffd58c`659f5bf0 ffffa301`936e7000 00000000`00000012 ffffd58c`659f5bf0 : BbNBus41+0x12ffa
ffff8389`a7ca79f8 ffffd58c`659f5bf0 : ffffa301`936e7000 00000000`00000012 ffffd58c`659f5bf0 fffff806`441a7e0e : 0x3
ffff8389`a7ca7a00 ffffa301`936e7000 : 00000000`00000012 ffffd58c`659f5bf0 fffff806`441a7e0e ffffd58c`5cb59000 : 0xffffd58c`659f5bf0
ffff8389`a7ca7a08 00000000`00000012 : ffffd58c`659f5bf0 fffff806`441a7e0e ffffd58c`5cb59000 ffffd58c`5cb640e0 : 0xffffa301`936e7000
ffff8389`a7ca7a10 ffffd58c`659f5bf0 : fffff806`441a7e0e ffffd58c`5cb59000 ffffd58c`5cb640e0 ffffd58c`5cb5ff90 : 0x12
ffff8389`a7ca7a18 fffff806`441a7e0e : ffffd58c`5cb59000 ffffd58c`5cb640e0 ffffd58c`5cb5ff90 ffffd58c`659f5bf0 : 0xffffd58c`659f5bf0
ffff8389`a7ca7a20 ffffd58c`5cb59000 : ffffd58c`5cb640e0 ffffd58c`5cb5ff90 ffffd58c`659f5bf0 ffffd58c`5cb59000 : BbNBus41+0x7e0e
ffff8389`a7ca7a28 ffffd58c`5cb640e0 : ffffd58c`5cb5ff90 ffffd58c`659f5bf0 ffffd58c`5cb59000 fffff806`441aeb21 : 0xffffd58c`5cb59000
ffff8389`a7ca7a30 ffffd58c`5cb5ff90 : ffffd58c`659f5bf0 ffffd58c`5cb59000 fffff806`441aeb21 ffffd58c`659f5bf0 : 0xffffd58c`5cb640e0
ffff8389`a7ca7a38 ffffd58c`659f5bf0 : ffffd58c`5cb59000 fffff806`441aeb21 ffffd58c`659f5bf0 00000000`00000000 : 0xffffd58c`5cb5ff90
ffff8389`a7ca7a40 ffffd58c`5cb59000 : fffff806`441aeb21 ffffd58c`659f5bf0 00000000`00000000 ffffd58c`5cb64cf0 : 0xffffd58c`659f5bf0
ffff8389`a7ca7a48 fffff806`441aeb21 : ffffd58c`659f5bf0 00000000`00000000 ffffd58c`5cb64cf0 ffffd58c`5cb64010 : 0xffffd58c`5cb59000
ffff8389`a7ca7a50 ffffd58c`659f5bf0 : 00000000`00000000 ffffd58c`5cb64cf0 ffffd58c`5cb64010 ffffd58c`659f5bf0 : BbNBus41+0xeb21
ffff8389`a7ca7a58 00000000`00000000 : ffffd58c`5cb64cf0 ffffd58c`5cb64010 ffffd58c`659f5bf0 fffff806`441b1e07 : 0xffffd58c`659f5bf0


SYMBOL_NAME: BbNBus41+18e9c

MODULE_NAME: BbNBus41

IMAGE_NAME: BbNBus41.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 18e9c

FAILURE_BUCKET_ID: 0x13a_11_SsKi_BbNBus41!unknown_function

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {546fedcc-0033-4505-ccc7-4195f1745991}

Followup: MachineOwner
---------

 

[Fix_that_Glitch]

Are you running more than one app at a time when this happens? Have you tried using one stick of ram at a time or do a memtest to rule out your memory? Have you installed any new hardware? Bios, drivers up to date? Also what is your pc build (parts)?

 

[allandg]

Have you recently installed or updated any drivers?

 

[pinapple198]

Have you recently installed or updated any drivers?

My first thought was to install the NVIDIA Graphics Driver, as it has an RTX 2060 in it. It was already BSODing previous to this install and continued to BSOD after installing it.

 

[allandg]

Okay. And do you have a disk image or restore point from a time prior to the bsod's starting?

If not, see if anything here helps (it says Windows 10, but it applies to W11 as well): https://www.thewindowsclub.com/kernel-mode-heap-corruption-on-windows-10

 

[pinapple198]

Are you running more than one app at a time when this happens? Have you tried using one stick of ram at a time or do a memtest to rule out your memory? Have you installed any new hardware? Bios, drivers up to date? Also what is your pc build (parts)?

We have some software running on this machine when it's logging overnight and this can be multiple instances of the same software (Depending on what's running). I have not tried using one stick of RAM, I could give this a go! I ran the Windows Memory Diagnostic tool which came back with no issues which is why I ruled out ram. No new hardware has been installed since we first got the PC. As far as I'm aware everything is up to date but I haven't checked for a bios update.

The PC parts are:

Processor (CPU)
Intel® Core™ i7 16-Core Processor i7-13700 (Up to 5.2 GHz) 30MB Cache

Motherboard
ASUS® PRIME B760-PLUS D4 (LGA1700, PCIe5.0, USB 3.2)

Memory (RAM)
16GB Corsair VENGEANCE DDR4 3200MHz (2 x 8GB)

Graphics Card
RTX 2060

M.2 SSD Drive
500GB SAMSUNG 970 EVO PLUS M.2, PCIe NVMe (up to 3500MB/R, 3200MB/W)

Power Supply
CORSAIR 550W CV SERIES™ CV-550 POWER SUPPLY

 

[pinapple198]

Okay. And do you have a disk image or restore point from a time prior to the bsod's starting?

If not, see if anything here helps (it says Windows 10, but it applies to W11 as well): https://www.thewindowsclub.com/kernel-mode-heap-corruption-on-windows-10

We don't have any unfortunately.

Thanks for the link, I'll try everything on there and see if it helps!

 

[Satan-IR]

How old is the system and mainly the PSU? That PSU is OK as far as wattage is concerned but not a good quality one. Having the system on 24/7 makes it age a bit sooner than other same age PCs used casually daily.

BSODS sound like a software/driver issue but that PSU might be causing problems. If available trying to power the system on with a known good working PSU with same or higher output capacity might narrow this down.

 

[pinapple198]

How old is the system and mainly the PSU? That PSU is OK as far as wattage is concerned but not a good quality one. Having the system on 24/7 makes it age a bit sooner than other same age PCs used casually daily.

BSODS sound like a software/driver issue but that PSU might be causing problems. If available trying to power the system on with a known good working PSU with same or higher output capacity might narrow this down.

We purchased this PC last year in May so it's not even a year old yet. We don't have any spare PSUs around but if this could fix the issue we would just order a PSU and install it!

 

[allandg]

1) Before you go through the hassle of replacing the psu (not my first thought, btw), I'd look at the Windows Club link and try some or all of those suggestions.

2) I'm sure I don't need to say this, but..... moving forward I would urge you to create images of your hd's (at least the system partitions if they are multi-partitioned) on a regular basis. I'm not say that would fix this issue - if the cause is hardware based it would not - still, it's a good practice for everyone to follow.

3) Please take a quick look in device management and see if there are any yellow or red symbols (start - run - devmgmt.msc)

4) One other thing to check is in Windows Update, see if Microsoft installed any drivers without you knowing (unless you have driver downloads disabled - which you should).

 

[Satan-IR]

We purchased this PC last year in May so it's not even a year old yet. We don't have any spare PSUs around but if this could fix the issue we would just order a PSU and install it!

I didn't mean the PSU is definitely causing the the problem and therefore replacing it would definitely solve it. By testing if BSODs happens with another known working PSU or not you would almost make certain or otherwise rule out whether the PSU is causing issues or not. I personally would try to see if it's an OS/software/driver issue that is causing the BSODs then move to hardware.

All that said as I mentioned that PSU is not the best quality 550W out there it is kind of "just enough" with an i7-13700 and a 2060. Generally speaking having a little headroom with PSUs is not a bad thing, especially when the unit is not the best out there.

Does the software you mentioned that does some work overnight utilize the computational aspects of the GPU or is it CPU-intensive work?

 

[pinapple198]

1) Before you go through the hassle of replacing the psu (not my first thought, btw), I'd look at the Windows Club link and try some or all of those suggestions.

2) I'm sure I don't need to say this, but..... moving forward I would urge you to create images of your hd's (at least the system partitions if they are multi-partitioned) on a regular basis. I'm not say that would fix this issue - if the cause is hardware based it would not - still, it's a good practice for everyone to follow.

3) Please take a quick look in device management and see if there are any yellow or red symbols (start - run - devmgmt.msc)

4) One other thing to check is in Windows Update, see if Microsoft installed any drivers without you knowing (unless you have driver downloads disabled - which you should).

So I've just been through the link and done all that was recommended and updated the BIOS to the latest update.

You're right, we need to set that up to prevent future issues so I will be doing this!

I checked device management, all seems clear on there nothing is showing yellow or red symbols.

After running all of the recommended things on the Windows Club link I'll keep my eye on the PC and check the logs on Monday see if there has been any issues over this weekend!

I appreciate the help!

 

[pinapple198]

I didn't mean the PSU is definitely causing the the problem and therefore replacing it would definitely solve it. By testing if BSODs happens with another known working PSU or not you would almost make certain or otherwise rule out whether the PSU is causing issues or not. I personally would try to see if it's an OS/software/driver issue that is causing the BSODs then move to hardware.

All that said as I mentioned that PSU is not the best quality 550W out there it is kind of "just enough" with an i7-13700 and a 2060. Generally speaking having a little headroom with PSUs is not a bad thing, especially when the unit is not the best out there.

Does the software you mentioned that does some work overnight utilize the computational aspects of the GPU or is it CPU-intensive work?

I'll keep it in mind if all else fails, who knows it could be the PSU

No the software isn't very resource hungry at all. The only reason we got the GPU was because the PC would be using three monitors so it was just for the display ports.

I've checked the PC while running multiple tests and all resources are running very low (CPU ~30% Memory ~40%). We did think this as a potential issue but when we analysed the resources used they never went over 50% usage so we ruled that out.

 

[gardenman]

Welcome to the forums.

If you look at the Debugger log file, near the end you will see the FAILURE line. That line, with the few lines above it, point to a specific driver that was the likely cause of this crash.

SYMBOL_NAME: BbNBus41+18e9c

MODULE_NAME: BbNBus41

IMAGE_NAME: BbNBus41.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 18e9c

FAILURE_BUCKET_ID: 0x13a_11_SsKi_BbNBus41!unknown_function

Driver filenames end with .sys. As we can see, the BbNBus41.sys driver was blamed for this crash.

If you look that driver up, there's not many results. We need more info about what that driver is. Search your computer for the file (likely located in C:\Windows\system32\drivers). If you find it, right click on it and choose Properties to get more information about the file. Look through all of the tabs in Properties. Try to find out what device the driver is for. Then try to find a driver update for that device (or an older version of the driver if a new one isn't available).

My guess is that since the BUS is part of the motherboard, look for a motherboard (chipset) driver update.
https://www.asus.com/us/motherboard...lpdesk_download?model2Name=PRIME-B760-PLUS-D4
Verify this is the correct motherboard before downloading anything.

This is only 1 crash. Multiple crash dumps would be better to help figure it out. Also, you posted the output from the Debugger. The actual dump files contain much more information. They are located in the C:\Windows\minidump folder and end with .DMP. Others here are able to read these dump files better than myself so if you post them maybe someone else will jump in and help.

 

[Satan-IR]

I'll keep it in mind if all else fails, who knows it could be the PSU

No the software isn't very resource hungry at all. The only reason we got the GPU was because the PC would be using three monitors so it was just for the display ports.

I've checked the PC while running multiple tests and all resources are running very low (CPU ~30% Memory ~40%). We did think this as a potential issue but when we analysed the resources used they never went over 50% usage so we ruled that out.

Yes, I asked about it because a GPU-intensive operation overnight would put strain on that PSU. If it's not GPU-bound and almost 1/3 of system resources are used while it's working you're good to go.

What @gardenman said it a good catch. If you upload the dump files somewere and give links we can have a look at them and probably pinpoint the driver that might be causing this.

 

[pinapple198]

Welcome to the forums.

If you look at the Debugger log file, near the end you will see the FAILURE line. That line, with the few lines above it, point to a specific driver that was the likely cause of this crash.



Driver filenames end with .sys. As we can see, the BbNBus41.sys driver was blamed for this crash.

If you look that driver up, there's not many results. We need more info about what that driver is. Search your computer for the file (likely located in C:\Windows\system32\drivers). If you find it, right click on it and choose Properties to get more information about the file. Look through all of the tabs in Properties. Try to find out what device the driver is for. Then try to find a driver update for that device (or an older version of the driver if a new one isn't available).

My guess is that since the BUS is part of the motherboard, look for a motherboard (chipset) driver update.
https://www.asus.com/us/motherboard...lpdesk_download?model2Name=PRIME-B760-PLUS-D4
Verify this is the correct motherboard before downloading anything.

This is only 1 crash. Multiple crash dumps would be better to help figure it out. Also, you posted the output from the Debugger. The actual dump files contain much more information. They are located in the C:\Windows\minidump folder and end with .DMP. Others here are able to read these dump files better than myself so if you post them maybe someone else will jump in and help.

Amazing! Thanks for the reply, I've found the driver that is causing the issue so I can actually pinpoint what it is

I searched around for the BbNBus41.sys driver and there was zero results any where but I had no idea I could look in the drivers folder like you mentioned. The driver is 'Brainboxes Boost.LAN Bus Driver' which we use on various PCs but we've never had an issue with it before. I will update that particular driver and see if that fixes the issues, even though it hasn't actually crashed in a week today.

As for the dump file I didn't realise that, I'll keep that in mind if I am still struggling upload them for people to view!

Thanks again!