Windows 10: Random BSODs, tried almost every possible fix. Advice?

My PC since building has randomly been crashing and BSOD'ing very frequently. I get different error codes almost every time, but every time I check the event viewer, it is a Kernel Power error. When I check BlueScreenView, the leading cause is almost always ntoskrnl.exe with maybe FLTMGR.sys. Sometimes it will BSOD and not create a dump file which is really frustrating.

Here is my build:

CPU: AMD RYZEN 5 3600

GPU: EVGA GEFORCE RTX 2070 Super

RAM: Corsair Vengeance RGB PRO DDR4 3200MHz 2x8GB

MOBO: MSI B450M Gaming Plus

Storage: Samsung 860 EVO 1 TB SATA form factor, not M.2

PSU: Corsair RMx 2018 650W

Wifi Card: TP-LINK TL-WDN4800 PCIe x1


Case: Antec Dark Phantom DP301M MicroATX Mid Tower


Accessories You wouldn't think it would be relevant, but given my extensive debugging, I'm not ruling anything out:


Keyboard: Corsair K68 RGB Wired


Mouse: Corsair Harpoon RGB


Speakers: Logitech S120 2.3 W 2.0 Channel


Headset: Steelseries Arctic 7


Monitors: Dell SE2416H 23.8" 1920x1080 60 Hz

& Dell S2417DG 23.8" 2560x1440 165 Hz Monitor


What I've tried:

1. Tried updating all the drivers and BIOS

2. Ran Memtest and Windows Memory Diagnostic on RAM 0 errors

3. Switched RAM slots and tried using one stick at a time same behavior

4. Tried switching PSUs with a friend's PSU same behavior

5. Tried switching GPUs with a friend's GPU same behavior

6. Ran Checkdisk and Samsung Magician for my SSD 0 errors

7. Clean installed Windows several times right now, only drivers are installed

8. Ran driver Verifier and found 0 errors. The last couple BSODs happened during the running of the verifier, which may or may not be related.

9. Disabled XMP and increased DRAM voltage by 0.05V. Decreased after no behavioral change

10. Booted in safe mode

11. Ran stress tests and found that temperatures did not exceed my maximum CPU temperature. Crashes were not correlated to any stress tests.

12. RMA'ed my MOBO. MSI reflashed it and said there were no issues.


13. Ran DDU uninstaller in safe mode to clean install my audio and GPU drivers.


14. Plugged my friend's SSD, GPU, and RAM separately in my PC. separately meaning that I replaced one at a time


15. Tried my SSD in my friend's PC.


16. Tried my RAM in my friend's PC. no changes



Noteworthy observations after all this:


1. With my friend's SSD in my PC his is a Samsung 850 1TB EVO with the same form factor as mine, my PC BSODs much less, but it still consistently BSODs upon the first reboot. It sometimes BSODs upon the second reboot after the first crash, and it'll occasionally BSOD while playing a light game and using Discord. The errors are still the same kernel power and caused by ntoskrnk.exe


2. With my SSD in my friend's PC, the PC doesn't BSOD at all. Weirdly, when I checked his event viewer out of curiosity, a kernel power error 41 still appeared despite no apparent issues. If I hadn't checked event viewer, nothing would be suspect and the average PC user would just go about his day.


3. With my RAM in my friend's PC, no behavior was affected.



What I suspect could be the problem after all this:


1. It' s almost 100% a hardware issue and not a driver issue.


2. Given the decrease in BSODs with my friend's SSD in my PC, my PC has multiple issues. The SSD was one.


3. My SSD has something weird going on as proven by the event viewer on his PC. Not sure if it's incompatible with my build or if it's corrupt.






Questions I have:


1. Do I have an incompatible part somewhere that PC Part Picker couldn't detect? My PSU has more than 200W extra than it needs to power my PC, so I don't know what the issue could be.


2. Could it be a faulty case or CPU? I think one of the case cables could possibly be faulty, which is pretty hard to debug. I can't test this with my friend's PC because his is ATX and mine is MicroATX.



Dump Files:


https://oitncsu-my.sharepoint.com/:f:/g/personal/sbdamic2_ncsu_edu/EnCbOza2l1NItPNLGZ_5nE4BfNIgnH3LVicCwZpeZl9VgQ?e=AZQZqm





TLDR: I've listed my dump files above. I'm experiencing random kernel power errors and have tried almost every known solution to fixing them. Not sure what my next course of action should be.


Thanks

:)

 

Random BSOD while browsing internet


BitDefender is nothing special. mwac.sys causes BSODs anywhere.
A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
In that very thread, the suggested action apparently worked.

The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
That is why I posted that my suggestion may work, or may not. Let us see where it goes.

 

Random BSOD while browsing internet

Sorry, Bitdefender is a problem: BSOD BAD_POOL_HEADER - mwac.sys - Malwarebytes Anti-Malware Help - Malwarebytes Forums

 

Random BSODs, tried almost every possible fix. Advice?

My PC since building has randomly been crashing and BSOD'ing very frequently. I get different error codes almost every time. Sometimes, the PC will restart without BSOD'ing, and sometimes it will BSOD and not create a dump file which is really frustrating.

Here is my build:

CPU: AMD RYZEN 5 3600

GPU: EVGA GEFORCE RTX 2070 Super

RAM: Corsair Vengeance RGB PRO DDR4 3200MHz 2x8GB

MOBO: MSI B450M Gaming Plus

Storage: Samsung 860 EVO 1 TB

PSU: Corsair RMx (2018) 650W

Wifi Card: TP-LINK TL-WDN4800 PCIe x1

Here are some of the error codes I've seen (there are certainly more from my PC crashing while away):

1. KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL

2. KERNEL_SECURITY_CHECK_FAILURE

3. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

4. KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE

5. SYSTEM_SERVICE_EXCEPTION

6. SYNTHETIC_WATCHDOG_TIMEOUT

7. DPC_WATCHDOG_VIOLATION

8. SECURE_KERNEL_ERRORWhat failed: Ntfs.sys

9. KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION

10. KMODE_EXCEPTION_NOT_HANDLED

11. APC_INDEX_MISMATCH

12. DRIVER_IRQL_NOT_LESS_OR_EQUALWhat failed: storport.sys

13. FAST_ERESOURCE_PRECONDITION_VIOLATION

14. DRIVER_OVERRAN_STACK_BUFFER

15. PAGE_FAULT_IN_NONPAGED_AREAWhat failed: win32kbase.sys

16. ATTEMPTED_TO_WRITE_READONLY_MEMORYWhat failed: ndis.sys

17. HYPERVISOR_ERROR

18. KERNEL_LOCK_ENTRY_LEAKED_ON_THREAD_TERMINATION

19. KERNEL_MODE_HEAP_CORRUPTION

20. MULTIPLE_IRP_COMPLETE_REQUESTS

21. IRQL_GT_ZERO_AT_SYSTEM_SERVICE

22. IRQL_NOT_LESS_OR_EQUAL

23. SYSTEM_SERVICE_EXCEPTIONWhat failed: nvlddmkm.sys

What I've tried:

1. Tried updating all the drivers and BIOS

2. Ran Memtest and Windows Memory Diagnostic on RAM (0 errors)

3. Switched RAM slots and tried using one stick at a time (same behavior)

4. Tried switching PSUs with a friend's PSU (same behavior)

5. Tried switching GPUs with a friend's GPU (same behavior)

6. Ran Checkdisk and Samsung Magician for my SSD (0 errors)

7. Clean installed Windows (right now, only drivers are installed)

8. Ran driver Verifier and found 0 errors. The last couple BSODs happened during the running of the verifier, which may or may not be related.

9. Disabled XMP and increased DRAM voltage by 0.05V. (Decreased after no behavioral change)

10. Booted in safe mode

11. Ran stress tests and found that temperatures did not exceed my maximum CPU temperature. Crashes were not correlated to any stress tests.

12. RMA'ed my MOBO. MSI reflashed it and said there were no issues.

13. Ran DDU uninstaller in safe mode to clean install my audio and GPU drivers.

14. All the events are Kernel-Power 41 events with EventLog 6008

When I check BlueScreenViewer to view my dumpfiles (5 most recent), ntoskrnl.exe is the common culprit behind all of them, but two of them also have nvlddmkm.sys highlighted as well.

I've been troubleshooting this for quite a while, and I'm not sure how to pinpoint the issue. Anyone else seen anything like this before? I feel like even GeekSquad would have trouble figuring out what's going on here.

Thanks