Question Existential crisis with corrupt drivers and BSOD.

[Sinoreth]

I've been getting bsods for the last 3 days. They weren't that regular before but got much worse over time.
I'm thinking maybe my RAM is faulty and corrupted my drivers. Can someone more experienced take a look at the minidumps? I've tried using driver verifier. There should be at least 2 dumps from it, i've also tried just uninstalling the corrupt driver at first, but it seems there is a lot of them and there would be no point if my ram is actually faulty.
Dumps

 

[rgd1101]

full system spec? include make and model of the psu

 

[Sinoreth]

full system spec? include make and model of the psu

Sure.
Here's PCPartPicker: https://pcpartpicker.com/list/d2xkj2
I've upgraded CPU and GPU recently, if that's important.

 

[maikutech]

I looked at the dumps you provided, most of them point back at the vga card.
Just to be sure that it maybe the problem, uninstall the drivers for it, do not let windows 10 auto install generic drivers for it.
https://www.nvidia.com/content/Driv...international-dch-whql.exe&lang=us&type=TITAN

Version:	460.89 WHQL
Release Date:	2020.12.15
Operating System:	Windows 10 64-bit
Language:	English (US)
File Size:	628.11 MB

Source:

https://www.nvidia.com/Download/driverResults.aspx/167753/en-us
Please read what partpicker suggests as a warning, system looks cool but may not work with parts you picked up over time
https://pcpartpicker.com/list/d2xkj2#compatibility_notes
Make sure windows 10 is at the latest version and let windows 10 install the recommended updates as suggested.

 

[Sinoreth]

I looked at the dumps you provided, most of them point back at the vga card.
Just to be sure that it maybe the problem, uninstall the drivers for it, do not let windows 10 auto install generic drivers for it.
https://www.nvidia.com/content/Driv...international-dch-whql.exe&lang=us&type=TITAN

Version:	460.89 WHQL
Release Date:	2020.12.15
Operating System:	Windows 10 64-bit
Language:	English (US)
File Size:	628.11 MB

Source:

https://www.nvidia.com/Download/driverResults.aspx/167753/en-us
Please read what partpicker suggests as a warning, system looks cool but may not work with parts you picked up over time
https://pcpartpicker.com/list/d2xkj2#compatibility_notes
Make sure windows 10 is at the latest version and let windows 10 install the recommended updates as suggested.

Huh. Now i've noticed it too, some kind of VGA Boot Driver. But the thing is, i haven't used VGA monitor for over 4 years now, and PC have been reassembled several times, with fresh Windows install and all.
To be honest i have no idea what's this all about. Can you point me to how can i uninstall that driver? I don't see any mentions of it in the Device Manager.


And yes, all the compatibility notes should be fine, and the Windows have been updated recently.
EDIT. I'm also using GeForce Experience to update my GPU drivers. It seems there is an update, will see if it'll help.
EDIT 2. I've used DDU to uninstall all possible drivers and reinstalled them clean. Not sure if it actually helped, but the frequency of BSODs decreased.

 

[Sinoreth]

5 more dumps if anyone is willing to take a look.
Checked my RAM with memtest86, 0 errors.
Checked all system with Malwarebytes, got about 10, cleaned them all.
It seemed that most of the bsods happened when i'm using chrome for some reason. Tried reinstalling just in-case, no help.
Tried updating every single driver i could, got another IRQL_NOT_LESS_OR_EQUAL and DRIVER_IRQL_NOT_LESS_OR_EQUAL just now.
Bsod sometimes mentions afd.sys as cause, as well as ntoskrnl.exe of course, what's this about?

Getting desperate.

 

[johnbl]

5 more dumps if anyone is willing to take a look.
Checked my RAM with memtest86, 0 errors.
Checked all system with Malwarebytes, got about 10, cleaned them all.
It seemed that most of the bsods happened then i used chrome for some reason. Tried reinstalling just in-case, no help.
Tried updating every single driver i could, got another IRQL_NOT_LESS_OR_EQUAL and DRIVER_IRQL_NOT_LESS_OR_EQUAL just now.
Bsod sometimes mentions afd.sys as cause, as well as ntoskrnl.exe of course, what's this about?

Getting desperate.

provide uncompressed .dmp files please

 

[Sinoreth]

provide uncompressed .dmp files please

Since the dump generated was too big for me to host anywhere(15.4 gb), i've tried to run WinDbg myself and got this:

***
Bugcheck Analysis

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000980, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000980, address which referenced memory
****
I'm not familiar with reading dumps, can somebody explain what does that mean?

 

[Sinoreth]

Here's the rest of this dump:

Spoiler

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


"C:\WINDOWS\System32\KERNELBASE.dll" was not found in the image list.
Debugger will attempt to load "C:\WINDOWS\System32\KERNELBASE.dll" at given base 0000000000000000. Please provide the full image name, including the extension (i.e. kernel32.dll) for more reliable results.Base address and size overrides can be given as .reload <image.ext>=<base>,<size>. KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2436 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on THEHIDEOUT Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 46772 Key : Analysis.Memory.CommitPeak.Mb Value: 93 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.1 ADDITIONAL_XML: 1 OS_BUILD_LAYERS: 1 BUGCHECK_CODE: d1 BUGCHECK_P1: 980 BUGCHECK_P2: 2 BUGCHECK_P3: 8 BUGCHECK_P4: 980 READ_ADDRESS: 0000000000000980 PROCESS_NAME: steam.exe BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 TRAP_FRAME: ffffed0c0cfe9660 -- (.trap 0xffffed0c0cfe9660) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=fffff8046f4b8180 rdx=fffff80471000000 rsi=0000000000000000 rdi=0000000000000000 rip=0000000000000980 rsp=ffffed0c0cfe97f0 rbp=0000000000000000 r8=ffffed0c0cfe9820 r9=fffff8046f4b8180 r10=0000000000000fff r11=ffffed0c0cfe9730 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc 0000000000000980 ?? ???
Resetting default scope

FAILED_INSTRUCTION_ADDRESS:
+0
0000000000000980 ?? ??? STACK_TEXT: ffffed0c0cfe9518 fffff80471407769 : 000000000000000a 0000000000000980 0000000000000002 0000000000000008 : nt!KeBugCheckEx ffffed0c0cfe9520 fffff80471403a69 : fffff80477c84000 ffffcf0e19495040 0000000000000000 0000000000000090 : nt!KiBugCheckDispatch+0x69 ffffed0c0cfe9660 0000000000000980 : 0000000000000007 ffffed0c0cfe9828 ffffed0c0cfe9820 fffff8046f4b8180 : nt!KiPageFault+0x469 ffffed0c0cfe97f0 0000000000000007 : ffffed0c0cfe9828 ffffed0c0cfe9820 fffff8046f4b8180 fffff8046f4b8180 : 0x980 ffffed0c0cfe97f8 ffffed0c0cfe9828 : ffffed0c0cfe9820 fffff8046f4b8180 fffff8046f4b8180 fffff804714351fe : 0x7 ffffed0c0cfe9800 ffffed0c0cfe9820 : fffff8046f4b8180 fffff8046f4b8180 fffff804714351fe fffff80400000000 : 0xffffed0c0cfe9828
ffffed0c0cfe9808 fffff8046f4b8180 : fffff8046f4b8180 fffff804714351fe fffff80400000000 0000000000000000 : 0xffffed0c0cfe9820 ffffed0c0cfe9810 fffff8046f4b8180 : fffff804714351fe fffff80400000000 0000000000000000 ffff820f00000000 : 0xfffff8046f4b8180
ffffed0c0cfe9818 fffff804714351fe : fffff80400000000 0000000000000000 ffff820f00000000 0000000000000000 : 0xfffff8046f4b8180 ffffed0c0cfe9820 fffff80471264d7f : ffffcf0e00000000 000000000000000b ffffed0c0cfe99e0 ffffbc0100000000 : nt!KiSwapThread+0x1cfeae ffffed0c0cfe98d0 fffff80471264623 : ffffcf0e00000047 fffff80400000000 ffffbc017adc0101 ffffcf0e2dc0a1c0 : nt!KiCommitThreadWait+0x14f ffffed0c0cfe9970 fffff8047162c6a1 : ffffcf0e2b404be0 0000000000000006 0000000000000001 0000000000000000 : nt!KeWaitForSingleObject+0x233 ffffed0c0cfe9a60 fffff8047162c74a : ffffcf0e2dc0a080 0000000000000000 0000000000000000 0000000000b53000 : nt!ObWaitForSingleObject+0x91 ffffed0c0cfe9ac0 fffff804714071b8 : 00000000064476c8 ffffed0c0cfe9b80 ffffed0c0cfe9b18 ffffffffffd9da60 : nt!NtWaitForSingleObject+0x6a ffffed0c0cfe9b00 0000000077d11cfc : 0000000077d11b5d 0000002377d9164c 0000000000000023 000000000351b274 : nt!KiSystemServiceCopyEnd+0x28 000000000165ef38 0000000077d11b5d : 0000002377d9164c 0000000000000023 000000000351b274 000000000167fb84 : wow64cpu!CpupSyscallStub+0xc 000000000165ef40 0000000077d111b9 : 000000000167f8b8 00007ffb5a7239b4 0000000000000000 00007ffb5a723aaf : wow64cpu!Thunk0ArgReloadState+0x5 000000000165eff0 00007ffb5a7238c9 : 000000000bdf9e48 0000000000000000 0000000000000000 000000000165f430 : wow64cpu!BTCpuSimulate+0x9 000000000165f030 00007ffb5a7232bd : 0000000000000000 0000000000000001 0000000000000000 0000000000000000 : wow64!RunCpuSimulation+0xd 000000000165f060 00007ffb5ade4aef : 0000000000000000 0000000000000000 0000000000000001 0000000000000000 : wow64!Wow64LdrpInitialize+0x12d 000000000165f310 00007ffb5ade49d3 : 0000000000000000 00007ffb5ad70000 0000000000000000 0000000000b53000 : ntdll!_LdrpInitialize+0x103 000000000165f3b0 00007ffb5ade497e : 000000000165f430 0000000000000000 0000000000000000 0000000000000000 : ntdll!LdrpInitialize+0x3b 000000000165f3e0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 00000000`00000000 : ntdll!LdrInitializeThunk+0xe


SYMBOL_NAME: nt!KiPageFault+469

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 469

FAILURE_BUCKET_ID: AV_CODE_AV_NULL_IP_nt!KiPageFault

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {4ce35ff9-c5cf-d66d-0323-0f05e33f6692}

Followup: MachineOwner
---------

 

[Sinoreth]

Another bsod, another dump:

Spoiler

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: 0000000000004c60, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 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 status)
Arg4: fffff80344c6aa50, address which referenced memory

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


"C:\WINDOWS\System32\KERNELBASE.dll" was not found in the image list.
Debugger will attempt to load "C:\WINDOWS\System32\KERNELBASE.dll" at given base 0000000000000000. Please provide the full image name, including the extension (i.e. kernel32.dll) for more reliable results.Base address and size overrides can be given as .reload <image.ext>=<base>,<size>. KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2718 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on THEHIDEOUT Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 33897 Key : Analysis.Memory.CommitPeak.Mb Value: 101 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.1 ADDITIONAL_XML: 1 OS_BUILD_LAYERS: 1 BUGCHECK_CODE: a BUGCHECK_P1: 4c60 BUGCHECK_P2: 2 BUGCHECK_P3: 1 BUGCHECK_P4: fffff80344c6aa50 WRITE_ADDRESS: 0000000000004c60 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 PROCESS_NAME: Spotify.exe TRAP_FRAME: fffffe8953c6f700 -- (.trap 0xfffffe8953c6f700) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=000000000000003f rbx=0000000000000000 rcx=0000000000000000 rdx=ffffc7006f4cf180 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80344c6aa50 rsp=fffffe8953c6f890 rbp=fffffe8953c6fb80 r8=fffffe8953c6faa8 r9=0000000000000000 r10=0000000000000001 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!ExpSetTimerObject+0x5e0: fffff80344c6aa50 f0480fba2b00 lock bts qword ptr [rbx],0 ds:0000000000000000=???????????????? Resetting default scope STACK_TEXT: fffffe8953c6f5b8 fffff80344e07769 : 000000000000000a 0000000000004c60 0000000000000002 0000000000000001 : nt!KeBugCheckEx fffffe8953c6f5c0 fffff80344e03a69 : 0000000000000000 0210005000000000 0000000000000000 0000000000000000 : nt!KiBugCheckDispatch+0x69 fffffe8953c6f700 fffff80344c6aa50 : fffffe8953c6faa8 fffffe8953c6fb80 ffffa6000e9d29f0 fffff80344c68200 : nt!KiPageFault+0x469 fffffe8953c6f890 fffff80344c6a3a5 : 00000000104e7b30 fffffe8953c6faa8 0000000000000000 00000000000493e0 : nt!ExpSetTimerObject+0x5e0 fffffe8953c6fa40 fffff80344e071b8 : ffffa6000b49d080 0000000000000000 0000000000000000 0000000000335000 : nt!NtSetTimerEx+0x1b5 fffffe8953c6fb00 00007ff827d8f584 : 00007ff825e8929c 0000000000000000 0000000000002258 000000000733f264 : nt!KiSystemServiceCopyEnd+0x28 000000000723e968 00007ff825e8929c : 0000000000000000 0000000000002258 000000000733f264 00007ff825e8a89d : ntdll!NtSetTimerEx+0x14 000000000723e970 00007ff825e891d9 : 0000000000335000 00007ff825e89190 0000000000337000 0000000000335000 : wow64!whNtSetTimerEx_TimerSetCoalescableTimer+0xac 000000000723ea10 00007ff825e89028 : 0000000000000008 0000000000335000 00007ff825e8a460 0000000000000060 : wow64!whNtSetTimerEx+0x49 000000000723ea50 0000000077da17c3 : 0000002377e2303c 0000000000000023 00000000000493e0 000000000733f33c : wow64!Wow64SystemServiceEx+0x168 000000000723f310 0000000077da11b9 : 000000000733fd24 00007ff825e839b4 000000000723f3e0 00007ff825e83aaf : wow64cpu!ServiceNoTurbo+0xb 000000000723f3c0 00007ff825e838c9 : 0000000006efe2e8 0000000000400130 0000000000000000 000000000723f800 : wow64cpu!BTCpuSimulate+0x9 000000000723f400 00007ff825e832bd : 0000000000000000 0000000000000001 0000000000000000 0000000000000000 : wow64!RunCpuSimulation+0xd 000000000723f430 00007ff827d64aef : 0000000000000000 0000000000000000 0000000000000001 0000000000000000 : wow64!Wow64LdrpInitialize+0x12d 000000000723f6e0 00007ff827d649d3 : 0000000000000000 00007ff827cf0000 0000000000000000 0000000000335000 : ntdll!_LdrpInitialize+0x103 000000000723f780 00007ff827d6497e : 000000000723f800 0000000000000000 0000000000000000 0000000000000000 : ntdll!LdrpInitialize+0x3b 000000000723f7b0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 00000000`00000000 : ntdll!LdrInitializeThunk+0xe


SYMBOL_NAME: nt!ExpSetTimerObject+5e0

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 5e0

FAILURE_BUCKET_ID: AV_nt!ExpSetTimerObject

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {31c0275a-852c-faf0-83a4-fbd606fe9cd8}

Followup: MachineOwner

I wonder if fresh Windows install will help.

 

[Sinoreth]

That's a new one.

Spoiler

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000004477, A driver tried to write to an unallocated address in the
user space of the system process. Parameter 2 contains the
address of the attempted write.
Arg2: 0000000000040293
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2749

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on THEHIDEOUT

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 2813

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

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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 1a

BUGCHECK_P1: 4477

BUGCHECK_P2: 40293

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

TRAP_FRAME: ffff920c7284c160 -- (.trap 0xffff920c7284c160)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000010000004 rbx=0000000000000000 rcx=ffffbb8480c9a080
rdx=ffffbb8480279150 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801439e2821 rsp=ffff920c7284c2f0 rbp=ffff920c7284c339
r8=ffffbb84898aea20 r9=000000000000003e r10=fffff80144b59910
r11=ffffbb8480c9a080 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
FLTMGR!FltSetStreamHandleContext+0x4d1:
fffff801439e2821 4d8906 mov qword ptr [r14],r8 ds:0000000000000000=????????????????
Resetting default scope

STACK_TEXT:
ffff920c7284bdd8 fffff80144c47f9d : 000000000000001a 0000000000004477 0000000000040293 0000000000000000 : nt!KeBugCheckEx
ffff920c7284bde0 fffff80144a0d227 : 0000000000000000 ffffa4d200000000 ffff920c7284c160 ffffa4d240000000 : nt!MiInPagePageTable+0x1961bd
ffff920c7284bf30 fffff80144a0c6ca : ffffbb848faba1f0 ffff920c00000000 ffffbb8480c9a6d0 0000000000000000 : nt!MiUserFault+0x5e7
ffff920c7284bfc0 fffff80144c0395e : ffffbb84898aeaa0 0000000000000000 0000000000000000 fffff80144a60725 : nt!MmAccessFault+0x16a
ffff920c7284c160 fffff801439e2821 : 0000000000000000 00000000000000fd ffff920c7284c400 ffff920c00000000 : nt!KiPageFault+0x35e
ffff920c7284c2f0 fffff80144a82147 : ffff920c7284d000 fffff80144d191de ffff920c72847000 ffff920c7284c400 : FLTMGR!FltSetStreamHandleContext+0x4d1
ffff920c7284c3a0 fffff80144b53848 : fffff801439e8a20 0000000000000000 0000000000000000 fffff801439e2680 : nt!FsFilterPerformCallbacks+0xe7
ffff920c7284c410 fffff80144b51543 : ffffbb848b9a70c0 ffffbb84884c39a0 0000000000000001 000000000033c000 : nt!FsRtlAcquireFileForModWriteEx+0x104
ffff920c7284c6f0 fffff80144bb298b : fffff80145450b40 0000000000000001 ffffbb84884c38d0 0000000000000000 : nt!MiGatherMappedPages+0x2b7
ffff920c7284c7b0 fffff80144b17e25 : ffffbb8480c9a080 ffffbb8480c9a080 0000000000000080 000f8067b4bbbdff : nt!MiMappedPageWriter+0x18b
ffff920c7284cc10 fffff80144bfcdd8 : ffffa8001c15c180 ffffbb8480c9a080 fffff80144b17dd0 0000000000000000 : nt!PspSystemThreadStartup+0x55
ffff920c7284cc60 0000000000000000 : ffff920c7284d000 ffff920c72847000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nt!MiInPagePageTable+1961bd

MODULE_NAME: nt

STACK_COMMAND: .thread ; .cxr ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 1961bd

FAILURE_BUCKET_ID: 0x1a_4477_nt!MiInPagePageTable

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {450c6f12-6cc4-7ba0-4c0b-62a961009d87}

Followup: MachineOwner
---------

 

[Saga Lout]

I think it's the right time to hang back until someone analyses the first dump and sets you out on the right course.

 

[maikutech]

5 more dumps if anyone is willing to take a look.
Checked my RAM with memtest86, 0 errors.
Checked all system with Malwarebytes, got about 10, cleaned them all.
It seemed that most of the bsods happened when i'm using chrome for some reason. Tried reinstalling just in-case, no help.
Tried updating every single driver i could, got another IRQL_NOT_LESS_OR_EQUAL and DRIVER_IRQL_NOT_LESS_OR_EQUAL just now.
Bsod sometimes mentions afd.sys as cause, as well as ntoskrnl.exe of course, what's this about?

Getting desperate.

afd.sys Blue Screen

Link to Minidump: https://www.dropbox.com/s/q9ms09t5h3f4xwd/072017-32171-01.dmp?dl=0 I've never experienced a BSOD like this before and I'm not sure what caused it. Could anyone offer some insight?

forums.tomshardware.com

Just for the heck of it please load eventviewer.exe, click on windows tab, system tab, look for any recent "red X marks" screen shot it with the error description.

SagaLout should be able to make sense of it if I don't come around again.

 

[Saga Lout]

Thanks for your help, Maikutech.

 

[Sinoreth]

Thanks for heads-up.
Nothing interesting about the Critical error...
https://drive.google.com/file/d/13e8bXbqEk9lKnurv7GV4NWRAdaUZHIS2/view?usp=sharing
But i've noticed that Malwarebytes service failes to start everytime system is loaded.
https://drive.google.com/file/d/1yfI8_IQQtLBHE5nAp9fiyvTZCUVuTo85/view?usp=sharing
Probably wouldn't cause a bsod, but who knows - i've uninstalled it completely just in-case.

Also noticed, there is a list of warnings, right before the bsods.

Spoiler

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user (Me) SID (S-1-5-21-3839660044-2485030554-429698755-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Again, not sure if relevant.

 

[johnbl]

looked at one bugcheck, bad memory address passed to network socket
strange driver installed:
C:\WINDOWS\SysWOW64\DRIVERS\ssgdio64.sys Fri Sep 9 11:40:54 2005
C:\WINDOWS\system32\drivers\rawaccel.sys Wed Oct 14 17:58:36 2020

I would remove these two drivers. use Autoruns for Windows - Windows Sysinternals | Microsoft Docs
this tool, uncheck the drivers so they will not load then reboot. or delete the entry and they will not load.

overclock driver installed: (most likely not related to the problem)
C:\Program Files (x86)\MSI Afterburner\RTCore64.sys Thu Sep 19 03:45:31 2019

-------
BiosVersion = 5602
BiosReleaseDate = 07/14/2020
BaseBoardManufacturer = ASUSTeK COMPUTER INC.
BaseBoardProduct = PRIME B350-PLUS
~MHz = REG_DWORD 3593
Identifier = REG_SZ AMD64 Family 23 Model 113 Stepping 0
ProcessorNameString = REG_SZ AMD Ryzen 5 3600 6-Core Processor


will take a quick look at a few other bugchecks.

 

[johnbl]

looked at one bugcheck, bad memory address passed to network socket
strange driver installed:
C:\WINDOWS\SysWOW64\DRIVERS\ssgdio64.sys Fri Sep 9 11:40:54 2005
C:\WINDOWS\system32\drivers\rawaccel.sys Wed Oct 14 17:58:36 2020

I would remove these two drivers. use Autoruns for Windows - Windows Sysinternals | Microsoft Docs
this tool, uncheck the drivers so they will not load then reboot. or delete the entry and they will not load.

overclock driver installed: (most likely not related to the problem)
C:\Program Files (x86)\MSI Afterburner\RTCore64.sys Thu Sep 19 03:45:31 2019

-------
BiosVersion = 5602
BiosReleaseDate = 07/14/2020
BaseBoardManufacturer = ASUSTeK COMPUTER INC.
BaseBoardProduct = PRIME B350-PLUS
~MHz = REG_DWORD 3593
Identifier = REG_SZ AMD64 Family 23 Model 113 Stepping 0
ProcessorNameString = REG_SZ AMD Ryzen 5 3600 6-Core Processor


will take a quick look at a few other bugchecks.

second bugcheck looked like some issue with power management.
I have been seeing a bunch of these lately, I do not know how to fix.
remove the overclock driver. maybe turn off the power management functions.
windows driver framework code is on the raw stack just before the bugcheck.
----------
bugcheck, raw stack shows
amd power management code mixed with some nvidia code right before the crash.
bad value used for the cpu instruction pointer (zero)
-------------
bugcheck stack pointer messed up.

start cmd.exe as an admin then run
sfc /scannow
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

see if it finds anything to repair. (I don't expect it will but it will not hurt)

if that fails you might disable your amd power management and see if that helps
it will lock cpu to certain settings so they will not be tweaked by amdppm.sys
to do this you would go into registry editor and find this key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\amdppm
Start to have a value of 4
you should note what the value was before you change it to 4 (disabled) then reboot.
you can later change it back.
here is the list of start values: ServiceStartMode Enum (System.ServiceProcess) | Microsoft Docs
-----------
check to see if windows update advanced update is trying to push out any driver fix for your machine.
I think there is just some bios /cpu version mismatch with the versions of amdppm.sys and mcupdate_AuthenticAMD.dll
that microsoft is providing. you do have
\C:\Program Files\AMD\RyzenMaster\bin\AMDRyzenMasterDriver.sys Tue Mar 31 21:07:41 2020
which should over ride the mcupdate_AuthenticAMD.dll file.

I think there are just problems right now with the chipset drivers, the bios, amd drivers from amd, and the amd drivers from microsoft.
I think AMD is doing updates next month for these problems.

you might be able to find bios settings to make the amd cpu more stable but I am just the wrong person for those problems.
(i have a intel cpu and have never looked at AMD settings to the point I would know of a fix)

I also have not been able to find the known bug list for
REG_SZ AMD64 Family 23 Model 113 Stepping 0
I see the known bugs for earlier models but not for this one.

 

[Sinoreth]

second bugcheck looked like some issue with power management.
I have been seeing a bunch of these lately, I do not know how to fix.
remove the overclock driver. maybe turn off the power management functions.
windows driver framework code is on the raw stack just before the bugcheck.
----------
bugcheck, raw stack shows
amd power management code mixed with some nvidia code right before the crash.
bad value used for the cpu instruction pointer (zero)
-------------
bugcheck stack pointer messed up.

start cmd.exe as an admin then run
sfc /scannow
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

see if it finds anything to repair. (I don't expect it will but it will not hurt)

if that fails you might disable your amd power management and see if that helps
it will lock cpu to certain settings so they will not be tweaked by amdppm.sys
to do this you would go into registry editor and find this key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\amdppm
Start to have a value of 4
you should note what the value was before you change it to 4 (disabled) then reboot.
you can later change it back.
here is the list of start values: ServiceStartMode Enum (System.ServiceProcess) | Microsoft Docs
-----------
check to see if windows update advanced update is trying to push out any driver fix for your machine.
I think there is just some bios /cpu version mismatch with the versions of amdppm.sys and mcupdate_AuthenticAMD.dll
that microsoft is providing. you do have
\C:\Program Files\AMD\RyzenMaster\bin\AMDRyzenMasterDriver.sys Tue Mar 31 21:07:41 2020
which should over ride the mcupdate_AuthenticAMD.dll file.

I think there are just problems right now with the chipset drivers, the bios, amd drivers from amd, and the amd drivers from microsoft.
I think AMD is doing updates next month for these problems.

you might be able to find bios settings to make the amd cpu more stable but I am just the wrong person for those problems.
(i have a intel cpu and have never looked at AMD settings to the point I would know of a fix)

I also have not been able to find the known bug list for
REG_SZ AMD64 Family 23 Model 113 Stepping 0
I see the known bugs for earlier models but not for this one.

Thanks, johnbl!
the sfc /scannow actually found some corrupt drivers and repaired them.
But right after that it bsod again.
I've also disabled amd power management like you recommended.

Windows just pushed out new security update.
Let's see if all of this helped.

 

[maikutech]

Could you please tell me the minimum of your system specs ?
I need to know what motherboard you have model name/ number I need to know what ram you have model name/ model number and I need to know your exact power supply a name with model number.

Since you keep having errors with power management as stated by someone else.
I'm guessing that your power supply maybe at fault but if it's on a frequent basis every day and it happens at intervals like every 3-6 hours I would probably look at getting a new power supply.

 

[Sinoreth]

Could you please tell me the minimum of your system specs ?
I need to know what motherboard you have model name/ number I need to know what ram you have model name/ model number and I need to know your exact power supply a name with model number.

Since you keep having errors with power management as stated by someone else.
I'm guessing that your power supply maybe at fault but if it's on a frequent basis every day and it happens at intervals like every 3-6 hours I would probably look at getting a new power supply.

I've compiled PCPartPicker higher in this thread: PCPartPicker
Just in-case that's not gonna work for you though:


Motherboard: Asus PRIME B350-PLUS
RAM: Corsair Vengeance LPX 2x8gb DDR4 - 2666 CL16
PSU: Cougar VTE 600 W 80+ Bronze Certified ATX Power Supply


My mobo and RAM are old, about 3-4 years.
The PSU is about 6 months old
My CPU is very new, AMD Ryzen 5 3600 3.6 GHz 6-Core Processor. The issues started after the first installation, so that also might be the cause. Maybe even that very rare case of faulty cpu.

Issues still persist. The thing i've notticed, is that it never happens when PC is busy with actively processing something. Games for example. 3 weeks, not a single crash in-game. Most of the bsods happen when i just browse Google Chrome.

I also have a problem with reapearing malware in Chrome. Might be relevant.