J
Joshua Naidoo
PC Specs
Ryzen 5 3600
Rx 5700
MSI x570 a-pro
HyperX 16gb 3200mhz ram
I have been experiencing constant blue screens. I used WhoCrashed and it is saying that the ntoskrnl.exe is the problem. I have tested new memory and have updated the drivers. I am struggling to figure how to resolve this issue.
On Wed 2020/06/10 3:01:24 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061020-4531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2D556B)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8017A2D556B, 0xFFFF858C2808AE38, 0xFFFF858C2808A670)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time
Continue reading...
Ryzen 5 3600
Rx 5700
MSI x570 a-pro
HyperX 16gb 3200mhz ram
I have been experiencing constant blue screens. I used WhoCrashed and it is saying that the ntoskrnl.exe is the problem. I have tested new memory and have updated the drivers. I am struggling to figure how to resolve this issue.
On Wed 2020/06/10 3:01:24 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061020-4531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2D556B)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8017A2D556B, 0xFFFF858C2808AE38, 0xFFFF858C2808A670)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time
Continue reading...