Associate
- Joined
- 22 Jan 2025
- Posts
- 8
- Location
- Manchester
Good morning all,
We have been suffering with BSOD over a considerable period of time now. The strange thing is that the issue generally occurs once a day once windows has started for the first time that day... The BSOD either occurs when Steam is downloading a game update or when using a web browser.
Once the PC has restarted, the issue appears to have gone.
My memory is 4x16 G-SKill 6400MHz running stable at 5000MHz on i9 12900KS Z690 motherboard. Cant remember the exact type. The frequency is 5000MHz with 4 slips of RAM because the memory controller can't handle running 4 slips at 6400MHz (Known issue with Intel 12th gen processors). Motherboard is a Asus ROG Maximus Z690 Extreme Glacial (fully water-cooled)
I have run the motherboard and Windows MemTest86 Free version several times taking circa 2 hours to complete 4 test runs of circa 10 different Tests be run. The memory Passes each time.
Following crash dumps I have extracted the following from the dump file created. They implicate that there is a memory issue: The Debugger info is in purple, with what I see as the concernting parts in red. Of note... this crash was during Steam game update download as indicated below in red.
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : false
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.156 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 42
Microsoft (R) Windows Debugger Version 10.0.27725.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\012325-18968-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 26100 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff806`f0000000 PsLoadedModuleList = 0xfffff806`f0ef4870
Debug session time: Thu Jan 23 21:48:32.718 2025 (UTC + 0:00)
System Uptime: 0 days 0:05:11.321
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000d1`e21f0018). Type ".hh dbgerr001" for details
Loading unloaded module list
............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`f04b85d0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff870b`6dd8ef80=000000000000001a
22: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
the PTE. Parameters 3/4 contain the low/high parts of the PTE.
Arg2: ffff9bb0c91b2328
Arg3: 0000004000000000
Arg4: 0000000000000000
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1062
Key : Analysis.Elapsed.mSec
Value: 2718
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 390
Key : Analysis.Init.Elapsed.mSec
Value: 6164
Key : Analysis.Memory.CommitPeak.Mb
Value: 90
Key : Analysis.Version.DbgEng
Value: 10.0.27725.1000
Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre
Key : Analysis.Version.Ext
Value: 1.2408.27.1
Key : Bugcheck.Code.LegacyAPI
Value: 0x1a
Key : Bugcheck.Code.TargetModel
Value: 0x1a
Key : Dump.Attributes.AsUlong
Value: 21008
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 0
Key : Failure.Bucket
Value: MEMORY_CORRUPTION_ONE_BIT
Key : Failure.Hash
Value: {e3faf315-c3d0-81db-819a-6c43d23c63a7}
Key : MemoryManagement.PFN
Value: 4000000
BUGCHECK_CODE: 1a
BUGCHECK_P1: 41792
BUGCHECK_P2: ffff9bb0c91b2328
BUGCHECK_P3: 4000000000
BUGCHECK_P4: 0
FILE_IN_CAB: 012325-18968-01.dmp
DUMP_FILE_ATTRIBUTES: 0x21008
Kernel Generated Triage Dump
FAULTING_THREAD: ffffe706f3066080
MEMORY_CORRUPTOR: ONE_BIT
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: steamwebhelper
STACK_TEXT:
ffff870b`6dd8ef78 fffff806`f02391f6 : 00000000`0000001a 00000000`00041792 ffff9bb0`c91b2328 00000040`00000000 : nt!KeBugCheckEx
ffff870b`6dd8ef80 fffff806`f02378c7 : 00000040`00000000 00000040`00000000 00000000`00000001 ffff9bcd`d8648d90 : nt!MiDecommitHandlePageFileFormatPte+0x212
ffff870b`6dd8efe0 fffff806`f02366e1 : ffffe706`00000080 ffffe706`e475e480 00000000`00000000 ffffe706`e475e080 : nt!MiDeleteVa+0x197
ffff870b`6dd8f060 fffff806`f0248bce : 00000000`00000000 ffffe706`00000000 ffff870b`00000080 ffffffff`ffffffff : nt!MiDeleteVaDirect+0x2b1
ffff870b`6dd8f180 fffff806`f02489eb : 7fffffff`fffffffc ffffe706`f3066080 00000000`00000000 ffffe706`e475e2e0 : nt!MiDeletePagablePteRange+0x1ba
ffff870b`6dd8f440 fffff806`f08bd3a4 : 00000000`00000000 ffff870b`6dd8f500 ffffe706`f206b180 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x4b
ffff870b`6dd8f490 fffff806`f08bd0fe : 00006192`00000000 ffffe706`f206b180 ffffe706`f3066080 00000000`00000000 : nt!MiDeleteVad+0x180
ffff870b`6dd8f540 fffff806`f08bcf0f : ffffe706`e9c211f0 ffffe706`f3066080 ffffe706`f3066080 ffffe706`f3066080 : nt!MiCleanVad+0x3e
ffff870b`6dd8f570 fffff806`f08bdc7e : ffffe706`00000000 ffffe706`e475e268 ffff870b`6dd8f6e0 00000000`00000000 : nt!MmCleanProcessAddressSpace+0xfb
ffff870b`6dd8f5f0 fffff806`f08bc82e : ffffe706`e475e080 ffffe706`e475e080 ffff870b`6dd8f6e0 00000000`00000000 : nt!PspRundownSingleProcess+0xc2
ffff870b`6dd8f680 fffff806`f095ed3b : 000000d1`e21fd000 00000000`00000000 ffff870b`6dd8f8a8 ffffe706`f3066080 : nt!PspExitLastThread+0xe6
ffff870b`6dd8f710 fffff806`f095e394 : 00000000`00000001 fffff806`f0272d01 00000000`00000000 00000000`00000000 : nt!PspExitThread+0x7bb
ffff870b`6dd8f800 fffff806`f026e00c : 00000000`40f60088 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSchedulerApcTerminate+0x34
ffff870b`6dd8f840 fffff806`f067e930 : 00000000`00000000 ffff870b`6dd8f8e0 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x47c
ffff870b`6dd8f8e0 fffff806`f068d40d : 00000000`b8268be6 ffffffff`fffffffe ffff870b`6dd8fa38 ffffffff`dc358e10 : nt!KiInitiateUserApc+0x70
ffff870b`6dd8fa20 00007ffb`9fb7f7a4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0xad
000000d1`e28ff628 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`9fb7f7a4
MODULE_NAME: hardware
IMAGE_NAME: memory_corruption
STACK_COMMAND: .process /r /p 0xffffe706e475e080; .thread 0xffffe706f3066080 ; kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}
Followup: MachineOwner
---------
I am going to get hold of MemTest86 Pro as the free version limits to 4 test runs, however I have no idea of the best test to use and how many runs.
Please can anyone provide any guidance as to steps best taken to resolve before I go out and buy a new 64GB (2x32GB) memory kit?
Thanks in advanced for any advice.
We have been suffering with BSOD over a considerable period of time now. The strange thing is that the issue generally occurs once a day once windows has started for the first time that day... The BSOD either occurs when Steam is downloading a game update or when using a web browser.
Once the PC has restarted, the issue appears to have gone.
My memory is 4x16 G-SKill 6400MHz running stable at 5000MHz on i9 12900KS Z690 motherboard. Cant remember the exact type. The frequency is 5000MHz with 4 slips of RAM because the memory controller can't handle running 4 slips at 6400MHz (Known issue with Intel 12th gen processors). Motherboard is a Asus ROG Maximus Z690 Extreme Glacial (fully water-cooled)
I have run the motherboard and Windows MemTest86 Free version several times taking circa 2 hours to complete 4 test runs of circa 10 different Tests be run. The memory Passes each time.
Following crash dumps I have extracted the following from the dump file created. They implicate that there is a memory issue: The Debugger info is in purple, with what I see as the concernting parts in red. Of note... this crash was during Steam game update download as indicated below in red.
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : false
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.156 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 42
Microsoft (R) Windows Debugger Version 10.0.27725.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\012325-18968-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 26100 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff806`f0000000 PsLoadedModuleList = 0xfffff806`f0ef4870
Debug session time: Thu Jan 23 21:48:32.718 2025 (UTC + 0:00)
System Uptime: 0 days 0:05:11.321
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000d1`e21f0018). Type ".hh dbgerr001" for details
Loading unloaded module list
............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`f04b85d0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff870b`6dd8ef80=000000000000001a
22: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
the PTE. Parameters 3/4 contain the low/high parts of the PTE.
Arg2: ffff9bb0c91b2328
Arg3: 0000004000000000
Arg4: 0000000000000000
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1062
Key : Analysis.Elapsed.mSec
Value: 2718
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 390
Key : Analysis.Init.Elapsed.mSec
Value: 6164
Key : Analysis.Memory.CommitPeak.Mb
Value: 90
Key : Analysis.Version.DbgEng
Value: 10.0.27725.1000
Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre
Key : Analysis.Version.Ext
Value: 1.2408.27.1
Key : Bugcheck.Code.LegacyAPI
Value: 0x1a
Key : Bugcheck.Code.TargetModel
Value: 0x1a
Key : Dump.Attributes.AsUlong
Value: 21008
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 0
Key : Failure.Bucket
Value: MEMORY_CORRUPTION_ONE_BIT
Key : Failure.Hash
Value: {e3faf315-c3d0-81db-819a-6c43d23c63a7}
Key : MemoryManagement.PFN
Value: 4000000
BUGCHECK_CODE: 1a
BUGCHECK_P1: 41792
BUGCHECK_P2: ffff9bb0c91b2328
BUGCHECK_P3: 4000000000
BUGCHECK_P4: 0
FILE_IN_CAB: 012325-18968-01.dmp
DUMP_FILE_ATTRIBUTES: 0x21008
Kernel Generated Triage Dump
FAULTING_THREAD: ffffe706f3066080
MEMORY_CORRUPTOR: ONE_BIT
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: steamwebhelper
STACK_TEXT:
ffff870b`6dd8ef78 fffff806`f02391f6 : 00000000`0000001a 00000000`00041792 ffff9bb0`c91b2328 00000040`00000000 : nt!KeBugCheckEx
ffff870b`6dd8ef80 fffff806`f02378c7 : 00000040`00000000 00000040`00000000 00000000`00000001 ffff9bcd`d8648d90 : nt!MiDecommitHandlePageFileFormatPte+0x212
ffff870b`6dd8efe0 fffff806`f02366e1 : ffffe706`00000080 ffffe706`e475e480 00000000`00000000 ffffe706`e475e080 : nt!MiDeleteVa+0x197
ffff870b`6dd8f060 fffff806`f0248bce : 00000000`00000000 ffffe706`00000000 ffff870b`00000080 ffffffff`ffffffff : nt!MiDeleteVaDirect+0x2b1
ffff870b`6dd8f180 fffff806`f02489eb : 7fffffff`fffffffc ffffe706`f3066080 00000000`00000000 ffffe706`e475e2e0 : nt!MiDeletePagablePteRange+0x1ba
ffff870b`6dd8f440 fffff806`f08bd3a4 : 00000000`00000000 ffff870b`6dd8f500 ffffe706`f206b180 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x4b
ffff870b`6dd8f490 fffff806`f08bd0fe : 00006192`00000000 ffffe706`f206b180 ffffe706`f3066080 00000000`00000000 : nt!MiDeleteVad+0x180
ffff870b`6dd8f540 fffff806`f08bcf0f : ffffe706`e9c211f0 ffffe706`f3066080 ffffe706`f3066080 ffffe706`f3066080 : nt!MiCleanVad+0x3e
ffff870b`6dd8f570 fffff806`f08bdc7e : ffffe706`00000000 ffffe706`e475e268 ffff870b`6dd8f6e0 00000000`00000000 : nt!MmCleanProcessAddressSpace+0xfb
ffff870b`6dd8f5f0 fffff806`f08bc82e : ffffe706`e475e080 ffffe706`e475e080 ffff870b`6dd8f6e0 00000000`00000000 : nt!PspRundownSingleProcess+0xc2
ffff870b`6dd8f680 fffff806`f095ed3b : 000000d1`e21fd000 00000000`00000000 ffff870b`6dd8f8a8 ffffe706`f3066080 : nt!PspExitLastThread+0xe6
ffff870b`6dd8f710 fffff806`f095e394 : 00000000`00000001 fffff806`f0272d01 00000000`00000000 00000000`00000000 : nt!PspExitThread+0x7bb
ffff870b`6dd8f800 fffff806`f026e00c : 00000000`40f60088 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSchedulerApcTerminate+0x34
ffff870b`6dd8f840 fffff806`f067e930 : 00000000`00000000 ffff870b`6dd8f8e0 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x47c
ffff870b`6dd8f8e0 fffff806`f068d40d : 00000000`b8268be6 ffffffff`fffffffe ffff870b`6dd8fa38 ffffffff`dc358e10 : nt!KiInitiateUserApc+0x70
ffff870b`6dd8fa20 00007ffb`9fb7f7a4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0xad
000000d1`e28ff628 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`9fb7f7a4
MODULE_NAME: hardware
IMAGE_NAME: memory_corruption
STACK_COMMAND: .process /r /p 0xffffe706e475e080; .thread 0xffffe706f3066080 ; kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}
Followup: MachineOwner
---------
I am going to get hold of MemTest86 Pro as the free version limits to 4 test runs, however I have no idea of the best test to use and how many runs.
Please can anyone provide any guidance as to steps best taken to resolve before I go out and buy a new 64GB (2x32GB) memory kit?
Thanks in advanced for any advice.
Last edited:
