Uszka schreef op dinsdag 11 januari 2022 @ 12:22: Welke foutmeldingen staan er in het Windows logboek?
De computer is opnieuw opgestart na een bugcontrole. De bugcontrole is 0x0000001e (0xffffffffc0000094, 0xfffff8001b923296, 0xffff9207eb8344a0, 0x000000000000005a). Er is een dump opgeslagen in: C:\Windows\MEMORY.DMP. Rapport-id: be8f2492-8733-40f7-83f7-eb3a44f9f358
Dit is de laatste error.
Whocrashed geeft het volgende aan:
Computer name: DESKTOP-6F76582
Windows version: Windows 10, 10.0, version 2009, build: 19042
Windows dir: C:\Windows
Hardware: ASRock, P67 Extreme4 Gen3
CPU: GenuineIntel Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz 8664, level: 6
4 logical processors, active mask: 15
RAM: 8571797504 bytes (8,0GB)
On Tue 11-1-2022 13:38:49 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\011122-9312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F70D0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000094, 0xFFFFF8001B923296, 0xFFFF9207EB8344A0, 0x5A)
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 might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 11-1-2022 13:38:49 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!HvlPerformEndOfInterrupt+0x4DEE)
Bugcheck code: 0x1E (0xFFFFFFFFC0000094, 0xFFFFF8001B923296, 0xFFFF9207EB8344A0, 0x5A)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.