M
MarcSchlenker
Hi Everyone,
I do have problems since September 2020 on my Windows 10 notebook. I have no a list of 14 Bluescreens and serveral tasks I had done since then. I will try to show the details as good as possible.
First 3 BlueScreens occured in September/October => I didn't recognized them as an upcoming problem.
In November and December I had 3 an 4 Blue Screens => Looked like something special
Several attempts by replacing RAM, tried to understand the BSOD messages and logs => no success. I also open the notebook and looked for dust. None. Fans spin correctly.
On 6th of January I did a complete new installation for Windows 10.
From then I had three BSODs. All my steps were related to some forum posts telling the RAM could be a problem. I've ordered a new 16 GB RAM - you will see it in the table below, when i used and don't used it. Also some errors in the event view (EnhancedStorage) pointed to the SSD. But I also read a forum post, where a user responded 2.5 years later, saying it has been definitely a wrong RAM. So I was a little optimistic - being on the right way.
Hardware
Schenker XMG P507 notebook
Windows 10.0.1904 Build 19042
Intel Core i7-6700HQ
C: (Windows) SSD 256 GB Modell Crucial_CT275MX300SSD4
D: HDD 1TB Modell ST1000LM048-2E7172
Intel(R) HD Graphics 530
NVIDIA GeForce GTX 1060
2 of 4 RAM slot used
.zip of 14 Minidump files + export of system information as .txt and the System's event logs from today.
Thanks for your help and any tipp's or tricks for this BSOD hunt.
Marc
WinDBG outout of todays MiniDump
Microsoft (R) Windows Debugger Version 10.0.19041.685 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\marcs\Desktop\Minidumps\012221-10250-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff801`6f400000 PsLoadedModuleList = 0xfffff801`7002a2f0
Debug session time: Fri Jan 22 17:33:16.989 2021 (UTC + 1:00)
System Uptime: 0 days 1:55:15.685
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_PROCESS_DIED (ef)
A critical system process died
Arguments:
Arg1: ffffa00e5d062080, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 4
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-N6G91CP
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 6
Key : Analysis.Memory.CommitPeak.Mb
Value: 74
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: ef
BUGCHECK_P1: ffffa00e5d062080
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
PROCESS_NAME: csrss.exe
CRITICAL_PROCESS: csrss.exe
ERROR_CODE: (NTSTATUS) 0x5ee67040 - <Unable to get error code text>
CRITICAL_PROCESS_REPORTGUID: {5713e05e-f739-4d0e-8b38-8d9a97bd83f7}
IMAGE_NAME: ntdll.dll
MODULE_NAME: ntdll
FAULTING_MODULE: 0000000000000000
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
STACK_TEXT:
ffffc485`56daf838 fffff801`6fd068f2 : 00000000`000000ef ffffa00e`5d062080 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffc485`56daf840 fffff801`6fc49b49 : 00000000`00000000 fffff801`6f75971d 00000000`00000002 fffff801`6f758d37 : nt!PspCatchCriticalBreak+0x10e
ffffc485`56daf8e0 fffff801`6fb09734 : ffffa00e`00000000 00000000`00000000 ffffa00e`5d062080 ffffa00e`5d0624b8 : nt!PspTerminateAllThreads+0x140b4d
ffffc485`56daf950 fffff801`6fb09a5c : ffffa00e`5d062080 00000000`00000000 00000000`00000016 ffffa00e`63c56080 : nt!PspTerminateProcess+0xe0
ffffc485`56daf990 fffff801`6f8071b5 : ffffa00e`5d062080 ffffa00e`5ee67040 ffffc485`56dafa80 ffffc485`56dafa80 : nt!NtTerminateProcess+0x9c
ffffc485`56dafa00 00007ffc`7046c534 : 00007ffc`6daf8d96 00000000`00000000 00000000`00000000 ffffffff`ee1e5d00 : nt!KiSystemServiceCopyEnd+0x25
00000088`0a90ea98 00007ffc`6daf8d96 : 00000000`00000000 00000000`00000000 ffffffff`ee1e5d00 00000000`00000574 : 0x00007ffc`7046c534
00000088`0a90eaa0 00000000`00000000 : 00000000`00000000 ffffffff`ee1e5d00 00000000`00000574 00000000`00000000 : 0x00007ffc`6daf8d96
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0xEF_csrss.exe_BUGCHECK_CRITICAL_PROCESS_5ee67040_ntdll.dll!TppFreeDirectParamsCache_IMAGE_ntdll.dll
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {438e1441-3655-5f04-b0a0-cfa02205ae59}
Followup: MachineOwner
---------
Continue reading...
I do have problems since September 2020 on my Windows 10 notebook. I have no a list of 14 Bluescreens and serveral tasks I had done since then. I will try to show the details as good as possible.
First 3 BlueScreens occured in September/October => I didn't recognized them as an upcoming problem.
In November and December I had 3 an 4 Blue Screens => Looked like something special
Several attempts by replacing RAM, tried to understand the BSOD messages and logs => no success. I also open the notebook and looked for dust. None. Fans spin correctly.
On 6th of January I did a complete new installation for Windows 10.
From then I had three BSODs. All my steps were related to some forum posts telling the RAM could be a problem. I've ordered a new 16 GB RAM - you will see it in the table below, when i used and don't used it. Also some errors in the event view (EnhancedStorage) pointed to the SSD. But I also read a forum post, where a user responded 2.5 years later, saying it has been definitely a wrong RAM. So I was a little optimistic - being on the right way.
Hardware
Schenker XMG P507 notebook
Windows 10.0.1904 Build 19042
Intel Core i7-6700HQ
C: (Windows) SSD 256 GB Modell Crucial_CT275MX300SSD4
D: HDD 1TB Modell ST1000LM048-2E7172
Intel(R) HD Graphics 530
NVIDIA GeForce GTX 1060
2 of 4 RAM slot used
| 06th of January 2021 | Windows 10 re-installed | |
| RAM: 8 GB (left) - 8 GB (right) | ||
| 08th of January | BSOD: ATTEMPTED_WRITE_TO_READONLY_MEMORY | File attached in .zip |
| Changed RAM: 8 GB (left) - 16 GB | ||
| Updated SSD Firmware via Crucial Storage Executive | ||
| 09th of January | BSOD: ATTEMPTED_WRITE_TO_READONLY_MEMORY | File attached in .zip |
| Changed RAM: 8 GB (old right) - 16 GB | ||
| Updated IntelChipset and IntelRapidStorage by manufacturer's provided versions. | ||
| 22th of january | BSOD: CRITICAL_PROCESS_DIED | |
| EventViewer attached | ||
| MiniDump attached | ||
| Current Configuration attached | ||
| Windows Update => up to date | ||
| SFC /SCANNOW no results |
.zip of 14 Minidump files + export of system information as .txt and the System's event logs from today.
Loading…
1drv.ms
Thanks for your help and any tipp's or tricks for this BSOD hunt.
Marc
WinDBG outout of todays MiniDump
Microsoft (R) Windows Debugger Version 10.0.19041.685 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\marcs\Desktop\Minidumps\012221-10250-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff801`6f400000 PsLoadedModuleList = 0xfffff801`7002a2f0
Debug session time: Fri Jan 22 17:33:16.989 2021 (UTC + 1:00)
System Uptime: 0 days 1:55:15.685
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_PROCESS_DIED (ef)
A critical system process died
Arguments:
Arg1: ffffa00e5d062080, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 4
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-N6G91CP
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 6
Key : Analysis.Memory.CommitPeak.Mb
Value: 74
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: ef
BUGCHECK_P1: ffffa00e5d062080
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
PROCESS_NAME: csrss.exe
CRITICAL_PROCESS: csrss.exe
ERROR_CODE: (NTSTATUS) 0x5ee67040 - <Unable to get error code text>
CRITICAL_PROCESS_REPORTGUID: {5713e05e-f739-4d0e-8b38-8d9a97bd83f7}
IMAGE_NAME: ntdll.dll
MODULE_NAME: ntdll
FAULTING_MODULE: 0000000000000000
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
STACK_TEXT:
ffffc485`56daf838 fffff801`6fd068f2 : 00000000`000000ef ffffa00e`5d062080 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffc485`56daf840 fffff801`6fc49b49 : 00000000`00000000 fffff801`6f75971d 00000000`00000002 fffff801`6f758d37 : nt!PspCatchCriticalBreak+0x10e
ffffc485`56daf8e0 fffff801`6fb09734 : ffffa00e`00000000 00000000`00000000 ffffa00e`5d062080 ffffa00e`5d0624b8 : nt!PspTerminateAllThreads+0x140b4d
ffffc485`56daf950 fffff801`6fb09a5c : ffffa00e`5d062080 00000000`00000000 00000000`00000016 ffffa00e`63c56080 : nt!PspTerminateProcess+0xe0
ffffc485`56daf990 fffff801`6f8071b5 : ffffa00e`5d062080 ffffa00e`5ee67040 ffffc485`56dafa80 ffffc485`56dafa80 : nt!NtTerminateProcess+0x9c
ffffc485`56dafa00 00007ffc`7046c534 : 00007ffc`6daf8d96 00000000`00000000 00000000`00000000 ffffffff`ee1e5d00 : nt!KiSystemServiceCopyEnd+0x25
00000088`0a90ea98 00007ffc`6daf8d96 : 00000000`00000000 00000000`00000000 ffffffff`ee1e5d00 00000000`00000574 : 0x00007ffc`7046c534
00000088`0a90eaa0 00000000`00000000 : 00000000`00000000 ffffffff`ee1e5d00 00000000`00000574 00000000`00000000 : 0x00007ffc`6daf8d96
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0xEF_csrss.exe_BUGCHECK_CRITICAL_PROCESS_5ee67040_ntdll.dll!TppFreeDirectParamsCache_IMAGE_ntdll.dll
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {438e1441-3655-5f04-b0a0-cfa02205ae59}
Followup: MachineOwner
---------
Continue reading...