Advertisement
Guest User

Untitled

a guest
Oct 30th, 2020
28
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 7.98 KB | None | 0 0
  1. System Information (local)
  2. --------------------------------------------------------------------------------
  3.  
  4. Computer name: DESKTOP-DTK64LT
  5. Windows version: Windows 10 , 10.0, build: 19042
  6. Windows dir: C:\Windows
  7. Hardware: Z390 M GAMING, Gigabyte Technology Co., Ltd., Z390 M GAMING-CF
  8. CPU: GenuineIntel Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz Intel8664, level: 6
  9. 6 logical processors, active mask: 63
  10. RAM: 8519155712 bytes (7,9GB)
  11.  
  12.  
  13.  
  14.  
  15. --------------------------------------------------------------------------------
  16. Crash Dump Analysis
  17. --------------------------------------------------------------------------------
  18.  
  19. Crash dumps are enabled on your computer.
  20.  
  21. Crash dump directories:
  22. C:\Windows
  23. C:\Windows\Minidump
  24.  
  25. On Fri 30/10/2020 18:56:12 your computer crashed or a problem was reported
  26. crash dump file: C:\Windows\Minidump\103020-22093-01.dmp
  27. This was probably caused by the following module: nvlddmkm.sys (0xFFFFF804418FB153)
  28. Bugcheck code: 0x3B (0xC0000005, 0xFFFFF804418FB153, 0xFFFF800408FC8FF0, 0x0)
  29. Error: SYSTEM_SERVICE_EXCEPTION
  30. file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_983b03c2be43c272\nvlddmkm.sys
  31. product: NVIDIA Windows Kernel Mode Driver, Version 457.09
  32. company: NVIDIA Corporation
  33. description: NVIDIA Windows Kernel Mode Driver, Version 457.09
  34. Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
  35. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  36. 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 457.09 , NVIDIA Corporation).
  37. Google query: nvlddmkm.sys NVIDIA Corporation SYSTEM_SERVICE_EXCEPTION
  38.  
  39.  
  40.  
  41. On Fri 30/10/2020 18:56:12 your computer crashed or a problem was reported
  42. crash dump file: C:\Windows\MEMORY.DMP
  43. This was probably caused by the following module: nvlddmkm.sys (0xFFFFF804418FB153)
  44. Bugcheck code: 0x3B (0xC0000005, 0xFFFFF804418FB153, 0xFFFF800408FC8FF0, 0x0)
  45. Error: SYSTEM_SERVICE_EXCEPTION
  46. file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_983b03c2be43c272\nvlddmkm.sys
  47. product: NVIDIA Windows Kernel Mode Driver, Version 457.09
  48. company: NVIDIA Corporation
  49. description: NVIDIA Windows Kernel Mode Driver, Version 457.09
  50. Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
  51. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  52. 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 457.09 , NVIDIA Corporation).
  53. Google query: nvlddmkm.sys NVIDIA Corporation SYSTEM_SERVICE_EXCEPTION
  54.  
  55.  
  56.  
  57. On Fri 30/10/2020 14:14:30 your computer crashed or a problem was reported
  58. crash dump file: C:\Windows\Minidump\103020-9843-01.dmp
  59. This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
  60. Bugcheck code: 0xEF (0xFFFFE58F99371080, 0x0, 0x0, 0x0)
  61. Error: CRITICAL_PROCESS_DIED
  62. file path: C:\Windows\system32\ntoskrnl.exe
  63. product: Microsoft® Windows® Operating System
  64. company: Microsoft Corporation
  65. description: NT Kernel & System
  66. Bug check description: This indicates that a critical system process died.
  67. There is a possibility this problem was caused by a virus or other malware.
  68. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  69.  
  70.  
  71.  
  72. On Fri 30/10/2020 03:17:55 your computer crashed or a problem was reported
  73. crash dump file: C:\Windows\Minidump\103020-6546-01.dmp
  74. This was probably caused by the following module: win32kbase.sys (0xFFFFC2E33DC259BB)
  75. Bugcheck code: 0x3B (0xC0000005, 0xFFFFC2E33DC259BB, 0xFFFFEC0F3FD2EE70, 0x0)
  76. Error: SYSTEM_SERVICE_EXCEPTION
  77. file path: C:\Windows\system32\win32kbase.sys
  78. product: Sistema Operacional Microsoft® Windows®
  79. company: Microsoft Corporation
  80. description: Driver de Kernel de Win32k Base
  81. Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
  82. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  83. The crash took place in a 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.
  84.  
  85.  
  86.  
  87. On Fri 30/10/2020 00:16:33 your computer crashed or a problem was reported
  88. crash dump file: C:\Windows\Minidump\103020-6656-01.dmp
  89. This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
  90. Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80515851112, 0xFFFFE40EDBD3E3C0, 0x0)
  91. Error: SYSTEM_SERVICE_EXCEPTION
  92. file path: C:\Windows\system32\ntoskrnl.exe
  93. product: Microsoft® Windows® Operating System
  94. company: Microsoft Corporation
  95. description: NT Kernel & System
  96. Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
  97. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  98. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  99.  
  100.  
  101.  
  102. On Thu 29/10/2020 16:24:24 your computer crashed or a problem was reported
  103. crash dump file: C:\Windows\Minidump\102920-6718-01.dmp
  104. This was probably caused by the following module: ntoskrnl.exe (nt+0x5D3BD4)
  105. Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8050F5D3BD4, 0xFFFFF58B1BBF9F78, 0xFFFFF58B1BBF97B0)
  106. Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
  107. file path: C:\Windows\system32\ntoskrnl.exe
  108. product: Microsoft® Windows® Operating System
  109. company: Microsoft Corporation
  110. description: NT Kernel & System
  111. Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
  112. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  113. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  114.  
  115.  
  116.  
  117.  
  118.  
  119. --------------------------------------------------------------------------------
  120. Conclusion
  121. --------------------------------------------------------------------------------
  122.  
  123. 6 crash dumps have been found and analyzed. 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:
  124.  
  125. nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 457.09 , NVIDIA Corporation)
  126.  
  127. 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.
  128.  
  129.  
  130. Read the topic general suggestions for troubleshooting system crashes for more information.
  131.  
  132. 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.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement