M
MortenSurén
My computer:
Motherboard: Asus Rog Strix z270f gaming
CPU: Intel core i5 7600k kaby lake
GPU: Asus geforce gtx 1070 rog strix gaming
RAM: Corsair vengance lpx ddr4 3000mhz
Crashdumps:
On Thu 1/17/2019 16:41:21 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\011719-5609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8041930D440)
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 1/17/2019 16:41:21 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+0x7EA9)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8041930D440)
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 Thu 1/17/2019 16:02:44 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\011719-5671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
Bugcheck code: 0x7F (0x8, 0xFFFFF8011C016E50, 0xFFFFDC0E47CB6A10, 0xFFFFF80119267E64)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also 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...
Motherboard: Asus Rog Strix z270f gaming
CPU: Intel core i5 7600k kaby lake
GPU: Asus geforce gtx 1070 rog strix gaming
RAM: Corsair vengance lpx ddr4 3000mhz
Crashdumps:
On Thu 1/17/2019 16:41:21 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\011719-5609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8041930D440)
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 1/17/2019 16:41:21 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+0x7EA9)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8041930D440)
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 Thu 1/17/2019 16:02:44 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\011719-5671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
Bugcheck code: 0x7F (0x8, 0xFFFFF8011C016E50, 0xFFFFDC0E47CB6A10, 0xFFFFF80119267E64)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also 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...