:strip_exif()/u/381207/54510562%2520-%2520Copy%2520-%2520Copy.gif?f=community)
Draai Windows 10 op een INtel Nuc5i3. Geen andere symptomen, geeft opeens een BSOD met een onachterhaalbare errorcode en start vervolgens terug op.
Heb de NUC 2dehands gekocht, er zat toen 4Gb RAM in, heb een identiek latje (zelfde EAN) bijgeplaatst en dat geeft Windows nu ook aan, 8Gb in totaal. Kan me niet herinneren of de BSODs ook voorkwamen zonder het extra latje.
Volgende stap zal wss zijn het verwijderen van het extra latje en zien of het dan nog voorkomt, maar voordat ik daarmee begin, heeft iemand een ideetje ivm. onderstaande WhoCrashed logs?
System Information (local)
--------------------------------------------------------------------------------
Computer name: DESKTOP-OO8B2K5
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\WINDOWS
Hardware: Intel Corporation, NUC5i3RYB
CPU: GenuineIntel Intel(R) Core(TM) i3-5010U CPU @ 2.10GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8469602304 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Thu 21/01/2016 17:28:09 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\012116-3343-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS! ?? ::FNODOBFM::`string'+0x5F7E)
Bugcheck code: 0x139 (0x3, 0xFFFFD000228DD6F0, 0xFFFFD000228DD648, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows®-besturingssysteem
company: Microsoft Corporation
description: NT-bestandssysteemstuurprogramma
Bug check description: The kernel has detected the corruption of a critical data structure.
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 Thu 21/01/2016 17:28:09 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS! ?? ::FNODOBFM::`string'+0x5F7E)
Bugcheck code: 0x139 (0x3, 0xFFFFD000228DD6F0, 0xFFFFD000228DD648, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows®-besturingssysteem
company: Microsoft Corporation
description: NT-bestandssysteemstuurprogramma
Bug check description: The kernel has detected the corruption of a critical data structure.
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 Thu 21/01/2016 17:02:10 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\012116-5093-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xBE (0xFFFFFB400487D5F8, 0x80000000001C0121, 0xFFFFD0002325A490, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 20/01/2016 16:41:25 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\012016-3296-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x645666C5B, 0x2, 0x1, 0xFFFFF8026FA89194)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Tue 19/01/2016 15:14:16 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011916-3656-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802F0F4BFA4, 0xFFFFD000237C5F30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Heb de NUC 2dehands gekocht, er zat toen 4Gb RAM in, heb een identiek latje (zelfde EAN) bijgeplaatst en dat geeft Windows nu ook aan, 8Gb in totaal. Kan me niet herinneren of de BSODs ook voorkwamen zonder het extra latje.
Volgende stap zal wss zijn het verwijderen van het extra latje en zien of het dan nog voorkomt, maar voordat ik daarmee begin, heeft iemand een ideetje ivm. onderstaande WhoCrashed logs?
System Information (local)
--------------------------------------------------------------------------------
Computer name: DESKTOP-OO8B2K5
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\WINDOWS
Hardware: Intel Corporation, NUC5i3RYB
CPU: GenuineIntel Intel(R) Core(TM) i3-5010U CPU @ 2.10GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8469602304 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Thu 21/01/2016 17:28:09 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\012116-3343-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS! ?? ::FNODOBFM::`string'+0x5F7E)
Bugcheck code: 0x139 (0x3, 0xFFFFD000228DD6F0, 0xFFFFD000228DD648, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows®-besturingssysteem
company: Microsoft Corporation
description: NT-bestandssysteemstuurprogramma
Bug check description: The kernel has detected the corruption of a critical data structure.
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 Thu 21/01/2016 17:28:09 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS! ?? ::FNODOBFM::`string'+0x5F7E)
Bugcheck code: 0x139 (0x3, 0xFFFFD000228DD6F0, 0xFFFFD000228DD648, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows®-besturingssysteem
company: Microsoft Corporation
description: NT-bestandssysteemstuurprogramma
Bug check description: The kernel has detected the corruption of a critical data structure.
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 Thu 21/01/2016 17:02:10 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\012116-5093-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xBE (0xFFFFFB400487D5F8, 0x80000000001C0121, 0xFFFFD0002325A490, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 20/01/2016 16:41:25 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\012016-3296-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x645666C5B, 0x2, 0x1, 0xFFFFF8026FA89194)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Tue 19/01/2016 15:14:16 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011916-3656-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802F0F4BFA4, 0xFFFFD000237C5F30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.