Detta är vad jag fick ut efter att ha kört WhoCrashed. Följde sedan denna video för att "lösa problemet". https://www.youtube.com/watch?v=K9xyjPM_bCQ (Vet ej vad detta gör och om det är en bra idé.... )
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 2017-03-19 10:21:42 your computer crashed
crash dump file: C:\Windows\Minidump\031917-3343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF803CD6B192D, 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 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 Sun 2017-03-19 10:21:42 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF803CD6B192D, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program 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 Sat 2017-03-18 15:19:35 your computer crashed
crash dump file: C:\Windows\Minidump\031817-3343-01.dmp
This was probably caused by the following module: fltmgr.sys (FLTMGR+0x44D4)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8081F8644D4, 0xFFFFBA8081646B70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Operativsystemet Microsoft® Windows®
company: Microsoft Corporation
description: Filterhanteraren för Microsofts filsystem
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 2017-03-01 19:13:54 your computer crashed
crash dump file: C:\Windows\Minidump\030117-3953-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF80606A83A9F)
Bugcheck code: 0xD1 (0x1A42504, 0xFF, 0x0, 0xFFFFF80606A83A9F)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Operativsystemet Microsoft® Windows®
company: Microsoft Corporation
description: Network Driver Interface Specification (NDIS)
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sat 2017-02-11 10:33:45 your computer crashed
crash dump file: C:\Windows\Minidump\021117-3234-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1F2B)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80890471F2B, 0xFFFFA4009D718E58, 0xFFFFA4009D718680)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_0cc477a6fec64d8c\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 378.66
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 378.66
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 378.66 , NVIDIA Corporation).
Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
12 crash dumps have been found and analyzed. Only 5 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 378.66 , 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.
