whocrashed e posta la lettura completa
Ecco il report completo, le bosd del 22 sono di diablo 3 le altre quasi tutte di gothic 3.
System Information (local)
computer name: MARCO-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8526315520 total
VM: 2147352576, free: 1914540032
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 22/09/2013 16:46:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092213-5101-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x23EB0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88007623EB0, 0xFFFFF880093D8548, 0xFFFFF880093D7DA0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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 Sun 22/09/2013 16:46:36 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1!VidMmInterface+0x125F0)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF88007623EB0, 0xFFFFF880093D8548, 0xFFFFF880093D7DA0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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 Sun 22/09/2013 12:38:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092213-4648-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C78045, 0xFFFFF8800C6F86B0, 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 Fri 20/09/2013 11:26:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092013-8252-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20EC8)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88006C21EC8, 0xFFFFF88002549568, 0xFFFFF88002548DC0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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 18/09/2013 17:26:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091813-5038-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002DBF44D, 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 Wed 18/09/2013 12:44:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091813-4570-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x21120)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88006F68120, 0xFFFFF88002549558, 0xFFFFF88002548DB0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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 18/09/2013 11:28:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091813-4430-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x10E (0x1F, 0xFFFFF8A009DFF530, 0x0, 0x90DF)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.
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 18/09/2013 11:21:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091813-4492-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7BE52)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002CD6E52, 0xFFFFF88002549818, 0xFFFFF88002549070)
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 18/09/2013 09:22:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091813-4664-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x20D7A4)
Bugcheck code: 0x50 (0xFFFFFCA001DA51B0, 0x1, 0xFFFFF88006C31FC0, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 327.23
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 327.23
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 327.23 , NVIDIA Corporation).
Google query: NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA
On Mon 16/09/2013 11:26:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091613-4524-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x23EB0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88006D51EB0, 0xFFFFF88002549548, 0xFFFFF88002548DA0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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 Fri 13/09/2013 13:10:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091313-5272-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x7B2F)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88001238B2F, 0xFFFFF8800334D838, 0xFFFFF8800334D090)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver file system NT
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 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 Thu 12/09/2013 13:13:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091213-4602-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F7DFCE, 0xFFFFF8800279B020, 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 Sun 08/09/2013 13:05:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090913-5194-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800B873068, 0xFFFFF8800B8728C0, 0xFFFFF880012A56DE)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver file system NT
Bug check description: This indicates a problem occurred in the NTFS file system.
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.
Conclusion
13 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 327.23 , NVIDIA Corporation)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from 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 actually 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.
- - - Updated - - -
Sembra che sia riuscito a risolvere il problema.
Ho flashato il BIOS con la versione 0706 uscita il 2 settembre sul sito di Asus per la mia mobo Z87-K.
Ho giocato circa tre ore a Diablo 3 senza incontrare nessun problema.
Speriamo che la soluzione sia definitiva!!
Grazie a tutti!!
