- Dec 26, 2023
- 5
- 1
- 15
Hey there, so I had posted a few weeks ago in the process of getting a build together as I had some confusions on PSUs and got that all straightened out.
I got this build together and spent about an hour installing drivers/software and went into a loop of bluescreens. After fighting for a couple days I reformatted from 11 back to 10 and was doing fine for 2-3 days I think before getting a blue screen again this morning.
----------------
My spec is as follows
H7 Flow
Windows 10 Pro [22H2] Build 19045.3803
Samsung 970 Evo M.2 2TB [MZ-V7S2T0B]
Gigabyte Z790 UD AX Rev 1.1 [Firmware version F8]
i7 13700kf
Noctua NH-D15
32gb vengeance ddr5 at 6GT, (2x 16) CL36
https://www.amazon.com/dp/B0B15DST2L?psc=1&ref=ppx_yo2ov_dt_b_product_details
Corsair RM750e
I plan to add a gigabyte 4060 eagle with it, but hit my budget where I'm currently at and figured I could grab it once I have the cash available.
As a result I am currently using my old card from some time ago the R9 200 series Twin Frozr. I believe its a 290x, however I can't remember at this point and failed to match it up comparing to the lists online.
----------------
I am a noob when it comes to UEFI and setting things in there so I believe there may be potential there is something wrong on that side but I am clueless! I did change one thing during the loop of bluescreens before reformatting. I noticed a 'DDR5 Booster' and questioned if it was trying to push it in ways it shouldn't be. I have not messed around with XMP or anything yet as I really don't know what I am doing. Ram according to MB is currently running at 4800 out of the potential 6000. (If that's even helpful) I did run memtest86 and came back in good shape.
During the bluescreen loop I did a bit of poor research and found some info on further diagnosing BSOD's, but I am very much still lost. I have until the end of the month to do a free return if it turns out there's an actual hardware issue so I am hoping to figure it out ASAP.
Here is my userbench
https://www.userbenchmark.com/UserRun/66943347
----------------
Below will be the full debug, however I wanted to point out the only things that stood out to me to try and test my understanding of what I am seeing here.
When searching dxgmms2 bsod I get information about graphics card issues. My probably very incorrect reading is thinking the drivers for this thing aren't getting along with the newer hardware / windows?
IRQL_NOT_LESS_OR_EQUAL
PROCESS_NAME: taskhostw.exe
TRAP_FRAME: fffffb8344c47170 -- (.trap 0xfffffb8344c47170)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
SYMBOL_NAME: dxgmms2!VIDMM_GLOBAL::Lock+1f9
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
I had a variety of codes on the first install however this is the only one I have experienced since reformatting. If it helps I can post up the list from before hand, I do not have the DBG info and figure it may help to not make this post any longer.
I got this build together and spent about an hour installing drivers/software and went into a loop of bluescreens. After fighting for a couple days I reformatted from 11 back to 10 and was doing fine for 2-3 days I think before getting a blue screen again this morning.
----------------
My spec is as follows
H7 Flow
Windows 10 Pro [22H2] Build 19045.3803
Samsung 970 Evo M.2 2TB [MZ-V7S2T0B]
Gigabyte Z790 UD AX Rev 1.1 [Firmware version F8]
i7 13700kf
Noctua NH-D15
32gb vengeance ddr5 at 6GT, (2x 16) CL36
https://www.amazon.com/dp/B0B15DST2L?psc=1&ref=ppx_yo2ov_dt_b_product_details
Corsair RM750e
I plan to add a gigabyte 4060 eagle with it, but hit my budget where I'm currently at and figured I could grab it once I have the cash available.
As a result I am currently using my old card from some time ago the R9 200 series Twin Frozr. I believe its a 290x, however I can't remember at this point and failed to match it up comparing to the lists online.
----------------
I am a noob when it comes to UEFI and setting things in there so I believe there may be potential there is something wrong on that side but I am clueless! I did change one thing during the loop of bluescreens before reformatting. I noticed a 'DDR5 Booster' and questioned if it was trying to push it in ways it shouldn't be. I have not messed around with XMP or anything yet as I really don't know what I am doing. Ram according to MB is currently running at 4800 out of the potential 6000. (If that's even helpful) I did run memtest86 and came back in good shape.
During the bluescreen loop I did a bit of poor research and found some info on further diagnosing BSOD's, but I am very much still lost. I have until the end of the month to do a free return if it turns out there's an actual hardware issue so I am hoping to figure it out ASAP.
Here is my userbench
https://www.userbenchmark.com/UserRun/66943347
----------------
Below will be the full debug, however I wanted to point out the only things that stood out to me to try and test my understanding of what I am seeing here.
When searching dxgmms2 bsod I get information about graphics card issues. My probably very incorrect reading is thinking the drivers for this thing aren't getting along with the newer hardware / windows?
IRQL_NOT_LESS_OR_EQUAL
PROCESS_NAME: taskhostw.exe
TRAP_FRAME: fffffb8344c47170 -- (.trap 0xfffffb8344c47170)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
SYMBOL_NAME: dxgmms2!VIDMM_GLOBAL::Lock+1f9
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
I had a variety of codes on the first install however this is the only one I have experienced since reformatting. If it helps I can post up the list from before hand, I do not have the DBG info and figure it may help to not make this post any longer.
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : false
AllowNugetExeUpdate : false
AllowNugetMSCredentialProviderInstall : false
AllowParallelInitializationOfLocalRepositories : true
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.032 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 36
Microsoft (R) Windows Debugger Version 10.0.25877.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff803`26a00000 PsLoadedModuleList = 0xfffff803`2762a770
Debug session time: Tue Jan 9 08:44:44.681 2024 (UTC - 5:00)
System Uptime: 1 days 0:53:01.317
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000d5`a6991018). Type ".hh dbgerr001" for details
Loading unloaded module list
.............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`26dfd6f0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffb83`44c47030=000000000000000a
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000800000076, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80326cf4c70, address which referenced memory
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1437
Key : Analysis.Elapsed.mSec
Value: 5153
Key : Analysis.IO.Other.Mb
Value: 7
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 32
Key : Analysis.Init.CPU.mSec
Value: 843
Key : Analysis.Init.Elapsed.mSec
Value: 218102
Key : Analysis.Memory.CommitPeak.Mb
Value: 109
Key : Bugcheck.Code.KiBugCheckData
Value: 0xa
Key : Bugcheck.Code.LegacyAPI
Value: 0xa
Key : Failure.Bucket
Value: AV_dxgmms2!VIDMM_GLOBAL::Lock
Key : Failure.Hash
Value: {f54654e1-4f15-1177-153e-8a94559e810b}
Key : Hypervisor.Enlightenments.Value
Value: 0
Key : Hypervisor.Enlightenments.ValueHex
Value: 0
Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 0
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: 0
Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0
Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 0
Key : Hypervisor.Flags.Epf
Value: 0
Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 0
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: 0
Key : Hypervisor.Flags.Phase0InitDone
Value: 0
Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0
Key : Hypervisor.Flags.RootScheduler
Value: 0
Key : Hypervisor.Flags.SynicAvailable
Value: 0
Key : Hypervisor.Flags.UseQpcBias
Value: 0
Key : Hypervisor.Flags.Value
Value: 16908288
Key : Hypervisor.Flags.ValueHex
Value: 1020000
Key : Hypervisor.Flags.VpAssistPage
Value: 0
Key : Hypervisor.Flags.VsmAvailable
Value: 0
Key : Hypervisor.RootFlags.AccessStats
Value: 0
Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 0
Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 0
Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0
Key : Hypervisor.RootFlags.HostTimelineSync
Value: 0
Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0
Key : Hypervisor.RootFlags.IsHyperV
Value: 0
Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 0
Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 0
Key : Hypervisor.RootFlags.MceEnlightened
Value: 0
Key : Hypervisor.RootFlags.Nested
Value: 0
Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 0
Key : Hypervisor.RootFlags.Value
Value: 0
Key : Hypervisor.RootFlags.ValueHex
Value: 0
Key : SecureKernel.HalpHvciEnabled
Value: 0
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: a
BUGCHECK_P1: 800000076
BUGCHECK_P2: 2
BUGCHECK_P3: 0
BUGCHECK_P4: fffff80326cf4c70
FILE_IN_CAB: MEMORY.DMP
READ_ADDRESS: 0000000800000076
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
PROCESS_NAME: taskhostw.exe
TRAP_FRAME: fffffb8344c47170 -- (.trap 0xfffffb8344c47170)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000025000000de rbx=0000000000000000 rcx=0000000000000067
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80326cf4c70 rsp=fffffb8344c47300 rbp=fffff803276e6b50
r8=fffffb8344c47408 r9=0000000000000000 r10=fffff803276e9f40
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!KiAbEntryGetLockedHeadEntry+0x100:
fffff803`26cf4c70 488b4320 mov rax,qword ptr [rbx+20h] ds:00000000`00000020=????????????????
Resetting default scope
STACK_TEXT:
fffffb83`44c47028 fffff803`26e11aa9 : 00000000`0000000a 00000008`00000076 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffffb83`44c47030 fffff803`26e0d563 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffffb83`44c47170 fffff803`26cf4c70 : 00000000`00000001 fffffb83`44c473c0 ffffd585`97a842f0 fffffb83`44c473f0 : nt!KiPageFault+0x463
fffffb83`44c47300 fffff803`26c424cd : ffff8a0e`2cd9e730 fffffb83`44c47409 fffffb83`44c47408 ffff8a0e`00000000 : nt!KiAbEntryGetLockedHeadEntry+0x100
fffffb83`44c473a0 fffff803`26c40e73 : 00000000`00000000 fffff803`00000000 00000000`00000000 ffff8a0e`00000001 : nt!KiAbProcessContextSwitch+0x11d
fffffb83`44c47470 fffff803`26c4085f : fffffb83`44c47688 fffff803`407ac6a8 fffffb83`44c47630 fffffb83`44c47ac0 : nt!KiSwapThread+0x43
fffffb83`44c47520 fffff803`26c40103 : 00000000`00000000 00000000`00000000 00000000`00000000 ffff8a0e`2cd9e1c0 : nt!KiCommitThreadWait+0x14f
fffffb83`44c475c0 fffff803`26cf60b0 : fffffb83`44c476e0 fffff803`0000001c ffff8a0e`2cd9e000 ffff8a0e`2cd9e000 : nt!KeWaitForSingleObject+0x233
fffffb83`44c476b0 fffff803`26c45512 : ffff8a0e`00000000 ffff8a0e`2cd9e118 00000000`00000000 fffff803`4062d04e : nt!ExfAcquirePushLockExclusiveEx+0x1a0
fffffb83`44c47760 fffff803`428eb079 : ffff8a0e`2c8c0080 fffff803`00000001 fffffb83`00000000 ffff8a0e`1cb71d10 : nt!ExAcquirePushLockExclusiveEx+0x1a2
fffffb83`44c477a0 fffff803`42881699 : fffffb83`44c47ac0 ffffd585`9c48ede0 ffffd585`75765c00 ffffffff`ffffffff : dxgmms2!VIDMM_GLOBAL::Lock+0x1f9
fffffb83`44c47860 fffff803`40631576 : 00000000`00000001 fffffb83`44c47ac0 ffffffff`ffffffff ffffd585`916db840 : dxgmms2!VidMmLock+0x9
fffffb83`44c47890 fffff803`26e11235 : ffff8a0e`2cd90000 ffff8a0e`2cd9e080 00000297`f4b3bbd0 fffffb83`44c47ac0 : dxgkrnl!DxgkLock2+0x396
fffffb83`44c47a40 00007ffd`e0515024 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000d5`a6b78238 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`e0515024
SYMBOL_NAME: dxgmms2!VIDMM_GLOBAL::Lock+1f9
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.19041.3758
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 1f9
FAILURE_BUCKET_ID: AV_dxgmms2!VIDMM_GLOBAL::Lock
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {f54654e1-4f15-1177-153e-8a94559e810b}
Followup: MachineOwner
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : false
AllowNugetExeUpdate : false
AllowNugetMSCredentialProviderInstall : false
AllowParallelInitializationOfLocalRepositories : true
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.032 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 36
Microsoft (R) Windows Debugger Version 10.0.25877.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff803`26a00000 PsLoadedModuleList = 0xfffff803`2762a770
Debug session time: Tue Jan 9 08:44:44.681 2024 (UTC - 5:00)
System Uptime: 1 days 0:53:01.317
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000d5`a6991018). Type ".hh dbgerr001" for details
Loading unloaded module list
.............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`26dfd6f0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffb83`44c47030=000000000000000a
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000800000076, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80326cf4c70, address which referenced memory
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1437
Key : Analysis.Elapsed.mSec
Value: 5153
Key : Analysis.IO.Other.Mb
Value: 7
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 32
Key : Analysis.Init.CPU.mSec
Value: 843
Key : Analysis.Init.Elapsed.mSec
Value: 218102
Key : Analysis.Memory.CommitPeak.Mb
Value: 109
Key : Bugcheck.Code.KiBugCheckData
Value: 0xa
Key : Bugcheck.Code.LegacyAPI
Value: 0xa
Key : Failure.Bucket
Value: AV_dxgmms2!VIDMM_GLOBAL::Lock
Key : Failure.Hash
Value: {f54654e1-4f15-1177-153e-8a94559e810b}
Key : Hypervisor.Enlightenments.Value
Value: 0
Key : Hypervisor.Enlightenments.ValueHex
Value: 0
Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 0
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: 0
Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0
Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 0
Key : Hypervisor.Flags.Epf
Value: 0
Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 0
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: 0
Key : Hypervisor.Flags.Phase0InitDone
Value: 0
Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0
Key : Hypervisor.Flags.RootScheduler
Value: 0
Key : Hypervisor.Flags.SynicAvailable
Value: 0
Key : Hypervisor.Flags.UseQpcBias
Value: 0
Key : Hypervisor.Flags.Value
Value: 16908288
Key : Hypervisor.Flags.ValueHex
Value: 1020000
Key : Hypervisor.Flags.VpAssistPage
Value: 0
Key : Hypervisor.Flags.VsmAvailable
Value: 0
Key : Hypervisor.RootFlags.AccessStats
Value: 0
Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 0
Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 0
Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0
Key : Hypervisor.RootFlags.HostTimelineSync
Value: 0
Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0
Key : Hypervisor.RootFlags.IsHyperV
Value: 0
Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 0
Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 0
Key : Hypervisor.RootFlags.MceEnlightened
Value: 0
Key : Hypervisor.RootFlags.Nested
Value: 0
Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 0
Key : Hypervisor.RootFlags.Value
Value: 0
Key : Hypervisor.RootFlags.ValueHex
Value: 0
Key : SecureKernel.HalpHvciEnabled
Value: 0
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: a
BUGCHECK_P1: 800000076
BUGCHECK_P2: 2
BUGCHECK_P3: 0
BUGCHECK_P4: fffff80326cf4c70
FILE_IN_CAB: MEMORY.DMP
READ_ADDRESS: 0000000800000076
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
PROCESS_NAME: taskhostw.exe
TRAP_FRAME: fffffb8344c47170 -- (.trap 0xfffffb8344c47170)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000025000000de rbx=0000000000000000 rcx=0000000000000067
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80326cf4c70 rsp=fffffb8344c47300 rbp=fffff803276e6b50
r8=fffffb8344c47408 r9=0000000000000000 r10=fffff803276e9f40
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!KiAbEntryGetLockedHeadEntry+0x100:
fffff803`26cf4c70 488b4320 mov rax,qword ptr [rbx+20h] ds:00000000`00000020=????????????????
Resetting default scope
STACK_TEXT:
fffffb83`44c47028 fffff803`26e11aa9 : 00000000`0000000a 00000008`00000076 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffffb83`44c47030 fffff803`26e0d563 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffffb83`44c47170 fffff803`26cf4c70 : 00000000`00000001 fffffb83`44c473c0 ffffd585`97a842f0 fffffb83`44c473f0 : nt!KiPageFault+0x463
fffffb83`44c47300 fffff803`26c424cd : ffff8a0e`2cd9e730 fffffb83`44c47409 fffffb83`44c47408 ffff8a0e`00000000 : nt!KiAbEntryGetLockedHeadEntry+0x100
fffffb83`44c473a0 fffff803`26c40e73 : 00000000`00000000 fffff803`00000000 00000000`00000000 ffff8a0e`00000001 : nt!KiAbProcessContextSwitch+0x11d
fffffb83`44c47470 fffff803`26c4085f : fffffb83`44c47688 fffff803`407ac6a8 fffffb83`44c47630 fffffb83`44c47ac0 : nt!KiSwapThread+0x43
fffffb83`44c47520 fffff803`26c40103 : 00000000`00000000 00000000`00000000 00000000`00000000 ffff8a0e`2cd9e1c0 : nt!KiCommitThreadWait+0x14f
fffffb83`44c475c0 fffff803`26cf60b0 : fffffb83`44c476e0 fffff803`0000001c ffff8a0e`2cd9e000 ffff8a0e`2cd9e000 : nt!KeWaitForSingleObject+0x233
fffffb83`44c476b0 fffff803`26c45512 : ffff8a0e`00000000 ffff8a0e`2cd9e118 00000000`00000000 fffff803`4062d04e : nt!ExfAcquirePushLockExclusiveEx+0x1a0
fffffb83`44c47760 fffff803`428eb079 : ffff8a0e`2c8c0080 fffff803`00000001 fffffb83`00000000 ffff8a0e`1cb71d10 : nt!ExAcquirePushLockExclusiveEx+0x1a2
fffffb83`44c477a0 fffff803`42881699 : fffffb83`44c47ac0 ffffd585`9c48ede0 ffffd585`75765c00 ffffffff`ffffffff : dxgmms2!VIDMM_GLOBAL::Lock+0x1f9
fffffb83`44c47860 fffff803`40631576 : 00000000`00000001 fffffb83`44c47ac0 ffffffff`ffffffff ffffd585`916db840 : dxgmms2!VidMmLock+0x9
fffffb83`44c47890 fffff803`26e11235 : ffff8a0e`2cd90000 ffff8a0e`2cd9e080 00000297`f4b3bbd0 fffffb83`44c47ac0 : dxgkrnl!DxgkLock2+0x396
fffffb83`44c47a40 00007ffd`e0515024 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000d5`a6b78238 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`e0515024
SYMBOL_NAME: dxgmms2!VIDMM_GLOBAL::Lock+1f9
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.19041.3758
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 1f9
FAILURE_BUCKET_ID: AV_dxgmms2!VIDMM_GLOBAL::Lock
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {f54654e1-4f15-1177-153e-8a94559e810b}
Followup: MachineOwner
Last edited:
Facebook
Twitter
Instagram