Hello everyone,
Over the past couple of months i've been getting BSODs whilst gaming or sometimes just about doing anything like using chrome or just file explorer. These BSODs sometimes make my SSD unable to be detected on boot with the 'Select Proper Boot Device' message. So I did the usual stuff like check drivers and storage drive health. Funnily enough I did find that after updating my Nvidia drivers (they were only 2 months outdated ), the BSODs stopped. But now they've returned URGH.
It's worth to note that I very recently got an extra 32GB of RAM which is identical to the RAM that I put in a couple years ago.
Some PC specs; RTX 3080, Ryzen 7 5800X, 64GB Corsair Vengeance. 750W PSU
So now I'm not sure if it's BIOS, chipset, the new RAM, or SSD related.
Anyhoo, here's my most recent minidump analysis.
Kind Regards. Beanbag.
<Mod Edit: Moved long debugger log to a spoiler.>
Over the past couple of months i've been getting BSODs whilst gaming or sometimes just about doing anything like using chrome or just file explorer. These BSODs sometimes make my SSD unable to be detected on boot with the 'Select Proper Boot Device' message. So I did the usual stuff like check drivers and storage drive health. Funnily enough I did find that after updating my Nvidia drivers (they were only 2 months outdated ), the BSODs stopped. But now they've returned URGH.
It's worth to note that I very recently got an extra 32GB of RAM which is identical to the RAM that I put in a couple years ago.
Some PC specs; RTX 3080, Ryzen 7 5800X, 64GB Corsair Vengeance. 750W PSU
So now I'm not sure if it's BIOS, chipset, the new RAM, or SSD related.
Anyhoo, here's my most recent minidump analysis.
Kind Regards. Beanbag.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000006, Exception code that caused the BugCheck
Arg2: fffff8071d73e052, Address of the instruction which caused the BugCheck
Arg3: ffffbd83f3527350, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ContextRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ContextRecord ***
*** ***
*************************************************************************
*** WARNING: Check Image - Checksum mismatch - Dump: 0x20397e, File: 0x203a06 - C:\ProgramData\Dbg\sym\BTHport.sys\5249EE07202000\BTHport.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2452
Key : Analysis.Elapsed.mSec
Value: 12361
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 4
Key : Analysis.Init.CPU.mSec
Value: 171
Key : Analysis.Init.Elapsed.mSec
Value: 25374
Key : Analysis.Memory.CommitPeak.Mb
Value: 94
Key : Bugcheck.Code.LegacyAPI
Value: 0x3b
Key : Dump.Attributes.AsUlong
Value: 1008
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: 0x3B_C0000006_nt!HvpGetCellPaged
Key : Failure.Hash
Value: {68f3db38-ae8e-4bae-c37a-85819946495f}
BUGCHECK_CODE: 3b
BUGCHECK_P1: c0000006
BUGCHECK_P2: fffff8071d73e052
BUGCHECK_P3: ffffbd83f3527350
BUGCHECK_P4: 0
FILE_IN_CAB: 121223-29953-01.dmp
DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump
CONTEXT: ffffbd83f3527350 -- (.cxr 0xffffbd83f3527350)
rax=00000141d4117000 rbx=0000000075f95b89 rcx=ffffd10aaf374000
rdx=00000141d4117000 rsi=0000000008446fe0 rdi=0000000000000fe0
rip=fffff8071d73e052 rsp=ffffbd83f3527d70 rbp=ffffbd83f3527eb0
r8=ffffbd83f3527e1c r9=0000000000000046 r10=ffffd10aaf374000
r11=ffffbd83f3527d58 r12=0000000000000000 r13=ffffd10aaf374000
r14=ffffbd83f3527e18 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050206
nt!HvpGetCellPaged+0xa2:
fffff807`1d73e052 8b0417 mov eax,dword ptr [rdi+rdx] ds:002b:00000141`d4117fe0=????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: Registry
STACK_TEXT:
ffffbd83`f3527d70 fffff807`1d73c7e2 : 00000000`75f95b89 00000000`00010cdf 00000000`c0000034 00000000`00000000 : nt!HvpGetCellPaged+0xa2
ffffbd83`f3527db0 fffff807`1d7467a9 : ffffd10a`cdf37950 ffffbd83`f3528130 ffffbd83`f3528028 ffffbd83`f3528150 : nt!CmpWalkOneLevel+0x5c2
ffffbd83`f3527f00 fffff807`1d742b35 : ffffd10b`0000001c ffffbd83`f3528440 ffffbd83`f35283c8 00000000`00000000 : nt!CmpDoParseKey+0x17d9
ffffbd83`f3528350 fffff807`1d6f2884 : fffff807`1d742801 ffff9306`00000000 ffff9306`57dc95e0 fffff807`1d321101 : nt!CmpParseKey+0x2e5
ffffbd83`f3528540 fffff807`1d6f1232 : ffff9306`57dc9501 ffffbd83`f3528760 00000000`00000040 ffff9306`307f2220 : nt!ObpLookupObjectName+0x1104
ffffbd83`f35286d0 fffff807`1d6f0a64 : 00000000`00000000 ffff9306`307f2220 00000000`00000000 00000000`00000000 : nt!ObOpenObjectByNameEx+0x1f2
ffffbd83`f3528800 fffff807`1d6efe38 : 00000000`00c8e328 00000000`00d8eb00 fffff807`1d4128a0 fffff807`1d32b07a : nt!CmOpenKey+0x2c4
ffffbd83`f3528a50 fffff807`1d42b6e8 : ffff9306`534f2080 00007ff8`539d5b01 00000000`00c8fda0 00007ff8`00000000 : nt!NtOpenKeyEx+0x48
ffffbd83`f3528aa0 00007ff8`53b11884 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`00c8e308 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`53b11884
SYMBOL_NAME: nt!HvpGetCellPaged+a2
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.22621.2715
STACK_COMMAND: .cxr 0xffffbd83f3527350 ; kb
BUCKET_ID_FUNC_OFFSET: a2
FAILURE_BUCKET_ID: 0x3B_C0000006_nt!HvpGetCellPaged
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {68f3db38-ae8e-4bae-c37a-85819946495f}
Followup: MachineOwner
---------
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000006, Exception code that caused the BugCheck
Arg2: fffff8071d73e052, Address of the instruction which caused the BugCheck
Arg3: ffffbd83f3527350, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ContextRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ContextRecord ***
*** ***
*************************************************************************
*** WARNING: Check Image - Checksum mismatch - Dump: 0x20397e, File: 0x203a06 - C:\ProgramData\Dbg\sym\BTHport.sys\5249EE07202000\BTHport.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2452
Key : Analysis.Elapsed.mSec
Value: 12361
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 4
Key : Analysis.Init.CPU.mSec
Value: 171
Key : Analysis.Init.Elapsed.mSec
Value: 25374
Key : Analysis.Memory.CommitPeak.Mb
Value: 94
Key : Bugcheck.Code.LegacyAPI
Value: 0x3b
Key : Dump.Attributes.AsUlong
Value: 1008
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: 0x3B_C0000006_nt!HvpGetCellPaged
Key : Failure.Hash
Value: {68f3db38-ae8e-4bae-c37a-85819946495f}
BUGCHECK_CODE: 3b
BUGCHECK_P1: c0000006
BUGCHECK_P2: fffff8071d73e052
BUGCHECK_P3: ffffbd83f3527350
BUGCHECK_P4: 0
FILE_IN_CAB: 121223-29953-01.dmp
DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump
CONTEXT: ffffbd83f3527350 -- (.cxr 0xffffbd83f3527350)
rax=00000141d4117000 rbx=0000000075f95b89 rcx=ffffd10aaf374000
rdx=00000141d4117000 rsi=0000000008446fe0 rdi=0000000000000fe0
rip=fffff8071d73e052 rsp=ffffbd83f3527d70 rbp=ffffbd83f3527eb0
r8=ffffbd83f3527e1c r9=0000000000000046 r10=ffffd10aaf374000
r11=ffffbd83f3527d58 r12=0000000000000000 r13=ffffd10aaf374000
r14=ffffbd83f3527e18 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050206
nt!HvpGetCellPaged+0xa2:
fffff807`1d73e052 8b0417 mov eax,dword ptr [rdi+rdx] ds:002b:00000141`d4117fe0=????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: Registry
STACK_TEXT:
ffffbd83`f3527d70 fffff807`1d73c7e2 : 00000000`75f95b89 00000000`00010cdf 00000000`c0000034 00000000`00000000 : nt!HvpGetCellPaged+0xa2
ffffbd83`f3527db0 fffff807`1d7467a9 : ffffd10a`cdf37950 ffffbd83`f3528130 ffffbd83`f3528028 ffffbd83`f3528150 : nt!CmpWalkOneLevel+0x5c2
ffffbd83`f3527f00 fffff807`1d742b35 : ffffd10b`0000001c ffffbd83`f3528440 ffffbd83`f35283c8 00000000`00000000 : nt!CmpDoParseKey+0x17d9
ffffbd83`f3528350 fffff807`1d6f2884 : fffff807`1d742801 ffff9306`00000000 ffff9306`57dc95e0 fffff807`1d321101 : nt!CmpParseKey+0x2e5
ffffbd83`f3528540 fffff807`1d6f1232 : ffff9306`57dc9501 ffffbd83`f3528760 00000000`00000040 ffff9306`307f2220 : nt!ObpLookupObjectName+0x1104
ffffbd83`f35286d0 fffff807`1d6f0a64 : 00000000`00000000 ffff9306`307f2220 00000000`00000000 00000000`00000000 : nt!ObOpenObjectByNameEx+0x1f2
ffffbd83`f3528800 fffff807`1d6efe38 : 00000000`00c8e328 00000000`00d8eb00 fffff807`1d4128a0 fffff807`1d32b07a : nt!CmOpenKey+0x2c4
ffffbd83`f3528a50 fffff807`1d42b6e8 : ffff9306`534f2080 00007ff8`539d5b01 00000000`00c8fda0 00007ff8`00000000 : nt!NtOpenKeyEx+0x48
ffffbd83`f3528aa0 00007ff8`53b11884 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`00c8e308 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`53b11884
SYMBOL_NAME: nt!HvpGetCellPaged+a2
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.22621.2715
STACK_COMMAND: .cxr 0xffffbd83f3527350 ; kb
BUCKET_ID_FUNC_OFFSET: a2
FAILURE_BUCKET_ID: 0x3B_C0000006_nt!HvpGetCellPaged
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {68f3db38-ae8e-4bae-c37a-85819946495f}
Followup: MachineOwner
---------
<Mod Edit: Moved long debugger log to a spoiler.>
Last edited by a moderator:
Facebook
Twitter
Instagram