Constant Bsods and Crashes on Windows 10 (5 years fine, only past month having issues)

I would suggest a memory test, if it gives errors it may be related to the motherboard in which case running the same test on different slots would be interesting to confirm.
 
OK, let's look elsewhere then. I'm going to ask you to enable Driver Verifier -the details on how to do this properly are at Driver Verifier Instructions - BSOD - Windows 11, 10, 8(.1), 7 and Vista.

Driver Verifier subjects selected drivers (typically all third-party drivers) to extra tests and checks every time they are called. These extra checks are designed to uncover drivers that are misbehaving. If any selected driver fails any of the Driver Verifier tests/checks then Driver Verifier will BSOD. The resulting minidump should contain enough information for us to identify the flaky driver. It's thus essential to keep all minidumps created whilst Driver Verifier is enabled.

Note: Because Driver Verifier is doing extra work each time a third-party driver is loaded you will notice some performance degradation with Driver Verifier enabled. This is a price you'll have to pay in order to locate any flaky drivers. And remember, Driver Verifier can only test drivers that are loaded, so you need to ensure that every third-party driver gets loaded by using all apps, features and devices.
 
I decided to reboot and download windows 11. So, right now I'm running in windows 11 home and am getting blue screens specifically when downloading games on steam. Should I still do the driver verifier?
 
Here's what I have done:

I did a custom reboot of windows 11, wiping my drive because the windows updates on my old windows 10 were not working and I believed that there was some type of windows corruption. While windows 11 was on my computer, I was consistently getting various blue screens. I tried looking all errors up, running scannow, running dism, and reinstalling fresh drivers for everything, but nothing worked.

So, I decided to reboot again and am now back to windows 10. I was able to download all drivers (motherboard and gpu) with no problem. I downloaded google chrome and then steam. While trying to download one of the games on steam I got my first blue screen with this now rebooted windows 10 which is "Unexpected Kernal Mode Trap".

What can I do solve this bsod?
 
I know that my ram isn't faulty since I conducted a check on the new sticks of ram and 31.9 gigs are showing up in task manager. I've also used the chkdsk /f and /r commands, but clearly that didn't really do anything.
 
This is the minidump from that:


************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true

EnableRedirectToV8JsProvider : false

-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.032 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.125 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 29

Microsoft (R) Windows Debugger Version 10.0.26100.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Eddie\Desktop\BSODump\072324-10765-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 (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff805`11e00000 PsLoadedModuleList = 0xfffff805`12a2a820
Debug session time: Tue Jul 23 00:51:12.865 2024 (UTC - 4:00)
System Uptime: 0 days 0:09:38.500
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.............
Loading User Symbols
PEB is paged out (Peb.Ldr = 0000001e`73683018). Type ".hh dbgerr001" for details
Loading unloaded module list
.......
For analysis of this file, run !analyze -v
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
BugCheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffffc5814cf0de70
Arg3: fffff18dc85d5f30
Arg4: fffff8051205ac29

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2656

Key : Analysis.Elapsed.mSec
Value: 4208

Key : Analysis.IO.Other.Mb
Value: 11

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 19

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x7f

Key : Failure.Bucket
Value: 0x7f_8_nt!KiDoubleFaultAbort

Key : Failure.Hash
Value: {d1f8395a-8c58-45da-6ebf-e8bb4aad2fc5}

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 7f

BUGCHECK_P1: 8

BUGCHECK_P2: ffffc5814cf0de70

BUGCHECK_P3: fffff18dc85d5f30

BUGCHECK_P4: fffff8051205ac29

FILE_IN_CAB: 072324-10765-01.dmp

TRAP_FRAME: ffff800000000000 -- (.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: steamwebhelper.exe

STACK_TEXT:
ffffc581`4cf0dd28 fffff805`122125a9 : 00000000`0000007f 00000000`00000008 ffffc581`4cf0de70 fffff18d`c85d5f30 : nt!KeBugCheckEx
ffffc581`4cf0dd30 fffff805`1220ca52 : 0004e184`0fffff7a 000200b9`2c468b00 48646873`70b84100 4804e2c1`4840148d : nt!KiBugCheckDispatch+0x69
ffffc581`4cf0de70 fffff805`1205ac29 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0x2d2
fffff18d`c85d5f30 fffff805`1201be30 : 00000000`00000000 00000000`00000000 fffff18d`c85d6250 00000000`00000000 : nt!MiSystemFault+0x29
fffff18d`c85d6030 fffff805`1220de6d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x400
fffff18d`c85d61d0 fffff805`122083c6 : fffff18d`c85d6520 fffff18d`c85d6590 fffff805`1215f799 fffff18d`c85d65d0 : nt!KiPageFault+0x36d
fffff18d`c85d6368 fffff805`1215f799 : fffff18d`c85d65d0 00000000`00000000 fffff18d`c85d6d98 00000000`000004d0 : nt!_chkstk+0x36
fffff18d`c85d6380 fffff805`1215d846 : fffff18d`c85d6d98 fffff18d`c85d6ad0 fffff18d`c85d6d98 fffff805`11eb0bf0 : nt!RtlDispatchException+0x119
fffff18d`c85d65a0 fffff805`122126ec : 00000000`00001000 fffff18d`c85d6e40 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff18d`c85d6c60 fffff805`1220df52 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x12c
fffff18d`c85d6e40 fffff805`121619a8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x452
fffff18d`c85d6fd0 fffff805`12161414 : fffff805`11e00000 fffff805`00000000 ffffffff`ffffff80 00007fff`fffeffff : nt!RtlpUnwindPrologue+0x248
fffff18d`c85d7030 fffff805`1215fb2f : fffff805`11ee3ef8 fffff18d`00000000 fffff18d`c85d76c0 fffff805`11ee3ef8 : nt!RtlpxVirtualUnwind+0x104
fffff18d`c85d70b0 fffff805`1215f84e : fffff18d`c85d7670 00000000`00000000 fffff18d`c85dba90 fffff805`12211d10 : nt!RtlVirtualUnwind+0x5f
fffff18d`c85d7130 fffff805`1215d846 : fffff18d`c85d8048 fffff18d`c85d7d80 fffff18d`c85d8048 fffff805`11eb0bf0 : nt!RtlDispatchException+0x1ce
fffff18d`c85d7850 fffff805`122126ec : 00000000`00001000 fffff18d`c85d80f0 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff18d`c85d7f10 fffff805`1220df52 : 00000000`00000006 00000000`00000000 00000000`00000000 01dadcbb`2c05d67e : nt!KiExceptionDispatch+0x12c
fffff18d`c85d80f0 fffff805`121619a8 : 00000000`0000000f 00000000`00000000 00000000`0002625a 01dadcbb`360548fc : nt!KiPageFault+0x452
fffff18d`c85d8280 fffff805`12161414 : fffff805`11e00000 fffff805`00000000 ffffffff`ffffff80 00007fff`fffeffff : nt!RtlpUnwindPrologue+0x248
fffff18d`c85d82e0 fffff805`1215fb2f : fffff805`11ee3ef8 fffff18d`00000000 fffff18d`c85d8970 fffff805`11ee3ef8 : nt!RtlpxVirtualUnwind+0x104
fffff18d`c85d8360 fffff805`1215f84e : fffff18d`c85d8920 00000000`00000000 fffff18d`c85dba90 fffff805`12211d10 : nt!RtlVirtualUnwind+0x5f
fffff18d`c85d83e0 fffff805`1215d846 : fffff18d`c85d92f8 fffff18d`c85d9030 fffff18d`c85d92f8 fffff805`11eb0bf0 : nt!RtlDispatchException+0x1ce
fffff18d`c85d8b00 fffff805`122126ec : 00000000`00001000 fffff18d`c85d93a0 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff18d`c85d91c0 fffff805`1220df52 : 00000000`00000000 000002bf`435bd3b8 00000000`00000022 000002c7`695a4d0a : nt!KiExceptionDispatch+0x12c
fffff18d`c85d93a0 fffff805`121619a8 : 00000000`00000001 000002bf`435bd540 000002bf`435bd560 00000000`00000001 : nt!KiPageFault+0x452
fffff18d`c85d9530 fffff805`12161414 : fffff805`11e00000 fffff805`00000000 ffffffff`ffffff80 00007fff`fffeffff : nt!RtlpUnwindPrologue+0x248
fffff18d`c85d9590 fffff805`1215fb2f : fffff805`11ee3ef8 fffff18d`00000000 fffff18d`c85d9c20 fffff805`11ee3ef8 : nt!RtlpxVirtualUnwind+0x104
fffff18d`c85d9610 fffff805`1215f84e : fffff18d`c85d9bd0 00000000`00000000 fffff18d`c85dba90 fffff805`12211d10 : nt!RtlVirtualUnwind+0x5f
fffff18d`c85d9690 fffff805`1215d846 : fffff18d`c85da5a8 fffff18d`c85da2e0 fffff18d`c85da5a8 fffff805`11eb0bf0 : nt!RtlDispatchException+0x1ce
fffff18d`c85d9db0 fffff805`122126ec : 00000000`00001000 fffff18d`c85da650 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff18d`c85da470 fffff805`1220df52 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x12c
fffff18d`c85da650 fffff805`121619a8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x452
fffff18d`c85da7e0 fffff805`12161414 : fffff805`11e00000 00000000`00000000 ffffffff`ffffff80 00007fff`fffeffff : nt!RtlpUnwindPrologue+0x248
fffff18d`c85da840 fffff805`1215fb2f : fffff805`11ee3ef8 00000000`00000000 ffff559c`ddfec1ee fffff805`11ee3ef8 : nt!RtlpxVirtualUnwind+0x104
fffff18d`c85da8c0 fffff805`1215f84e : fffff18d`c85dae80 00000000`00000000 fffff18d`c85db090 fffff805`12211d10 : nt!RtlVirtualUnwind+0x5f
fffff18d`c85da940 fffff805`1215d846 : fffff18d`c85db858 fffff18d`c85db590 fffff18d`c85db858 fffff18d`c85dbaa8 : nt!RtlDispatchException+0x1ce
fffff18d`c85db060 fffff805`122126ec : 00000000`00001000 fffff18d`c85db900 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff18d`c85db720 fffff805`1220df52 : 00002c64`002699e0 00002c64`002699e0 00002c64`092b6140 00000000`000000b0 : nt!KiExceptionDispatch+0x12c
fffff18d`c85db900 fffff805`12211d10 : 00000000`00000000 00000000`00000000 00000000`00000000 00002c64`002699e0 : nt!KiPageFault+0x452
fffff18d`c85dba90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit


SYMBOL_NAME: nt!KiDoubleFaultAbort+2d2

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.4648

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 2d2

FAILURE_BUCKET_ID: 0x7f_8_nt!KiDoubleFaultAbort

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {d1f8395a-8c58-45da-6ebf-e8bb4aad2fc5}

Followup: MachineOwner
---------
 
Let's back up a step. You said iin post #24...
I decided to reboot and download windows 11. So, right now I'm running in windows 11 home...
Click to expand...
That raises some important questions....
  • Did you simply upgrade your existing Windows 10 to Windows 11?
  • Or did you boot Windows 11 installation media and clean install Windows 11, deleting existing UEFI partitions during the install?
  • Does your motherboard vendor have drivers specifically for Windows 11? Are these drivers installed?
  • Do you have drivers for all other devices that are specifically for Windows 11? Are these drivers installed?
TBH I'd rather you'd not done that because all it really does is complicate the problem. Everything has now changed on your system so we're effectively starting from scratch. Let me know how you installed Windows 11 and we'll work forward from there.
 
I used installation media and deleted partitions. Yes, my motherboard and all my other devices had drivers specifically for windows 11.

But after using windows 11, the secure boot and tmp were not really working and made the os unstable so I used installation media to go back to windows 10 and deleted partitions once again.

I’m sorry I thought this would have accelerated the process because it eliminates the possibility that it is due to corrupt windows.
 
Unfortunately, initiative like this often backfires and complicates the situation in my experience, usually to the point where an unbootable system is the result. The intention is always good, but not having a clue of the cause is the caveat since this sort of action is almost always taken when hardware is the cause so there's a huge risk involved. When the cause is likely hardware-related, you must be careful with what steps to take since it's quite easy to make a bigger mess at that point, here I'm speaking from recent personal experience as well.

Have you had any other crashes since the 0x7F?
 
I have not had any other crashes since the 0x7f, but I also gave up on downloading stuff. I thought it would be smart to just focus on this one before doing anything else. Do you know what I can do to solve the 0x7f?
 
Just got another bluescreen: irql_not_less_or_equal

Here's the log:
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true

EnableRedirectToV8JsProvider : false

-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.032 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.015 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 29

Microsoft (R) Windows Debugger Version 10.0.26100.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Eddie\Desktop\BSODump\072324-9453-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 (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff805`46c00000 PsLoadedModuleList = 0xfffff805`4782a820
Debug session time: Tue Jul 23 15:54:51.888 2024 (UTC - 4:00)
System Uptime: 0 days 13:41:11.522
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000069`cf843018). Type ".hh dbgerr001" for details
Loading unloaded module list
..................
For analysis of this file, run !analyze -v
1: kd> !analyze -v
*******************************************************************************
* *
* 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: 000000003cee6020, 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: fffff80546eccce0, address which referenced memory

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2733

Key : Analysis.Elapsed.mSec
Value: 2925

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 0

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0xa

Key : Failure.Bucket
Value: AV_nt!KiDeliverApc

Key : Failure.Hash
Value: {f94393b9-4308-5aa6-9044-71825dde3286}

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: a

BUGCHECK_P1: 3cee6020

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80546eccce0

FILE_IN_CAB: 072324-9453-01.dmp

READ_ADDRESS: fffff805478fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
000000003cee6020

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Risk of Rain 2.exe

TRAP_FRAME: fffff400a26516d0 -- (.trap 0xfffff400a26516d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=000000003cee6000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80546eccce0 rsp=fffff400a2651860 rbp=fffff400a26518b9
r8=0000000000000000 r9=0000000000000002 r10=0000fffff8054700
r11=ffffc100a46d7c40 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po cy
nt!KiDeliverApc+0x190:
fffff805`46eccce0 488b4f30 mov rcx,qword ptr [rdi+30h] ds:00000000`00000030=????????????????
Resetting default scope

STACK_TEXT:
fffff400`a2651588 fffff805`470125a9 : 00000000`0000000a 00000000`3cee6020 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff400`a2651590 fffff805`4700df78 : 00000000`00000000 fffff805`470063d6 fffff805`47925440 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff400`a26516d0 fffff805`46eccce0 : ffffc100`00000000 d20c525f`2c30528d 00000000`00000000 00000000`00000001 : nt!KiPageFault+0x478
fffff400`a2651860 fffff805`46eccb0b : 00000000`000003bc 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x190
fffff400`a2651920 fffff805`46e159ef : ffffd20c`525f2c30 fffff400`a2651a01 ffffd20c`50125080 fffff805`46e37803 : nt!KiCheckForKernelApcDelivery+0x2b
fffff400`a2651950 fffff805`4721cdf1 : 00000000`00000000 ffffd20c`501251c0 fffff400`a26519e0 00000000`00000000 : nt!KeLeaveCriticalRegionThread+0x2f
fffff400`a2651980 fffff805`4721cb71 : ffffd20c`4b640080 00000000`00100000 00000000`00000000 00000000`00000001 : nt!ObpReferenceObjectByHandleWithTag+0x231
fffff400`a2651a10 fffff805`4721c8b8 : 00000000`00000000 00000000`00000000 00000000`00000001 ffffd20c`4bccd200 : nt!ObReferenceObjectByHandleWithTag+0x31
fffff400`a2651a60 fffff805`4721c85a : ffffd20c`50125080 00000000`00000000 00000000`00000000 ffffd20c`4bccd260 : nt!ObWaitForSingleObject+0x48
fffff400`a2651ac0 fffff805`47011d08 : ffffd20c`50125080 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtWaitForSingleObject+0x6a
fffff400`a2651b00 00007ffe`6ab2d5e4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000069`d00ff7c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`6ab2d5e4


SYMBOL_NAME: nt!KiDeliverApc+190

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.4648

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 190

FAILURE_BUCKET_ID: AV_nt!KiDeliverApc

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f94393b9-4308-5aa6-9044-71825dde3286}

Followup: MachineOwner
 
I ran memtest86 and the Windows Memory Diagnostic Test and both didn't detect any problems. Should I do the driver verifier? Also could it have anything to do with BIOS version? (I'm at F40 rn)
 
When you get new BSODs please always rerun the Sysnative file collection app and upload the new output. The text of analyze -v isn't terribly useful to us, even uploading individual dumps means we're not seeing other important troubleshooting data.

I think it's wise to enable Driver Verifier. That you've had issues on two different Windows versions does rather suggest a hardware cause, but in my experience when most people do a reinstall they also install all their third-party stuff - and often reinstall the problem. If Driver verifier has not triggered any dumps after 48 hours then it's unlikely to be a rogue driver. it is important however, to use every device, every feature, even every app that you have installed, because driver verifier can only check drivers as they are loaded so you need to use the all the devices/features/apps to be sure that every driver gets loaded at some point.
 
My computer is a lot slower right now and getting a lot of blue screens, but none of them are the ones listed on the instructions page. So, does that mean this isn't a driver problem?
 
Can I stop the driver verifier now?

I feel like it's confirmed that it isn't that because I've done everything I normally do. Playing one of the games I play causes an blue screen usually 5-10 minutes in, but now I can't even enter that game and it blue screens with "irql_not_less_or_equal", not one of the indicators for the driver verifier. I also can't do any dumps because every single time I try running the Sysnative file collection app, I bluescreen again.
 
Yes, you can disable Driver Verifier. This doesn't seem to be a rogue driver (TBH I didn't think it was, but we had to check)


In looking through your logs I came across three of these errors....
Code: 
Log Name:      Application
Source:        Microsoft-Windows-Security-SPP
Date:          23/07/2024 09:57:07
Event ID:      8198
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-JVNQO2H
Description:
License Activation (slui.exe) failed with the following error code:
hr=0x800704CF
Command-line arguments:
RuleId=31e71c49-8da7-4a2f-ad92-45d98a1c79ba;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=8db63db6-4f8f-46d6-a448-66444faaaa72;NotificationInterval=1440;Trigger=UserLogon;SessionId=2
Note that they are dated last Sunday (23rd) so there is still a question regarding the validity of your Windows license. The 0x800704CF error code there indicates that no valid license was found. You never did enter the slmg /dlv command that I asked you to earlier, so please do that now and post the display that results.

  • From where did this copy of Windows come?
  • Was it pre-installed on the PC or did you buy it separately?
  • Did you buy a cheaper license from a third-party online?
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top