BSOD W7/W10

[Verwijderd]

Zoals de titel doet vermoeden heb ik wat problemen met als gevolg een BSOD.

Onlangs heb ik weer eens een nieuwe pc gebouwd waarbij ik W10 heb geïnstalleerd.
Eigenlijk vanaf het begin heb ik storingen gehad waarbij memory management als error werd gegeven.
Later heb ik W7 geïnstalleerd om te kijken of het daarmee verholpen was. Dit bleek niet het geval.
Laatste drivers zijn geïnstalleerd. Ook heb ik oudere drivers van de videokaart gehad.
Memtest 1 ronde uitgevoerd en windows memory test uitgevoerd.


De storingen zijn heel willekeurig, maar soms meerdere keren per uur. Zo lang je niks doet gebeurt er ook niks(logisch). Maar vaak tijdens muziek luisteren of gaming duurt het niet lang voordat de pc er mee uit scheidt.
Bij dumpfiles word aangegeven dat het aan hall.dll ligt, dan weer ntoskrnl .
Ik zal vanavond de bestanden delen van "WhoCrashed".

Het systeem:
Windows 10 / 7
MSI Z170I gaming pro AC
MSI GTX960 gaming 2G
WD Green WD20NPVX - HDD
Intel Core i5-6600K / 3.5 GHz - 6 MB cache
Samsung 850 EVO - SSD

Corsair Vengeance LPX - DDR4 - 16 GB : 2 x 8 GB - DIMM 288-PIN - 2400 MHz
/ PC4-19200 - CL14 - 1.2 V - niet-gebufferd - niet-ECC

Corsair 550 RM550X

Ik ben erg benieuwd of er mensen zijn met hetzelfde probleem.
Ook zou ik graag willen weten of er iemand is die een idee heeft om dit probleem te verhelpen.

Bedankt.

[Verwijderd]

Hierbij de uitdraai van Windows 7:

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 24-1-2016 9:42:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012416-5756-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC80)
Bugcheck code: 0x1A (0x41284, 0x12001, 0x0, 0xFFFFF70001080000)
Error: MEMORY_MANAGEMENT
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 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.


On Sun 24-1-2016 9:42:56 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalSendSoftwareInterrupt+0x47)
Bugcheck code: 0x1A (0x41284, 0x12001, 0x0, 0xFFFFF70001080000)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 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.

[Verwijderd]

Hierbij de uitdraai van Windows 10:

System Information (local)
--------------------------------------------------------------------------------

Computer name: W1064PRO1511
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\Windows
Hardware: MS-7980, MSI, Z170I GAMING PRO AC (MS-7980)
CPU: GenuineIntel Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17133355008 bytes total


--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 23-1-2016 20:46:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012316-4953-01.dmp
This was probably caused by the following module: win32kfull.sys (win32kfull!DestroyWindowsHotKeys+0x59)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF961736E9B99, 0xFFFFD0017574EE10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.


On Sat 23-1-2016 20:46:09 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32kfull.sys (win32kfull!DestroyWindowsHotKeys+0x59)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF961736E9B99, 0xFFFFD0017574EE10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.


On Fri 22-1-2016 21:50:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012216-4734-01.dmp
This was probably caused by the following module: hal.dll (hal!HalpTimerClockIpiRoutine+0x15)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a 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.


On Fri 22-1-2016 19:29:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012216-4500-01.dmp
This was probably caused by the following module: dxgmms2.sys (dxgmms2!VIDMM_RECYCLE_RANGE::DebouncedDecommit+0x5F)
Bugcheck code: 0x1A (0x41284, 0xB3A10000, 0x0, 0xFFFFF58010804000)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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 20-1-2016 17:17:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012016-4468-01.dmp
This was probably caused by the following module: dxgmms2.sys (dxgmms2!VIDMM_MDL_RANGE::Lock+0x60)
Bugcheck code: 0x1A (0x5003, 0xFFFFF58010804000, 0x64CBD, 0x64E0100C99FA)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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 Sat 16-1-2016 17:55:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011616-5281-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!operator delete+0x11)
Bugcheck code: 0x19 (0x20, 0xFFFFC0013D9DD130, 0xFFFFC0013D9DD1B0, 0x5080204)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.
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 15-1-2016 19:26:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011516-4562-01.dmp
This was probably caused by the following module: win32kfull.sys (win32kfull!DwmAsyncZorderSprite+0x72)
Bugcheck code: 0x19 (0x3, 0xFFFFC000DE151180, 0xFFFFC000DE151180, 0x80FFFFC000DE1511)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
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.
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 Sat 9-1-2016 14:51:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010916-4078-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41201, 0xFFFFF68000A4C198, 0xC1, 0xFFFFE00106D122A0)
Error: MEMORY_MANAGEMENT
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.


On Sat 9-1-2016 12:45:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010916-3953-01.dmp
This was probably caused by the following module: netio.sys (NETIO!RtlGetNextExpiredTimerWheelEntry+0xFA)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801CA012B9A, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 a standard Microsoft module. Your system configuration

[Verwijderd]

Niemand die mij kan helpen?

[br00ky]

Schopje naar WOS.

[Thralas]

Je zou Driver Verifier kunnen proberen te enablen.

Er bestaat wel de kans dat je er andere (brakke) drivers mee opspoort.

Verder iets van AV of tuningsoftware geinstalleerd? Gooi het eraf en kijk of het helpt.

[Shaggy_NL]

Houd er rekening mee dat, ook al hij aan geeft dat het waarschijnlijk niet aan hardware falen ligt, het toch altijd je geheugen zou kunnen zijn.

Misschien een idee om MemTest aan te zetten voor een dag?

[Verwijderd]

Memtest is inderdaad een goede manier om e.e.a. uit te sluiten. Deze heb ik eerder al uitgevoerd, maar niet een dag lang.

Driver verifiër kan ik nog proberen, maar ik heb i.i.g. W10 clean geïnstalleerd om vage softwareproblemen te voorkomen, zoals met AV bijvoorbeeld het geval kan zijn.
Tuningssoftware is dus ook nog niet geïnstalleerd (ook niet MSI zelf)

Ik zal dus eens driververifiër en Memtest hun werk laten doen.
Mocht dit iets opleveren, dan plaats ik dat zsm.