Windows 10: Multiple BSOD. Can't find the source of the problem.

Hi.


Not long ago I started having multiple random BSOD:


IRQL NOT LESS OR EQUAL

KERNEL SECURITY CHECK FAILURE

SYSTEM SERVICE EXCEPTION

SYSTEM THREAD EXCEPTION NOT HANDLED

PAGE FAULT IN NONPAGED AREA

MEMORY MANAGEMENT

KMODE_EXCEPTION_NOT_HANDLED

TIMER OR DPC INVALID

DPC_WATCHDOG_VIOLATION




Sometimes while gaming, other times when the computer was idling, when powering on, when powering off...


After looking into the issue I got the advice of reinstalling windows and after doing it it got better but I still get some BSOD every now and then.


I checked my drives and one HDD had some bad/corrupt sectors. I Have a new one the BSOD still happen.

I've ran Memtest multiple times for all the ram sticks and ram slots and it didn't find errors.

System File Checker doesn't find any issues.

Windows memory diagnostic doesn't find errors.

GPU Drivers are updated.

I tried driver verifier and ocasionally it does finds problems with stuff like my wireless usb adapter of my headset software. I updated the drivers but verifier keeps catching them. I don't know how to determine if that is the source of the BSOD.


I have some random ideas but nothing solid.

Maybe it is the GPU?

Could it be that all the RAM slots became faulty for some reason?

The PSU is old 2012. Could that cause instability by itself?

Recently I moved my PC and currently Everything comes from the same plug via a plug strip. Maybe that's too much? I already had some BSOD before moving the PC, but each component had its own plug.


What else could it be?


Here is the latest minidump analysis by windbg preview:


Microsoft R Windows Debugger Version 10.0.20153.1000 AMD64

Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\Minidump\102420-6906-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 SingleUserTSEdition build lab: 19041.1.amd64fre.vb_release.191206-1406Machine Name:Kernel base = 0xfffff800`23200000 PsLoadedModuleList = 0xfffff800`23e2a310Debug session time: Sat Oct 24 13:29:57.994 2020 UTC + 2:00System Uptime: 0 days 4:28:08.714Loading Kernel Symbols.............................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list...............For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff800`235f45a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffdd8a`f80b5950=000000000000000a11: 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: 00000000000000b8, 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: fffff800235fb821, address which referenced memoryDebugging Details:------------------*** WARNING: Unable to verify checksum for win32k.sysKEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 3015 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-9EE4MNE Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 10130 Key : Analysis.Memory.CommitPeak.Mb Value: 84 Key : Analysis.System Value: CreateObject 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.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: aBUGCHECK_P1: b8BUGCHECK_P2: 2BUGCHECK_P3: 0BUGCHECK_P4: fffff800235fb821READ_ADDRESS: fffff80023efb390: Unable to get MiVisibleStateUnable to get NonPagedPoolStartUnable to get NonPagedPoolEndUnable to get PagedPoolStartUnable to get PagedPoolEndfffff80023e0f340: Unable to get Flags value from nt!KdVersionBlockfffff80023e0f340: Unable to get Flags value from nt!KdVersionBlockunable to get nt!MmSpecialPagesInUse 00000000000000b8 BLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemTRAP_FRAME: ffffdd8af80b5a90 -- .trap 0xffffdd8af80b5a90NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000000000 rbx=0000000000000000 rcx=00000000063200e6rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000rip=fffff800235fb821 rsp=ffffdd8af80b5c20 rbp=000f8067bcbbbdff r8=0000000000000000 r9=ffff81014e740180 r10=fffff80023f24a00r11=0000000000000000 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei ng nz na pe ncnt!SwapContext+0x221:fffff800`235fb821 4c3bb7b8000000 cmp r14,qword ptr [rdi+0B8h] ds:00000000`000000b8=????????????????Resetting default scopeSTACK_TEXT: ffffdd8a`f80b5948 fffff800`23606569 : 00000000`0000000a 00000000`000000b8 00000000`00000002 00000000`00000000 : nt!KeBugCheckExffffdd8a`f80b5950 fffff800`23602869 : fffff800`235f0690 fffff800`2347460a 00000000`00000001 fffff800`23200000 : nt!KiBugCheckDispatch+0x69ffffdd8a`f80b5a90 fffff800`235fb821 : 000f8067`bcbbbdff 00000000`00000001 ffff8101`00000000 fffff800`235f80ca : nt!KiPageFault+0x469ffffdd8a`f80b5c20 fffff800`235f81e6 : ffffffff`00000000 ffff8101`4e74b340 ffffa30f`e7104080 00000000`000002f4 : nt!SwapContext+0x221ffffdd8a`f80b5c60 00000000`00000000 : ffffdd8a`f80b6000 ffffdd8a`f80b0000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x176SYMBOL_NAME: nt!SwapContext+221MODULE_NAME: ntIMAGE_NAME: ntkrnlmp.exeIMAGE_VERSION: 10.0.19041.572STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 221FAILURE_BUCKET_ID: AV_nt!SwapContextOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {47b746a3-60bf-1f5a-5fa5-88903b6a3204}Followup: MachineOwner---------

Here are my PC components:

CPU: AMD Ryzen 5 3600 3.6GHz

RAM: Corsair Vengeance LPX DDR4 3200 PC4-25600 16GB 2x8GB CL16 I expanded with other 16 GB but currently I have only 2 8gb installed

Motherboard: MSI B450 Tomahawk

GPU: Sapphire Pulse Radeon RX 580 8GB GDDR5

SSD OS W10: Samsung 850 Evo SSD Series 120GB SATA3 5 years old

SSD 2 Programs: Crucial MX500 SSD 500GB SATA

HDD Data: Seagate Barracuda ST4000DM004 4000GB Serial ATA II

Other: 4 port USB PCIe slot. I have a Valve Index Headset, a HOTAS and a webcam but currently only the keyboard, mouse and a USB wireles adapter are plugged in.


No Overclocking.



Any pointers please?

:)

 

Weird BSOD problem


Hi Everyone,

I have a weird BSOD problem which I cannot solve for a while(it persists still after upgrade to Windows 10 from Windows 7)

The main strange thing about this is that I get BSOD only after cold boot.
So it acts like this:

1. start PC.
2. Get to Windows Logo Screen
3. BSOD
4. Restart
5. Get to menu where I can try to repair or Start NormallyIf I Choose Repair, it will fail to repair and will try to restoreIf I Choose Start Normally, it will start OK, no BSOD, can work normally, games, browse internet, everything is normal.6. Shutdown PC
7. Next time when I start is all over again i.e. Go to Step 1

I have this problem for a while, so what I tried:

1. Another Windows 7
2. Another HDD
3. Only HDD connected
4. Changed RAM
5. Tried with built in GPU
6. Upgraded to Windows 10

Result is the same as above every time.

Please suggest what could be the cause.
Logs collected with DM_Log_Collector, attached.


Thank you

PS. This thread is a continuation of this one: Frequent multiple errors BSOD. Solved - Windows 7 Help Forums the only thing changed is Windows 10 now. instead of Windows 7. If that helps somehow.

 

Multiple BSOD

Bug Check 0x1A: MEMORY_MANAGEMENT

https://msdn.microsoft.com/en-us/library/windows/hardware/ff557391(v=vs.85).aspx

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

 

[SOLVED] Multiple random BSODs, all pointing to the kernel


No BSODs yet but I haven't been playing World of Warcraft which I suspect to be a possible cause.

Was the driver verifier step necessary or just a suggestion?