Windows 10: BSOD every 5 minutes

***moved on english forum***


Hello guys,


I really need your support there, my PC crashes every 5 minutes with BSOD, ive done A LOT OF TEST, tested all my componant, all is good.


New new Windows, all driver ok etc... etc...


Here is my minidump crash link :


https://1drv.ms/u/s!AnwVeJUqOmBSgiSVbCGkczMNOxUq?e=3DFM0O


Can you help me pllllllls :


I give you my WhoCrashed :


System Information local



Computer name: DESKTOP-85K9Q64
Windows version: Windows 10 , 10.0, build: 19041
Windows dir: C:\Windows
Hardware: MS-7C37, Micro-Star International Co., Ltd., MPG X570 GAMING PLUS MS-7C37
CPU: AuthenticAMD AMD Ryzen 7 3700X 8-Core Processor AMD8664, level: 23
16 logical processors, active mask: 65535
RAM: 34308075520 bytes 32,0GB






Crash Dump Analysis





Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Tue 26/05/2020 16:02:13 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052620-8984-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x39D860
Bugcheck code: 0xD1 0x0, 0xFF, 0xA6, 0x0
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 26/05/2020 16:02:13 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe nt!setjmpex+0x8179
Bugcheck code: 0xD1 0x0, 0xFF, 0xA6, 0x0
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 26/05/2020 15:47:46 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052620-9921-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x39D860
Bugcheck code: 0x139 0x4, 0xFFFFEE8B614B4FC0, 0xFFFFEE8B614B4F18, 0x0
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.



On Tue 26/05/2020 11:54:18 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052620-4015-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x39D860
Bugcheck code: 0x192 0xFFFFA1087BAF6080, 0xFFFFD50D33C251B8, 0x0, 0x0
Error: KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL
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 lock tracked by AutoBoost was acquired while executing at DISPATCH_LEVEL or above.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

:)

 

my son laptiop wifi disconnect after 5 minutes

• If you have an identical laptop try comparing the wifi and security settings of the one that does not disconnect with the one that does. If you find any differences change the settings of the one that does not work to the one that does.

• If you do not have an identical laptop see this post and the three replies for possible solutions: Wifi disconnects every 5 minutes.

@Samuria : If you have any suggestions please reply.

 

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

 

Need Serious Help: How To Record Video of What is Done on my PC?

I suggest the following simple steps:

1. Set the autosave options in MS Office to a low value say 5 minutes.
2. Setup file history to autosave frequently - the shortest period is 5 mins
3. Install Macrium Reflect Free and configure it to do a daily incremental system backup

You should be well covered if you do the above to protect your key files.