Question PC randomly Freeze

Sep 19, 2021
19
0
10
Hi everyone i have this wierd problem my pc at least once a day freeze randomly and after few mins system reboot and happens randomly not only when gaming i tried to update gpu and windows and all the drivers i tried most of the solutions and i’m like 100% sure it’s hardware issue because i tried to format and reinstall the windows and while installing the windows it froze i’m not overclocking and i don’t have overheating issue at all i did gpu and cpu stress test for many hours and the pc didn’t freeze or reboot i tried to update my bios didn’t solve the issue i did memory test no error and i did hardisks test no error two and i’m so lost i have been having this issue for more than year and i tried my best to find solutions but no luck this is my spec :

msi gtx 1660ti
Ryzen 2600x
Msi tomahawk b450
Seasonic gold 550W
Silicon Power Ace A55 2.5" 128GB SSD
1TB WD Blue
G.skill ripjaws v series 16GB (2x8)
NZXT h500i
 
Sep 19, 2021
19
0
10
The issue is wierd it sometime happens while i’m playing or even watching youtube or using discord but most often while gaming and i notice it appears more games than the others like fifa 21 and valheim
 
Sep 19, 2021
19
0
10
Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.

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

On Sun 9/19/2021 4:24:53 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\091921-10281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F71C0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF80111AFA320, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 9/15/2021 9:42:06 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\091521-9812-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x3AD0)
Bugcheck code: 0x119 (0x2, 0xFFFFFFFFC000000D, 0xFFFFF88E4155B960, 0xFFFFB389CA14BCD0)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
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 Sun 8/29/2021 3:55:47 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\082921-10671-01.dmp
This was probably caused by the following module: amdppm.sys (amdppm+0x2ec7)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF800186FA320, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\drivers\amdppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.



On Sun 8/22/2021 5:50:50 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\082221-14187-01.dmp
This was probably caused by the following module: 0n87.sys (0n87)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8022E8FA320, 0x0)
Error: DPC_WATCHDOG_VIOLATION
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).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: 0n87.sys .
Google query: 0n87.sys DPC_WATCHDOG_VIOLATION



On Fri 8/6/2021 11:56:11 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\080721-9968-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF80419A5AE7F)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80419A5AE7F, 0xFFFFFA84D42C8FB8, 0xFFFFFA84D42C87F0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\System32\DriverStore\FileRepository\nvmdi.inf_amd64_a871a754b978bc7f\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 461.40
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 461.40
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 461.40 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



The following dump files were found but could not be read. These files may be corrupted:
C:\Windows\LiveKernelReports\PoW32kWatchdog-20210919-1623.dmp
 
Sep 19, 2021
19
0
10
unplug the hdd and try system to see if you have any freexe also use whocrashed to see if system have minidump files in the other thing try another sata cable from board to ssd and bios is up to date with driver .
crash dumps have been found and analyzed. Only 5 are included in this report. If dump files are found and they could not be analuzed, it means they are corrupted. Because crash dumps are an emergency measure it is not uncommon for this to happen, however often it points to a problem in the storage stack. It is suggested that you run CHKDSK on your system drive to check your drive for errors.
2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 461.40 , NVIDIA Corporation)
0n87.sys

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
 
Sep 19, 2021
19
0
10
could be the gpu was not fully seated in the slot or power cable got loose with vibration at least you have a working system this is good news .
almost 20 days no freezing thanks god thanks for ur time and help dude tbh until now i have no idea what fixed the problem about i'm so happy that i will not need to replaec my gpu