Hello guys,
I was downloading a steam game and my PC suddenly crashed. I have 3 monitors, not sure if that has something to do with it. Logs are attached.
My PC specs:
5900x
32GB Gskill ram overclocked to 3600Hz
AMD 6900XT
noctua NH d15
super flower 850W psu
Asus x570 TUF mobo
Windows version 22H2
file link: debug.zip - Google Drive
Remove your memory overclock and/or just keep an eye on it. One error, not so much to worry about. more, may show an issue, but you do have the ram overclocked.
11: kd> !analyze -v
*******************************************************************************
* *
* 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: 00000000000005cc, physical page number
Arg3: 0000022664db6d40, zero
Arg4: ffffa0014f4e2000, zero
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2765
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 4750
Key : Analysis.Init.CPU.mSec
Value: 202
Key : Analysis.Init.Elapsed.mSec
Value: 4632
Key : Analysis.Memory.CommitPeak.Mb
Value: 74
Key : BlackBox.SmDecompressionFailure.CompressedSize
Value: 0x5cc
Key : BlackBox.SmDecompressionFailure.CompressionFormat
Value: 0x3
Key : BlackBox.SmDecompressionFailure.SourceDataHash
Value: 0xbc4806fd
Key : BlackBox.SmDecompressionFailure.SourceDataOffset
Value: 0x16d40
Key : BlackBox.SmDecompressionFailure.SourcePFN1
Value: 0x749f31
Key : BlackBox.SmDecompressionFailure.SourcePFN2
Value: 0x3ed930
Key : BlackBox.SmDecompressionFailure.TargetPFN
Value: 0x56f9fa
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 12b
BUGCHECK_P1: ffffffffc00002c4
BUGCHECK_P2: 5cc
BUGCHECK_P3: 22664db6d40
BUGCHECK_P4: ffffa0014f4e2000
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: MemCompression
STACK_TEXT:
ffff9c01`4931b818 fffff804`29799752 : 00000000`0000012b ffffffff`c00002c4 00000000`000005cc 00000226`64db6d40 : nt!KeBugCheckEx
ffff9c01`4931b820 fffff804`2963cdd1 : 00000000`00000000 00000000`c00002c4 ffffa001`4f4e2000 00000000`00000000 : nt!ST_STORE<SM_TRAITS>::StDmPageError+0x10a
ffff9c01`4931b880 fffff804`29470c91 : 00000000`00000004 fffff804`294707fa 00000000`00000000 00000000`00000001 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x1cc11d
ffff9c01`4931b940 fffff804`29470560 : 00000000`00000001 00000000`00016d40 00000000`00000000 ffff8789`000fe000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xa5
ffff9c01`4931b990 fffff804`2947115c : ffff8789`ffffffff ffff8789`f1d2b000 ffff9c01`4931ba70 ffff8789`f82b5310 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x180
ffff9c01`4931ba30 fffff804`294713d1 : 00000000`00000001 fffff804`00000000 00000000`00000000 fffff804`29470a81 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xc8
ffff9c01`4931bae0 fffff804`29546b8e : ffff8789`f67bc000 ffff8789`f82b5310 ffff8789`f1d2b000 ffff8789`f67bd9c0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x85
ffff9c01`4931bb60 fffff804`29471d85 : ffff8789`fdbce0c0 00000000`00000080 fffff804`29546a40 ffff9c01`4926d368 : nt!SMKM_STORE<SM_TRAITS>::SmStReadThread+0x14e
ffff9c01`4931bbd0 fffff804`29601ed8 : ffffa001`31f96180 ffff8789`fdbce0c0 fffff804`29471d30 6d533c18`ac704104 : nt!PspSystemThreadStartup+0x55
ffff9c01`4931bc20 00000000`00000000 : ffff9c01`4931c000 ffff9c01`49315000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: nt!ST_STORE<SM_TRAITS>::StDmPageError+10a
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.2364
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 10a
FAILURE_BUCKET_ID: 0x12B_c00002c4_StCtDecompressFailed_nt!ST_STORE_SM_TRAITS_::StDmPageError
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {c6a6bb4d-3b77-dff6-2d9b-75f5d0f61a50}
Followup: MachineOwner
---------
thank you good sir, I use AMD so it was recommended by reddit to Overclock ram to 3600, the default was 3200. I can put it back to default then.
Hello,
this happened again, not sure if my RAM is going bad. Can you check 1 more time. I did not want to make a new thread if its the same issue. BSOD_file.zip - Google Drive
@tomdsr
i dont think ive ever seen this bug check before (see below).
first, open an elevated command prompt and type "sfc /scannow"
if that finds issues, see here.
if the above finds no issues, run memtest to test the memory and/or run driver verifier to see if a driver is not playing nice. Please make sure to read the tutorial for verifier thoroughly as it will tell you how to get back to normal if verifier bluescreens before booting (cant turn it off that way if it wont boot).
19: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
QUOTA_UNDERFLOW (21)
This bugcheck occurs if a kernel component mishandles quota charges and
returns more quota than was previously charged to a particular quota block.
Arguments:
Arg1: 0000000000000000, The process (if any) that was initially charged.
Arg2: 0000000000000001, The quota type in question (paged pool, nonpaged pool, etc.)
Arg3: 0000000010f004f1, The initial charge amount to return.
Arg4: 00000000081934dd, The remaining (unreturned) charge.
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1906
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 12258
Key : Analysis.Init.CPU.mSec
Value: 265
Key : Analysis.Init.Elapsed.mSec
Value: 32743
Key : Analysis.Memory.CommitPeak.Mb
Value: 74
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 21
BUGCHECK_P1: 0
BUGCHECK_P2: 1
BUGCHECK_P3: 10f004f1
BUGCHECK_P4: 81934dd
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: explorer.exe
STACK_TEXT:
ffff8105`bc6d77a8 fffff804`3902a131 : 00000000`00000021 00000000`00000000 00000000`00000001 00000000`10f004f1 : nt!KeBugCheckEx
ffff8105`bc6d77b0 fffff804`392375d6 : 00000000`00000000 ffff9e8a`c312a030 ffff9e8a`986ebf00 ffff9e8a`a66abd40 : nt!PspReturnQuota+0x1fe081
ffff8105`bc6d7810 fffff804`39237468 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObpFreeObject+0x116
ffff8105`bc6d7870 fffff804`38e173f7 : 00000000`00000000 00000000`00000000 ffff8105`bc6d79f9 ffff9e8a`c312a060 : nt!ObpRemoveObjectRoutine+0x88
ffff8105`bc6d78d0 fffff804`392249a9 : ffff9e8a`c312a030 ffff8906`4affb390 ffff8906`4affb390 ffff8906`4affb390 : nt!ObfDereferenceObjectWithTag+0xc7
ffff8105`bc6d7910 fffff804`392287dc : 00000000`000040e4 fffff804`3928de25 ffff2dc8`68a73c62 00000000`2300edd8 : nt!ObCloseHandleTableEntry+0x6c9
ffff8105`bc6d7a50 fffff804`3900d9f8 : 00000000`21fe4600 ffff8105`bc6d7b40 ffff8105`bc6d7b40 ffff9e8a`00000000 : nt!NtClose+0xec
ffff8105`bc6d7ac0 00007ffc`de50d2a4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`2300f0b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`de50d2a4
SYMBOL_NAME: nt!PspReturnQuota+1fe081
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.2486
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 1fe081
FAILURE_BUCKET_ID: 0x21_nt!PspReturnQuota
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {e09333c9-b4c4-6d2b-abd9-55f32ac61379}
Followup: MachineOwner
---------
Hi, I did the elevated command promt and did the sfc scan and it found some errors, but it said successfully fixed errors. Then I tried to do that again and checked health and it said healthy from your link. I also ran a memtest using TM5 with ABSOLUT.cfg and it ran fine no errors. I have not done driver verifier yet, I will do that next and report back
Hello, could you analyze 1 more file? This just happened, I was using FOXIT pdf reader. I ran SFC and it sometimes finds errors and then fixes itself. driver verifier no problems
-PC-(2023-02-22_13-02-44).zip - Google Drive @tomdsr
faulty hardware corrupted page
17: kd> !analyze -v
*******************************************************************************
* *
* 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: 0000000000000948, physical page number
Arg3: 000001970798abb0, zero
Arg4: ffffe40194aa0000, zero
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2109
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 17013
Key : Analysis.Init.CPU.mSec
Value: 217
Key : Analysis.Init.Elapsed.mSec
Value: 2094
Key : Analysis.Memory.CommitPeak.Mb
Value: 73
Key : BlackBox.SmDecompressionFailure.CompressedSize
Value: 0x948
Key : BlackBox.SmDecompressionFailure.CompressionFormat
Value: 0x3
Key : BlackBox.SmDecompressionFailure.SourceDataHash
Value: 0xd7dd0184
Key : BlackBox.SmDecompressionFailure.SourceDataOffset
Value: 0xabb0
Key : BlackBox.SmDecompressionFailure.SourcePFN1
Value: 0x145237
Key : BlackBox.SmDecompressionFailure.SourcePFN2
Value: 0x3ee036
Key : BlackBox.SmDecompressionFailure.TargetPFN
Value: 0x40e4c
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 12b
BUGCHECK_P1: ffffffffc00002c4
BUGCHECK_P2: 948
BUGCHECK_P3: 1970798abb0
BUGCHECK_P4: ffffe40194aa0000
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: MemCompression
STACK_TEXT:
ffffa081`e4efd1b8 fffff802`22d99542 : 00000000`0000012b ffffffff`c00002c4 00000000`00000948 00000197`0798abb0 : nt!KeBugCheckEx
ffffa081`e4efd1c0 fffff802`22c48a85 : 00000000`00000001 00000000`c00002c4 ffffe401`94aa0000 00000000`00040000 : nt!ST_STORE<SM_TRAITS>::StDmPageError+0x10a
ffffa081`e4efd220 fffff802`22a60819 : 00000000`00000004 fffff802`22a60bd2 00000000`00000000 00000000`00000001 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x1e8249
ffffa081`e4efd2e0 fffff802`22a61144 : 00000000`00000001 00000000`0000abb0 00000000`00000000 ffffba0a`00010000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xa5
ffffa081`e4efd330 fffff802`22a60564 : 00000000`ffffffff ffffba0a`151e8000 ffffa081`e4efd410 ffffba0a`014ec950 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x180
ffffa081`e4efd3d0 fffff802`22a60279 : ffffe401`7dce6730 00000000`00000001 00000000`00000000 00000000`00000000 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xc8
ffffa081`e4efd480 fffff802`22a60131 : ffffba09`ffe97000 ffffba0a`014ec950 ffffba0a`151e8000 ffffba09`ffe989c0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x85
ffffa081`e4efd500 fffff802`22af9a48 : ffffba09`fe0530c0 ffffba09`ffe97000 00000000`00000000 ffffba09`f1acd780 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
ffffa081`e4efd530 fffff802`22a5dbab : fffff802`22a60110 ffffa081`e4efd5d0 00000000`00000003 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x78
ffffa081`e4efd5a0 fffff802`22b50d34 : ffffa081`e4efd6a0 00000000`31526d73 00000000`000003ff fffff802`235229c0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xc7
ffffa081`e4efd670 fffff802`22b50768 : 00000000`0000000c 00000000`000003ff ffffa081`e4efd720 fffff802`235229c0 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1ac
ffffa081`e4efd6c0 fffff802`22a5ebd7 : 00000000`0000000c 00000000`00000010 ffffba0a`014ec950 ffffba09`f1acd780 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xc0
ffffa081`e4efd750 fffff802`22a4ee0b : ffffba09`00000010 ffffba09`f1acd840 00000000`00000000 ffffba09`ffe97000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x167
ffffa081`e4efd7c0 fffff802`22b47700 : 0000007f`00000100 00000000`00000000 ffffa081`e4efda18 fffff802`22b451f0 : nt!SmPageRead+0x33
ffffa081`e4efd810 fffff802`22b44d4d : 00000000`00000002 ffffa081`e4efd8a0 ffffa081`e4efda18 ffffba09`f1acd730 : nt!MiIssueHardFaultIo+0x10c
ffffa081`e4efd860 fffff802`22aa4dd8 : 00000000`c0033333 00000000`00000001 00000183`d132414f 00000000`00000000 : nt!MiIssueHardFault+0x29d
ffffa081`e4efd920 fffff802`22c09bd8 : 00000000`000c000c ffffa081`e4efdb40 00000183`8e510000 00000000`00000001 : nt!MmAccessFault+0x468
ffffa081`e4efdac0 00007fff`2cb35bb6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x358
00000080`07dfef90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`2cb35bb6
SYMBOL_NAME: nt!ST_STORE<SM_TRAITS>::StDmPageError+10a
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.2604
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 10a
FAILURE_BUCKET_ID: 0x12B_c00002c4_StCtDecompressFailed_nt!ST_STORE_SM_TRAITS_::StDmPageError
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {c6a6bb4d-3b77-dff6-2d9b-75f5d0f61a50}
Followup: MachineOwner
---------
@tomdsr, check the parameters values and check whether they're correct per the description. In this case they're not matching, you can also tell by looking at the stack. This is not a memory manager error, but a compressed store manager error for which the parameters are different which don't match the description.
The first parameter is a NTSTATUS error indicating a corrupt file has been detected
Initially, I would be suspicious of RAM and storage drive here first. The RAM would ideally be tested by removing all but one module and see how that goes, then switch slots and see how that goes. Eventually once all slots have been tested and it continues to crash, then use any of the other modules and repeat.Code:17: kd> !error ffffffffc00002c4 Error code: (NTSTATUS) 0xc00002c4 (3221226180) - The system file %1 has become corrupt and has been replaced.
Quote