Nicola Giovannoni
Nuovo Utente
- Messaggi
- 5
- Reazioni
- 2
- Punteggio
- 24
Salve,come da titolo da circa un paio di settimane ho bsods frequenti e molto fastidiosi.
Si presentano sempre piu spesso quando apro un gioco,se il pc è fermo o se apro solo chrome et simila non crasha.
Ho scaricato whocrashed e questo è quello che è venuto fuori
[FONT=Segoe UI, Arial]System Information (local)
[/FONT]
[FONT=Segoe UI, Arial]Computer name: DESKTOP-A96488J
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\Windows
Hardware: ASRock, H170 Pro4
CPU: GenuineIntel Intel(R) Core(TM) i5-6600 CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8518025216 bytes total
[/FONT]
[FONT=Segoe UI, Arial]
Crash Dump Analysis
[/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]
[FONT=Segoe UI, Arial][/FONT]
[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Tue 12/07/2016 14:20:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071216-12453-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x5012, 0xFFFFF58010804000, 0x2394D, 0x2A7CE)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
[/FONT]
[FONT=Segoe UI, Arial]On Tue 12/07/2016 14:20:36 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x5012, 0xFFFFF58010804000, 0x2394D, 0x2A7CE)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
[/FONT]
[FONT=Segoe UI, Arial]On Mon 11/07/2016 22:55:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071216-9281-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgkrnl.sys[/FONT] (dxgkrnl!DXGDEVICE::DestroyAllocations+0x54B)
Bugcheck code: 0x19 (0x25, 0x21, 0x5, 0xFFFFC0006E6F84C0)
Error: [FONT=Segoe UI, Arial]BAD_POOL_HEADER[/FONT]
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics Kernel
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
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.
[/FONT]
[FONT=Segoe UI, Arial]On Mon 11/07/2016 17:29:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071116-13265-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]win32kfull.sys[/FONT] (win32kfull!DwmSyncGetCompositionAttribute+0xD2)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF9605D53D96E, 0xFFFFD00023474F80, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
file path: C:\Windows\system32\win32kfull.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Full/Desktop Win32k Kernel Driver
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 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.
[/FONT]
[FONT=Segoe UI, Arial]On Mon 11/07/2016 17:17:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071116-12500-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFF59010860F5C, 0x2, 0x1, 0xFFFFF80166AB3200)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.
[/FONT]
[FONT=Segoe UI, Arial]On Mon 11/07/2016 17:01:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071116-13875-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41201, 0xFFFFF6800039BF68, 0xA5D001001E35D867, 0xFFFFE001241B7A50)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
[/FONT]
[FONT=Segoe UI, Arial]On Mon 11/07/2016 16:34:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071116-14328-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFF58050808EC8, 0x2, 0x0, 0xFFFFF803AAC93DB0)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.
[/FONT]
[FONT=Segoe UI, Arial]On Mon 11/07/2016 14:54:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071116-11546-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFE00030B11224, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
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.
[/FONT]
[FONT=Segoe UI, Arial]On Mon 11/07/2016 14:14:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071116-14640-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x4E (0x99, 0x141DD3, 0x2, 0x800014000141DD4)
Error: [FONT=Segoe UI, Arial]PFN_LIST_CORRUPT[/FONT]
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
[/FONT]
[FONT=Segoe UI, Arial]On Mon 11/07/2016 12:35:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071116-12015-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntfs.sys[/FONT] (NTFS!NtfsCopyReadA+0x217)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF803A527AF5E)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\ntfs.sys
product: [FONT=Segoe UI, Arial]Sistema operativo Microsoft® Windows®[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Driver file system NT
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.
Ho provato a far girare il pc con una ram alla volta,il problema si presenta lo stesso con entrambe le ram,che siano fallate entrambe?
[/FONT]
Si presentano sempre piu spesso quando apro un gioco,se il pc è fermo o se apro solo chrome et simila non crasha.
Ho scaricato whocrashed e questo è quello che è venuto fuori
[FONT=Segoe UI, Arial]System Information (local)
[/FONT]
[FONT=Segoe UI, Arial]Computer name: DESKTOP-A96488J
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\Windows
Hardware: ASRock, H170 Pro4
CPU: GenuineIntel Intel(R) Core(TM) i5-6600 CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8518025216 bytes total
[/FONT]
[FONT=Segoe UI, Arial]
Crash Dump Analysis
[/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]
[FONT=Segoe UI, Arial][/FONT]
[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Tue 12/07/2016 14:20:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071216-12453-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x5012, 0xFFFFF58010804000, 0x2394D, 0x2A7CE)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
[/FONT]
[FONT=Segoe UI, Arial]On Tue 12/07/2016 14:20:36 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x5012, 0xFFFFF58010804000, 0x2394D, 0x2A7CE)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
[/FONT]
[FONT=Segoe UI, Arial]On Mon 11/07/2016 22:55:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071216-9281-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgkrnl.sys[/FONT] (dxgkrnl!DXGDEVICE::DestroyAllocations+0x54B)
Bugcheck code: 0x19 (0x25, 0x21, 0x5, 0xFFFFC0006E6F84C0)
Error: [FONT=Segoe UI, Arial]BAD_POOL_HEADER[/FONT]
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics Kernel
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
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.
[/FONT]
[FONT=Segoe UI, Arial]On Mon 11/07/2016 17:29:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071116-13265-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]win32kfull.sys[/FONT] (win32kfull!DwmSyncGetCompositionAttribute+0xD2)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF9605D53D96E, 0xFFFFD00023474F80, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
file path: C:\Windows\system32\win32kfull.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Full/Desktop Win32k Kernel Driver
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 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.
[/FONT]
[FONT=Segoe UI, Arial]On Mon 11/07/2016 17:17:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071116-12500-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFF59010860F5C, 0x2, 0x1, 0xFFFFF80166AB3200)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.
[/FONT]
[FONT=Segoe UI, Arial]On Mon 11/07/2016 17:01:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071116-13875-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41201, 0xFFFFF6800039BF68, 0xA5D001001E35D867, 0xFFFFE001241B7A50)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
[/FONT]
[FONT=Segoe UI, Arial]On Mon 11/07/2016 16:34:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071116-14328-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFF58050808EC8, 0x2, 0x0, 0xFFFFF803AAC93DB0)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.
[/FONT]
[FONT=Segoe UI, Arial]On Mon 11/07/2016 14:54:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071116-11546-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFE00030B11224, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
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.
[/FONT]
[FONT=Segoe UI, Arial]On Mon 11/07/2016 14:14:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071116-14640-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x4E (0x99, 0x141DD3, 0x2, 0x800014000141DD4)
Error: [FONT=Segoe UI, Arial]PFN_LIST_CORRUPT[/FONT]
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
[/FONT]
[FONT=Segoe UI, Arial]On Mon 11/07/2016 12:35:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071116-12015-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntfs.sys[/FONT] (NTFS!NtfsCopyReadA+0x217)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF803A527AF5E)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\ntfs.sys
product: [FONT=Segoe UI, Arial]Sistema operativo Microsoft® Windows®[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Driver file system NT
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.
Ho provato a far girare il pc con una ram alla volta,il problema si presenta lo stesso con entrambe le ram,che siano fallate entrambe?
[/FONT]
