Question Need Help With BSOD! please <:L

steelseeker · Dec 31, 2021

hello, so over the past 4 months i been on and off blue screening and did some tests thinking it was becase of ram. i replaced my name with new ram and still keep having the same issues, i have also did a clean install of windows 10 on my ssd to see if that fixs the issue it keeps happening when am in games like path of exile and ark.

i have tryed googling the errors and done what all have said. new ram clean install disable drivers update ect, my system besides the blue screens seem to be ruining normally but randomly blue screen when playing games. some time just useing firefox.

i have i5-9600k 3.7hz
ddr4 3600hz ram
2070 super gtx
tb ssd for C drive
all my parts are like 1 year old or 2.
and 1 ssd for games and normal harddrive for stuff :l
here are 2 of my recent crashs, did a fresh clean in stall 1 week ago didnt play much games so didnt blue screen. then started and it happend

the old ram i had a i did a ram test that boots from flash drive and it had 50 errors so i asumed i had bad ram.

steelseeker · Dec 31, 2021

steelseeker · Dec 31, 2021

i can only think of one thing atm and thats my ssd is failing ? but i dont know how to check that. also when i crashed 1 time my game was only installed on my other ssd. and the most recent one was on my main c drive. i have a ssd drive for ark its 500gb and ark is 420gb XD

steelseeker · Dec 31, 2021

Loading Dump File [C:\Windows\Minidump\123121-10953-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff8002ae00000 PsLoadedModuleList = 0xfffff8002ba2a1b0
Debug session time: Fri Dec 31 16:54:17.355 2021 (UTC - 5:00)
System Uptime: 3 days 9:04:06.049
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....
Loading User Symbols
Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff8002b1f70d0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffc50cc921eff0=00000000000000fc
1: kd> !analyze -v
***

*
Bugcheck Analysis *
*

***

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory. The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name is printed on
the BugCheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: ffff808cdddb7270, Virtual address for the attempted execute.
Arg2: 8a0000016be009e3, PTE contents.
Arg3: ffffc50cc921f220, (reserved)
Arg4: 0000000000000003, (reserved)

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3140

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 23030

Key : Analysis.Init.CPU.mSec
Value: 531

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

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

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1

FILE_IN_CAB: 123121-10953-01.dmp

BUGCHECK_CODE: fc

BUGCHECK_P1: ffff808cdddb7270

BUGCHECK_P2: 8a0000016be009e3

BUGCHECK_P3: ffffc50cc921f220

BUGCHECK_P4: 3

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: voicemeeter8x64.exe

TRAP_FRAME: ffffc50cc921f220 -- (.trap 0xffffc50cc921f220)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000002a781e3fda0 rbx=0000000000000000 rcx=fffff7d7c0001000
rdx=000002a78aba9c44 rsi=0000000000000000 rdi=0000000000000000
rip=ffff808cdddb7270 rsp=ffffc50cc921f3b8 rbp=0000000000000000
r8=fffffffff729615c r9=000002a781e3f438 r10=fffff8002b163250
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
ffff808cdddb7270 80969800000000 adc byte ptr [rsi+98h],0 ds:0000000000000098=??
Resetting default scope

STACK_TEXT:
ffffc50cc921efe8 fffff8002b283e28 : 00000000000000fc ffff808cdddb7270 8a0000016be009e3 ffffc50cc921f220 : nt!KeBugCheckEx
ffffc50cc921eff0 fffff8002b275637 : 0000000000000011 0000000000000003 0000000000000000 ffffc50cc921f140 : nt!MiCheckSystemNxFault+0x12dd20
ffffc50cc921f030 fffff8002b09f55f : 0000000000000000 0000000000000011 ffffc50cc921f2a0 0000000000000000 : nt!MiRaisedIrqlFault+0x14237b
ffffc50cc921f080 fffff8002b20525e : 0000000000000001 fffff8002b0f3f00 ffffc50cc921f748 0000000000000050 : nt!MmAccessFault+0x4ef
ffffc50cc921f220 ffff808cdddb7270 : ffff808ce221eab0 0000000000989680 000000000000270f ffff808cdddb7270 : nt!KiPageFault+0x35e
ffffc50cc921f3b8 ffff808ce221eab0 : 0000000000989680 000000000000270f ffff808cdddb7270 0000000000000000 : 0xffff808c

dddb7270
ffffc50c

c921f3c0 0000000000989680 : 000000000000270f ffff808cdddb7270 0000000000000000 ffff808c00000000 : 0xffff808ce221eab0
ffffc50cc921f3c8 000000000000270f : ffff808cdddb7270 0000000000000000 ffff808c00000000 ffffc50cc921f524 : 0x989680
ffffc50cc921f3d0 ffff808cdddb7270 : 0000000000000000 ffff808c00000000 ffffc50cc921f524 0000000011652c79 : 0x270f
ffffc50cc921f3d8 0000000000000000 : ffff808c00000000 ffffc50cc921f524 0000000011652c79 000002a781c8569d : 0xffff808c`dddb7270

SYMBOL_NAME: nt!MiCheckSystemNxFault+12dd20

MODULE_NAME: nt

IMAGE_VERSION: 10.0.19041.1415

STACK_COMMAND: .cxr; .ecxr ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 12dd20

FAILURE_BUCKET_ID: 0xFC_nt!MiCheckSystemNxFault

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {a6ae5288-6b71-974a-9b09-23f14d998164}

steelseeker · Dec 31, 2021

that was my dump file. so does that mean voicemeater is blue screening me?

steelseeker · Dec 31, 2021

Loading Dump File [C:\Windows\Minidump\122821-9593-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80068a00000 PsLoadedModuleList = 0xfffff8006962a1b0
Debug session time: Tue Dec 28 07:03:09.075 2021 (UTC - 5:00)
System Uptime: 0 days 3:58:19.769
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
.......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff80068df70d0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffa906cf49e5a0=000000000000003b
3: kd> !analyze -v
***

*
Bugcheck Analysis *
*

***

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff8007ec8c482, Address of the instruction which caused the BugCheck
Arg3: ffffa906cf49eea0, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3249

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 19391

Key : Analysis.Init.CPU.mSec
Value: 312

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

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

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1

FILE_IN_CAB: 122821-9593-01.dmp

BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8007ec8c482

BUGCHECK_P3: ffffa906cf49eea0

BUGCHECK_P4: 0

CONTEXT: ffffa906cf49eea0 -- (.cxr 0xffffa906cf49eea0)
rax=0000000000000001 rbx=ffff8008aca79000 rcx=0000000000000011
rdx=ffff8008aca79088 rsi=ffff8008aca79000 rdi=ffff8008a8b65298
rip=fffff8007ec8c482 rsp=ffffa906cf49f8a0 rbp=ffffa906cf49f949
r8=ffffa906cf49f8b0 r9=ffff8008acaa3c20 r10=fffff80068c07c80
r11=ffff8008a435c220 r12=000000000193a000 r13=00000000016dfda0
r14=ffff8008a8b65298 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00250246
dxgkrnl!DXGGLOBAL::CheckExclusiveOwnership+0x212:
fffff800

7ec8c482 418bd7          mov     edx,r15d
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Spotify.exe

STACK_TEXT: 
ffffa906

cf49f8a0 fffff8007ec8c241 : 00007ffe71ac8100 00000000017def18 00000000000007ff fffff800

000007ff : dxgkrnl!DXGGLOBAL::CheckExclusiveOwnership+0x212
ffffa906

cf49f9b0 fffff80068e08ab5 : 0000000000000000 0000000006b6d200 ffffa906cf49fa18 ffffffff

ffdbd630 : dxgkrnl!DxgkCheckExclusiveOwnership+0x41
ffffa906

cf49fa00 00007ffe71ad3554 : 0000000000000000 0000000000000000 0000000000000000 00000000

00000000 : nt!KiSystemServiceCopyEnd+0x25
00000000

016de028 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffe71ad3554

SYMBOL_NAME: dxgkrnl!DXGGLOBAL::CheckExclusiveOwnership+212

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

IMAGE_VERSION: 10.0.19041.1415

STACK_COMMAND: .cxr 0xffffa906cf49eea0 ; kb

BUCKET_ID_FUNC_OFFSET: 212

FAILURE_BUCKET_ID: 0x3B_c0000005_dxgkrnl!DXGGLOBAL::CheckExclusiveOwnership

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {d8ccb9b4-0a41-7120-6d4b-fedf74268eac}

Followup: MachineOwner

steelseeker · Dec 31, 2021

i also have a hyperx cloud 2 hedset am woundering if that could make me blue screen? i think my blue screen issues have been around the same time i got this headset but that sounds kind crazy :/

Colif · Dec 31, 2021

2nd BSOD mentioned DirectX. 99% of DirectX errors caused by GPU drivers

try running DDU in safe mode and reinstall GPU drivers - https://forums.tomshardware.com/faq...n-install-of-your-video-card-drivers.2402269/

the other 1% of the errors can be Audio, so maybe headset?

Open Windows File Explore
Navigate to C:\Windows\Minidump
Copy the mini-dump files out onto your Desktop
Do not use Winzip, use the built in facility in Windows
Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
Then post a link here to the zip file, so we can take a look for you . . .

no rush with dumps, its NYE. I don't think the person who checks dumps for me will be around today but I could be wrong.

steelseeker · Dec 31, 2021

Colif said:
2nd BSOD mentioned DirectX. 99% of DirectX errors caused by GPU drivers

try running DDU in safe mode and reinstall GPU drivers - https://forums.tomshardware.com/faq...n-install-of-your-video-card-drivers.2402269/

the other 1% of the errors can be Audio, so maybe headset?

Open Windows File Explore

Navigate to C:\Windows\Minidump

Copy the mini-dump files out onto your Desktop

Do not use Winzip, use the built in facility in Windows

Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder

Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)

Then post a link here to the zip file, so we can take a look for you . . .

so restart and start in safemode and use ddu, then just restart back into normal boot and reinstall drivers?. also i did some google some people have had blue screens useing my headset, problom is its hard to repcate bluescreening its random it seems

Colif · Dec 31, 2021

steelseeker said:
so restart and start in safemode and use ddu, then just restart back into normal boot and reinstall drivers?.

thats the shortened version, yes.

BSOD will happen when they ready to.
Dump files might show more, they at least show what drivers are running at time. your reports don't.

steelseeker · Dec 31, 2021

Colif said:
thats the shortened version, yes.

BSOD will happen when they ready to.
Dump files might show more, they at least show what drivers are running at time. your reports don't.

okay, done reinstalling drivers gpu and i'll contine to play intell i get another hopefully its fix 😀 thanks will post back if i get another

Colif · Dec 31, 2021

might be audio since one victim of a crash was Voicemeter.

the minidump files should still be in your folder unless one of the programs you ran to get results deleted them.

steelseeker · Dec 31, 2021

Colif said:
might be audio since one victim of a crash was Voicemeter.

the minidump files should still be in your folder unless one of the programs you ran to get results deleted them.

Yea i was thinking that am going to do some testing i guss see if i dont crash for awhile with the fresh gpu drivers, if that doesnt help disable voicemeter go back to default sound settings

steelseeker · Dec 31, 2021

Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80080400000 PsLoadedModuleList = 0xfffff8008102a1b0
Debug session time: Fri Dec 31 18:49:03.448 2021 (UTC - 5:00)
System Uptime: 0 days 0:23:56.141
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....
Loading User Symbols
Loading unloaded module list
.........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800807f70d0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffc81a2f0e660=000000000000003b
0: kd> !analyze -v
***

*
Bugcheck Analysis *
*

***

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: ffff8a49eb218884, Address of the instruction which caused the BugCheck
Arg3: fffffc81a2f0ef60, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2186

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 4438

Key : Analysis.Init.CPU.mSec
Value: 390

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

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

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1

FILE_IN_CAB: 123121-9562-01.dmp

BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: ffff8a49eb218884

BUGCHECK_P3: fffffc81a2f0ef60

BUGCHECK_P4: 0

CONTEXT: fffffc81a2f0ef60 -- (.cxr 0xfffffc81a2f0ef60)
rax=0000000000000000 rbx=0000000000000000 rcx=ffff8a0645f77a20
rdx=ffff8a06410864c0 rsi=0000000000000040 rdi=0000000000000000
rip=ffff8a49eb218884 rsp=fffffc81a2f0f960 rbp=0000000000000000
r8=fffffc81a2f0f970 r9=0000000000000001 r10=0000000000000000
r11=fffffc81a2f0f8f0 r12=0000000000000040 r13=00007ffab3c64a40
r14=ffff8a0645f77a20 r15=ffff8a49eb4507c0
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050286
win32kbase!CInpPushLock::UnLockExclusive+0x4:
ffff8a49eb218884 4883610800 and qword ptr [rcx+8],0 ds:002b:ffff8a0645f77a28=ffff8c081b4f1080
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: NVIDIA Share.exe

STACK_TEXT:
fffffc81a2f0f960 ffff8a49eb5cbc4f : 000000a953b3f630 0000000000000000 0000000000000040 000000a953b3ee30 : win32kbase!CInpPushLock::UnLockExclusive+0x4
fffffc81a2f0f990 ffff8a49ebef48b6 : ffff8c081b4f1080 fffffc81a2f0fa80 000001f8d4eecf50 0000000000000020 : win32kfull!NtUserGetQueueStatus+0x13f
fffffc81a2f0f9d0 fffff80080808ab5 : 00007ffa5f9dd690 ffff8c08183d9860 fffffc81a2f0fa80 fffffc81a2f0fa80 : win32k!NtUserGetQueueStatus+0x16
fffffc81a2f0fa00 00007ffab24f9684 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25
000000a953b3f5f8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffa`b24f9684

SYMBOL_NAME: win32kbase!CInpPushLock::UnLockExclusive+4

MODULE_NAME: win32kbase

IMAGE_NAME: win32kbase.sys

IMAGE_VERSION: 10.0.19041.1173

STACK_COMMAND: .cxr 0xfffffc81a2f0ef60 ; kb

BUCKET_ID_FUNC_OFFSET: 4

FAILURE_BUCKET_ID: 0x3B_c0000005_win32kbase!CInpPushLock::UnLockExclusive

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {53cc9aae-24c8-f5e6-3e8a-2f62b8f6e2b8}

Followup: MachineOwner

steelseeker · Dec 31, 2021

uninstalled voice meter now going to play for abit see if i get another blue screen

steelseeker · Dec 31, 2021

okay so, voicemeter was disabled, still blue screened new error tho?

steelseeker · Dec 31, 2021

***

*
Bugcheck Analysis *
*

***

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff800190fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout

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: TickPeriods *

*

*
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3265

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 15630

Key : Analysis.Init.CPU.mSec
Value: 265

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

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

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1

FILE_IN_CAB: 123121-9312-01.dmp

BUGCHECK_CODE: 133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff800190fb320

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME: ffff8105bae3f550 -- (.trap 0xffff8105bae3f550)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000001fd332cf rbx=0000000000000000 rcx=ffff8105bae3f768
rdx=ffff8105bd962628 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80018680c67 rsp=ffff8105bae3f6e0 rbp=00000000ffffffff
r8=ffff8105bd962440 r9=ffff8105bd962450 r10=fffff80018729a30
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!KeYieldProcessorEx+0x17:
fffff800

18680c67 4883c420        add     rsp,20h
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
ffff8500

f4c79e18 fffff8001881f3fa : 0000000000000133 0000000000000000 0000000000000501 00000000

00000500 : nt!KeBugCheckEx
ffff8500

f4c79e20 fffff80018616953 : 00000680f4fb581d ffff8500f4cc0180 0000000000000000 ffff8500

f4cc0180 : nt!KeAccumulateTicks+0x20624a
ffff8500

f4c79e80 fffff8001861643a : ffff99039fcd00e0 ffff8105bae3f5d0 0000000077394600 00000000

1ffffda0 : nt!KeClockInterruptNotify+0x453
ffff8500

f4c79f30 fffff800186de135 : ffff99039fcd00e0 fffff80018752527 0000000000000000 00000000

00000000 : nt!HalpTimerClockIpiRoutine+0x1a
ffff8500

f4c79f60 fffff800187f8b7a : ffff8105bae3f5d0 ffff99039fcd00e0 0000066fbe9e45e9 00000000

00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffff8500

f4c79fb0 fffff800187f90e7 : 00000305bb756f68 ffff6634659c406f 0000000080000000 fffff800

187f90f4 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff8105

bae3f550 fffff80018680c67 : ffffffffffffffd2 fffff80018729b60 0000000000000010 00000000

00000286 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff8105

bae3f6e0 fffff80018729b79 : 0000000000010001 0000000000000000 0000000000000000 00000000

00000000 : nt!KeYieldProcessorEx+0x17
ffff8105

bae3f710 fffff8001869a32e : ffff8500f4cc3240 000000001fd332cf 0000000000000004 ffff8500

f4cc0180 : nt!ExpGetPoolTagInfoTarget+0x149
ffff8105

bae3f760 fffff80018699614 : 0000000000000000 0000000000000000 0000000000140001 00000000

00000000 : nt!KiExecuteAllDpcs+0x30e
ffff8105

bae3f8d0 fffff800187fac3e : ffffffff00000000 ffff8500f4cc0180 ffff8500f4ccb1c0 ffff9903

ae785080 : nt!KiRetireDpcList+0x1f4
ffff8105

bae3fb60 0000000000000000 : ffff8105bae40000 ffff8105bae39000 0000000000000000 00000000`00000000 : nt!KiIdleLoop+0x9e

SYMBOL_NAME: nt!KeAccumulateTicks+20624a

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.1415

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 20624a

FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {88dc98ce-f842-4daa-98d0-858621db6b0f}

Followup: MachineOwner

gardenman · Dec 31, 2021

Please enclose large log files in the Spoiler tag. You can do this in the editor by clicking on "..." and choosing Spoiler.

I have edited some of your previous posts to use the spoiler tag. . You can also click on Edit on the previous posts to see how I did it. Thanks.

Colif · Jan 1, 2022

i faded away a few hours ago, only had 4 hours sleep in the last 25 hours. I will sleep eventually. Just don't expect much.

Can you give us the minidump reports instead of the conversions?

Open Windows File Explore
Navigate to C:\Windows\Minidump
Copy the mini-dump files out onto your Desktop
Do not use Winzip, use the built in facility in Windows
Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
Then post a link here to the zip file, so we can take a look for you . . .

Gardenman has a program that he wrote that converts results for me, it will show drivers running and that might offer me some clues.

One of your last crashes mentioned Nvidia again but as victim, until I see dump results I would be guessing at cause.

steelseeker · Jan 1, 2022

Colif said:
i faded away a few hours ago, only had 4 hours sleep in the last 25 hours. I will sleep eventually. Just don't expect much.

Can you give us the minidump reports instead of the conversions?

Open Windows File Explore

Navigate to C:\Windows\Minidump

Copy the mini-dump files out onto your Desktop

Do not use Winzip, use the built in facility in Windows

Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder

Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)

Then post a link here to the zip file, so we can take a look for you . . .

Gardenman has a program that he wrote that converts results for me, it will show drivers running and that might offer me some clues.

One of your last crashes mentioned Nvidia again but as victim, until I see dump results I would be guessing at cause.

https://www.dropbox.com/s/cezwjbuleg9g7zv/dump files.zip?dl=0 ty

gardenman · Jan 1, 2022

I ran the dump files through the debugger and got the following information: https://jsfiddle.net/k9jnhw04/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:	123121-9562-01.dmp (Dec 31 2021 - 18:49:03)
Bugcheck:	SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:	memory_corruption (Process: NVIDIA Share.exe)
Uptime:	0 Day(s), 0 Hour(s), 23 Min(s), and 56 Sec(s)

File information:	123121-9312-01.dmp (Dec 31 2021 - 19:34:32)
Bugcheck:	DPC_WATCHDOG_VIOLATION (133)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 31 Min(s), and 59 Sec(s)

File information:	123121-10953-01.dmp (Dec 31 2021 - 16:54:17)
Bugcheck:	ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (FC)
Probably caused by:	memory_corruption (Process: voicemeeter8x64.exe)
Uptime:	3 Day(s), 9 Hour(s), 04 Min(s), and 06 Sec(s)

Possible Motherboard page: https://www.asus.com/us/Motherboards-Components/Motherboards/PRIME/PRIME-Z390-A/
There is a BIOS update available for your system. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

steelseeker · Jan 1, 2022

yea thats my MB, so i should update my mother bored bios? also am going to play today with out voicemetter on and hid- complaint headset disabled in device manger, because i went threw event viwer and had some errors with it and looked at some reditposts and other posts saying to disable it helped some people, some people with my headset "hyper cloud 2" had this issue.

steelseeker · Jan 1, 2022

this is my latest dumpfile, played for 3 hours with no issues then bluescreened. with my hid complaint headset disabled . no voice meter or spottily on, little stumped on what to do now and dono what is causeing this issue or if its hardware failers most parts are less then 2 years old besdies my 2 spare hard drives

https://www.dropbox.com/s/4l8udhapbgjvfj1/010122-9468-01.zip?dl=0
im really greatfull for all the help

steelseeker · Jan 1, 2022

am just really hoping its not my gpu i dont have another to test/money to afford new one with these crazy prices, okay so i read some other forums idk if this could help or not maybe try turning off xmp in bois? i did use it befor i swtiched ram and i did a ram test with my old ram befor i replaced it and it had 50 errors on memtest the boot one, was the reason i replaced old ram with new. some one said that fixed there issue i couldnt care if i have less speed on ram as long i can play games more then 4hours XD. let me know what you guys think

okay so edit
i tryed driver verifier and did all driver besides microsoft had some issues rebooting but when i fix thoes and got to bios the driver that failed was razer. here is the dump.
not 100% that was my issue but tryed it and going to play with out it for abit see if it fixed it.

so TLDR Removed razer drivers turned off xmp in bios. ty for help sorry for repeat posting? just trying to work threw my fixs /temps / get help XD thanks
file https://www.dropbox.com/s/btk9q8loztn6919/010222-9078-01.zip?dl=0

Colif · Jan 3, 2022

i was going to ask how old your Razer stuff was as

Jul 26 2008

Razer Synapse Service.sys

Razer Synapse driver

seems old to me. I was going to suggest an update as even the newest Razer drivers you had are from 2020
this could be a problem too

Nov 02 2017

cfosspeed6.sys

cFosSpeed driver (cFos Software)

its used for speeding up internet.

that is based on the last dumps Gardenman converted, I don't have results for your latest ones.

Question Need Help With BSOD! please <:L

Distinguished

Distinguished

Distinguished

Distinguished

Distinguished

Distinguished

Distinguished

Win 11 Master

Distinguished

Win 11 Master

Distinguished

Win 11 Master

Distinguished

Distinguished

Distinguished

Distinguished

Distinguished

Splendid

Win 11 Master

Distinguished

Splendid

Distinguished

Distinguished

Distinguished

Win 11 Master

Share this page