From TA, 6 Months ago, written in Text.
Embed
  1. System Information (local)
  2. Computer name: DESKTOP-7D6OM2T
  3. Windows version: Windows 10 , 10.0, build: 16299
  4. Windows dir: C:\WINDOWS
  5. Hardware: Z170N-Gaming 5, Gigabyte Technology Co., Ltd.
  6. CPU: GenuineIntel Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz Intel586, level: 6
  7. 8 logical processors, active mask: 255
  8. RAM: 17126187008 bytes total
  9.  
  10.  
  11.  
  12. Crash Dump Analysis
  13. Crash dump directory: C:\WINDOWS\Minidump
  14.  
  15. Crash dumps are enabled on your computer.
  16.  
  17. On Fri 1/26/2018 12:18:39 PM your computer crashed
  18. crash dump file: C:\WINDOWS\Minidump\012618-8187-01.dmp
  19. This was probably caused by the following module: ntoskrnl.exe (nt+0x1756E0)
  20. Bugcheck code: 0x50 (0xFFFFB8071911C1D0, 0x0, 0xFFFFF800B29222CE, 0x2)
  21. Error: PAGE_FAULT_IN_NONPAGED_AREA
  22. file path: C:\WINDOWS\system32\ntoskrnl.exe
  23. product: Microsoft® Windows® Operating System
  24. company: Microsoft Corporation
  25. description: NT Kernel & System
  26. Bug check description: This indicates that invalid system memory has been referenced.
  27. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  28. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  29.  
  30.  
  31.  
  32. On Fri 1/26/2018 12:18:39 PM your computer crashed
  33. crash dump file: C:\WINDOWS\memory.dmp
  34. This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
  35. Bugcheck code: 0x50 (0xFFFFB8071911C1D0, 0x0, 0xFFFFF800B29222CE, 0x2)
  36. Error: PAGE_FAULT_IN_NONPAGED_AREA
  37. Bug check description: This indicates that invalid system memory has been referenced.
  38. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  39. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  40.  
  41.  
  42.  
  43.  
  44. Conclusion
  45. 2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
  46.  
  47.  
  48. Read the topic general suggestions for troubleshooting system crashes for more information.
  49.  
  50. 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.
  51.  
  52.