What driver is causing my computer to crash?

Question

I feel as if I have tried every conceivable option to stop my pc from constantly crashing while I am working. After numerous driver update attempts, memtest, system repairs, and sfc scans I am still dealing with daily BSODs. I'm not sure if it's a driver, a hardware issue, software, or something else. I finally resorted to downloading the Windows Debugging tool so I could read my minidump files.

Sadly, I have become stumped once again, as I cannot make sense of the dump file after analyzing it. If someone who understands this could please point out what is causing the crashes, I would be extremely grateful.

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: fffff8014bc0de70, Address of the instruction which caused the BugCheck
Arg3: fffff80151082920, 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: 2468

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 6464

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

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

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

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8014bc0de70

BUGCHECK_P3: fffff80151082920

BUGCHECK_P4: 0

CONTEXT: fffff80151082920 -- (.cxr 0xfffff80151082920)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=ffffbe8800000009 rsi=fffff80148b529a8 rdi=ffffbe8890fc7260
rip=fffff8014bc0de70 rsp=ffff8184968b4750 rbp=00000021699cd8fb
r8=0000000000000000 r9=fffff8014ba00000 r10=fffff80148b51ac0
r11=0000000000000000 r12=0000000000000067 r13=0000000000000067
r14=fffff80148b529a0 r15=fffff80148b529a8
iopl=0 nv up ei ng nz na pe cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050283
nt!KiInsertTimerTable+0xd0:
fffff8014bc0de70 4c8b42f8 mov r8,qword ptr [rdx-8] ds:002b:ffffbe8800000001=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Discord.exe

STACK_TEXT:
ffff8184968b4750 fffff8014bc119b4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiInsertTimerTable+0xd0
ffff8184968b47d0 fffff8014bd76da2 : 0000000000000000 0000000000000000 0000000000000000 0000000000000001 : nt!ExpSetTimerObject+0x424
ffff8184968b4980 fffff8014bd76c4a : ffff8184968b4a48 0000000000000000 0000000000500f33 ffff818400501802 : nt!ExpSetTimer+0xe2
ffff8184968b49f0 fffff8014be090f1 : 0000000000000660 ffffbe888da05080 000000000f7fe9b8 0000000000000000 : nt!NtSetTimer+0xda
ffff8184968b4a90 00007ffb8610da54 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceExitPico+0x2bc
000000000f7fe998 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffb`8610da54

SYMBOL_NAME: nt!KiInsertTimerTable+d0

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.1165

STACK_COMMAND: .cxr 0xfffff80151082920 ; kb

BUCKET_ID_FUNC_OFFSET: d0

FAILURE_BUCKET_ID: 0x3B_c0000005_nt!KiInsertTimerTable

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {1da1bf28-017d-bdc5-930b-2530179e6d8c}

And a Second Crash Several Hours Later

Bugcheck Analysis

KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL (192)
A lock tracked by AutoBoost was acquired while executing at DISPATCH_LEVEL or
above.
Arguments:
Arg1: ffff868aa41e8080, The address of the thread.
Arg2: fffff80441c481c0, The lock address.
Arg3: 0000000000000000, The IRQL at which the lock was acquired.
Arg4: 0000000000000000, Reserved.

Debugging Details:

---

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 3905

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 5386

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

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

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

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 192

BUGCHECK_P1: ffff868aa41e8080

BUGCHECK_P2: fffff80441c481c0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: TWCU.exe

LOCK_ADDRESS: fffff80441c44a20 -- (!locks fffff80441c44a20)
Cannot get _ERESOURCE type

Resource @ nt!PiEngineLock (0xfffff80441c44a20) Available
1 total locks

PNP_TRIAGE_DATA:
Lock address : 0xfffff80441c44a20
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0

STACK_TEXT:
ffff800f96b270f8 fffff80441207dc2 : 0000000000000192 ffff868aa41e8080 fffff80441c481c0 0000000000000000 : nt!KeBugCheckEx
ffff800f96b27100 fffff804415f15c3 : 0000000000000040 ffff800f96b27b00 0000000000000000 0000000000000008 : nt!ExAcquirePushLockSharedEx+0x142
ffff800f96b27150 fffff80441672849 : 0000000000000005 ffff800f96b27340 0000000000000000 0000000000000001 : nt!CmpCallCallBacksEx+0xd3
ffff800f96b27260 fffff804414090f1 : 0000000000000000 00000000000001d0 ffff9a806ad57000 fffff8044128d5d9 : nt!NtEnumerateKey+0x299
ffff800f96b27460 fffff804413fb030 : fffff80441754325 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceExitPico+0x2bc
ffff800f96b27668 fffff80441754325 : 0000000000000000 0000000000000000 0000000000000000 ffff9a80494e2de0 : nt!KiServiceLinkage
ffff800f96b27670 fffff804418ad95d : 000000000000004e ffff800f96b277d0 0000000003bdc804 ffff800f00000000 : nt!_RegRtlEnumKey+0x89
ffff800f96b27760 fffff804417dae60 : ffff800f96b27968 0000000000000014 0000000000000000 0000000000000000 : nt!PiCMEnumerateSubKeys+0x151
ffff800f96b277f0 fffff804415d8163 : ffff800f96b27940 0000000000000062 000000000047080b fffff804415f5bee : nt!PiCMHandleIoctl+0x202ce0
ffff800f96b27830 fffff804416ee1ea : 000000000047080b fffff804416ee180 ffff868a94f76600 fffff8044120afca : nt!PiCMFastIoDeviceDispatch+0x53
ffff800f96b27880 fffff80441674b22 : 000000000047080b 0000000000000001 0000000000501802 ffff868aa684d2d0 : nt!PiDaFastIoDispatch+0x6a
ffff800f96b278e0 fffff80441674786 : 000000000000024c 0000000000000000 0000000000000001 0000000000000000 : nt!IopXxxControlFile+0x382
ffff800f96b27a20 fffff804414090f1 : 0000000000000000 0000000000000000 0000000000000000 000000000000024c : nt!NtDeviceIoControlFile+0x56
ffff800f96b27a90 0000000077b01cfc : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceExitPico+0x2bc
000000000382ecf8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x77b01cfc

SYMBOL_NAME: nt!ExAcquirePushLockSharedEx+142

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.1165

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 142

FAILURE_BUCKET_ID: 0x192_nt!ExAcquirePushLockSharedEx

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {292e4563-5d10-0ceb-86fc-152da5e999ce}

And a Third from the Day Before

Bugcheck Analysis

KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL (192)
A lock tracked by AutoBoost was acquired while executing at DISPATCH_LEVEL or
above.
Arguments:
Arg1: ffffdf83172d2080, The address of the thread.
Arg2: ffffdf8316481530, The lock address.
Arg3: 0000000000000000, The IRQL at which the lock was acquired.
Arg4: 0000000000000000, Reserved.

Debugging Details:

---

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 2249

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 2242

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

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

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

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 192

BUGCHECK_P1: ffffdf83172d2080

BUGCHECK_P2: ffffdf8316481530

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: voicemeeterpro

STACK_TEXT:
ffff89026224c0c8 fffff80305e13e7f : 0000000000000192 ffffdf83172d2080 ffffdf8316481530 0000000000000000 : nt!KeBugCheckEx
ffff89026224c0d0 fffff80305d2eeb5 : ffff89026224c470 ffff89026224c4a0 ffffdf83172d2080 ffff957900000000 : nt!KeAbPreAcquire+0x20cb1f
ffff89026224c120 ffff8bc171fcd529 : ffff89026224c470 0000000000000001 0000000000000000 ffff89026224cb70 : nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+0x35
ffff89026224c150 ffff8bc171fc4de3 : ffff89026224c470 ffff8bc171fcd4e0 ffff0beebd8172d5 00001f8000290000 : cdd!CddBitmap::BitBltCallback+0x49
ffff89026224c1a0 ffff8bc171fc5583 : fffff8034e800114 ffff8b83406f7880 ffff8b834292abf0 ffff8b834868d598 : cdd!ClipDstRects+0x53
ffff89026224c3a0 ffff8bc171fc44a6 : 0000000200000305 000000a700000000 00000000000000a8 000000a800000002 : cdd!BitBltBitmap+0x533
ffff89026224c7e0 ffff8bc171fd07ef : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : cdd!DrvBitBltInternal+0x1a6
ffff89026224caa0 ffff8bc171ca7d15 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : cdd!DrvCopyBits+0x4f
ffff89026224cb10 ffff8bc171ca50a4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : win32kfull!INVOKEOFFCOPYBITS+0x125
ffff89026224cbe0 ffff8bc171ca7be4 : ffff890000000001 0000000000000000 ffff8b834412f420 7fffffff00000000 : win32kfull!SpBitBlt+0x184
ffff89026224d100 ffff8bc171ec8ca5 : 0000000000000000 000000000801007e ffff8bc171f3c780 00000000070f1bd5 : win32kfull!SpCopyBits+0x44
ffff89026224d170 ffff8bc171ea27de : 0000000000000000 0000000000000003 0000000000000003 ffff89026224d3f0 : win32kfull!OffCopyBits+0xed
ffff89026224d230 ffff8bc171ea2baf : ffffdf83000002c3 ffff8b8340613fa0 0000000000000000 0000000000000000 : win32kfull!MulBitBlt+0x4ee
ffff89026224d4e0 ffff8bc171ca31f5 : 0000000000000000 ffff8b83408e0240 ffff8b83408e0240 ffff8b834864b2c0 : win32kfull!MulCopyBits+0x2bf
ffff89026224d690 ffff8bc171ca5d1b : 0000000077a04660 0000000000000000 000000000041a000 0000000000000f33 : win32kfull!NtGdiBitBltInternal+0xa65
ffff89026224d9b0 ffff8bc17199989b : 0000000000000008 fffff6d8257e7273 ffff89026224daa8 fffff80305e090cc : win32kfull!NtGdiBitBlt+0x5b
ffff89026224da20 fffff80305e090f1 : ffffdf83172d2080 fffff80305fa5060 0000000000000000 000000000085000f : win32k!NtGdiBitBlt+0x7f
ffff89026224da90 00007ffc950e0054 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceExitPico+0x2bc
000000000030ddf8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffc`950e0054

SYMBOL_NAME: cdd!CddBitmap::BitBltCallback+49

MODULE_NAME: cdd

IMAGE_NAME: cdd.dll

IMAGE_VERSION: 10.0.19041.1165

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 49

FAILURE_BUCKET_ID: 0x192_cdd!CddBitmap::BitBltCallback

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {63fb8d99-19e4-e4cd-6732-f0e23e32ce1d}

Answer 1

Hi AlecSchmiemeier-0333 ,

Please run V2 > post a share link into this thread

https://www.windowsq.com/resources/v2-log-collector.8/
https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post: Vote = a helpful post
.
.
.
.
.

Answer 2

Hello @Alec Schmiemeier

It seems that the crashes are not identical, so we might be talking about a system corruption or a BIOS configuration issue:

1. Check if you have recently updated the system BIOS or made any changes. I would suggest save the current BIOS profile and load Default settings.
2. Try repairing the windows image with DISM?
   Examples here: https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/repair-a-windows-image

Best regards,

Answer 3

Hello @Alec Schmiemeier

After the Minidump analyses , we can find the error is constantly changing indication no pattern through we can converge on the problem. Usually BSOD stand for Conflicts between your Hardware drivers and Windows. So please try the Following suggestion

1. Update the BIOS and all drivers of the PC.
2. Use the Process Monitor to check if any drivers in particular is causing these Issues.
3. Repair update the PC with latest ISO.
4. Clean install the PC .

Post back if any of the steps was helpful