Windows 8.1 Mavi Ekran Hatası

--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-HH6FM2D
Windows version: Windows 10 , 10.0, build: 17083
Windows dir: C:\WINDOWS
Hardware: MS-7A31, Micro-Star International Co., Ltd, X370 XPOWER GAMING TITANIUM (MS-7A31)
CPU: AuthenticAMD AMD Ryzen 7 1800X Eight-Core Processor AMD586, level: 23
16 logical processors, active mask: 65535
RAM: 17123778560 bytes total




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

Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Fri 26.01.2018 01:29:45 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012618-13671-01.dmp
uptime: 00:02:24
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x7F (0x8, 0xFFFFF80008B96E70, 0xFBFFF80008B85B50, 0xFFFFF80006DC8060)
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.



On Fri 26.01.2018 01:26:54 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012618-13125-01.dmp
uptime: 01:44:04
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8003F015552, 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 Thu 25.01.2018 23:42:25 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012518-12703-02.dmp
uptime: 01:23:56
This was probably caused by the following module: Unknown (0xFFFFD000217BECE0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8000176CDDD, 0xFFFFD000217BF4D8, 0xFFFFD000217BECE0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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.
A third party driver was identified as the probable root cause of this system error.
Google query: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Thu 25.01.2018 22:18:03 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012518-13015-01.dmp
uptime: 00:07:17
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF96000232E09, 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 Thu 25.01.2018 22:10:20 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012518-12515-01.dmp
uptime: 01:32:46
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960001BAD14, 0xFFFFD00022852BB0, 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 25.01.2018 20:37:08 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012518-12218-01.dmp
uptime: 00:33:36
This was probably caused by the following module: hal.dll (hal+0x1DD3C)
Bugcheck code: 0x5C (0x201, 0xFFFFFFFFFFD01520, 0xFFFFFFFFC000000D, 0x1)
Error: HAL_INITIALIZATION_FAILED
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check appears very infrequently.
This is 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 25.01.2018 18:49:21 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012518-11765-01.dmp
uptime: 01:36:32
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0xA (0x1, 0xC, 0x1, 0xFFFFF803E11E44AB)
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 25.01.2018 17:12:23 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012518-11671-01.dmp
uptime: 00:16:25
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8020B023E18, 0xFFFFD00022B7BA00, 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 25.01.2018 16:55:31 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012518-12984-01.dmp
uptime: 00:00:46
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800012BD46F, 0xFFFFF800CD78C4A8, 0xFFFFF800CD78BCB0)
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 Thu 25.01.2018 16:46:29 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012518-12828-01.dmp
uptime: 00:01:41
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80237AFB10E, 0xFFFFD000243756F0, 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 25.01.2018 16:44:22 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012518-20000-01.dmp
uptime: 00:03:42
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x7F (0x8, 0xFFFFF80043F96E70, 0xFFFFD0002988BFE0, 0xFFFFF800420DCEBD)
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.



On Thu 25.01.2018 16:40:14 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012518-13281-01.dmp
uptime: 00:05:43
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x19 (0x24, 0x2, 0x1, 0xFFFFE00000F31F20)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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. This problem might also be caused because of overheating (thermal issue).
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 25.01.2018 16:32:35 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012518-13218-01.dmp
uptime: 00:15:14
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF8020AC89946, 0xFFFFD000238F6EA0, 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 25.01.2018 16:16:54 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012518-13812-01.dmp
uptime: 00:52:15
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1A (0x41287, 0x0, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred. An illegal page fault occurred while holding working set synchronization.
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. This problem might also be caused because of overheating (thermal issue).
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 25.01.2018 15:24:12 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012518-12500-01.dmp
uptime: 00:07:16
This was probably caused by the following module: ntoskrnl.exe (nt+0xA9317)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80327CC1317, 0xFFFFD000215C9198, 0xFFFFD000215C89A0)
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.



On Thu 25.01.2018 15:14:07 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012518-12687-01.dmp
uptime: 00:09:59
This was probably caused by the following module: usbxhci.sys (0xFFFFF800034BEC03)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800034BEC03, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
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 a storage driver or controller 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 Thu 25.01.2018 15:03:42 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012518-13625-01.dmp
uptime: 00:26:16
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8035C42B61E)
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 25.01.2018 14:36:56 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012518-15140-01.dmp
uptime: 00:51:50
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8009E6C3445, 0xFFFFD00022596980, 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 Wed 24.01.2018 23:34:37 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012518-14218-01.dmp
uptime: 02:48:24
This was probably caused by the following module: ntoskrnl.exe (nt+0xA1A4A)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800D36A4A4A, 0xFFFFD00027D60568, 0xFFFFD00027D5FD70)
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.



On Wed 24.01.2018 20:45:48 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012418-14953-01.dmp
uptime: 00:10:59
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0xC5 (0x771, 0x2, 0x0, 0xFFFFF800EB29D676)
Error: DRIVER_CORRUPTED_EXPOOL
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 the system attempted to access invalid memory at a process IRQL that was too high.
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 24.01.2018 20:34:22 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012418-15921-01.dmp
uptime: 04:36:13
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800C8E45BB0, 0xFFFFD00022B3A2E0, 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 Wed 24.01.2018 15:57:38 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012418-15953-01.dmp
uptime: 16:34:07
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8018B2BEF2E, 0xFFFFD000287BFB70, 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 23.01.2018 23:23:05 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012318-13265-01.dmp
uptime: 01:40:33
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x50 (0xFFFFD000237BD9B0, 0x0, 0xFFFFF80119BC3201, 0x1)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 23.01.2018 21:42:06 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012318-15843-01.dmp
uptime: 00:15:58
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF80002536C3C)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002536C3C, 0xFFFFD000275773D8, 0xFFFFD00027576BE0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 390.65
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 390.65
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 390.65 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Tue 23.01.2018 21:25:43 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012318-14109-01.dmp
uptime: 00:01:34
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80158EB1E9C, 0xFFFFD00020BA2600, 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 23.01.2018 21:23:44 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012318-25546-01.dmp
uptime: 01:16:14
This was probably caused by the following module: ntfs.sys (Ntfs+0xC360E)
Bugcheck code: 0x24 (0xAD0007108E, 0xF0, 0x0, 0x0)
Error: NTFS_FILE_SYSTEM
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® İşletim Sistemi
company: Microsoft Corporation
description: NT Dosya Sistemi Sürücüsü
Bug check description: This indicates a problem occurred in the NTFS file system.
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 Tue 23.01.2018 20:05:44 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012318-21703-01.dmp
uptime: 00:03:53
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x50 (0xFFFFF6FB40000000, 0x0, 0x0, 0x6)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 23.01.2018 19:52:54 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012318-26062-01.dmp
uptime: 02:00:41
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF80000366964, 0xFFFFD0002AFC5FC8, 0xFFFFD0002AFC57D0)
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 Tue 23.01.2018 17:51:48 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012318-17468-01.dmp
uptime: 00:13:34
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802DBACCB3C, 0xFFFFD00025190780, 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 23.01.2018 17:28:44 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012318-9937-01.dmp
uptime: 00:30:36
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF960000B8046, 0xFFFFD00027DBCE00, 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 23.01.2018 16:57:42 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012318-13859-01.dmp
uptime: 00:50:48
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x199256)
Bugcheck code: 0xF7 (0xD81ED8CC27E1A444, 0x6ED172B6DDA7, 0xFFFF912E8D492258, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 390.65
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 390.65
Bug check description: This indicates that a driver has overrun a stack-based buffer.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 390.65 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation DRIVER_OVERRAN_STACK_BUFFER



On Tue 23.01.2018 16:06:28 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012318-12140-01.dmp
uptime: 00:50:41
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF803B0DC8929, 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 Tue 23.01.2018 15:15:18 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012318-12953-01.dmp
uptime: 16:02:37
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600020F477, 0xFFFFD000245DDF60, 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 Mon 22.01.2018 23:12:16 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012218-12656-01.dmp
uptime: 01:39:05
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800512C0002, 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 Mon 22.01.2018 21:32:44 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012218-12375-01.dmp
uptime: 00:22:50
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0xA (0xFFFFF80353C00038, 0xC, 0x1, 0xFFFFF8034F8C4F86)
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 Mon 22.01.2018 21:09:29 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012218-13203-01.dmp
uptime: 00:58:32
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x4E (0x7, 0x11D66C, 0x1100011D38B, 0x0)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
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 Mon 22.01.2018 20:09:40 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012218-12531-01.dmp
uptime: 01:16:44
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80001EE0A30, 0x0, 0x400049D0)
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 Mon 22.01.2018 18:45:20 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012218-14250-01.dmp
uptime: 00:04:50
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960002DDB80, 0xFFFFD00024086BC0, 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 Mon 22.01.2018 18:31:51 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012218-18296-01.dmp
uptime: 00:08:13
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0xD1 (0xFFFFFFFFDB9F48C5, 0x2, 0x0, 0xFFFFF802BAC149FC)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Mon 22.01.2018 18:23:12 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012218-20500-01.dmp
uptime: 01:58:17
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80283E580BF, 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 Mon 22.01.2018 16:24:30 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012218-11140-02.dmp
uptime: 00:02:46
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960003C4BBF, 0xFFFFD00022F58DB0, 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 Mon 22.01.2018 16:21:19 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012218-11281-01.dmp
uptime: 00:01:41
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8003B85BCBC, 0x0, 0x5408)
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 Mon 22.01.2018 16:19:12 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012218-10828-01.dmp
uptime: 00:09:19
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802D16B6AD2, 0xFFFFD000271BDD60, 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 Mon 22.01.2018 16:09:23 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012218-11093-01.dmp
uptime: 02:43:37
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600023004C, 0xFFFFD00024A5FB80, 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 Mon 22.01.2018 13:14:29 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012218-12515-01.dmp
uptime: 00:13:28
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80313D9915F, 0xFFFFD000223D2DA0, 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 Mon 22.01.2018 13:00:35 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012218-11140-01.dmp
uptime: 01:24:54
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF8000266DE10)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF8B, 0x1, 0xFFFFF8000266DE10, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 390.65
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 390.65
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 390.65 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA



On Sun 21.01.2018 21:12:24 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012118-11687-01.dmp
uptime: 00:16:06
This was probably caused by the following module: ntoskrnl.exe (nt+0x1500A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80001505318, 0xFFFFD0002151DC18, 0xFFFFD0002151D420)
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 Sun 21.01.2018 20:55:54 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012118-16125-01.dmp
uptime: 00:33:26
This was probably caused by the following module: hal.dll (0xFFFFF802C18470BC)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF802C18470BC, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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.



The following dump files were found but could not be read. These files may be corrupt:
C:\WINDOWS\Minidump\012218-16265-01.dmp
C:\WINDOWS\Minidump\012518-12484-01.dmp




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

50 crash dumps have been found and analyzed. Only 48 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 390.65 , NVIDIA Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.