Windows 10: BSOD's every 10 minutes or so

Hello,


I am getting regular BSODs every 5 - 30 minutes.


My PC was fine two days ago. I turned it on yesterday and got a ton of BSODs. I did a system restore, which seemed to fix everything, until today when my PC began to get them again. I tried to do another system restore, but this time the BSODs returned about an hour later. My Windows install is recent two weeks old and all drivers were freshly installed last week so are recent. RAM is new and has already been thoroughly tested.


The issue does not occur in Safe Mode. I suspect this is a driver issue but cannot tell which, as the only ones I see in dump files are svchost, ntoskrnl, and ntkrnlmp, which are all windows processes that also run in Safe Mode.


Most of the BSODs don't generate dump files; the PC restarts before the dump file is generated, even though I have auto-restart off. I did get one dump file and one LiveKernalReport: dump files

https://1drv.ms/u/s!AqLx5w_nkC9RiaEipWnKMlK6ELBGGg?e=UDZEOS


Please help me troubleshoot this issue. I need this PC for work and school.


Here are the crash reports from WhoCrashed:

On Fri 11/6/2020 2:58:50 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\110620-7984-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3F5210
Bugcheck code: 0xF7 0xFFEDE184A93DB810, 0xB5F7926C5A76, 0xFFFF4A086D93A589, 0x0
Error: DRIVER_OVERRAN_STACK_BUFFER
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a driver has overrun a stack-based buffer.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Thu 11/5/2020 3:36:21 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\LiveKernelReports\PoW32kWatchdog-20201105-1536.dmp
This was probably caused by the following module: ntkrnlmp.exe nt!IoUnregisterShutdownNotification+0xF84
Bugcheck code: 0x1A1 0xFFFF99027ECC4040, 0x0, 0x0, 0x0
Error: CUSTOM_ERROR

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

:)

 

CLOCK_WATCHDOG_TIMEOUT After Leaving PC for 5-10 Minutes


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.

The 0x101(CLOCK_WATCHDOG_TIMEOUT) is mostly caused by BIOS or hardware problem, the challenge is to find software problems.
I suggest to update your BIOS.
Code:

Code:

BIOS Version:              American Megatrends Inc. 2001   , 7/8/2011

Attachment 51031

 

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.

 

Windows 10 - Sleep Works But Only if 5 Minutes or Less

What about the Troubleshooting tutorial steps here:

https://www.makeuseof.com/tag/fix-windows-10-sl...

I've never seen at least one them not be successful.

I had suggested first to set Display at 0, Sleep at 1 minute and Hibernate at 2 minutes and then after each step sit back to observe. I have rarely had to work all the way through the list.

Absolute thoroughness is required when troubleshooting Sleep, skipping nothing and asking back if you need any help to complete a step. We often find out later that the fix was the skipped step, so please do not skip any. If you need help performing any step
I will help.