Ik heropen dit topic maar weer even. Het is een week lang helemaal goed gegaan. Plotseling weer blue screen op hetzelfde moment als toen: bij het aanvullen van een FB albumpje. Maar daarna ook tot 3x achter elkaar tijdens de opstart. Kan op dit moment niets meer met de pc behalve in de veilige modus opstarten.
Ik heb Whocrashed weer laten lopen (heb ik met ConEmu er gelukkig nog op staan):
Ik heb Whocrashed weer laten lopen (heb ik met ConEmu er gelukkig nog op staan):
Code:
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 29-11-2015 8:38:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112915-15756-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88006AB5520, 0x0, 0x0)
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 Sun 29-11-2015 8:38:16 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tdx.sys (tdx+0x7DB8)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88006AB5520, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tdx.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TDI Translation Driver
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 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 KMODE_EXCEPTION_NOT_HANDLED
On Sun 29-11-2015 8:34:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112915-17004-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880076A0520, 0x0, 0x0)
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 Sun 29-11-2015 8:30:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112915-18439-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88006864520, 0x0, 0x0)
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 Sun 29-11-2015 8:26:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112915-20217-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880068DED30, 0x0, 0x0)
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 Sat 28-11-2015 15:34:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112815-19656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880075C5520, 0x0, 0x0)
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 Sat 28-11-2015 15:30:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112815-26083-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88002898D30, 0x0, 0x0)
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.
Laatst bewerkt door een moderator:
