Het blauwe scherm kwam steeds te snel om het met de normale modus van Windows te doen dus heb ik het maar via veiligheidsmodus met netwerktoegang gedaan. Weet niet of dit heek veel uit maakt. Het resultaat staat hier onder.
computer name: JESPER-HP
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: HP Pavilion g6 Notebook PC, Hewlett-Packard, 183E
CPU: GenuineIntel Intel(R) Core(TM) i7-3612QM CPU @ 2.10GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 4188385280 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 8-5-2015 20:05:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050815-29218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72A40)
Bugcheck code: 0x50 (0xFFFFFA800266D024, 0x1, 0xFFFFF80002E577F0, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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.
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 8-5-2015 20:05:48 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFFA800266D024, 0x1, 0xFFFFF80002E577F0, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.
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 8-5-2015 20:03:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050815-35225-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x5D144)
Bugcheck code: 0x116 (0xFFFFFA800B01D010, 0xFFFFF88001C07900, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
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 an attempt to reset the display driver and recover from a timeout failed.
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.
Google query: Microsoft Corporation VIDEO_TDR_ERROR
On Fri 8-5-2015 20:01:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050815-20997-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x5D144)
Bugcheck code: 0x116 (0xFFFFFA80045304E0, 0xFFFFF8800504A900, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
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 an attempt to reset the display driver and recover from a timeout failed.
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.
Google query: Microsoft Corporation VIDEO_TDR_ERROR
On Fri 8-5-2015 18:10:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050815-21933-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x5D144)
Bugcheck code: 0x116 (0xFFFFFA80045804E0, 0xFFFFF88004EE3900, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
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 an attempt to reset the display driver and recover from a timeout failed.
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.
Google query: Microsoft Corporation VIDEO_TDR_ERROR
On Thu 23-4-2015 19:38:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042915-25771-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x5D144)
Bugcheck code: 0x116 (0xFFFFFA80051D9010, 0xFFFFF88003136900, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
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 an attempt to reset the display driver and recover from a timeout failed.
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.
Google query: Microsoft Corporation VIDEO_TDR_ERROR
On Wed 22-4-2015 20:26:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042315-24382-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x10FD62)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002F59D62, 0xFFFFF8800A352858, 0xFFFFF8800A3520B0)
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 22-4-2015 17:22:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042215-24913-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x5D144)
Bugcheck code: 0x116 (0xFFFFFA8004E38010, 0xFFFFF88004207900, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
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 an attempt to reset the display driver and recover from a timeout failed.
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.
Google query: Microsoft Corporation VIDEO_TDR_ERROR
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
8 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:
dxgkrnl.sys (DirectX Graphics Kernel, Microsoft 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 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.
