Salve ragazzi,
scrivo qui da voi poichè non so più cosa fare per questo problema di continue schermate blu con errori sempre diversi che mi si presentano periodicamente sul mio nuovo pc assemblato da circa 1 settimana.
Configurazione pc:
- cpu intel i5 6600k 3.5 ghz no fan
- dissipatore arctic freeze 13
- mobo asrock z170 pro4
- ram corsaire vengeance 8gb (2x4) ddr4 2300 mhz
- gpu ATI gigabyte r9 390 8gb
- alimentatore xfx 750w non modulare (certificazione 80+ gold)
- case corsair spec 3
fino ad ora ho giocato a League of Legends e Hearos of the Stom su questo pc e queste schermate blu con conseguente arresto improvviso del pc le ho sl su Heros of the Storm. Ho avviato lo strumento di risoluzione problemi di windows tramite software e tramite terminale, ho avviato programmi per diagnosi e risoluzione problemi come MemTest86, Pc Heath Advisor ecc ma nulla, ho aggiornato tutti i driver possibile per tutti i componenti e niente :cav: ... a questo punto credo sia un problema di qualche componente hardware oppure il problema si windows 10 che è incompatibile che qualche componente hardware del mio pc... vi incollo tutto il rapporto di whocrashed che riporta tutti gli errori che ho avuto. Pls help me guys!!! :look:
Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 25/04/2016 09:40:12 your computer crashed
This was likely caused by the following module: fltmgr.sys
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8018172F089, 0xFFFFD00161DF2718, 0xFFFFD00161DF1F30)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\042516-11265-01.dmp
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Gestione filtri file system Microsoft
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 24/04/2016 20:21:55 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41201, 0xFFFFF68000176A08, 0xFB200001BB482847, 0xFFFFE00158710D50)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\042416-10437-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 24/04/2016 16:21:16 your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0x7A8, 0x2538116EFC0, 0xFFFFD001F1FD5000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
Dump file: C:\Windows\Minidump\042416-10843-01.dmp
On Sun 24/04/2016 13:46:49 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41201, 0xFFFFF680002DBEC0, 0x95500002137A5847, 0xFFFFE000AFF5EEC0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\042416-10000-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 24/04/2016 12:54:40 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41792, 0xFFFFF6800000BC38, 0x100000000000000, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\042416-11203-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 24/04/2016 09:47:08 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41201, 0xFFFFF680000FA9C8, 0xB9D00001DFF80847, 0xFFFFE001108FF7C0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\042416-12765-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sat 23/04/2016 20:26:57 your computer crashed
This was likely caused by the following module: dxgkrnl.sys
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801DF843044, 0xFFFFD0019CC4C940, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\042316-10968-01.dmp
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sat 23/04/2016 18:56:58 your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0xE70, 0x20C07D48940, 0xFFFFD0002441A000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
Dump file: C:\Windows\Minidump\042316-14546-01.dmp
On Sat 23/04/2016 16:28:24 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xFFFFD00020000020, 0x2, 0x0, 0xFFFFF8010FD242C5)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\042316-10281-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sat 23/04/2016 11:54:34 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41792, 0xFFFFF6BFFFD97D48, 0x400000000000000, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\042316-11015-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sat 23/04/2016 09:14:39 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80146231AD6, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\042316-11562-01.dmp
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver file system NT
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
11 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really 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.
scrivo qui da voi poichè non so più cosa fare per questo problema di continue schermate blu con errori sempre diversi che mi si presentano periodicamente sul mio nuovo pc assemblato da circa 1 settimana.
Configurazione pc:
- cpu intel i5 6600k 3.5 ghz no fan
- dissipatore arctic freeze 13
- mobo asrock z170 pro4
- ram corsaire vengeance 8gb (2x4) ddr4 2300 mhz
- gpu ATI gigabyte r9 390 8gb
- alimentatore xfx 750w non modulare (certificazione 80+ gold)
- case corsair spec 3
fino ad ora ho giocato a League of Legends e Hearos of the Stom su questo pc e queste schermate blu con conseguente arresto improvviso del pc le ho sl su Heros of the Storm. Ho avviato lo strumento di risoluzione problemi di windows tramite software e tramite terminale, ho avviato programmi per diagnosi e risoluzione problemi come MemTest86, Pc Heath Advisor ecc ma nulla, ho aggiornato tutti i driver possibile per tutti i componenti e niente :cav: ... a questo punto credo sia un problema di qualche componente hardware oppure il problema si windows 10 che è incompatibile che qualche componente hardware del mio pc... vi incollo tutto il rapporto di whocrashed che riporta tutti gli errori che ho avuto. Pls help me guys!!! :look:
Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 25/04/2016 09:40:12 your computer crashed
This was likely caused by the following module: fltmgr.sys
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8018172F089, 0xFFFFD00161DF2718, 0xFFFFD00161DF1F30)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\042516-11265-01.dmp
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Gestione filtri file system Microsoft
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 24/04/2016 20:21:55 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41201, 0xFFFFF68000176A08, 0xFB200001BB482847, 0xFFFFE00158710D50)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\042416-10437-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 24/04/2016 16:21:16 your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0x7A8, 0x2538116EFC0, 0xFFFFD001F1FD5000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
Dump file: C:\Windows\Minidump\042416-10843-01.dmp
On Sun 24/04/2016 13:46:49 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41201, 0xFFFFF680002DBEC0, 0x95500002137A5847, 0xFFFFE000AFF5EEC0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\042416-10000-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 24/04/2016 12:54:40 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41792, 0xFFFFF6800000BC38, 0x100000000000000, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\042416-11203-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 24/04/2016 09:47:08 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41201, 0xFFFFF680000FA9C8, 0xB9D00001DFF80847, 0xFFFFE001108FF7C0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\042416-12765-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sat 23/04/2016 20:26:57 your computer crashed
This was likely caused by the following module: dxgkrnl.sys
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801DF843044, 0xFFFFD0019CC4C940, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\042316-10968-01.dmp
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sat 23/04/2016 18:56:58 your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0xE70, 0x20C07D48940, 0xFFFFD0002441A000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
Dump file: C:\Windows\Minidump\042316-14546-01.dmp
On Sat 23/04/2016 16:28:24 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xFFFFD00020000020, 0x2, 0x0, 0xFFFFF8010FD242C5)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\042316-10281-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sat 23/04/2016 11:54:34 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41792, 0xFFFFF6BFFFD97D48, 0x400000000000000, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\042316-11015-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sat 23/04/2016 09:14:39 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80146231AD6, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\042316-11562-01.dmp
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver file system NT
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
11 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really 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.
