Question BSOD with new PC

Toggle sidebar Toggle sidebar
Zakuta

Zakuta

Reputable
Feb 11, 2021
21
1
4,515
Problem:
Since I've had this computer (october 2019), it hasn't stopped giving BSOD (MACHINE_CHECK_EXCEPTION and CLOCK_WATCHDOG_TIMEOUT) at any time: playing games, using the web browser, or even with nothing open. In Linux the same thing happens playing, only that it freezes and restarts

PC Specs:
Intel Core I5-9400F
MSI Z370-A Pro
Geforce GTX1660Ti ASUS Dual
RAM Kingstone 2x8GB 2666MHz
SSD 240GB WD Green
HDD 1TB Seagate Barracuda
PSU 550w 80+ Sentey

I tried to:
  1. Updating BIOS
  2. Using another disk
  3. Using Linux and Windows
  4. Doing a clean installation
  5. Updating drivers
  6. Adding fans on the back case

BSOD Logs:

https://imgur.com/a/RQqoUGa
 
Sort by date Sort by votes
Zakuta said:
Problem:
Since I've had this computer (october 2019), it hasn't stopped giving BSOD (MACHINE_CHECK_EXCEPTION and CLOCK_WATCHDOG_TIMEOUT) at any time: playing games, using the web browser, or even with nothing open. In Linux the same thing happens playing, only that it freezes and restarts

PC Specs:
Intel Core I5-9400F
MSI Z370-A Pro
Geforce GTX1660Ti ASUS Dual
RAM Kingstone 2x8GB 2666MHz
SSD 240GB WD Green
HDD 1TB Seagate Barracuda
PSU 550w 80+ Sentey

I tried to:
  1. Updating BIOS
  2. Using another disk
  3. Using Linux and Windows
  4. Doing a clean installation
  5. Updating drivers
  6. Adding fans on the back case
BSOD Logs:

https://imgur.com/a/RQqoUGa
Click to expand...
Have you tried running memtest86?
 
Upvote 0 Downvote
It’s too hard to read that photo image but if you got any more than zero errors then that means the memory is bad and you have to let it run for four full passes


The fact that this happens in Linux and windows makes me believe this is a hardware issue and you should RMA the unit
 
Upvote -1 Downvote
Mandark said:
It’s too hard to read that photo image but if you got any more than zero errors then that means the memory is bad and you have to let it run for four full passes


The fact that this happens in Linux and windows makes me believe this is a hardware issue and you should RMA the unit
Click to expand...
Sorry for the poor quality, it was 3AM and I didn't check it right

Here I upload it with better quality:
https://imgur.com/a/32SyEWh
 
Upvote 0 Downvote
I agree about the comment above with the PSU possibly being faulty so you might want to check that out
 
Upvote -1 Downvote
Zakuta said:
Problem:
Since I've had this computer (october 2019), it hasn't stopped giving BSOD (MACHINE_CHECK_EXCEPTION and CLOCK_WATCHDOG_TIMEOUT) at any time: playing games, using the web browser, or even with nothing open. In Linux the same thing happens playing, only that it freezes and restarts

PC Specs:
Intel Core I5-9400F
MSI Z370-A Pro
Geforce GTX1660Ti ASUS Dual
RAM Kingstone 2x8GB 2666MHz
SSD 240GB WD Green
HDD 1TB Seagate Barracuda
PSU 550w 80+ Sentey

I tried to:
  1. Updating BIOS
  2. Using another disk
  3. Using Linux and Windows
  4. Doing a clean installation
  5. Updating drivers
  6. Adding fans on the back case
BSOD Logs:

https://imgur.com/a/RQqoUGa
Click to expand...
Well, I installed WhoCrashed to have more information about what was wrong, and now in addition to the ntoskrnl.exe, there is intelppm.sys and win32kfull.sys

Crash dumps are enabled on your computer.

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

On Sat 13/2/2021 19:15:38 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021321-6390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0x9C (0x80000001, 0xFFFF8D80CF8A7B10, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 13/2/2021 19:15:38 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: win32kfull.sys (win32kfull+0xE403F)
Bugcheck code: 0x9C (0x80000001, 0xFFFF8D80CF8A7B10, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\Windows\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 13/2/2021 18:53:59 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021321-6343-01.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x138f)
Bugcheck code: 0x101 (0x20, 0x0, 0xFFFF8000EFD80180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (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.



On Sat 13/2/2021 18:38:21 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021321-7828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0x9C (0x80000001, 0xFFFFB4008935BB10, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 13/2/2021 18:33:57 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021321-6703-01.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x138f)
Bugcheck code: 0x101 (0x20, 0x0, 0xFFFFB7816F980180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (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.



On Sat 13/2/2021 14:24:14 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021321-9062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0x9C (0x80000001, 0xFFFFF80367298B10, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


Maybe this helps to know what it is, although I still have in mind to buy another psu to try
 
Upvote 0 Downvote
Zakuta said:
Well, I installed WhoCrashed to have more information about what was wrong, and now in addition to the ntoskrnl.exe, there is intelppm.sys and win32kfull.sys

Crash dumps are enabled on your computer.

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

On Sat 13/2/2021 19:15:38 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021321-6390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0x9C (0x80000001, 0xFFFF8D80CF8A7B10, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 13/2/2021 19:15:38 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: win32kfull.sys (win32kfull+0xE403F)
Bugcheck code: 0x9C (0x80000001, 0xFFFF8D80CF8A7B10, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\Windows\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 13/2/2021 18:53:59 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021321-6343-01.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x138f)
Bugcheck code: 0x101 (0x20, 0x0, 0xFFFF8000EFD80180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (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.



On Sat 13/2/2021 18:38:21 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021321-7828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0x9C (0x80000001, 0xFFFFB4008935BB10, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 13/2/2021 18:33:57 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021321-6703-01.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x138f)
Bugcheck code: 0x101 (0x20, 0x0, 0xFFFFB7816F980180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (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.



On Sat 13/2/2021 14:24:14 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021321-9062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0x9C (0x80000001, 0xFFFFF80367298B10, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


Maybe this helps to know what it is, although I still have in mind to buy another psu to try
Click to expand...
Always a different .sys, I've already tried disabling Intel SpeedStep and C-States, plus changing the Intelppm to 4 ..


Crash dumps are enabled on your computer.

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

On Mon 15/2/2021 00:21:44 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021521-11328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3f5a80)
Bugcheck code: 0x101 (0x20, 0x0, 0xFFFFAB012AB80180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
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 an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 15/2/2021 00:21:44 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntfs.sys (ntfs+0xa4b5)
Bugcheck code: 0x101 (0x20, 0x0, 0xFFFFAB012AB80180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Controlador del sistema de archivos NTFS
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Sun 14/2/2021 10:02:20 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021421-11671-01.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x44a2)
Bugcheck code: 0x101 (0x20, 0x0, 0xFFFF990177180180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (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.



On Sun 14/2/2021 02:23:59 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021421-11984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0x9C (0x80000001, 0xFFFFF8002A898B10, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 
Upvote 0 Downvote
white.a.drew said:
In cmd as admin in the following order....

Sfc /scannow

DISM /Online /Cleanup-Image /CheckHealth

DISM /Online /Cleanup-Image /ScanHealth

DISM /Online /Cleanup-Image /RestoreHealth

/Source:repairSource\install.wim
Click to expand...
I already did it and it does not detect errors, a while after installing the chipset I received this bsod

On Tue 16/2/2021 04:03:22 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021621-6781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3f5a80)
Bugcheck code: 0x101 (0x20, 0x0, 0xFFFF82811C380180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
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 an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
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 16/2/2021 04:03:22 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!memset+0x31f7c)
Bugcheck code: 0x101 (0x20, 0x0, 0xFFFF82811C380180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 
Upvote 0 Downvote
Zakuta said:
I already did it and it does not detect errors, a while after installing the chipset I received this bsod

On Tue 16/2/2021 04:03:22 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021621-6781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3f5a80)
Bugcheck code: 0x101 (0x20, 0x0, 0xFFFF82811C380180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
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 an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
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 16/2/2021 04:03:22 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!memset+0x31f7c)
Bugcheck code: 0x101 (0x20, 0x0, 0xFFFF82811C380180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Click to expand...
How are you installing windows.... It could be as simple as a currupted install plateform. Which in turn is just installing a completely currupted copy of windows on your system
 
Upvote 0 Downvote
white.a.drew said:
How are you installing windows.... It could be as simple as a currupted install plateform. Which in turn is just installing a completely currupted copy of windows on your system
Click to expand...
I have installed it multiple times from USB, I tried switching version or asking someone else to try to install it and it remains the same so I guess it is a processor issue
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom