Přidat otázku mezi oblíbenéZasílat nové odpovědi e-mailem BSOD

nebo z Who Crashed
System Information (local)
--------------------------------------------------------------------------------

Computer name: PATRIK
Windows version: Windows 10 , 10.0, build: 17134
Windows dir: C:\Windows
Hardware: AB350-Gaming 3, Gigabyte Technology Co., Ltd., AB350-Gaming 3-CF
CPU: AuthenticAMD AMD Ryzen 3 1200 Quad-Core Processor AMD586, level: 23
4 logical processors, active mask: 15
RAM: 8538116096 bytes total

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer.

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

On Tue 20.11.2018 16:45:39 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112018-6828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A9690)
Bugcheck code: 0xA (0xFFFFF80280B0E070, 0x2, 0x0, 0xFFFFF80281BC5806)
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 Tue 20.11.2018 16:45:39 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!setjmpex+0x7499)
Bugcheck code: 0xA (0xFFFFF80280B0E070, 0x2, 0x0, 0xFFFFF80281BC5806)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Tue 20.11.2018 16:35:24 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112018-6343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A9690)
Bugcheck code: 0x3B (0xC0000047, 0xFFFFF80105483758, 0xFFFFBE8E8963D930, 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 Tue 20.11.2018 16:11:23 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112018-20171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A9690)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800C0178270, 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.

Reakce na odpověď

1 Zadajte svou přezdívku:
2 Napište svou odpověď:
3 Pokud chcete dostat ban, zadejte libovolný text:

Zpět do poradny