Windows 10: Multiple BSOD need help!

Just started about a month ago keep getting multiple bsod errors here are the logs from Windbg

I've tried Virus Scan, Full Hard Drive windows install refresh and memtest86 with 8 passes 0 errors


Can anyone help me diagnose these blue screens I keep getting thanks!




Microsoft R Windows Debugger Version 10.0.19528.1000 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Users\Kalel\Desktop\012120-7828-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 18362 MP 8 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS Personal18362.1.amd64fre.19h1_release.190318-1202Machine Name:Kernel base = 0xfffff804`4a200000 PsLoadedModuleList = 0xfffff804`4a648150Debug session time: Tue Jan 21 19:35:13.357 2020 UTC - 7:00System Uptime: 2 days 9:36:44.291Loading Kernel Symbols......................................................................................................................................................................................Loading User SymbolsLoading unloaded module list................................For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff804`4a3c14e0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff804`4da67700=000000000000000a0: 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: 0000000000000324, memory referencedArg2: 0000000000000002, IRQLArg3: 0000000000000001, 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: fffff8044a26bd8c, address which referenced memoryDebugging Details:------------------*** WARNING: Unable to verify checksum for win32k.sysKEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 11 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-K9GOCAR Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 15 Key : Analysis.Memory.CommitPeak.Mb Value: 68 Key : Analysis.System Value: CreateObjectADDITIONAL_XML: 1BUGCHECK_CODE: aBUGCHECK_P1: 324BUGCHECK_P2: 2BUGCHECK_P3: 1BUGCHECK_P4: fffff8044a26bd8cWRITE_ADDRESS: fffff8044a7733b8: Unable to get MiVisibleStateUnable to get NonPagedPoolStartUnable to get NonPagedPoolEndUnable to get PagedPoolStartUnable to get PagedPoolEndfffff8044a62a3c8: Unable to get Flags value from nt!KdVersionBlockfffff8044a62a3c8: Unable to get Flags value from nt!KdVersionBlockunable to get nt!MmSpecialPagesInUse 0000000000000324 CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemTRAP_FRAME: fffff8044da67840 -- .trap 0xfffff8044da67840NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000000000 rbx=0000000000000000 rcx=00000000150fb08erdx=ffffb50805683600 rsi=0000000000000000 rdi=0000000000000000rip=fffff8044a26bd8c rsp=fffff8044da679d0 rbp=0000000000000008 r8=fffff8044da67c58 r9=0000000000000000 r10=00000000ffffffffr11=0000000000000001 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei pl zr na po ncnt!KiTimerWaitTest+0x12c:fffff804`4a26bd8c e40f in al,0FhResetting default scopeMISALIGNED_IP: nt!KiTimerWaitTest+12cfffff804`4a26bd8c e40f in al,0FhSTACK_TEXT: fffff804`4da676f8 fffff804`4a3d32e9 : 00000000`0000000a 00000000`00000324 00000000`00000002 00000000`00000001 : nt!KeBugCheckExfffff804`4da67700 fffff804`4a3cf62b : 00000000`00000003 00000000`00000000 ffffb507`fd980a40 fffff804`46287f08 : nt!KiBugCheckDispatch+0x69fffff804`4da67840 fffff804`4a26bd8c : 00000000`00000000 000001e2`ebe27fcc 00000000`00000000 00000000`00010001 : nt!KiPageFault+0x46bfffff804`4da679d0 fffff804`4a26b9f2 : ffffb508`05683600 000001e2`e6974452 00000000`00000002 ffffb507`fdc98010 : nt!KiTimerWaitTest+0x12cfffff804`4da67a80 fffff804`4a26a7e9 : 00000000`00000014 00000000`00989680 00000000`0078b9a5 00000000`000000bd : nt!KiProcessExpiredTimerList+0xd2fffff804`4da67b70 fffff804`4a3c5024 : 00000000`00000000 fffff804`46282180 fffff804`4a791400 ffffb508`029634c0 : nt!KiRetireDpcList+0x4e9fffff804`4da67da0 00000000`00000000 : fffff804`4da68000 fffff804`4da62000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x84SYMBOL_NAME: nt!KiTimerWaitTest+12cIMAGE_NAME: hardwareIMAGE_VERSION: 10.0.18362.592STACK_COMMAND: .thread ; .cxr ; kbMODULE_NAME: hardwareFAILURE_BUCKET_ID: IP_MISALIGNEDOS_VERSION: 10.0.18362.1BUILDLAB_STR: 19h1_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {201b0e5d-db2a-63d2-77be-8ce8ff234750}Followup: MachineOwner---------


Second error


Microsoft R Windows Debugger Version 10.0.19528.1000 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Users\Kalel\Desktop\011920-8125-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 18362 MP 8 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS Personal18362.1.amd64fre.19h1_release.190318-1202Machine Name:Kernel base = 0xfffff802`69400000 PsLoadedModuleList = 0xfffff802`69848150Debug session time: Sun Jan 19 09:57:31.880 2020 UTC - 7:00System Uptime: 3 days 1:36:42.571Loading Kernel Symbols.........................................................................................................................................................................................Loading User SymbolsLoading unloaded module list.........................For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff802`695c14e0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffd981`52bacb60=00000000000001241: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************WHEA_UNCORRECTABLE_ERROR 124A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffff8f869e7eb028, Address of the WHEA_ERROR_RECORD structure.Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.Arg4: 0000000000070150, Low order 32-bits of the MCi_STATUS value.Debugging Details:------------------fffff8026982a3c8: Unable to get Flags value from nt!KdVersionBlockfffff8026982a3c8: Unable to get Flags value from nt!KdVersionBlockfffff8026982a3c8: Unable to get Flags value from nt!KdVersionBlockKEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 4 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-K9GOCAR Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 4 Key : Analysis.Memory.CommitPeak.Mb Value: 70 Key : Analysis.System Value: CreateObject Key : WHEA.MCiStatus.Code Value: 0xb200000000070150 Key : WHEA.MCiStatus.McaError Value: 0x0150 Key : WHEA.MCiStatus.ModelError Value: 0x0007 Key : WHEA.MCiStatus.Reserved Value: 0x00000000ADDITIONAL_XML: 1BUGCHECK_CODE: 124BUGCHECK_P1: 0BUGCHECK_P2: ffff8f869e7eb028BUGCHECK_P3: b2000000BUGCHECK_P4: 70150CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemSTACK_TEXT: ffffd981`52bacb58 fffff802`693a4fe8 : 00000000`00000124 00000000`00000000 ffff8f86`9e7eb028 00000000`b2000000 : nt!KeBugCheckExffffd981`52bacb60 fffff802`6af81920 : ffff8f86`9a2eaa10 00000000`00000000 ffff8f86`9e7eb028 00000000`00000000 : hal!HalBugCheckSystem+0xd8ffffd981`52bacba0 fffff802`69740952 : ffff8f86`9a2eaa10 ffffd981`52bacc29 00000000`00000000 ffff8f86`9e7eb028 : PSHED!PshedBugCheckSystem+0x10ffffd981`52bacbd0 fffff802`693a6946 : ffffd981`52baccf0 00000000`00000001 ffff8f86`9a2eaa60 ffff8f86`9a2eaa10 : nt!WheaReportHwError+0x382ffffd981`52bacc90 fffff802`693a6dda : 00000000`00000010 ffff8f86`9a2eaa60 ffffd981`52bace48 ffffd981`52bad090 : hal!HalpMcaReportError+0x72ffffd981`52bacdf0 fffff802`693a6cb4 : ffff8f86`99ea1600 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xf2ffffd981`52bace40 fffff802`693a6f20 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe0ffffd981`52bace80 fffff802`693a5fc8 : 00000000`00000000 ffffd981`52bad110 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4ffffd981`52baceb0 fffff802`693a71a7 : ffff8f86`99ea1600 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5cffffd981`52bacee0 fffff802`696a4a20 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37ffffd981`52bacf10 fffff802`695d04ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x10ffffd981`52bacf40 fffff802`695d0171 : ffffd981`00000000 fffff802`695d00ae fffff802`650e2180 00000000`00000000 : nt!KxMcheckAbort+0x7affffd981`52bad080 fffff802`695c9ff7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x271ffff878a`ae229918 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!guard_dispatch_icall+0x7MODULE_NAME: GenuineIntelIMAGE_NAME: GenuineIntel.sysSTACK_COMMAND: .thread ; .cxr ; kbFAILURE_BUCKET_ID: 0x124_0_GenuineIntel_BANK0_MSCOD0007_MCACOD0150_PCC_UC_IMAGE_GenuineIntel.sysOS_VERSION: 10.0.18362.1BUILDLAB_STR: 19h1_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {e0a97988-5b74-5f7f-f215-d313e998f8a6}Followup: MachineOwner

:)

 

Multiple BSOD - Please Help

I've recently ran into multiple BSOD and need assistance in solving them. I've done "chkdsk /f /r", "sfc /scannow" and "mssched.exe" and it says that my system has no errors.

Here is a link to my dump files. Minidump.zip

List of Errors:

PAGE_FAULT_IN_NONPAGED_AREA

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

SYSTEM_SERVICE_EXCEPTION

BAD_POOL_HEADER

BAD_POOL_CALLER

IRQL_NOT_LESS_OR_EQUAL

KERNAL_SECURITY_CHECK_FAILURE

 

Multiple BSOD

Bug Check 0x1A: MEMORY_MANAGEMENT

Bug Check 0x1A MEMORY_MANAGEMENT - Windows drivers

MEMORY_MANAGEMENT BSODs, accompanied by occasional app crashes/GPUTDR.

MEMORY_MANAGEMENT BSODs, accompanied by occasional app crashes/GPUTDR.

The relevant Parameter appears to be 0x41284 which means, A PTE or the working set list is corrupted, which in itself means nothing to most of us poor Windows users. I still wonder if this is not just bad RAM?

Is it possible to remove one stick of RAM for testing purposes and then test all sticks one at a time (that's is you have multiple sticks of RAM, otherwise it is a daft suggestion on my part).

 

help to remote connect

not sure how to use both programs u 2 suggested, i need more helpful steps thanks