ASRock Forums : BSOD after ram upgrade https://forum.asrock.com/ Copyright (c) 2006-2013 Web Wiz Forums - All Rights Reserved. Thu, 16 Apr 2026 12:24:22 +0000 Mon, 31 Jul 2023 08:42:16 +0000 http://blogs.law.harvard.edu/tech/rss Web Wiz Forums 12.04 360 https://forum.asrock.com/RSS_post_feed.asp?TID=25374 <![CDATA[ASRock Forums]]> https://forum.asrock.com/forum_images/web_wiz_forums_black.png https://forum.asrock.com/ <![CDATA[BSOD after ram upgrade : For people with the same problem...]]> https://forum.asrock.com/forum_posts.asp?TID=25374&PID=106809&title=bsod-after-ram-upgrade#106809 Author: xardas228
Subject: 25374
Posted: 31 Jul 2023 at 8:42am

For people with the same problem in the future, I sent the ram for warranty, the new one works fine. Memtest86, Testmem5 and the built-in windows tool didn't show any errors and the ram after warranty replacement with a new one works fine, so these tools don't show all errors.
]]> Mon, 31 Jul 2023 08:42:16 +0000 https://forum.asrock.com/forum_posts.asp?TID=25374&PID=106809&title=bsod-after-ram-upgrade#106809 <![CDATA[BSOD after ram upgrade : Prime 95, Blend test pass 2 hours...]]> https://forum.asrock.com/forum_posts.asp?TID=25374&PID=103176&title=bsod-after-ram-upgrade#103176 Author: xardas228
Subject: 25374
Posted: 30 Jan 2023 at 4:24pm

Prime 95, Blend test pass 2 hours with no errors, Large FFTs test pass 6 hours without errors. I tested 1.25V, 1.3V, AutoVoltage with no XMP 2133Mhz, nothing helped. I tried Driver Verifier, it didn't boot because: ene.sys, dtliteusbbus.sys, droidcam.sys. I deleted Daemon Tools, DroidCam, and the ene.sys file itself because I couldn't figure out what it was related to (Other forums say it's related to RGB control apps, which I never had installed) After all, Driver Verifier worked for ~ 11 hours and no blue screen so I turned it off hoping it might help. Two days later 2 blue screens: PAGE_FAULT_IN_NONPAGED_AREA (50), DRIVER_OVERRAN_STACK_BUFFER (f7)]]> Mon, 30 Jan 2023 16:24:07 +0000 https://forum.asrock.com/forum_posts.asp?TID=25374&PID=103176&title=bsod-after-ram-upgrade#103176 <![CDATA[BSOD after ram upgrade : First, this is the wrong forum,...]]> https://forum.asrock.com/forum_posts.asp?TID=25374&PID=103022&title=bsod-after-ram-upgrade#103022 Author: eccential
Subject: 25374
Posted: 21 Jan 2023 at 1:41am

First, this is the wrong forum, since you have an Intel CPU/Motherboard.
But that's unlikely to be relevant for your particular question.

Most memory test programs just walk patterns (including random data patterns), but are not good at testing timing issues, because that requires memory control to switch mode frequently in the most unusual timings. These tests are useful for defects in DRAM chips (stuck at 0 or 1), but not at finding timing issues.

So I wouldn't consider "passing some memory test programs" as the final say in whether the DIMM is good.

2666MT/s isn't very fast in today's standard, and I see Corsair specs the DIMM at 1.2V. So if default XMP profile isn't reliable, I'd consider it a broken product, assuming it's installed correctly.

It's DDR4, so you open the tab and just push down on the DIMM until it fully seats. No real need for "soft touches" like the newer DDR5 memory.

Go back to normal XMP profile, run Prime95 or something, and my guess is that it'll get errors. And if it does fail, I'd just return it.
]]> Sat, 21 Jan 2023 01:41:09 +0000 https://forum.asrock.com/forum_posts.asp?TID=25374&PID=103022&title=bsod-after-ram-upgrade#103022 <![CDATA[BSOD after ram upgrade : After change to 1.25V still got...]]> https://forum.asrock.com/forum_posts.asp?TID=25374&PID=103021&title=bsod-after-ram-upgrade#103021 Author: xardas228
Subject: 25374
Posted: 20 Jan 2023 at 10:59pm

After change to 1.25V still got BSOD: MEMORY_MANAGEMENT (1a)
I will change the voltage to 1.3 and then try to disable XMP and set it to 2133Mhz, and if that doesn't help then I have no idea what to do next.]]> Fri, 20 Jan 2023 22:59:32 +0000 https://forum.asrock.com/forum_posts.asp?TID=25374&PID=103021&title=bsod-after-ram-upgrade#103021 <![CDATA[BSOD after ram upgrade : Just got new one: Spoiler FAULTY_HARDWARE_CORRUPTED_PAGE...]]> https://forum.asrock.com/forum_posts.asp?TID=25374&PID=103014&title=bsod-after-ram-upgrade#103014 Author: xardas228
Subject: 25374
Posted: 20 Jan 2023 at 8:18am

Just got new one:
Spoiler Spoiler

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: 0000000000000667, physical page number
Arg3: 000001fd1c531910, zero
Arg4: ffffe7004c600000, zero

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 3030

    Key : Analysis.DebugAnalysisManager
    Value: Create

    Key : Analysis.Elapsed.mSec
    Value: 18521

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

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

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

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

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

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

    Key : BlackBox.SmDecompressionFailure.CompressedSize
    Value: 0x667

    Key : BlackBox.SmDecompressionFailure.CompressionFormat
    Value: 0x3

    Key : BlackBox.SmDecompressionFailure.SourceDataHash
    Value: 0xf7ed5c35

    Key : BlackBox.SmDecompressionFailure.SourceDataOffset
    Value: 0x11910

    Key : BlackBox.SmDecompressionFailure.SourcePFN1
    Value: 0x167830

    Key : BlackBox.SmDecompressionFailure.SourcePFN2
    Value: 0xffffffffffffffff

    Key : BlackBox.SmDecompressionFailure.TargetPFN
    Value: 0x7d5949

    Key : Bugcheck.Code.DumpHeader
    Value: 0x12b

    Key : Bugcheck.Code.Register
    Value: 0x12b

    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


FILE_IN_CAB: 012023-16906-01.dmp

BUGCHECK_CODE: 12b

BUGCHECK_P1: ffffffffc00002c4

BUGCHECK_P2: 667

BUGCHECK_P3: 1fd1c531910

BUGCHECK_P4: ffffe7004c600000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: MemCompression

STACK_TEXT:
ffffe60c`bc9470f8 fffff800`25199642     : 00000000`0000012b ffffffff`c00002c4 00000000`00000667 000001fd`1c531910 : nt!KeBugCheckEx
ffffe60c`bc947100 fffff800`2509104d     : 00000000`00000001 00000000`c00002c4 ffffe700`4c600000 00000000`0004c3d9 : nt!ST_STORE<SM_TRAITS>::StDmPageError+0x10a
ffffe60c`bc947160 fffff800`24f51289     : 00000000`00000004 fffff800`24f51642 00000000`00000000 00000000`00000001 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x13fda1
ffffe60c`bc947220 fffff800`24f51bb4     : 00000000`00000001 00000000`00011910 ffffc00d`db09d000 ffffc00d`00004000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xa5
ffffe60c`bc947270 fffff800`24f50fd4     : fffff800`ffffffff ffffc00d`e168f000 ffffe60c`bc947350 ffffc00d`e2679190 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x180
ffffe60c`bc947310 fffff800`24f50ce9     : ffffe700`143e6730 00000000`00000001 00000000`00000000 00000000`00000000 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xc8
ffffe60c`bc9473c0 fffff800`24f50ba1     : ffffc00d`db09d000 ffffc00d`e2679190 ffffc00d`e168f000 ffffc00d`db09e9c0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x85
ffffe60c`bc947440 fffff800`24e96fb8     : ffffc00d`d7b1a080 ffffc00d`db09d000 00000000`00000000 ffffc00d`ed2dfaf0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
ffffe60c`bc947470 fffff800`24f4e61b     : fffff800`24f50b80 ffffe60c`bc947510 00000000`00000003 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x78
ffffe60c`bc9474e0 fffff800`24eee304     : ffffe60c`bc9475e0 00000000`31526d73 00000000`000003ff fffff800`259239c0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xc7
ffffe60c`bc9475b0 fffff800`24eedd38     : 00000000`0000000c 00000000`000003ff ffffe60c`bc947660 fffff800`259239c0 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1ac
ffffe60c`bc947600 fffff800`24f4f647     : 00000000`0000000c 00000000`00000004 ffffc00d`e2679190 ffffc00d`ed2dfaf0 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xc0
ffffe60c`bc947690 fffff800`24f408db     : ffffc00d`00000004 ffffc00d`ed2dfbb0 00000000`00000000 ffffc00d`db09d000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x167
ffffe60c`bc947700 fffff800`24ee4cd0     : 0000007f`00000100 00000000`00000000 ffffe60c`bc947958 fffff800`24ee27a0 : nt!SmPageRead+0x33
ffffe60c`bc947750 fffff800`24ee22fd     : 00000000`00000002 ffffe60c`bc9477e0 ffffe60c`bc947958 ffffc00d`ed2dfaa0 : nt!MiIssueHardFaultIo+0x10c
ffffe60c`bc9477a0 fffff800`24e422b8     : 00000000`c0033333 00000000`00000001 00000005`c23896f0 00000000`00000000 : nt!MiIssueHardFault+0x29d
ffffe60c`bc947860 fffff800`25009cd8     : 00000000`7c4a7716 ffffc00d`dacde080 00000000`00000000 ffffc00d`00000000 : nt!MmAccessFault+0x468
ffffe60c`bc947a00 00000266`9bcbeee8     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x358
0000006f`2b93ce20 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00000266`9bcbeee8


SYMBOL_NAME: nt!ST_STORE<SM_TRAITS>::StDmPageError+10a

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.2486

STACK_COMMAND: .cxr; .ecxr ; 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
---------

What voltage will be good for start testing stability ? 1.25 ?]]> Fri, 20 Jan 2023 08:18:17 +0000 https://forum.asrock.com/forum_posts.asp?TID=25374&PID=103014&title=bsod-after-ram-upgrade#103014 <![CDATA[BSOD after ram upgrade : Increase the voltage to the ram....]]> https://forum.asrock.com/forum_posts.asp?TID=25374&PID=102965&title=bsod-after-ram-upgrade#102965 Author: bjlockie
Subject: 25374
Posted: 18 Jan 2023 at 2:21pm

Increase the voltage to the ram.]]> Wed, 18 Jan 2023 14:21:08 +0000 https://forum.asrock.com/forum_posts.asp?TID=25374&PID=102965&title=bsod-after-ram-upgrade#102965 <![CDATA[BSOD after ram upgrade : I forgot about system specification:Asrock...]]> https://forum.asrock.com/forum_posts.asp?TID=25374&PID=102962&title=bsod-after-ram-upgrade#102962 Author: xardas228
Subject: 25374
Posted: 18 Jan 2023 at 7:17am

I forgot about system specification:
Asrock B460M-HDV
Intel core i3-10400f
Gigabyte 1660 Super
2x16GB Corsair Vengeance 2666Mhz CL16
SilentiumPC Vero L3 600W
Win 10 64bit]]> Wed, 18 Jan 2023 07:17:30 +0000 https://forum.asrock.com/forum_posts.asp?TID=25374&PID=102962&title=bsod-after-ram-upgrade#102962 <![CDATA[BSOD after ram upgrade : HiAfter replacing the ram with...]]> https://forum.asrock.com/forum_posts.asp?TID=25374&PID=102961&title=bsod-after-ram-upgrade#102961 Author: xardas228
Subject: 25374
Posted: 18 Jan 2023 at 7:14am

Hi
After replacing the ram with a larger one, BSOD appears. Ram is tested in memtest and TestMem5. Ram runs on XMP 2666Mhz and is on the QVL list. It's Corsair CMK32GX4M2A2666C16, previous ram wasn't on QVL list and work just fine.
BSODs from last to first:
Spoiler Spoiler

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: ffffc03ffe569020
Arg3: 0000000001000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 2515

    Key : Analysis.DebugAnalysisManager
    Value: Create

    Key : Analysis.Elapsed.mSec
    Value: 5036

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

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

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

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

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

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

    Key : Bugcheck.Code.DumpHeader
    Value: 0x1a

    Key : Bugcheck.Code.Register
    Value: 0x1a

    Key : MemoryManagement.PFN
    Value: 1000

    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


FILE_IN_CAB: 010523-15531-01.dmp

BUGCHECK_CODE: 1a

BUGCHECK_P1: 41792

BUGCHECK_P2: ffffc03ffe569020

BUGCHECK_P3: 1000000

BUGCHECK_P4: 0

MEMORY_CORRUPTOR: ONE_BIT

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: dwm.exe

STACK_TEXT:
ffffee0b`b755f028 fffff801`146c5f8a     : 00000000`0000001a 00000000`00041792 ffffc03f`fe569020 00000000`01000000 : nt!KeBugCheckEx
ffffee0b`b755f030 fffff801`14638ac6     : 00000000`00000000 ffffee0b`b755f600 00000000`00000833 ffffc03f`fe569020 : nt!MiDeleteVa+0x153a
ffffee0b`b755f130 fffff801`14638bdb     : ffffc060`1fff2b48 ffffb006`839c3700 ffffee0b`00000000 ffffee0b`b755f5a0 : nt!MiWalkPageTablesRecursively+0x776
ffffee0b`b755f1d0 fffff801`14638bdb     : ffffc060`300fff90 ffffb006`839c3700 ffffee0b`00000001 ffffee0b`b755f5b0 : nt!MiWalkPageTablesRecursively+0x88b
ffffee0b`b755f270 fffff801`14638bdb     : ffffc060`00000000 ffffb006`839c3700 ffffee0b`00000002 ffffee0b`b755f5c0 : nt!MiWalkPageTablesRecursively+0x88b
ffffee0b`b755f310 fffff801`1460b83b     : 00000000`00000000 ffffb006`839c3700 00000000`00000003 ffffee0b`b755f5d0 : nt!MiWalkPageTablesRecursively+0x88b
ffffee0b`b755f3b0 fffff801`146c4821     : ffffee0b`b755f550 ffffb006`00000000 ffffc03e`00000002 ffffc060`00000000 : nt!MiWalkPageTables+0x36b
ffffee0b`b755f4b0 fffff801`146ceb20     : 00000000`00000001 ffffee0b`00000000 ffffb006`839c3550 ffffb006`83a0c040 : nt!MiDeletePagablePteRange+0x4f1
ffffee0b`b755f7c0 fffff801`14a91749     : ffffb006`89866d40 00000000`00000000 ffffb006`00000000 ffffb006`00000000 : nt!MiDeleteVad+0x360
ffffee0b`b755f8d0 fffff801`14a910f4     : ffffb006`89866d40 ffffb006`84711d30 ffffb006`83a0c040 00000000`00000000 : nt!MiUnmapVad+0x49
ffffee0b`b755f900 fffff801`14a90b93     : ffffb006`898667a0 ffffb006`898667a0 ffffb006`89866d40 ffffb006`839c3080 : nt!MiCleanVad+0x30
ffffee0b`b755f930 fffff801`149dd7fc     : ffffffff`00000000 ffffffff`ffffffff 00000000`00000001 ffffb006`839c3080 : nt!MmCleanProcessAddressSpace+0x137
ffffee0b`b755f9b0 fffff801`14d0b2b2     : fffff801`15125440 ffffb006`839c3080 fffff801`14d0b280 00000000`00000000 : nt!PspRundownSingleProcess+0x20c
ffffee0b`b755fa40 fffff801`14652bc5     : ffffb006`83a0c040 fffff801`14676070 ffffb006`754b08a0 00000000`00000000 : nt!PspProcessRundownWorkerSingle+0x32
ffffee0b`b755fa70 fffff801`14671d85     : ffffb006`83a0c040 00000000`00000080 ffffb006`754cc080 00c7028b`018e0584 : nt!ExpWorkerThread+0x105
ffffee0b`b755fb10 fffff801`14801ed8     : ffffcb01`7c7de180 ffffb006`83a0c040 fffff801`14671d30 01bf00df`003a00cb : nt!PspSystemThreadStartup+0x55
ffffee0b`b755fb60 00000000`00000000     : ffffee0b`b7560000 ffffee0b`b7559000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


MODULE_NAME: hardware

IMAGE_NAME: memory_corruption

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Followup:     MachineOwner
---------

Spoiler Spoiler

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff80550619f8b, Address of the instruction which caused the BugCheck
Arg3: ffff95833e7de5f0, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 3014

    Key : Analysis.DebugAnalysisManager
    Value: Create

    Key : Analysis.Elapsed.mSec
    Value: 6683

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

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

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

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

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

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

    Key : Bugcheck.Code.DumpHeader
    Value: 0x3b

    Key : Bugcheck.Code.Register
    Value: 0x3b

    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


FILE_IN_CAB: 011723-19203-01.dmp

BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80550619f8b

BUGCHECK_P3: ffff95833e7de5f0

BUGCHECK_P4: 0

CONTEXT: ffff95833e7de5f0 -- (.cxr 0xffff95833e7de5f0)
rax=ffff81069b367080 rbx=0005781120ead7cc rcx=0005781120ead2b4
rdx=000000006e457350 rsi=ffff8106913dc080 rdi=0005781120ead2e4
rip=fffff80550619f8b rsp=ffff95833e7deff0 rbp=ffff95833e7dfa80
r8=ffff95833e7df030 r9=7fff81068f3f74b8 r10=7ffffffffffffffc
r11=00000000000000b0 r12=0000000000000000 r13=0000000000000000
r14=ffff81068f3f7080 r15=ffff81068f3f7660
iopl=0        nv up ei pl nz na po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b             efl=00050207
nt!ObReferenceObjectSafeWithTag+0xb:
fffff805`50619f8b 488b01          mov     rax,qword ptr [rcx] ds:002b:00057811`20ead2b4=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: GameOverlayUI.exe

STACK_TEXT:
ffff9583`3e7deff0 fffff805`50a260b7     : ffff8106`9b367568 ffff8106`00000000 ffff8106`00000000 00000000`00000000 : nt!ObReferenceObjectSafeWithTag+0xb
ffff9583`3e7df020 fffff805`50a495f7     : 00000000`00000000 00000000`00010400 00000000`00000000 00000000`00000000 : nt!ExpGetProcessInformation+0xee7
ffff9583`3e7df680 fffff805`50a487a7     : ffff8106`913dc080 00000000`00000000 00000000`00000000 00000000`06b6f800 : nt!ExpQuerySystemInformation+0xd07
ffff9583`3e7df9c0 fffff805`5080d9f5     : 00000000`02460000 ffff8106`94504080 ffff9583`3e7dfa18 ffffffff`ff676980 : nt!NtQuerySystemInformation+0x37
ffff9583`3e7dfa00 00007ffc`1e94d784     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000000`06a6e008 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`1e94d784


SYMBOL_NAME: nt!ObReferenceObjectSafeWithTag+b

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.2486

STACK_COMMAND: .cxr 0xffff95833e7de5f0 ; kb

BUCKET_ID_FUNC_OFFSET: b

FAILURE_BUCKET_ID: AV_nt!ObReferenceObjectSafeWithTag

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {1c61df56-75ba-a141-16b9-d16181e7aa96}

Followup:     MachineOwner
---------

Spoiler Spoiler

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffff908401cae250, memory referenced.
Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE.
     bit 1 is set if the fault was due to a write, clear if a read.
     bit 3 is set if the processor decided the fault was due to a corrupted PTE.
     bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
     - ARM64: bit 1 is set if the fault was due to a write, clear if a read.
     bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff80703bd2eb1, If non-zero, the instruction address which referenced the bad memory
     address.
Arg4: 0000000000000002, (reserved)

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


KEY_VALUES_STRING: 1

    Key : AV.Type
    Value: Read

    Key : Analysis.CPU.mSec
    Value: 5015

    Key : Analysis.DebugAnalysisManager
    Value: Create

    Key : Analysis.Elapsed.mSec
    Value: 7552

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

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

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

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

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

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

    Key : Bugcheck.Code.DumpHeader
    Value: 0x50

    Key : Bugcheck.Code.Register
    Value: 0x50

    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


FILE_IN_CAB: 011723-13812-01.dmp

BUGCHECK_CODE: 50

BUGCHECK_P1: ffff908401cae250

BUGCHECK_P2: 0

BUGCHECK_P3: fffff80703bd2eb1

BUGCHECK_P4: 2

READ_ADDRESS: fffff807044fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
ffff908401cae250

MM_INTERNAL_CODE: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: svchost.exe

TRAP_FRAME: ffff830d0b45e8b0 -- (.trap 0xffff830d0b45e8b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000006d rbx=0000000000000000 rcx=ffffb40d5caf7040
rdx=ffff908401cae250 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80703bd2eb1 rsp=ffff830d0b45ea48 rbp=0000000000000000
r8=000000000000007f r9=0000000000000000 r10=fffff80703bd2ea0
r11=ffff830d0b45eac0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0        nv up ei pl nz na pe nc
nt!wcsncmp+0x11:
fffff807`03bd2eb1 663b02          cmp     ax,word ptr [rdx] ds:ffff9084`01cae250=????
Resetting default scope

STACK_TEXT:
ffff830d`0b45e608 fffff807`03c36e57     : 00000000`00000050 ffff9084`01cae250 00000000`00000000 ffff830d`0b45e8b0 : nt!KeBugCheckEx
ffff830d`0b45e610 fffff807`03a42250     : ffffb40d`00000005 00000000`00000000 ffff830d`0b45e930 00000000`00000000 : nt!MiSystemFault+0x1d6bd7
ffff830d`0b45e710 fffff807`03c09cd8     : 00000000`00000080 ffffb40d`4a002290 00000000`00000037 00000000`00000350 : nt!MmAccessFault+0x400
ffff830d`0b45e8b0 fffff807`03bd2eb1     : fffff807`08df362c 00000000`00000000 00000000`00000001 00000000`00000001 : nt!KiPageFault+0x358
ffff830d`0b45ea48 fffff807`08df362c     : 00000000`00000000 00000000`00000001 00000000`00000001 00000000`41636450 : nt!wcsncmp+0x11
ffff830d`0b45ea50 fffff807`08df3b71     : ffff9084`8b775bb0 ffffb40d`5caf7140 ffffb40d`5caf7040 ffffc511`76636bc4 : pdc!PdcpGetActivationStatsByTask+0x50
ffff830d`0b45eaa0 fffff807`08de5d18     : ffffb40d`52f07720 ffffb40d`5caf7010 00000000`00000003 00000000`00000008 : pdc!PdcReferenceActivationStats+0xa5
ffff830d`0b45ead0 fffff807`08de6d72     : 00000000`c0000001 00000000`00000000 ffffb40d`52f07720 fffff807`03af7906 : pdc!PdcpReferenceActivationInstance+0x98
ffff830d`0b45eb40 fffff807`08dd1619     : ffff830d`0b45f160 ffff830d`0b45ed10 ffff9084`88b4f5c0 ffff830d`0b45f0c8 : pdc!PdcpV2Activation+0x1ce
ffff830d`0b45ebb0 fffff807`08de933b     : ffff830d`00000000 00000062`5f800a01 ffff830d`0b45ed10 00000062`5f800a01 : pdc!PdcV2ActivatorReceive+0x11
ffff830d`0b45ebe0 fffff807`08de8d5f     : ffff830d`0b45f160 ffff830d`0b45ed10 ffff9084`88b4f5c0 00000000`00000000 : pdc!PdcProcessReceivedUserMessage+0x4b
ffff830d`0b45ec10 fffff807`08de87f2     : 00000000`000000a0 ffff830d`0b45f160 00000000`000000a0 00000000`00000000 : pdc!PdcProcessMessage+0x4b3
ffff830d`0b45f060 fffff807`08de8619     : ffffb40d`4bc822a0 ffff9084`82a01e00 ffff9084`82a04480 ffffb40d`00000110 : pdc!PdcpAlpcProcessMessages+0x6a
ffff830d`0b45f4a0 fffff807`03b2278f     : ffffb40d`4bc842c0 ffff9084`88a3f8b0 00000000`000002e0 fffff807`00000000 : pdc!PdcMessageCallback+0x9
ffff830d`0b45f4d0 fffff807`03b226bc     : ffff9084`88a3f8b0 ffffb40d`4bbb4cb0 ffffb40d`4bc842c0 ffffb40d`4bbb4cb0 : nt!ExNotifyWithProcessing+0xc7
ffff830d`0b45f530 fffff807`03e2adec     : ffffffff`00000002 ffffffff`00000000 ffffb40d`4bc842c0 ffff9084`95b69c70 : nt!ExNotifyCallback+0xc
ffff830d`0b45f560 fffff807`03e2a4a4     : ffffb40d`00000000 00000000`00000000 ffff9084`95b69c70 fffff807`03ed440f : nt!AlpcpCompleteDispatchMessage+0x8bc
ffff830d`0b45f610 fffff807`03e2a17f     : 00000000`00020000 00000076`39a7d960 00000000`00000000 00000000`00000000 : nt!AlpcpDispatchNewMessage+0x2d4
ffff830d`0b45f670 fffff807`03e2c1dc     : ffff830d`0b45f830 00000076`39a7d960 00000000`00000000 ffffb40d`57d09001 : nt!AlpcpSendMessage+0x9ff
ffff830d`0b45f7b0 fffff807`03e2cbe6     : ffffb40d`55129df0 00000000`00020000 00000076`39a7d960 00000000`00000000 : nt!AlpcpProcessSynchronousRequest+0x31c
ffff830d`0b45f8d0 fffff807`03c0d9f5     : ffffb40d`57d09080 ffff830d`0b45fa80 00000076`39a7d878 ffff830d`0b45f9a8 : nt!NtAlpcSendWaitReceivePort+0x1d6
ffff830d`0b45f990 00007ffd`8c64e234     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000076`39a7d858 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`8c64e234


SYMBOL_NAME: pdc!PdcpGetActivationStatsByTask+50

MODULE_NAME: pdc

IMAGE_NAME: pdc.sys

IMAGE_VERSION: 10.0.19041.1052

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 50

FAILURE_BUCKET_ID: AV_R_(null)_pdc!PdcpGetActivationStatsByTask

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {4a3012ad-fbed-e911-5d10-6b73333e9486}

Followup:     MachineOwner
---------
]]> Wed, 18 Jan 2023 07:14:52 +0000 https://forum.asrock.com/forum_posts.asp?TID=25374&PID=102961&title=bsod-after-ram-upgrade#102961