- Mar 21, 2020
- 3
- 0
- 10
Hey everyone,
My Screen started to freezes and remains like that, but sometimes i get a bluescreen,it just happens while gaming, this is crash reports from whocrashed:
Computer name: DESKTOP-QPFN3SD
Windows version: Windows 10 , 10.0, version 1903, build: 18362
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., PRIME H310M-K R2.0
CPU: GenuineIntel Intel(R) Core(TM) i3-9100F CPU @ 3.60GHz Intel8664, level: 6
4 logical processors, active mask: 15
RAM: 8522108928 bytes (7.9GB)
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Fri 5/22/2020 12:39:45 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\052220-16593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2380)
Bugcheck code: 0xEF (0xFFFFC589EC34C080, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 5/22/2020 10:31:04 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\052220-5343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0x162 (0xFFFFDE077BD7E080, 0xFFFFDE077B7554F0, 0xFFFFFFFF, 0x0)
Error: KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE
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 released by a thread that did not own the lock.
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 Fri 5/22/2020 10:31:04 PM 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+0x57AD2)
Bugcheck code: 0x162 (0xFFFFDE077BD7E080, 0xFFFFDE077B7554F0, 0xFFFFFFFF, 0x0)
Error: KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE
Bug check description: This indicates that a lock tracked by AutoBoost was released by a thread that did not own the lock.
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 Fri 5/22/2020 12:17:38 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\052220-19031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2380)
Bugcheck code: 0xA (0x3, 0x2, 0x0, 0xFFFFF8060BE00156)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
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 Thu 5/21/2020 10:34:23 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\052120-18015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2380)
Bugcheck code: 0x139 (0x2, 0xFFFFB081B349F700, 0xFFFFB081B349F658, 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.
The following dump files were found but could not be read. These files may be corrupted:
C:\WINDOWS\Minidump\052220-6906-01.dmp
i had a problem with my pc before 1 week, and i had to change the motherboard, but it is the same model.
My pc specs are: Intel(R) Core(TM) i3-9100F CPU @3.60GHz
Motherboard:ASUS Prime H310M-K R2.0
GPU: GeForce GTX 1650
8GB RAM
SSD 240 GB
My Screen started to freezes and remains like that, but sometimes i get a bluescreen,it just happens while gaming, this is crash reports from whocrashed:
Computer name: DESKTOP-QPFN3SD
Windows version: Windows 10 , 10.0, version 1903, build: 18362
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., PRIME H310M-K R2.0
CPU: GenuineIntel Intel(R) Core(TM) i3-9100F CPU @ 3.60GHz Intel8664, level: 6
4 logical processors, active mask: 15
RAM: 8522108928 bytes (7.9GB)
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Fri 5/22/2020 12:39:45 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\052220-16593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2380)
Bugcheck code: 0xEF (0xFFFFC589EC34C080, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 5/22/2020 10:31:04 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\052220-5343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0x162 (0xFFFFDE077BD7E080, 0xFFFFDE077B7554F0, 0xFFFFFFFF, 0x0)
Error: KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE
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 released by a thread that did not own the lock.
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 Fri 5/22/2020 10:31:04 PM 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+0x57AD2)
Bugcheck code: 0x162 (0xFFFFDE077BD7E080, 0xFFFFDE077B7554F0, 0xFFFFFFFF, 0x0)
Error: KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE
Bug check description: This indicates that a lock tracked by AutoBoost was released by a thread that did not own the lock.
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 Fri 5/22/2020 12:17:38 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\052220-19031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2380)
Bugcheck code: 0xA (0x3, 0x2, 0x0, 0xFFFFF8060BE00156)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
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 Thu 5/21/2020 10:34:23 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\052120-18015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2380)
Bugcheck code: 0x139 (0x2, 0xFFFFB081B349F700, 0xFFFFB081B349F658, 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.
The following dump files were found but could not be read. These files may be corrupted:
C:\WINDOWS\Minidump\052220-6906-01.dmp
i had a problem with my pc before 1 week, and i had to change the motherboard, but it is the same model.
My pc specs are: Intel(R) Core(TM) i3-9100F CPU @3.60GHz
Motherboard:ASUS Prime H310M-K R2.0
GPU: GeForce GTX 1650
8GB RAM
SSD 240 GB
Facebook
Twitter
Instagram