Windows 10: BSOD

I've been trying to fix this BSOD issue for quite a while now and can't seem to fix it.


Updated all drivers. Ran memtest, sfc scannow and all those stuff that I saw on google but nothing fixes it. Only thing that I haven't tries is doing a clean reinstall which I want to avoid because out internet is really slow and I do not have a back up HDD where I can store my files. Can anyone help me please :


[COLOR=rgba17, 17, 17, 1]Windows version: Windows 10, 10.0, version 2009, build: 19042
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., TUF B450M-PRO GAMING
CPU: AuthenticAMD AMD Ryzen 5 3500 6-Core Processor 8664, level: 23
6 logical processors, active mask: 63
RAM: 17089171456 bytes 15.9GB

[/COLOR]



Crash Dump Analysis



[COLOR=rgba17, 17, 17, 1]Crash dumps are enabled on your computer. [/COLOR]

[COLOR=rgba17, 17, 17, 1]Crash dump directories: [/COLOR]
[COLOR=rgba17, 17, 17, 1]C:\WINDOWS[/COLOR]
[COLOR=rgba17, 17, 17, 1]C:\WINDOWS\Minidump[/COLOR]

[COLOR=rgba17, 17, 17, 1]On Thu 4/8/2021 5:39:16 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\040821-5906-01.dmp
This was probably caused by the following module: [COLOR=rgba17, 17, 17, 1]ntoskrnl.exe[/COLOR] nt+0x3F5C50
Bugcheck code: 0x139 0x3, 0xFFFFF588E8A37600, 0xFFFFF588E8A37558, 0x0
Error: [COLOR=rgba17, 17, 17, 1]KERNEL_SECURITY_CHECK_FAILURE[/COLOR]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [COLOR=rgba17, 17, 17, 1]Microsoft® Windows® Operating System[/COLOR]
company: [COLOR=rgba17, 17, 17, 1]Microsoft Corporation[/COLOR]
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

[/COLOR]

[COLOR=rgba17, 17, 17, 1]On Thu 4/8/2021 5:39:16 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: [COLOR=rgba17, 17, 17, 1]ntkrnlmp.exe[/COLOR] nt!setjmpex+0x81C9
Bugcheck code: 0x139 0x3, 0xFFFFF588E8A37600, 0xFFFFF588E8A37558, 0x0
Error: [COLOR=rgba17, 17, 17, 1]KERNEL_SECURITY_CHECK_FAILURE[/COLOR]
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

[/COLOR]

[COLOR=rgba17, 17, 17, 1]On Tue 4/6/2021 1:14:58 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\040621-6062-01.dmp
This was probably caused by the following module: [COLOR=rgba17, 17, 17, 1]amdppm.sys[/COLOR] amdppm+0x2ec7
Bugcheck code: 0x133 0x1, 0x1E00, 0xFFFFF8021C6FB320, 0x0
Error: [COLOR=rgba17, 17, 17, 1]DPC_WATCHDOG_VIOLATION[/COLOR]
file path: C:\WINDOWS\system32\drivers\amdppm.sys
product: [COLOR=rgba17, 17, 17, 1]Microsoft® Windows® Operating System[/COLOR]
company: [COLOR=rgba17, 17, 17, 1]Microsoft Corporation[/COLOR]
description: Processor Device Driver
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs thermal issue.
The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system. [/COLOR]

:)

 

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.

 

7 different BSoD

Hey guys,

I have a serious problem. I make it as short as possible:

• system runs 100 % fine with the 10.12
• updatet to Catalyst 11.1 -> BSoD
• updatet to 11.1 Hotfix -> BSoD
• rollback to 10.12 -> BSoD
• removed ALL AMD files manually, installed 10.12 -> BSoD

• Temps are fine
• no sfc /scannow errors
• no chkdsk errors
• Prime, Furmark all fine
• regardless what driver I install -> BSoD
• I did no hw changes, no OC

Here are my BSoDs I receive:

• 0x0000010e
• 0x1000007e
• 0x0000007e
• 0x0000004e
• 0x0000003b
• dxgmms1.sys
• PFN_LIST_CORRUPT

They all refer to the GPU of course ...

From now on I receive a BSoD every time I try to play a game (especially BC2 and SC II) even if I completely remove the old driver and make a clean install.
Apparently the 11.1 damaged my system irreparable.

Any advice or info would be very much appreciated *Smile

 

BAD_POOL_HEADER BSOD, Dump File attached


Hi Groggubus,

Welcome to the 10forums

Please remove / disable items from the startup in taskmanager
These programs could interfere with the boot process giving you trouble and increase the boot time.

Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
Please remove Daemon Tools and run the SPTD pass through remover.

1. Uninstall Daemon Tools
2. Download the SPTD standalone installer and follow these steps:
   • Double click the executable to open it
   • Click on the button shown below

If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window

Please follow this suggestion for the BSOD

1. Please open BitDefender and go to the modules,
2. Go to the firewall settings,
3. Uncheck 'Block port scans in the network',
4. Reboot your system <-- IMPORTANT