Na update van Win10 last van blauwe schermen (critical proces died, kernel security check failure, memory management). Bij een eerdere update in 2016 was dit ook ook zo en na gebruik van dit forum en diverse scans en updates (o.a. driver Intel) opgelost maar nu weer hetzelfde. Probleemoplosser gedraaid, correcties met restorehealth, sfc /scannow etc. , enkele updates van drivers. Weet niet waar het nu nog mis gaat maar mijn kennis houdt op en zojuist na herstart zelfs in Outlook. Eerst leek het beperkt tot Google Chrome of Microsoft Edge. Ook app Foto's van Windows werkt niet meer.
Erg blij met tips...
2
PC Web Plus - Member
PC Web Plus - Member
"GlaryUtilities" waarom die meuk?
Er wordt niets sneller door files en registersleutels te wissen of heb je schijfruimte te kort?
En zet de uitdraai van Whocrashed hier eens neer.
http://www.resplendence.com/whocrashed
En een weblink van Speccy, geen schermafrukken of foto's, de weblink a.u.b.
https://www.piriform.com/speccy/download
http://www.piriform.com/docs/speccy/using-speccy/publishing-a-speccy-profile-to-the-web
Er wordt niets sneller door files en registersleutels te wissen of heb je schijfruimte te kort?
En zet de uitdraai van Whocrashed hier eens neer.
http://www.resplendence.com/whocrashed
En een weblink van Speccy, geen schermafrukken of foto's, de weblink a.u.b.
https://www.piriform.com/speccy/download
http://www.piriform.com/docs/speccy/using-speccy/publishing-a-speccy-profile-to-the-web
"Dit is mijn handtekening of sig."
Sometimes, a vendor may misleadingly advertise the I/O clock rate by labeling the MT/s as MHz
https://www.piriform.com/speccy/download
https://www.piriform.com/docs/speccy/us ... to-the-web
Sometimes, a vendor may misleadingly advertise the I/O clock rate by labeling the MT/s as MHz
https://www.piriform.com/speccy/download
https://www.piriform.com/docs/speccy/us ... to-the-web
4
PC Web Plus - Member
PC Web Plus - Member
System Information (local)
--------------------------------------------------------------------------------
Computer name: STUDEERKAMER
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\WINDOWS
Hardware: ASRock, H81M-HDS
CPU: GenuineIntel Intel(R) Core(TM) i5-4430 CPU @ 3.00GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8246423552 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Mon 3-7-2017 14:57:41 your computer crashed
crash dump file: C:\WINDOWS\Minidump\070317-24953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x139 (0x3, 0xFFFFB381511DE860, 0xFFFFB381511DE7B8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 3-7-2017 13:46:02 your computer crashed
crash dump file: C:\WINDOWS\Minidump\070317-22578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x1A (0x41201, 0xFFFFF6BFFC2FF008, 0x49, 0xFFFFDF80C130C7B0)
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. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 3-7-2017 12:40:09 your computer crashed
crash dump file: C:\WINDOWS\Minidump\070317-25843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0xEF (0xFFFFB788A7F9C7C0, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 crash dumps have been found and analyzed. No offending third party drivers have been found.
SPECCY:
http://speccy.piriform.com/results/0jce ... eawVuLAtIw
--------------------------------------------------------------------------------
Computer name: STUDEERKAMER
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\WINDOWS
Hardware: ASRock, H81M-HDS
CPU: GenuineIntel Intel(R) Core(TM) i5-4430 CPU @ 3.00GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8246423552 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Mon 3-7-2017 14:57:41 your computer crashed
crash dump file: C:\WINDOWS\Minidump\070317-24953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x139 (0x3, 0xFFFFB381511DE860, 0xFFFFB381511DE7B8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 3-7-2017 13:46:02 your computer crashed
crash dump file: C:\WINDOWS\Minidump\070317-22578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x1A (0x41201, 0xFFFFF6BFFC2FF008, 0x49, 0xFFFFDF80C130C7B0)
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. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 3-7-2017 12:40:09 your computer crashed
crash dump file: C:\WINDOWS\Minidump\070317-25843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0xEF (0xFFFFB788A7F9C7C0, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 crash dumps have been found and analyzed. No offending third party drivers have been found.
SPECCY:
http://speccy.piriform.com/results/0jce ... eawVuLAtIw