question

AlecSchmiemeier-0333 avatar image
0 Votes"
AlecSchmiemeier-0333 asked Docs-4663 commented

What driver is causing my computer to crash?

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:
fffff801`4bc0de70 4c8b42f8 mov r8,qword ptr [rdx-8] ds:002b:ffffbe88`00000001=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Discord.exe

STACK_TEXT:
ffff8184`968b4750 fffff801`4bc119b4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInsertTimerTable+0xd0
ffff8184`968b47d0 fffff801`4bd76da2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : nt!ExpSetTimerObject+0x424
ffff8184`968b4980 fffff801`4bd76c4a : ffff8184`968b4a48 00000000`00000000 00000000`00500f33 ffff8184`00501802 : nt!ExpSetTimer+0xe2
ffff8184`968b49f0 fffff801`4be090f1 : 00000000`00000660 ffffbe88`8da05080 00000000`0f7fe9b8 00000000`00000000 : nt!NtSetTimer+0xda
ffff8184`968b4a90 00007ffb`8610da54 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x2bc
00000000`0f7fe998 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 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:
ffff800f`96b270f8 fffff804`41207dc2 : 00000000`00000192 ffff868a`a41e8080 fffff804`41c481c0 00000000`00000000 : nt!KeBugCheckEx
ffff800f`96b27100 fffff804`415f15c3 : 00000000`00000040 ffff800f`96b27b00 00000000`00000000 00000000`00000008 : nt!ExAcquirePushLockSharedEx+0x142
ffff800f`96b27150 fffff804`41672849 : 00000000`00000005 ffff800f`96b27340 00000000`00000000 00000000`00000001 : nt!CmpCallCallBacksEx+0xd3
ffff800f`96b27260 fffff804`414090f1 : 00000000`00000000 00000000`000001d0 ffff9a80`6ad57000 fffff804`4128d5d9 : nt!NtEnumerateKey+0x299
ffff800f`96b27460 fffff804`413fb030 : fffff804`41754325 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x2bc
ffff800f`96b27668 fffff804`41754325 : 00000000`00000000 00000000`00000000 00000000`00000000 ffff9a80`494e2de0 : nt!KiServiceLinkage
ffff800f`96b27670 fffff804`418ad95d : 00000000`0000004e ffff800f`96b277d0 00000000`03bdc804 ffff800f`00000000 : nt!_RegRtlEnumKey+0x89
ffff800f`96b27760 fffff804`417dae60 : ffff800f`96b27968 00000000`00000014 00000000`00000000 00000000`00000000 : nt!PiCMEnumerateSubKeys+0x151
ffff800f`96b277f0 fffff804`415d8163 : ffff800f`96b27940 00000000`00000062 00000000`0047080b fffff804`415f5bee : nt!PiCMHandleIoctl+0x202ce0
ffff800f`96b27830 fffff804`416ee1ea : 00000000`0047080b fffff804`416ee180 ffff868a`94f76600 fffff804`4120afca : nt!PiCMFastIoDeviceDispatch+0x53
ffff800f`96b27880 fffff804`41674b22 : 00000000`0047080b 00000000`00000001 00000000`00501802 ffff868a`a684d2d0 : nt!PiDaFastIoDispatch+0x6a
ffff800f`96b278e0 fffff804`41674786 : 00000000`0000024c 00000000`00000000 00000000`00000001 00000000`00000000 : nt!IopXxxControlFile+0x382
ffff800f`96b27a20 fffff804`414090f1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`0000024c : nt!NtDeviceIoControlFile+0x56
ffff800f`96b27a90 00000000`77b01cfc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x2bc
00000000`0382ecf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 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:
ffff8902`6224c0c8 fffff803`05e13e7f : 00000000`00000192 ffffdf83`172d2080 ffffdf83`16481530 00000000`00000000 : nt!KeBugCheckEx
ffff8902`6224c0d0 fffff803`05d2eeb5 : ffff8902`6224c470 ffff8902`6224c4a0 ffffdf83`172d2080 ffff9579`00000000 : nt!KeAbPreAcquire+0x20cb1f
ffff8902`6224c120 ffff8bc1`71fcd529 : ffff8902`6224c470 00000000`00000001 00000000`00000000 ffff8902`6224cb70 : nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+0x35
ffff8902`6224c150 ffff8bc1`71fc4de3 : ffff8902`6224c470 ffff8bc1`71fcd4e0 ffff0bee`bd8172d5 00001f80`00290000 : cdd!CddBitmap::BitBltCallback+0x49
ffff8902`6224c1a0 ffff8bc1`71fc5583 : fffff803`4e800114 ffff8b83`406f7880 ffff8b83`4292abf0 ffff8b83`4868d598 : cdd!ClipDstRects+0x53
ffff8902`6224c3a0 ffff8bc1`71fc44a6 : 00000002`00000305 000000a7`00000000 00000000`000000a8 000000a8`00000002 : cdd!BitBltBitmap+0x533
ffff8902`6224c7e0 ffff8bc1`71fd07ef : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : cdd!DrvBitBltInternal+0x1a6
ffff8902`6224caa0 ffff8bc1`71ca7d15 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : cdd!DrvCopyBits+0x4f
ffff8902`6224cb10 ffff8bc1`71ca50a4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32kfull!INVOKEOFFCOPYBITS+0x125
ffff8902`6224cbe0 ffff8bc1`71ca7be4 : ffff8900`00000001 00000000`00000000 ffff8b83`4412f420 7fffffff`00000000 : win32kfull!SpBitBlt+0x184
ffff8902`6224d100 ffff8bc1`71ec8ca5 : 00000000`00000000 00000000`0801007e ffff8bc1`71f3c780 00000000`070f1bd5 : win32kfull!SpCopyBits+0x44
ffff8902`6224d170 ffff8bc1`71ea27de : 00000000`00000000 00000000`00000003 00000000`00000003 ffff8902`6224d3f0 : win32kfull!OffCopyBits+0xed
ffff8902`6224d230 ffff8bc1`71ea2baf : ffffdf83`000002c3 ffff8b83`40613fa0 00000000`00000000 00000000`00000000 : win32kfull!MulBitBlt+0x4ee
ffff8902`6224d4e0 ffff8bc1`71ca31f5 : 00000000`00000000 ffff8b83`408e0240 ffff8b83`408e0240 ffff8b83`4864b2c0 : win32kfull!MulCopyBits+0x2bf
ffff8902`6224d690 ffff8bc1`71ca5d1b : 00000000`77a04660 00000000`00000000 00000000`0041a000 00000000`00000f33 : win32kfull!NtGdiBitBltInternal+0xa65
ffff8902`6224d9b0 ffff8bc1`7199989b : 00000000`00000008 fffff6d8`257e7273 ffff8902`6224daa8 fffff803`05e090cc : win32kfull!NtGdiBitBlt+0x5b
ffff8902`6224da20 fffff803`05e090f1 : ffffdf83`172d2080 fffff803`05fa5060 00000000`00000000 00000000`0085000f : win32k!NtGdiBitBlt+0x7f
ffff8902`6224da90 00007ffc`950e0054 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x2bc
00000000`0030ddf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 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}

windows-10-generalwindows-10-hardware-performance
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Docs-4663 avatar image
0 Votes"
Docs-4663 answered

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
.
.
.
.
.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

LimitlessTechnology-2700 avatar image
0 Votes"
LimitlessTechnology-2700 answered Docs-4663 commented

Hello @AlecSchmiemeier-0333

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://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/repair-a-windows-image

Best regards,

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

While looking into my BIOS for any changes or updates, I discovered it may actually be outdated. I'm going to update it to the most recent version and see if that fixes the issue.

Thank you for your advice so far.

0 Votes 0 ·
Docs-4663 avatar image Docs-4663 AlecSchmiemeier-0333 ·

When available post a share link with V2 log collector results.

0 Votes 0 ·
LimitlessTechnology-2700 avatar image
0 Votes"
LimitlessTechnology-2700 answered

Hello @AlecSchmiemeier-0333

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

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.