di valyfilm » 02/01/17 11:31
Ciao Davide. Non c'è un pulsante "report" quindi basta cliccare su analize. L'ho fatto e sembra che il problema sia causato da un bug. Mi domando come mai dopo anni si è fatto vivo solo adesso.
System Information (local)
--------------------------------------------------------------------------------
Computer name: PC
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\WINDOWS
Hardware: Aspire MC605, Acer
CPU: GenuineIntel Intel(R) Core(TM) i5-3350P CPU @ 3.10GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8533438464 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Mon 02/01/2017 10.56.28 your computer crashed
crash dump file: C:\WINDOWS\Minidump\010217-22734-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x3E15B0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8011C2B15B0, 0xFFFFBC804BA85378, 0xFFFFBC804BA84BA0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nvaewu.inf_amd64_8cbfa7509ac4e6cb\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 369.09
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 369.09
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 369.09 , NVIDIA Corporation).
Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Mon 02/01/2017 00.44.01 your computer crashed
crash dump file: C:\WINDOWS\Minidump\010217-21828-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x3E15B0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF804F2C815B0, 0xFFFFB9018D1AA378, 0xFFFFB9018D1A9BA0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nvaewu.inf_amd64_8cbfa7509ac4e6cb\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 369.09
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 369.09
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 369.09 , NVIDIA Corporation).
Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Sun 01/01/2017 21.28.11 your computer crashed
crash dump file: C:\WINDOWS\Minidump\010117-24500-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x3E15B0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80F391515B0, 0xFFFF8F01B4D2D2B8, 0xFFFF8F01B4D2CAE0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nvaewu.inf_amd64_8cbfa7509ac4e6cb\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 369.09
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 369.09
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 369.09 , NVIDIA Corporation).
Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Sat 31/12/2016 21.49.08 your computer crashed
crash dump file: C:\WINDOWS\Minidump\123116-22703-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x3E15B0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80AD16315B0, 0xFFFFA9011CFC57F8, 0xFFFFA9011CFC5020)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nvaewu.inf_amd64_8cbfa7509ac4e6cb\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 369.09
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 369.09
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 369.09 , NVIDIA Corporation).
Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
4 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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 369.09 , 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.
