Windows 10: multiples BSOD with many reasons

Hey, I'm writing here because i'm a little bit desperate, as I tried many tutorials in order to "fix" my computer....I encounter many BSOD with many reasons last one was resource not owned, ntoskrnl.exe, fltmgr.sys, ... I passed all the tests lenovo diagnostic tool tell me that all my hardware is ok, chkdsk and sfcscannow are ok.I updated my computer with last windows update W11, did an update on every driver, and also did a clean reinstall of W11.My config is:LenovoRyzen 7 seriesµ16Gb Ram brand newNvidia 2060 notepadSSD Samsung 500Gb In advance, thanks for your help !

:)

 

BSOD Unknown Reason

The dump file on the 18th was caused by Quick Heal again. The later ones appear to be due to bit flips. I would recommend enabling Driver Verifier on all third-party drivers using the following instructions:

1) Search for verifier using the Start Menu and select the verifier.exe, accept the UAC prompt and you should be presented with the following screen:





2) Tick the following options as shown below





3) Ensure that you select the option to enable you to select drivers yourself





4) Select all drivers which are not Microsoft related and then click the Finish button. Afterwards, please reboot the computer and Driver Verifier will continue to run in the background. Please do not select the drivers which are prefixed with dump_

 

[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?

 

Multiple BSOD

Bug Check 0x1A: MEMORY_MANAGEMENT

Bug Check 0x1A MEMORY_MANAGEMENT - Windows drivers

MEMORY_MANAGEMENT BSODs, accompanied by occasional app crashes/GPUTDR.

http://www.tomshardware.com/forum/3...t-bsods-accompanied-occasional-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).