Jump to content

Bluescreen of death code 12b

eric_s
By eric_s
in Troubleshooting
 Share
Posted

My PC bluescreened today and I'm a little new to reading .dmp files. Can anyone offer some insight please?

  

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true

   EnableRedirectToV8JsProvider : 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.109 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 41

Microsoft (R) Windows Debugger Version 10.0.27553.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\050724-5562-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 22621 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff805`31a00000 PsLoadedModuleList = 0xfffff805`326134a0
Debug session time: Tue May  7 21:23:34.514 2024 (UTC - 6:00)
System Uptime: 1 days 23:17:17.493
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............................
Loading User Symbols
PEB address is NULL !
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`31e18040 48894c2408      mov     qword ptr [rsp+8],rcx ss:ffffa68a`aa48ebf0=000000000000012b

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

FAULTY_HARDWARE_CORRUPTED_PAGE (12b)
This BugCheck indicates that a single bit error was found in this page.  This is a hardware memory error.
Arguments:
Arg1: ffffffffc00002c4, virtual address mapping the corrupted page
Arg2: 000000000000032e, physical page number
Arg3: 000002a0b8eb19c0, zero
Arg4: ffffb780663ad000, zero

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1405

    Key  : Analysis.Elapsed.mSec
    Value: 4430

    Key  : Analysis.IO.Other.Mb
    Value: 21

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 31

    Key  : Analysis.Init.CPU.mSec
    Value: 186

    Key  : Analysis.Init.Elapsed.mSec
    Value: 421077

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 101

    Key  : BlackBox.SmDecompressionFailure.CompressedSize
    Value: 0x32e

    Key  : BlackBox.SmDecompressionFailure.CompressionFormat
    Value: 0x3

    Key  : BlackBox.SmDecompressionFailure.SourceDataHash
    Value: 0x72d096ba

    Key  : BlackBox.SmDecompressionFailure.SourceDataOffset
    Value: 0x19c0

    Key  : BlackBox.SmDecompressionFailure.SourcePFN1
    Value: 0x77e5c1

    Key  : BlackBox.SmDecompressionFailure.SourcePFN2
    Value: 0xffffffffffffffff

    Key  : BlackBox.SmDecompressionFailure.TargetPFN
    Value: 0x52e814

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x12b

    Key  : Bugcheck.Code.TargetModel
    Value: 0x12b

    Key  : Dump.Attributes.AsUlong
    Value: 808

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: 0x12B_c00002c4_StCtDecompressFailed_nt!ST_STORE_SM_TRAITS_::StDmPageError

    Key  : Failure.Hash
    Value: {c6a6bb4d-3b77-dff6-2d9b-75f5d0f61a50}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1497cf94

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 4853999

    Key  : Hypervisor.Flags.ValueHex
    Value: 4a10ef

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7


BUGCHECK_CODE:  12b

BUGCHECK_P1: ffffffffc00002c4

BUGCHECK_P2: 32e

BUGCHECK_P3: 2a0b8eb19c0

BUGCHECK_P4: ffffb780663ad000

FILE_IN_CAB:  050724-5562-01.dmp

DUMP_FILE_ATTRIBUTES: 0x808
  Kernel Generated Triage Dump

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  MemCompression

STACK_TEXT:  
ffffa68a`aa48ebe8 fffff805`31fc498f     : 00000000`0000012b ffffffff`c00002c4 00000000`0000032e 000002a0`b8eb19c0 : nt!KeBugCheckEx
ffffa68a`aa48ebf0 fffff805`31e5f50b     : 00000000`00000200 00000000`00000003 ffff830b`9a4f6050 000002a0`b8eb19c0 : nt!ST_STORE<SM_TRAITS>::StDmPageError+0xfb
ffffa68a`aa48ec40 fffff805`31fc5968     : 00000000`00000004 fffff805`31fbf0f2 00000000`00000000 00000000`00000001 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x2c5
ffffa68a`aa48ed10 fffff805`31fc65c8     : 00000000`00000001 00000000`0000d289 ffff830b`9a4f6050 ffff830b`00001000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xa0
ffffa68a`aa48ed60 fffff805`31fc5155     : ffffffff`ffffffff ffff830b`bf2be000 ffffa68a`aa48ee40 ffff830b`bf7d3f50 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x1c4
ffffa68a`aa48ee00 fffff805`31fbebeb     : ffffa68a`aa48f039 00000000`00000001 fffff805`32669580 ffff830b`9d7f70c0 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xc9
ffffa68a`aa48eeb0 fffff805`31fbeac1     : ffff830b`9a4f6000 ffff830b`bf7d3f50 ffff830b`bf2be000 ffff830b`9a4f79c0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x93
ffffa68a`aa48ef30 fffff805`31c2934a     : ffff830b`a18b10f4 ffff830b`9a4f6000 00000000`00000000 ffff830b`bf2be000 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
ffffa68a`aa48ef60 fffff805`31e5ef8e     : fffff805`31fbeaa0 ffffa68a`aa48f000 00000000`00000002 ffff830b`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x7a
ffffa68a`aa48efd0 fffff805`31fc09c8     : ffffa68a`00000001 ffff830b`848f01c8 00000000`000003ff ffff830b`bf7d3f50 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xd6
ffffa68a`aa48f0a0 fffff805`31fbe2d3     : 00000000`000003ff 00000000`000003ff ffffa68a`aa48f150 ffff830b`bf7d3f50 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x48
ffffa68a`aa48f0f0 fffff805`31e5ea22     : 00000000`0000000c ffff830b`bf7d3f50 00000000`00000001 00000000`00000001 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0x1d7
ffffa68a`aa48f180 fffff805`31fc7c42     : ffff830b`9d7f7180 ffffa68a`aa48f240 00000000`00000001 ffffa68a`00000000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x1cc
ffffa68a`aa48f200 fffff805`31e50a40     : ffff830b`20358ab8 00000000`00000001 ffff830b`a1721700 fffff805`31c370c9 : nt!SmPageRead+0x42
ffffa68a`aa48f240 fffff805`31d4d657     : 00000000`00000002 ffffa68a`aa48f380 ffff830b`9d7f7070 ffff830b`9d7f7070 : nt!MiIssueHardFaultIo+0x102ac0
ffffa68a`aa48f290 fffff805`31c301e1     : 00000000`c0033333 00000000`00000001 00004d94`11f2ff30 ffffa68a`00000000 : nt!MiIssueHardFault+0x207
ffffa68a`aa48f340 fffff805`31e291fa     : ffff830b`a18b1080 00000000`00000000 000000c2`2ddfd7c7 ffff830b`00000000 : nt!MmAccessFault+0x331
ffffa68a`aa48f460 00007ffb`64154318     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x37a
000000c2`2ddfd720 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`64154318


SYMBOL_NAME:  nt!ST_STORE<SM_TRAITS>::StDmPageError+fb

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.3527

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  fb

FAILURE_BUCKET_ID:  0x12B_c00002c4_StCtDecompressFailed_nt!ST_STORE_SM_TRAITS_::StDmPageError

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c6a6bb4d-3b77-dff6-2d9b-75f5d0f61a50}

Followup:     MachineOwner

 

Thanks is advanced!

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
29 minutes ago, eric_s said:

FAULTY_HARDWARE_CORRUPTED_PAGE (12b) 

This BugCheck indicates that a single bit error was found in this page.  This is a hardware memory error.

Your RAM might potentially be defective. I'd recommend to run some memory checks, e.g. the Microsoft Memory Diagnostics tool, as recommended here:

https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x12b---faulty-hardware-corrupted-page

Remember to either quote or @mention others, so they are notified of your reply

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

 

10 hours ago, Eigenvektor said:

Your RAM might potentially be defective. I'd recommend to run some memory checks, e.g. the Microsoft Memory Diagnostics tool, as recommended here:

https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x12b---faulty-hardware-corrupted-page

The page file is basically treated like RAM so this error can also be storage. This was corruption in the page file so just from this the storage would be the main suspect. Now, what it looks like in the stack depends on where the issue is detected, not where it was created. So it can still be RAM. Making any conclusion from just one dump file is often not accurate because so many things can affect memory. 

 

@eric_s Could you provide more dump files? And I prefer having the actual dump files to look at, there's much more to debugging than just the !analyze output.  Go to C:\Windows\Minidump and check if you have any minidump files. If you do, go back to the Windows folder and copy the Minidump folder itself to the Downloads folder (You can use the desktop if you don't have OneDrive syncing files). Zip the copied folder and attach it to a post. Please follow the instructions to the letter as Windows doesn't like you messing with files in this location.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

If it's a one off, I wouldn't dig into things honestly. Only if it becomes a frequent problem. Many things can cause Windows to halt itself but that doesn't mean anything is broken. You could've had an unlucky bit flip in RAM, and that could be enough. Has this happened more than once? 

"Any sufficiently advanced technology is indistinguishable from magic" - Arthur C. Clarke
Just because it may seem like magic, I'm not a wizard, just a nerd. I am fallible. 

Use the quote button or @<username> to reply to people | Mark solved troubleshooting topics as such, selecting the correct answer, and follow them to get replies!
Community Standards | Guides & Tutorials | Troubleshooting Section

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author

Thanks a bunch for your comments everyone! I actually ran the sfc /scannow command and it found some corrupt files. I'll probably just leave it for now and really dig into it if it happens again.

 

Thanks again!

Link to comment
Share on other sites
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing Troubleshooting

×