Blue screen windows 10

A

arekbaran

Hello. I have not a nice problem, after the format of my computer, blue screens started to appear literally every 5 minutes, I decided to transfer the bios, then the problem started to appear less often, most often when downloading a larger file, but recently it appeared to me just after turning on the computer. The computer was running perfectly through the format. I did tests in WHOCRASHED and bluscreenview here are the results;

Computer name: DESKTOP-4DHEBHG
Windows version: Windows 10 , 10.0, build: 19041
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., PRIME B450M-A
CPU: AuthenticAMD AMD Ryzen 5 3600 6-Core Processor AMD8664, level: 23
12 logical processors, active mask: 4095
RAM: 17111674880 bytes (15,9GB)




Crash Dump Analysis
Crash dumps are enabled on your computer.

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

On Sat 26.09.2020 12:42:24 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092620-10359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0x192 (0xFFFF8681BC6B1080, 0xFFFF8681B8FFF370, 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.



On Sat 26.09.2020 12:42:24 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: fltmgr.sys (FLTMGR!FltDecodeParameters+0x1B6C)
Bugcheck code: 0x192 (0xFFFF8681BC6B1080, 0xFFFF8681B8FFF370, 0x0, 0x0)
Error: KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL
file path: C:\Windows\system32\drivers\fltmgr.sys
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Menedżer filtrów systemu plików firmy Microsoft
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 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 Fri 25.09.2020 18:28:53 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092520-9750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8044DE488F5, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
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 25.09.2020 15:58:55 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092520-9796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8022B40E5B6, 0xFFFFAA81103FF920, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Thu 24.09.2020 18:35:48 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092420-9796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0x192 (0xFFFFE688E4C22040, 0xFFFFE688E45FE5A0, 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.



On Wed 23.09.2020 19:23:07 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092320-8203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0x139 (0x2, 0xFFFF8B081803DE80, 0xFFFF8B081803DDD8, 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.


092620-10359-01.dmp 26.09.2020 12:42:24 0x00000192 ffff8681`bc6b1080 ffff8681`b8fff370 00000000`00000000 00000000`00000000 FLTMGR.SYS FLTMGR.SYS+5dbc x64 ntoskrnl.exe+3f3ea0 C:\Windows\Minidump\092620-10359-01.dmp 12 15 19041 2 559 036 26.09.2020 12:47:27

092520-9750-01.dmp 25.09.2020 18:28:53 KMODE_EXCEPTION_NOT_HANDLED 0x0000001e ffffffff`c0000005 fffff804`4de488f5 00000000`00000000 ffffffff`ffffffff ntoskrnl.exe ntoskrnl.exe+3f3ea0 x64 ntoskrnl.exe+3f3ea0 C:\Windows\Minidump\092520-9750-01.dmp 12 15 19041 2 316 612 25.09.2020 18:29:39

092520-9796-01.dmp 25.09.2020 15:58:55 SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff802`2b40e5b6 ffffaa81`103ff920 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+3f3ea0 x64 ntoskrnl.exe+3f3ea0 C:\Windows\Minidump\092520-9796-01.dmp 12 15 19041 2 459 372 25.09.2020 16:20:57

092420-9796-01.dmp 24.09.2020 18:35:48 0x00000192 ffffe688`e4c22040 ffffe688`e45fe5a0 00000000`00000000 00000000`00000000 FLTMGR.SYS FLTMGR.SYS+61cd x64 ntoskrnl.exe+3f3ea0 C:\Windows\Minidump\092420-9796-01.dmp 12 15 19041 2 586 148 24.09.2020 18:37:07

092320-8203-01.dmp 23.09.2020 19:23:07 0x00000139 00000000`00000002 ffff8b08`1803de80 ffff8b08`1803ddd8 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+3f3ea0 x64 ntoskrnl.exe+3f3ea0 C:\Windows\Minidump\092320-8203-01.dmp 12 15 19041 1 504 500 23.09.2020 19:23:50

Continue reading...
 

Similar threads

O
Replies
0
Views
45
Oskar Podkaura
O
O
Replies
0
Views
39
omega omega1
O
T
Replies
0
Views
60
tnmq28p43bgekyjd97ucr6
T
J
Replies
0
Views
46
Jordan S1
J
Back
Top Bottom