cancel
Showing results for 
Search instead for 
Did you mean: 

Drivers & Software

rattz
Adept I

RX550 BSOD Memory Management

I recently switched my rock solid twin Invidia 9600GT based setup to a single RX550. I'm now getting BSOD errors multiple times per day. During working sessions as well as when switching between users.

BSOD dump file explanation attached - can anyone make clue of this? I have to assume it's related to the card since that's all that's changed. Well, that and adding a Benq 3200U screen off an HDMI that the card is driving.

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


Loading Dump File
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff802`48800000 PsLoadedModuleList = 0xfffff802`48c48210
Debug session time: Fri Oct 18 01:27:42.461 2019 (UTC - 4:00)
System Uptime: 0 days 6:02:10.113
Loading Kernel Symbols
.....................................Page 200574815 too large to be in the dump file.
Page 20014dd14 too large to be in the dump file.
..........................
................................................................
................................................................
...........................
Loading User Symbols
PEB address is NULL !
Loading unloaded module list
.....................
For analysis of this file, run !analyze -v
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 000000000000003f, An inpage operation failed with a CRC error. Parameter 2 contains
the pagefile offset. Parameter 3 contains the page CRC value.
Parameter 4 contains the expected CRC value.
Arg2: 00000000000004d1
Arg3: 00000000000004d1
Arg4: 000000006d952c5e

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


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: SKU

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 3802

BIOS_DATE: 03/15/2018

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: Z170-A

BASEBOARD_VERSION: Rev 1.xx

DUMP_TYPE: 1

BUGCHECK_P1: 3f

BUGCHECK_P2: 4d1

BUGCHECK_P3: 4d1

BUGCHECK_P4: 6d952c5e

ADDITIONAL_DEBUG_TEXT: Memory Manager detected corruption of a pagefile page while performing an in-page operation.
The data read from storage does not match the original data written.
This indicates the data was corrupted by the storage stack, or device hardware.


BUGCHECK_STR: 0x1a_3f

CPU_COUNT: 8

CPU_MHZ: fa8

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: C6'00000000 (cache) C6'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: MemCompression

CURRENT_IRQL: 2

PAGE_HASH_ERRORS_DETECTED: 1

ANALYSIS_SESSION_HOST: DESKTOP-V2ITCG2

ANALYSIS_SESSION_TIME: 10-18-2019 08:14:57.0059

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

LAST_CONTROL_TRANSFER: from fffff80248a63d96 to fffff802489c1220

STACK_TEXT:
ffff988f`fbe4f2f8 fffff802`48a63d96 : 00000000`0000001a 00000000`0000003f 00000000`000004d1 00000000`000004d1 : nt!KeBugCheckEx
ffff988f`fbe4f300 fffff802`4888df32 : ffff8802`8e087030 ffffffff`ffffffff 00000000`00000000 ffff8802`8e087120 : nt!MiValidatePagefilePageHash+0x10176a
ffff988f`fbe4f3e0 fffff802`4888d47d : 00000000`00000002 ffff988f`00000000 ffff988f`fbe4f598 fffff802`00000000 : nt!MiWaitForInPageComplete+0x472
ffff988f`fbe4f4f0 fffff802`48872f9b : 00000000`c0033333 00000000`00000000 000001ce`64f70000 00000000`00000001 : nt!MiIssueHardFault+0x1ad
ffff988f`fbe4f5f0 fffff802`488ff9d4 : fffffbfd`feff7000 ffff8802`8a850540 00000000`00000000 000001ce`64f70000 : nt!MmAccessFault+0x40b
ffff988f`fbe4f790 fffff802`48890a9c : 00000000`00000001 fffffb80`e7327b80 ffff988f`fbe4f920 fffffbfd`feff77f8 : nt!MiFaultInProbeAddress+0xbc
ffff988f`fbe4f840 fffff802`488ff05e : ffff8802`87120180 ffff988f`fbe4f920 ffff988f`fbe4f989 ffff8802`f0154990 : nt!MiLockPageLeafPageTable+0x15c
ffff988f`fbe4f8b0 fffff802`4895576c : ffff988f`fbe4f989 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiProbeLeafFrame+0x12
ffff988f`fbe4f8e0 fffff802`48946d89 : 00000000`00040000 fffff802`48848563 ffff8802`900818d0 00000000`00000000 : nt!MmStoreProbeAndLockPages+0x9c
ffff988f`fbe4f9f0 fffff802`4894776e : 00000000`00040000 00000000`00000000 ffff988f`fbe4fa60 ffff8802`87120080 : nt!SmKmProbeAndLockAddress+0x5d
ffff988f`fbe4fa20 fffff802`4892c431 : 00000000`00040000 00000000`00000004 000001ce`64f70000 00000000`00020000 : nt!SmKmStoreHelperCommandProcess+0xa2
ffff988f`fbe4fa90 fffff802`4892a725 : ffff8802`e0ee8080 00000000`00000080 fffff802`4892c3d0 0000246f`b19bbfff : nt!SmKmStoreHelperWorker+0x61
ffff988f`fbe4fb10 fffff802`489c886a : ffffbc80`eaac0180 ffff8802`e0ee8080 fffff802`4892a6d0 00000000`00000246 : nt!PspSystemThreadStartup+0x55
ffff988f`fbe4fb60 00000000`00000000 : ffff988f`fbe50000 ffff988f`fbe49000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


THREAD_SHA1_HASH_MOD_FUNC: d627376e0006f896a5bb34a3fddea97d67228383

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 2c06a9d9b00207c458754cf3da271943887a6c12

THREAD_SHA1_HASH_MOD: 7f608ac2fbce9034a3386b1d51652e4911d30234

SYMBOL_NAME: PAGE_HASH_ERRORS_INPAGE

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .thread ; .cxr ; kb

FOLLOWUP_NAME: MachineOwner

BUCKET_ID: PAGE_HASH_ERRORS_0x1a_3f

DEFAULT_BUCKET_ID: PAGE_HASH_ERRORS_0x1a_3f

PRIMARY_PROBLEM_CLASS: PAGE_HASH_ERRORS_0x1a_3f

FAILURE_BUCKET_ID: PAGE_HASH_ERRORS_0x1a_3f

TARGET_TIME: 2019-10-18T05:27:42.000Z

OSBUILD: 18362

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: unknown_date

BUILDDATESTAMP_STR: 190318-1202

BUILDLAB_STR: 19h1_release

BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME: 23c2

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:page_hash_errors_0x1a_3f

FAILURE_ID_HASH: {6a2d4548-0eec-578d-e8f1-9e2239aa9a00}

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

*** Memory manager detected 1 instance(s) of corrupted pagefilepage(s) while performing in-page operations.

Tags (2)
0 Likes
9 Replies
pokester
MVP

Re: RX550 BSOD Memory Management

When you installed the new card did you uninstall the old Nvidia software first? Of just power it off and put a new card in and install it's driver? I would suggest you run DDU from wagnardsoft_com, follow it's included instructions and then re-install the AMD driver again. Report back if this does not help.

Good Luck!

rattz
Adept I

Re: RX550 BSOD Memory Management

You know it - powered off, took out the old, in with the new, install drivers!

I just completed running through the full DDU uninstall of both NVidia and AMD in safe mode, reinstalled AMD, then reconnected to the web.

Will see if that makes a difference - fingers crossed. I'll be sure to report back here - hopefully not for a few days!

rattz
Adept I

Re: RX550 BSOD Memory Management

Sadly ... another crash last night. Given that the graphics card was the only significant change, am I safe to assume it's the card causing this? Is there anything specific in the crash dump that is a smoking gun?

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 000000000000003f, An inpage operation failed with a CRC error. Parameter 2 contains
the pagefile offset. Parameter 3 contains the page CRC value.
Parameter 4 contains the expected CRC value.
Arg2: 0000000000004351
Arg3: 0000000000004351
Arg4: 00000000eb000105

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


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: SKU

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 3802

BIOS_DATE: 03/15/2018

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: Z170-A

BASEBOARD_VERSION: Rev 1.xx

DUMP_TYPE: 1

BUGCHECK_P1: 3f

BUGCHECK_P2: 4351

BUGCHECK_P3: 4351

BUGCHECK_P4: eb000105

ADDITIONAL_DEBUG_TEXT: Memory Manager detected corruption of a pagefile page while performing an in-page operation.
The data read from storage does not match the original data written.
This indicates the data was corrupted by the storage stack, or device hardware.


BUGCHECK_STR: 0x1a_3f

CPU_COUNT: 8

CPU_MHZ: fa8

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: C6'00000000 (cache) C6'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: MemCompression

CURRENT_IRQL: 2

PAGE_HASH_ERRORS_DETECTED: 1

ANALYSIS_SESSION_HOST: DESKTOP-V2ITCG2

ANALYSIS_SESSION_TIME: 10-19-2019 09:26:34.0735

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

TRAP_FRAME: fffffd0e9c6c6950 -- (.trap 0xfffffd0e9c6c6950)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffa3890fbe1080
rdx=ffffcf83b2ad1018 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80045439bf7 rsp=fffffd0e9c6c6ae0 rbp=0000000000000000
r8=fffffd0e9c6c6b28 r9=0000000000000001 r10=ffffa388a54362c0
r11=fffffd0e9c6c6c50 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!ExAcquirePushLockExclusiveEx+0x107:
fffff800`45439bf7 f0480fba2e00 lock bts qword ptr [rsi],0 ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80045663d96 to fffff800455c1220

STACK_TEXT:
fffffd0e`9c6c5a08 fffff800`45663d96 : 00000000`0000001a 00000000`0000003f 00000000`00004351 00000000`00004351 : nt!KeBugCheckEx
fffffd0e`9c6c5a10 fffff800`4548df32 : ffffa389`04c815b0 ffffffff`ffffffff 00000000`00000000 ffffa389`04c816a0 : nt!MiValidatePagefilePageHash+0x10176a
fffffd0e`9c6c5af0 fffff800`4548d47d : 00000000`00000002 fffffd0e`00000000 fffffd0e`9c6c5ca8 fffff800`00000000 : nt!MiWaitForInPageComplete+0x472
fffffd0e`9c6c5c00 fffff800`45472f9b : 00000000`c0033333 00000000`00000000 000001d1`cf01b910 00000000`00000000 : nt!MiIssueHardFault+0x1ad
fffffd0e`9c6c5d00 fffff800`455cf320 : ffffcf83`b2a6a790 fffffd0e`9c6c5ea8 fffffd0e`9c6c62c8 00000000`00000000 : nt!MmAccessFault+0x40b
fffffd0e`9c6c5ea0 fffff800`4555e150 : ffffe101`9d210000 ffffa388`ad4d2050 fffff800`4545cfc0 ffffe101`9d210000 : nt!KiPageFault+0x360
fffffd0e`9c6c6038 fffff800`4545cfc0 : ffffe101`9d210000 ffffe101`9d210000 00000000`00000002 000001d1`cf01b910 : nt!RtlDecompressBufferXpressLz+0x50
fffffd0e`9c6c6050 fffff800`4555fed9 : 00000000`00000000 ffffa389`00000004 00000000`00000000 ffffa388`ad4d3788 : nt!RtlDecompressBufferEx+0x60
fffffd0e`9c6c60a0 fffff800`4555fd64 : 00000000`00000004 fffffd0e`9c6c62b0 00000000`00000000 00000000`0000023c : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x155
fffffd0e`9c6c6180 fffff800`4555fbe2 : 00000000`00000001 00000000`0000b910 ffffa388`0000b910 ffffa389`00001000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xa0
fffffd0e`9c6c61d0 fffff800`4555fa0b : ffffa389`ffffffff ffffa389`0f6d5000 fffffd0e`9c6c62b0 ffffa389`099e9bd0 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x186
fffffd0e`9c6c6270 fffff800`4555f851 : ffffa389`0f6d5000 00000000`00000000 00000000`00000004 ffffa388`ad4d3788 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xcb
fffffd0e`9c6c6320 fffff800`4555f761 : ffffa388`ad4d2000 ffffa389`099e9bd0 ffffa389`0f6d5000 ffffa388`ad4d39b0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x85
fffffd0e`9c6c63a0 fffff800`45469e18 : ffffa389`0fbe1080 ffffa388`ad4d2000 00000000`00000000 00000000`00000000 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
fffffd0e`9c6c63d0 fffff800`45562cc1 : fffff800`4555f740 fffffd0e`9c6c6480 00000000`00000003 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x78
fffffd0e`9c6c6440 fffff800`4554b941 : fffffd0e`9c6c6540 fffff800`4598db78 ffffa388`ad4d2000 fffffd0e`9c6c6690 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xcd
fffffd0e`9c6c6510 fffff800`4554b527 : 00000000`0000000c ffffa388`ad4d2000 fffffd0e`9c6c65c0 ffffa389`099e9bd0 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1a5
fffffd0e`9c6c6560 fffff800`45561fd3 : 00000000`0000000c ffffa389`099e9bd0 00000000`00000001 00000000`00000001 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xbf
fffffd0e`9c6c65f0 fffff800`455636af : ffffa389`00000001 ffffa389`04c6d400 00000000`00000000 ffffa388`ad4d2000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x167
fffffd0e`9c6c6660 fffff800`4548e05b : fffff800`45868d00 00000000`00000001 fffff800`45868dc0 fffff800`45474ee6 : nt!SmPageRead+0x33
fffffd0e`9c6c66b0 fffff800`4548d759 : 00000000`00000002 fffffd0e`9c6c6740 fffffd0e`9c6c68a8 ffffdfef`f3e0eca8 : nt!MiIssueHardFaultIo+0x117
fffffd0e`9c6c6700 fffff800`45472f9b : 00000000`c0033333 00000000`00000000 ffffcf83`b2ad1018 ffffcf83`b2ad1018 : nt!MiIssueHardFault+0x489
fffffd0e`9c6c67b0 fffff800`455cf320 : ffffa389`0fb57550 fffff800`43451459 00000000`00000000 00000000`00000001 : nt!MmAccessFault+0x40b
fffffd0e`9c6c6950 fffff800`45439bf7 : ffffa389`0fbe1080 ffffcf83`b2ad1018 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x360
fffffd0e`9c6c6ae0 fffff800`4548a126 : ffffa389`0fbe1080 00000000`00000000 00000000`00000002 ffffcf83`b1151160 : nt!ExAcquirePushLockExclusiveEx+0x107
fffffd0e`9c6c6b20 fffff800`45a20641 : ffffa389`020d6290 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MI_LOCK_RELOCATIONS_EXCLUSIVE+0x22
fffffd0e`9c6c6b50 fffff800`45a2022e : 00000000`00000000 fffffd0e`9c6c6e20 ffffa389`0fbe1080 00000000`00000000 : nt!MiRelocateImageAgain+0x5d
fffffd0e`9c6c6be0 fffff800`45a1fcc6 : 00000000`00000002 fffffd0e`00000000 ffffa389`0fb57550 fffffd0e`9c6c6e20 : nt!MiValidateExistingImage+0x66
fffffd0e`9c6c6c80 fffff800`459da493 : ffffa389`0fb57550 fffffd0e`9c6c6e20 ffffa389`0fbe1080 ffffa389`0fb57550 : nt!MiShareExistingControlArea+0xc2
fffffd0e`9c6c6cb0 fffff800`459da8c4 : ffffa389`020d6290 00000000`00000000 ffffa389`0fb57550 00000000`00000000 : nt!MiCreateImageOrDataSection+0x1a3
fffffd0e`9c6c6da0 fffff800`459d9f1f : 00000000`11000000 fffffd0e`9c6c7111 00000000`00000000 00000000`00000002 : nt!MiCreateSection+0xf4
fffffd0e`9c6c6f20 fffff800`459d9cb0 : fffffd0e`9c6c7178 fffffd0e`00000005 fffffd0e`9c6c70e8 fffff800`4549d906 : nt!MiCreateSectionCommon+0x1ff
fffffd0e`9c6c7000 fffff800`45a43870 : 00000000`00000900 ffffffff`ffe91ca0 00000000`00000020 ffffffff`80008a28 : nt!NtCreateSection+0x60
fffffd0e`9c6c7070 fffff800`45a43afc : 00000000`00000060 00000000`00000000 00000000`00000000 ffffa389`11000000 : nt!PfpFileBuildReadSupport+0x1cc
fffffd0e`9c6c7170 fffff800`45ac1f3e : ffffcf83`00000000 fffffd0e`00000074 ffffcf84`00000000 ffffcf83`00000006 : nt!PfpPrefetchFilesTrickle+0x138
fffffd0e`9c6c7260 fffff800`45ac1bbd : ffffcf84`14f86000 ffffcf84`14f86000 fffffd0e`9c6c7480 00000000`00000000 : nt!PfpPrefetchRequestPerform+0x2b6
fffffd0e`9c6c73d0 fffff800`459ffed6 : 00000000`00000001 00000000`00000001 ffffcf84`14f86000 ffffa388`b15c28e0 : nt!PfpPrefetchRequest+0x129
fffffd0e`9c6c7450 fffff800`459ff064 : 00000000`00000000 00000000`00000000 ffffa388`ad331160 fffffd0e`9c6c7601 : nt!PfSetSuperfetchInformation+0x16e
fffffd0e`9c6c7550 fffff800`455d2b15 : ffffa389`0fbe1080 0000003b`00000001 0000003b`0f47fb00 fffffd0e`9c6c7a80 : nt!NtSetSystemInformation+0x294
fffffd0e`9c6c7a00 00007ffe`221bf534 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
0000003b`0f47f948 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`221bf534


THREAD_SHA1_HASH_MOD_FUNC: b0f37d33d831f7e7b06df735409c5cc5f4273ab1

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 8e43038369b2cfc9a984f20cd5be5ba70a7b018a

THREAD_SHA1_HASH_MOD: bdb2db9ed9fa84ae2bc0df3e54fb8a634a1593e3

SYMBOL_NAME: PAGE_HASH_ERRORS_INPAGE

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .thread ; .cxr ; kb

FOLLOWUP_NAME: MachineOwner

BUCKET_ID: PAGE_HASH_ERRORS_0x1a_3f

DEFAULT_BUCKET_ID: PAGE_HASH_ERRORS_0x1a_3f

PRIMARY_PROBLEM_CLASS: PAGE_HASH_ERRORS_0x1a_3f

FAILURE_BUCKET_ID: PAGE_HASH_ERRORS_0x1a_3f

TARGET_TIME: 2019-10-19T04:12:23.000Z

OSBUILD: 18362

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: unknown_date

BUILDDATESTAMP_STR: 190318-1202

BUILDLAB_STR: 19h1_release

BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME: 1233

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:page_hash_errors_0x1a_3f

FAILURE_ID_HASH: {6a2d4548-0eec-578d-e8f1-9e2239aa9a00}

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

*** Memory manager detected 1 instance(s) of corrupted pagefilepage(s) while performing in-page operations.

0 Likes
elstaci
MVP

Re: RX550 BSOD Memory Management

To eliminate physically defective RAM MEMORY, run MEMTEST86 for 2-3 passes. If it shows no errors at all then your memory modules are good. Which most likely indicate a driver or hardware issue.

Also run SFC /scannow in a elevated Command Prompt or Powershell to eliminate any Windows corruption.

Also run CHKDSK to verify that the hard drive or SSD is not failing or has bad sectors. According to this website : Fix: Error Performing Inpage Operation - Appuals.com  it could be a corrupted Windows system file(s) or bad hard drive.

I would also update your both your BIOS and Motherboard CHIPSET to the latest versions. Also for AMD Drivers to work correctly Windows needs to be fully updated via Windows Update.

Also make sure your Intel Graphics driver is the latest.

To verify it is the AMD GPU Card or it driver, remove the AMD GPU Card and install the Nvidea GPU card again and see if the BSOD's stop. If it does it verifies that it is either the GPU card or it driver that is causing the BSODs.

Sometimes you need to configure the RX550 power level to 50 on Wattman.

Here is the latest RX550 AMD Driver from AMD Download page: https://www.amd.com/en/support/graphics/radeon-500-series/radeon-rx-500-series/radeon-rx-550 

Here is the previous RX550 Drivers from AMD Download page: https://www.amd.com/en/support/previous-drivers/graphics/radeon-500-series/radeon-rx-500-series/rade... 

rattz
Adept I

Re: RX550 BSOD Memory Management

Wow - great, thanks! 

I just switched the card to another PCI slot - will see if that makes any difference and will also start running though your checklist.

elstaci
MVP

Re: RX550 BSOD Memory Management

From your Dump file that you posted could indicate hard drive failure:

ADDITIONAL_DEBUG_TEXT: Memory Manager detected corruption of a pagefile page while performing an in-page operation.
The data read from storage does not match the original data written.
This indicates the data was corrupted by the storage stack, or device hardware.

0 Likes
pokester
MVP

Re: RX550 BSOD Memory Management

You could have just a simple page file corruption too. Meaning there is NO HARDWARE issue at all. Any hard drive can get a an error in the data and when this happens to the page file it can cause big problems. The flowing shows how to delete the page file and you can enable it again when you are done. It is simple to try and won't harm a thing and is possible it could be your issue based on that dump file. How to delete pagefile.sys in Windows 10? | MyWindowsHub 

You should most certainly run a disk check too. Disk Error Checking: How to run CHKDSK in Windows 10 

I would not start getting too crazy on changing too many things until you do the simple checks first. Changing others can not be the fix and even introduce new issues. 

Also depending on Motherboard not all the PCIe slots run at the same speed. Make sure that 2nd slot runs at full speed.

If you do these things I would honestly suggest you put your old graphics card back in and if all is well again, if so I would suspect your issue is your new card and would return or exchange if possible. 

The most recent thing you did is usually the issue. In your case the GPU. Not to say a hard drive cant fail at any time. As you have your old GPU around I am guessing. I would run it for a couple days and see what happens. Always eliminate the easy and obvious variables first. 

0 Likes
rattz
Adept I

Re: RX550 BSOD Memory Management

Update as I'm sure that you're all on the edge of your seats ...

I ran a CHKDSK against my boot drive (SSD) and found nothing (~2 hours). Haven't run against my pagefile drive yet (separate SSD) since my wife has been using the machine and I can't afford a potential 'days' of downtime if it took that long. Ran 2 passes of MEMTEST - all clear.

But - I think we've had only 1 crash since and seems stable the last couple of days. If it goes again, then I'll run the CHKDSK against the page file. 

I'll report back!

0 Likes
rattz
Adept I

Re: RX550 BSOD Memory Management

CHKDSK on the page file SSD drive reported no errors. And then the machine promptly BSOD about 5 minutes after rebooting. Another page file error.

Checked the page file - wow! I had it set to automatically mange the size - and Windows had allocated 32GB! I reconfigured for a max 4984MB on the boot SSD. This was the 'recommended' size - why would Windows make a system managed size of 32GB and then tell me the recommended size is 5GB?

Will see what happens now ...

0 Likes