Windows 10: BSOD's with codes "IRQL_NOT_LESS_OR_EQUAL", "CRITICAL_PROCESS_DIED" and...

Hello,


I am using this PC since December 2019, when I bought it. As far as I can remember, it was giving me some trouble regarding BSODs from the beginning. The BSODs I usually receive are: "IRQL_NOT_LESS_OR_EQUAL", "CRITICAL_PROCESS_DIED" and "PAGE_FAULT_IN_NONPAGED_AREA". I have used WhoCrashed and Windbg to read the minidump files and they differ saying which one is the driver that is causing all this. WhoCrashed normally says it is ntoskrnl.sys or ntdll.sys. However, Windbg says it is vchost.exe and csrss.exe. At this point I don't know what to believe in.


After all this time, I have been in contact with the customer attention service of the company I bought this PC and the brand manufacturers of the components. I have tried to give a try to almost any solution I could find online, but nothing seems to work out just fine. One of the few options remaining is changing the component that is causing the problem, if there is any hardware issue, and I don't want to get to that point.


But this is not the only problem I have. Some programs just crash with no codes and no messages, they just crash and close instantly. This normally happens when I play a game which doesn't require a lot of resources like League of Legends or Rocket League. Anyway it sometimes makes crash some other programs or browser windows, saying "STATUS_ACCESS_VIOLATION".


My specs are:

Gigabyte X570 Gaming X

AMD Ryzen 5 3600X 3.8GHz up to 4.1GHz

Gigabyte GeForce GTX 1070 Windforce OC 8GB DDR5

AData 2x8GB 3200MHz

Crucial CT1000P1SSD8 1TB SSD M.2



Since I'm not able to upload the dump files into de OneDrive I don't know why I will show right below the output:


-----------------------------------------------------------------------------------------------------------------


[COLOR=rgba30, 30, 30, 1]Microsoft R Windows Debugger Version 10.0.21306.1007 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Users\santi\Desktop\Minidump\032821-5250-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: srv*Executable search path is: Windows 10 Kernel Version 19041 MP 12 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalEdition build lab: 19041.1.amd64fre.vb_release.191206-1406Machine Name:Kernel base = 0xfffff805`6ca00000 PsLoadedModuleList = 0xfffff805`6d62a490Debug session time: Sun Mar 28 11:52:14.555 2021 UTC + 2:00System Uptime: 0 days 0:00:04.179Loading Kernel Symbols.......................................................................................................................................Loading User SymbolsLoading unloaded module list......For analysis of this file, run [/COLOR][COLOR=rgba0, 0, 255, 1]!analyze -v[/COLOR][COLOR=rgba30, 30, 30, 1]nt!KeBugCheckEx:fffff805`6cdf5c50 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8486`b6f6e0c0=000000000000001e2: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************KMODE_EXCEPTION_NOT_HANDLED 1eThis is a very common bugcheck. Usually the exception address pinpointsthe driver/function that caused the problem. Always note this addressas well as the link date of the driver/image that contains this address.Arguments:Arg1: ffffffffc0000005, The exception code that was not handledArg2: fffff8056d0261aa, The address that the exception occurred atArg3: 0000000000000000, Parameter 0 of the exceptionArg4: 0000000001000008, Parameter 1 of the exceptionDebugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 3765 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 5121 Key : Analysis.Init.CPU.mSec Value: 343 Key : Analysis.Init.Elapsed.mSec Value: 8116 Key : Analysis.Memory.CommitPeak.Mb Value: 71 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.1BUGCHECK_CODE: 1eBUGCHECK_P1: ffffffffc0000005BUGCHECK_P2: fffff8056d0261aaBUGCHECK_P3: 0BUGCHECK_P4: 1000008READ_ADDRESS: fffff8056d6fb390: Unable to get MiVisibleStateUnable to get NonPagedPoolStartUnable to get NonPagedPoolEndUnable to get PagedPoolStartUnable to get PagedPoolEndunable to get nt!MmSpecialPagesInUse 0000000001000008 EXCEPTION_PARAMETER2: 0000000001000008BLACKBOXBSD: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxbsd[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXNTFS: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxntfs[/COLOR][COLOR=rgba30, 30, 30, 1]CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: csrss.exeTRAP_FRAME: ffff800000000000 -- [/COLOR][COLOR=rgba0, 0, 255, 1].trap 0xffff800000000000[/COLOR][COLOR=rgba30, 30, 30, 1]Unable to read trap frame at ffff8000`00000000STACK_TEXT: ffff8486`b6f6e0b8 fffff805`6ce9158f : 00000000`0000001e ffffffff`c0000005 fffff805`6d0261aa 00000000`00000000 : nt!KeBugCheckExffff8486`b6f6e0c0 fffff805`6ce07cac : 00000000`00001000 ffff8486`b6f6e960 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x166b2fffff8486`b6f6e780 fffff805`6ce03e43 : fffff805`00000000 fffff805`00000000 00000000`00000000 00000000`624e4d43 : nt!KiExceptionDispatch+0x12cffff8486`b6f6e960 fffff805`6d0261aa : 00000000`00000000 ffffab88`00000001 ffff8486`00000000 00000000`00000000 : nt!KiPageFault+0x443ffff8486`b6f6eaf0 fffff805`6cc5ee34 : 00000000`6b8d0912 ffffab88`802a2d60 00000000`00000000 00000000`00000000 : nt!CmpUnlockKcb+0xaffff8486`b6f6eb20 fffff805`6d0242e1 : ffffab88`802a11d0 00000000`00080000 00000000`00000002 00000000`00000000 : nt!CmpDrainDelayDerefContext+0xb4ffff8486`b6f6eb60 fffff805`6d022b6d : ffffab88`95972d78 00000000`00000000 ffff8486`b6f6edf9 00000000`00000000 : nt!CmpDereferenceKeyControlBlock+0x341ffff8486`b6f6ebe0 fffff805`6cffb270 : ffffda04`c86fe140 ffffab88`802772b0 00000000`00000000 00000000`00000000 : nt!CmpDeleteKeyObject+0x12dffff8486`b6f6ec70 fffff805`6cc61277 : 00000000`00000000 00000000`00000000 ffff8486`b6f6edf9 ffffab88`802772e0 : nt!ObpRemoveObjectRoutine+0x80ffff8486`b6f6ecd0 fffff805`6d028cde : ffffda04`c86fe140 00000000`00000001 00000000`00000001 ffffda04`c86fe140 : nt!ObfDereferenceObjectWithTag+0xc7ffff8486`b6f6ed10 fffff805`6d02c95c : 00000000`0000056c fffff805`6cdf9ab0 00000000`00000010 00000000`00040086 : nt!ObCloseHandleTableEntry+0x29effff8486`b6f6ee50 fffff805`6ce075b8 : 00000000`00000000 00000000`000e000c ffff8486`b6f6ef40 00000001`00000000 : nt!NtClose+0xecffff8486`b6f6eec0 fffff805`6cdf9ab0 : fffff805`6d0aff41 00000000`00000000 ffff8486`b6f6f160 ffff8486`b6f6f300 : nt!KiSystemServiceCopyEnd+0x28ffff8486`b6f6f058 fffff805`6d0aff41 : 00000000`00000000 ffff8486`b6f6f160 ffff8486`b6f6f300 00000000`00000000 : nt!KiServiceLinkageffff8486`b6f6f060 fffff805`6d0afcdf : 00000000`00000103 00000000`00000000 00000000`00000000 ffff8486`b6f6f304 : nt!_CmGetDeviceRegPropWorker+0x1e1ffff8486`b6f6f1b0 fffff805`6d0aee6c : 00000000`00000000 00000000`c0000034 ffffda04`00000000 fffff805`6cc5e40a : nt!_CmGetDeviceRegProp+0xffffff8486`b6f6f2c0 fffff805`6d0aecbb : 00000000`00000d5c 00000000`00000000 00000000`00001001 ffff8486`b6f6f5f0 : nt!_CmGetDeviceSoftwareKey+0x74ffff8486`b6f6f3d0 fffff805`6d017fb0 : 00000000`0000003e 00000000`00000012 ffffda04`52504e50 fffff805`6ce075b8 : nt!_CmGetDeviceSoftwareKeyPath+0x5bffff8486`b6f6f4d0 fffff805`6d0183d0 : ffffda04`cacea0f0 ffff8486`b6f6f5a0 00000000`000000f0 00000000`00000000 : nt!_CmGetDeviceRegKeyPath+0xccffff8486`b6f6f520 fffff805`6d0179a3 : 00000000`00000000 ffffda04`cacea0f0 fffff805`00000000 00000000`00000000 : nt!_CmOpenDeviceRegKeyWorker+0xccffff8486`b6f6f5e0 fffff805`6d0d24a8 : 00000000`00000000 00000000`00000012 ffffda04`cad1b360 00000000`00000002 : nt!_CmOpenDeviceRegKey+0xefffff8486`b6f6f640 fffff805`80f7019f : 00000000`00020019 ffff8486`b6f6f6f1 00000000`00000000 ffff8486`b6f6f9e0 : nt!IoOpenDeviceRegistryKey+0xc8ffff8486`b6f6f690 00000000`00020019 : ffff8486`b6f6f6f1 00000000`00000000 ffff8486`b6f6f9e0 00000000`00000000 : nvlddmkm+0xcc019fffff8486`b6f6f698 ffff8486`b6f6f6f1 : 00000000`00000000 ffff8486`b6f6f9e0 00000000`00000000 ffff8486`b6f6f6c0 : 0x20019ffff8486`b6f6f6a0 00000000`00000000 : ffff8486`b6f6f9e0 00000000`00000000 ffff8486`b6f6f6c0 00000000`00000000 : 0xffff8486`b6f6f6f1SYMBOL_NAME: nt!CmpUnlockKcb+aMODULE_NAME: [/COLOR][COLOR=rgba0, 0, 255, 1]nt[/COLOR][COLOR=rgba30, 30, 30, 1]IMAGE_NAME: ntkrnlmp.exeIMAGE_VERSION: 10.0.19041.867STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: aFAILURE_BUCKET_ID: 0x1E_c0000005_R_nt!CmpUnlockKcbOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {d9512d5e-2f71-cc98-9011-5a9465f822c7}Followup: MachineOwner---------NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2103.1004.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\atlmfc.natvis'NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2103.1004.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\ObjectiveC.natvis'NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2103.1004.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\concurrency.natvis'NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2103.1004.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\cpp_rest.natvis'NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2103.1004.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Kernel.natvis'NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2103.1004.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\stl.natvis'NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2103.1004.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Data.Json.natvis'NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2103.1004.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Geolocation.natvis'NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2103.1004.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Sensors.natvis'NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2103.1004.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Media.natvis'NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2103.1004.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\windows.natvis'NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2103.1004.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\winrt.natvis'Microsoft R Windows Debugger Version 10.0.21306.1007 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Users\santi\Desktop\Minidump\MEMORY.DMP]Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.************* Path validation summary **************Response Time ms LocationDeferred srv*Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 19041 MP 12 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalEdition build lab: 19041.1.amd64fre.vb_release.191206-1406Machine Name:Kernel base = 0xfffff806`2cc00000 PsLoadedModuleList = 0xfffff806`2d82a490Debug session time: Sun Mar 28 15:07:07.436 2021 UTC + 2:00System Uptime: 0 days 3:14:31.059Loading Kernel Symbols................................................................................................................................................................................Loading User SymbolsPEB is paged out Peb.Ldr = 0000006d`8862a018. Type ".hh dbgerr001" for detailsLoading unloaded module list......For analysis of this file, run [/COLOR][COLOR=rgba0, 0, 255, 1]!analyze -v[/COLOR][COLOR=rgba30, 30, 30, 1]nt!KeBugCheckEx:fffff806`2cff5c50 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffd909`2dc5a8b0=000000000000000a4: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************IRQL_NOT_LESS_OR_EQUAL aAn attempt was made to access a pageable or completely invalid address at aninterrupt request level IRQL that is too high. This is usuallycaused by drivers using improper addresses.If a kernel debugger is available get the stack backtrace.Arguments:Arg1: 0000000001000002, memory referencedArg2: 0000000000000002, IRQLArg3: 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 statusArg4: fffff8062ce452e4, address which referenced memoryDebugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2515 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 2534 Key : Analysis.Init.CPU.mSec Value: 656 Key : Analysis.Init.Elapsed.mSec Value: 4781 Key : Analysis.Memory.CommitPeak.Mb Value: 73 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.1BUGCHECK_CODE: aBUGCHECK_P1: 1000002BUGCHECK_P2: 2BUGCHECK_P3: 0BUGCHECK_P4: fffff8062ce452e4READ_ADDRESS: 0000000001000002 BLACKBOXBSD: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxbsd[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXNTFS: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxntfs[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXWINLOGON: 1PROCESS_NAME: RocketLeague.exeDPC_STACK_BASE: FFFFD9092DC5AFB0TRAP_FRAME: ffffd9092dc5a9f0 -- [/COLOR][COLOR=rgba0, 0, 255, 1].trap 0xffffd9092dc5a9f0[/COLOR][COLOR=rgba30, 30, 30, 1]NOTE: The trap frame does not contain all registers.[/COLOR][COLOR=rgba0, 0, 255, 1]Some register values may be zeroed or incorrect.[/COLOR][COLOR=rgba30, 30, 30, 1]rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000005rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000rip=fffff8062ce452e4 rsp=ffffd9092dc5ab80 rbp=ffffdc8fbfd6e250 r8=0000000000000102 r9=0000000000000000 r10=fffff8062aba7ac0r11=0000001b2c7e5a11 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei pl nz na pe ncnt!KiTimerWaitTest+0x1f4:fffff806`2ce452e4 0fb74602 movzx eax,word ptr [rsi+2] ds:00000000`00000002=????Resetting default scopeSTACK_TEXT: ffffd909`2dc5a8a8 fffff806`2d007b69 : 00000000`0000000a 00000000`01000002 00000000`00000002 00000000`00000000 : nt!KeBugCheckExffffd909`2dc5a8b0 fffff806`2d003e69 : 00000000`00000002 ffffc801`a3240180 00000000`00000000 fffff806`2ce4b0b6 : nt!KiBugCheckDispatch+0x69ffffd909`2dc5a9f0 fffff806`2ce452e4 : ffffdc8f`bfd6e188 00000000`00000000 ffffdc8f`bfd6e250 00000000`00000000 : nt!KiPageFault+0x469ffffd909`2dc5ab80 fffff806`2ce44e7c : ffffdc8f`bfd6e180 00000000`00000000 ffffd909`2dc5ae68 ffffdc8f`c2ca51c0 : nt!KiTimerWaitTest+0x1f4ffffd909`2dc5ac30 fffff806`2ce072e9 : ffffc801`a30e3180 0000d824`00000000 00000000`00000000 00000000`0006cb37 : nt!KiProcessExpiredTimerList+0xdcffffd909`2dc5ad20 fffff806`2cffcc95 : c024b48b`4426048d ffffc801`a30e3180 ffffdc8f`b84c6ac0 0000021d`7f75c730 : nt!KiRetireDpcList+0x9d9ffffd909`2dc5afb0 fffff806`2cffca80 : fffff806`2cff1d40 fffff806`2ceec5ca 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5ffffd909`3251eac0 fffff806`2cffc335 : 0000021d`7f75c730 fffff806`2cff7ce1 00000000`0000002f ffffdc8f`00000000 : nt!KiDispatchInterruptContinueffffd909`3251eaf0 fffff806`2cff7ce1 : 00000000`0000002f ffffdc8f`00000000 00000000`00000000 ffffdc8f`00000000 : nt!KiDpcInterruptBypass+0x25ffffd909`3251eb00 00007ff6`e59769df : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0xb10000006d`88cff4b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff6`e59769dfSYMBOL_NAME: nt!KiTimerWaitTest+1f4MODULE_NAME: [/COLOR][COLOR=rgba0, 0, 255, 1]nt[/COLOR][COLOR=rgba30, 30, 30, 1]IMAGE_NAME: ntkrnlmp.exeSTACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 1f4FAILURE_BUCKET_ID: AV_nt!KiTimerWaitTestOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {8c029a8d-9f29-4bde-2664-6010a6365158}Followup: MachineOwner---------[/COLOR]



[COLOR=rgba30, 30, 30, 1]Microsoft R Windows Debugger Version 10.0.21306.1007 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\Minidump\032621-6890-01.dmp]Mini Kernel Dump File: Only registers and stack trace are available************* Path validation summary **************Response Time ms LocationDeferred srv*Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 19041 MP 12 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalEdition build lab: 19041.1.amd64fre.vb_release.191206-1406Machine Name:Kernel base = 0xfffff803`42000000 PsLoadedModuleList = 0xfffff803`42c2a3b0Debug session time: Fri Mar 26 11:11:57.123 2021 UTC + 2:00System Uptime: 1 days 12:45:57.747Loading Kernel Symbols..........................................................................................................................................................................Loading User SymbolsLoading unloaded module list...................For analysis of this file, run [/COLOR][COLOR=rgba0, 0, 255, 1]!analyze -v[/COLOR][COLOR=rgba30, 30, 30, 1]nt!KeBugCheckEx:fffff803`423f5210 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff586`838a7940=00000000000000ef3: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************CRITICAL_PROCESS_DIED ef A critical system process diedArguments:Arg1: ffffc68c010c9080, Process object or thread objectArg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.Arg3: 0000000000000000Arg4: 0000000000000000Debugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 3859 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 5025 Key : Analysis.Init.CPU.mSec Value: 233 Key : Analysis.Init.Elapsed.mSec Value: 4527 Key : Analysis.Memory.CommitPeak.Mb Value: 74 Key : CriticalProcessDied.ExceptionCode Value: 25d2080 Key : CriticalProcessDied.Process Value: svchost.exe 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.1BUGCHECK_CODE: efBUGCHECK_P1: ffffc68c010c9080BUGCHECK_P2: 0BUGCHECK_P3: 0BUGCHECK_P4: 0PROCESS_NAME: svchost.exeCRITICAL_PROCESS: svchost.exeERROR_CODE: NTSTATUS 0x25d2080 - <Unable to get error code text>BLACKBOXBSD: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxbsd[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXNTFS: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxntfs[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXPNP: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxpnp[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1STACK_TEXT: fffff586`838a7938 fffff803`42906fb2 : 00000000`000000ef ffffc68c`010c9080 00000000`00000000 00000000`00000000 : nt!KeBugCheckExfffff586`838a7940 fffff803`427d7e33 : 00000000`00000000 fffff803`42260ec5 00000000`00000002 fffff803`42260def : nt!PspCatchCriticalBreak+0x10efffff586`838a79e0 fffff803`4264a9b0 : ffffc68c`00000000 00000000`00000000 ffffc68c`010c9080 ffffc68c`010c94b8 : nt!PspTerminateAllThreads+0x1ee427fffff586`838a7a50 fffff803`4264a7ac : ffffc68c`010c9080 00000000`00000000 0000007a`79b7fc4c fffff803`4270470a : nt!PspTerminateProcess+0xe0fffff586`838a7a90 fffff803`42406bb8 : ffffc68c`010c9080 ffffc68c`025d2080 fffff586`838a7b80 ffffc68c`010c9080 : nt!NtTerminateProcess+0x9cfffff586`838a7b00 00007ffb`a95ac324 : 00007ffb`a9622693 00007ffb`a9651364 0000007a`79b7fc10 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x280000007a`79b7ada8 00007ffb`a9622693 : 00007ffb`a9651364 0000007a`79b7fc10 00000000`00000000 00007ffb`a9510000 : 0x00007ffb`a95ac3240000007a`79b7adb0 00007ffb`a9651364 : 0000007a`79b7fc10 00000000`00000000 00007ffb`a9510000 00000000`00000004 : 0x00007ffb`a96226930000007a`79b7adb8 0000007a`79b7fc10 : 00000000`00000000 00007ffb`a9510000 00000000`00000004 00007ffb`a95b331d : 0x00007ffb`a96513640000007a`79b7adc0 00000000`00000000 : 00007ffb`a9510000 00000000`00000004 00007ffb`a95b331d 00007ffb`a9651364 : 0x0000007a`79b7fc10SYMBOL_NAME: nt!PspCatchCriticalBreak+10eMODULE_NAME: [/COLOR][COLOR=rgba0, 0, 255, 1]nt[/COLOR][COLOR=rgba30, 30, 30, 1]IMAGE_NAME: ntkrnlmp.exeIMAGE_VERSION: 10.0.19041.631STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 10eFAILURE_BUCKET_ID: 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_25d2080_nt!PspCatchCriticalBreakOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {de1d74e5-11b2-d13b-0fd0-e2e4eddb3f80}Followup: MachineOwner--------[/COLOR]

:)

 

Critical_Process_Died BSOD

Hi,

In order to resolve your concern, we suggest that you to follow these steps:

• If you've installed any new apps or devices, uninstall or unplug them and restart your PC.
• Make sure your PC has the latest updates:

• Go to the search box.
• Type Windows Update then Enter.
• Select Check for updates.
• In the Settings menu, select Check for updates button.
• When it's finished, restart your PC.

You may also check this
link for more troubleshooting steps regarding critical_process_died error message.

Let us know how it goes.

 

IRQL_Not_Less_Or_Equal

sigh
If your computer auto restarts on BSOD find the setting in windows to make it stop.
Second step is to look for the error code of the BSOD.
Perhaps easier would be to use an online application such as bluescreen viewer.
Once you know which driver is causing the problem you can look further into fixing it.

 

BSOD Error: CRITICAL_PROCESS_DIED

My laptop experienced a BSOD with an analysis by "Who Crashed" as follows-

On Sat 11/10/2018 2:08:03 PM your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\MEMORY.DMP

This was probably caused by the following module: ntkrpamp.exe (nt!PsSetLegoNotifyRoutine+0x46C)

Bugcheck code: 0xEF (0xFFFFFFFFA8C97440, 0x0, 0x0, 0x0)

Error: CRITICAL_PROCESS_DIED

Bug check description: This indicates that a critical system process died.

There is a possibility this problem was caused by a virus or other malware.

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntkrpamp.exe .

Google query: ntkrpamp.exe CRITICAL_PROCESS_DIED

Following is a link to my "one drive" BSOD folder with memory.dmp and other files for evaluation:

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

Please advise resolution for the said BSOD. Thanx!