F5F Stay Refreshed Hardware Desktop Problem with PC lasting three weeks and no clear solution

Problem with PC lasting three weeks and no clear solution

Problem with PC lasting three weeks and no clear solution

O
Ob22007
Member
Find
121
10-31-2024, 04:55 PM
#1
So I have been experiencing grey screens and driver timeout since 22/10/23 and idk what to do. I have been runing the same build for around 5 6 years and it never gave me any problems. Today I experienced a bsod and I am unable to find a solution. i have used ddu many times, reinstalled windows from iso file and ran mem test but no luck. I have stress tested my pc for hours and it didnt give any issue like flickering or crashes. Grey screen suddenly pops up while doing normal work and I am unable to do anything except to do a hard reset.
In Reliability Index, found hardware issue like livekernal 117. livekernal 141, livekernal 193, livekernal 1b0, Bluescreen 1a.
I have done ddu, reinstalled gpu drivers(old and new) millions of times, ran mem test, ran memory diagnostic, done basic cmd commands, and much more( cant remeber honestly, Did whatever I found but now i am exhausted).
I encountered a bsod which led me to believe that the issue lies with the ram(
Stop Code: Memory_Management)
. here is the minidump file for the bsod and grey screen
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : false
AllowNugetExeUpdate : false
AllowNugetMSCredentialProviderInstall : false
AllowParallelInitializationOfLocalRepositories : true
-- 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.031 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 36
Microsoft ® Windows Debugger Version 10.0.25877.1004 AMD64
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidumps\111123-8078-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 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff806`80e00000 PsLoadedModuleList = 0xfffff806`81a2a2b0
Debug session time: Sat Nov 11 12:57:41.484 2023 (UTC + 5:00)
System Uptime: 0 days 10:37:13.164
Loading Kernel Symbols
..
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.............................................................
................................................................
...................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000d4`b337b018). Type ".hh dbgerr001" for details
Loading unloaded module list
.................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`811fbca0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffbd8f`e159be60=000000000000001a
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000061948, The subtype of the BugCheck.
Arg2: 0000000000000000
Arg3: 0000000000000001
Arg4: 0000000000000000
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2436
Key : Analysis.Elapsed.mSec
Value: 4769
Key : Analysis.IO.Other.Mb
Value: 5
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 20
Key : Analysis.Init.CPU.mSec
Value: 515
Key : Analysis.Init.Elapsed.mSec
Value: 37739
Key : Analysis.Memory.CommitPeak.Mb
Value: 84
Key : Bugcheck.Code.LegacyAPI
Value: 0x1a
Key : Dump.Attributes.AsUlong
Value: 8
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Failure.Bucket
Value: 0x1a_61948_dxgmms2!VIDMM_RECYCLE_MULTIRANGE::Rotate
Key : Failure.Hash
Value: {ec362d5e-ccbe-e8ef-00c8-b53907af7897}
BUGCHECK_CODE: 1a
BUGCHECK_P1: 61948
BUGCHECK_P2: 0
BUGCHECK_P3: 1
BUGCHECK_P4: 0
FILE_IN_CAB: 111123-8078-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: RadeonSoftware
STACK_TEXT:
ffffbd8f`e159be58 fffff806`8123c050 : 00000000`0000001a 00000000`00061948 00000000`00000000 00000000`00000001 : nt!KeBugCheckEx
ffffbd8f`e159be60 fffff806`8105e6d4 : 00000000`00000002 00000000`00000001 00000000`00000001 00000000`00000000 : nt!MiDereferenceIoPages+0x1daa48
ffffbd8f`e159bef0 fffff806`8145ce4f : ffffbd8f`e159c4b8 00000000`00000003 ffffe304`ed2b1990 00000238`211d0000 : nt!MiReplaceRotateWithDemandZero+0x224
ffffbd8f`e159c1a0 fffff806`8c87309a : ffffe304`eb777a60 ffffd201`54e30b80 00000000`00000003 ffffbd8f`e159c580 : nt!MmRotatePhysicalView+0x40f
ffffbd8f`e159c440 fffff806`8c872d81 : ffffd201`648c4310 00000000`746c6644 ffffbd8f`00000003 00000000`00000000 : dxgmms2!VIDMM_RECYCLE_MULTIRANGE::Rotate+0x2c2
ffffbd8f`e159c500 fffff806`8c8646f7 : ffffe304`e8e6a900 ffffd201`652bed60 ffffe304`eb7f3040 fffff806`8103eef4 : dxgmms2!VIDMM_RECYCLE_HEAP_MGR::Rotate+0xb1
ffffbd8f`e159c590 fffff806`8c84e51a : 00000000`00000000 ffffd201`652bed60 ffffd201`00000000 ffffd201`5c37ae90 : dxgmms2!VIDMM_GLOBAL::Rotate+0x7b
ffffbd8f`e159c600 fffff806`8c81f2a1 : ffffd201`652bed60 fffff806`00000001 ffffe304`00000000 ffffe304`ee77b000 : dxgmms2!VIDMM_MEMORY_SEGMENT::TransferToSystem+0x30fba
ffffbd8f`e159c790 fffff806`8c8260bb : ffffe304`ee784c20 ffffbd8f`e159c8e0 ffffe304`ee77b000 00000000`00000000 : dxgmms2!VIDMM_MEMORY_SEGMENT::EvictResource+0xb1
ffffbd8f`e159c7e0 fffff806`8c83c3a8 : ffffe304`ee77b000 ffffe304`ee784c10 ffffe304`ee77b000 ffffe304`ee77b000 : dxgmms2!VIDMM_GLOBAL:
😛
rocessDeferredCommand+0xa9b
ffffbd8f`e159ca00 fffff806`8c846839 : ffffd201`553be500 ffffe304`e3cc5000 00000000`00000000 fffff806`81b27a00 : dxgmms2!VIDMM_WORKER_THREAD::Run+0xb78
ffffbd8f`e159cbe0 fffff806`811265f5 : ffffe304`eb7f3040 fffff806`8c846830 ffffd201`553be500 00000000`00000000 : dxgmms2!VidMmWorkerThreadProc+0x9
ffffbd8f`e159cc10 fffff806`812048d8 : fffff806`7be07180 ffffe304`eb7f3040 fffff806`811265a0 00000000`00000246 : nt!PspSystemThreadStartup+0x55
ffffbd8f`e159cc60 00000000`00000000 : ffffbd8f`e159d000 ffffbd8f`e1597000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: dxgmms2!VIDMM_RECYCLE_MULTIRANGE::Rotate+2c2
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.19041.3205
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 2c2
FAILURE_BUCKET_ID: 0x1a_61948_dxgmms2!VIDMM_RECYCLE_MULTIRANGE::Rotate
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {ec362d5e-ccbe-e8ef-00c8-b53907af7897}
Followup: MachineOwner
---------
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000061948, The subtype of the BugCheck.
Arg2: 0000000000000000
Arg3: 0000000000000001
Arg4: 0000000000000000
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2281
Key : Analysis.Elapsed.mSec
Value: 2275
Key : Analysis.IO.Other.Mb
Value: 5
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 20
Key : Analysis.Init.CPU.mSec
Value: 2953
Key : Analysis.Init.Elapsed.mSec
Value: 42511
Key : Analysis.Memory.CommitPeak.Mb
Value: 85
Key : Bugcheck.Code.LegacyAPI
Value: 0x1a
Key : Dump.Attributes.AsUlong
Value: 8
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Failure.Bucket
Value: 0x1a_61948_dxgmms2!VIDMM_RECYCLE_MULTIRANGE::Rotate
Key : Failure.Hash
Value: {ec362d5e-ccbe-e8ef-00c8-b53907af7897}
BUGCHECK_CODE: 1a
BUGCHECK_P1: 61948
BUGCHECK_P2: 0
BUGCHECK_P3: 1
BUGCHECK_P4: 0
FILE_IN_CAB: 111123-8078-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: RadeonSoftware
STACK_TEXT:
ffffbd8f`e159be58 fffff806`8123c050 : 00000000`0000001a 00000000`00061948 00000000`00000000 00000000`00000001 : nt!KeBugCheckEx
ffffbd8f`e159be60 fffff806`8105e6d4 : 00000000`00000002 00000000`00000001 00000000`00000001 00000000`00000000 : nt!MiDereferenceIoPages+0x1daa48
ffffbd8f`e159bef0 fffff806`8145ce4f : ffffbd8f`e159c4b8 00000000`00000003 ffffe304`ed2b1990 00000238`211d0000 : nt!MiReplaceRotateWithDemandZero+0x224
ffffbd8f`e159c1a0 fffff806`8c87309a : ffffe304`eb777a60 ffffd201`54e30b80 00000000`00000003 ffffbd8f`e159c580 : nt!MmRotatePhysicalView+0x40f
ffffbd8f`e159c440 fffff806`8c872d81 : ffffd201`648c4310 00000000`746c6644 ffffbd8f`00000003 00000000`00000000 : dxgmms2!VIDMM_RECYCLE_MULTIRANGE::Rotate+0x2c2
ffffbd8f`e159c500 fffff806`8c8646f7 : ffffe304`e8e6a900 ffffd201`652bed60 ffffe304`eb7f3040 fffff806`8103eef4 : dxgmms2!VIDMM_RECYCLE_HEAP_MGR::Rotate+0xb1
ffffbd8f`e159c590 fffff806`8c84e51a : 00000000`00000000 ffffd201`652bed60 ffffd201`00000000 ffffd201`5c37ae90 : dxgmms2!VIDMM_GLOBAL::Rotate+0x7b
ffffbd8f`e159c600 fffff806`8c81f2a1 : ffffd201`652bed60 fffff806`00000001 ffffe304`00000000 ffffe304`ee77b000 : dxgmms2!VIDMM_MEMORY_SEGMENT::TransferToSystem+0x30fba
ffffbd8f`e159c790 fffff806`8c8260bb : ffffe304`ee784c20 ffffbd8f`e159c8e0 ffffe304`ee77b000 00000000`00000000 : dxgmms2!VIDMM_MEMORY_SEGMENT::EvictResource+0xb1
ffffbd8f`e159c7e0 fffff806`8c83c3a8 : ffffe304`ee77b000 ffffe304`ee784c10 ffffe304`ee77b000 ffffe304`ee77b000 : dxgmms2!VIDMM_GLOBAL:
😛
rocessDeferredCommand+0xa9b
ffffbd8f`e159ca00 fffff806`8c846839 : ffffd201`553be500 ffffe304`e3cc5000 00000000`00000000 fffff806`81b27a00 : dxgmms2!VIDMM_WORKER_THREAD::Run+0xb78
ffffbd8f`e159cbe0 fffff806`811265f5 : ffffe304`eb7f3040 fffff806`8c846830 ffffd201`553be500 00000000`00000000 : dxgmms2!VidMmWorkerThreadProc+0x9
ffffbd8f`e159cc10 fffff806`812048d8 : fffff806`7be07180 ffffe304`eb7f3040 fffff806`811265a0 00000000`00000246 : nt!PspSystemThreadStartup+0x55
ffffbd8f`e159cc60 00000000`00000000 : ffffbd8f`e159d000 ffffbd8f`e1597000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: dxgmms2!VIDMM_RECYCLE_MULTIRANGE::Rotate+2c2
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.19041.3205
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 2c2
FAILURE_BUCKET_ID: 0x1a_61948_dxgmms2!VIDMM_RECYCLE_MULTIRANGE::Rotate
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {ec362d5e-ccbe-e8ef-00c8-b53907af7897}
Followup: MachineOwner
---------
6: kd> !blackboxpnp
PnpActivityId : {00000000-0000-0000-0000-000000000000}
PnpActivityTime : 133441627482246196
PnpEventInformation: 3
PnpEventInProgress : 0
PnpProblemCode : 24
PnpVetoType : 0
DeviceId : DISPLAY\VSC5A37\1&8713bca&0&UID0
VetoString :
6: kd> lmvm dxgmms2
Browse full module list
start end module name
fffff806`8c7b0000 fffff806`8c891000 dxgmms2 # (pdb symbols) C:\ProgramData\Dbg\sym\dxgmms2.pdb\4195ABCFBDAE22D6532698212FC99B081\dxgmms2.pdb
Loaded symbol image file: dxgmms2.sys
Mapped memory image file: C:\ProgramData\Dbg\sym\dxgmms2.sys\4C1E73FAe1000\dxgmms2.sys
Image path: dxgmms2.sys
Image name: dxgmms2.sys
Browse all global symbols functions data
Image was built with /Brepro flag.
Timestamp: 4C1E73FA (This is a reproducible build file hash, not a timestamp)
CheckSum: 000DD17D
ImageSize: 000E1000
File version: 10.0.19041.3205
Product version: 10.0.19041.3205
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: dxgmms2.sys
OriginalFilename: dxgmms2.sys
ProductVersion: 10.0.19041.3205
FileVersion: 10.0.19041.3205 (WinBuild.160101.0800)
FileDescription: DirectX Graphics MMS
LegalCopyright: © Microsoft Corporation. All rights reserved.
6: kd> lmvm dxgmms2
Browse full module list
start end module name
fffff806`8c7b0000 fffff806`8c891000 dxgmms2 # (pdb symbols) C:\ProgramData\Dbg\sym\dxgmms2.pdb\4195ABCFBDAE22D6532698212FC99B081\dxgmms2.pdb
Loaded symbol image file: dxgmms2.sys
Mapped memory image file: C:\ProgramData\Dbg\sym\dxgmms2.sys\4C1E73FAe1000\dxgmms2.sys
Image path: dxgmms2.sys
Image name: dxgmms2.sys
Browse all global symbols functions data
Image was built with /Brepro flag.
Timestamp: 4C1E73FA (This is a reproducible build file hash, not a timestamp)
CheckSum: 000DD17D
ImageSize: 000E1000
File version: 10.0.19041.3205
Product version: 10.0.19041.3205
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: dxgmms2.sys
OriginalFilename: dxgmms2.sys
ProductVersion: 10.0.19041.3205
FileVersion: 10.0.19041.3205 (WinBuild.160101.0800)
FileDescription: DirectX Graphics MMS
LegalCopyright: © Microsoft Corporation. All rights reserved.
My Build: ( I know the build is old)
CPU: I7-4770
CPU cooler: CoolerMaster
Motherboard: Intel Desktop Board DH87RL
Ram: 1600 mhz ddr3 16gb
SSD/HDD: Samsung Evo 1tb. hdd 500gb. ssd 128 gb
GPU: Rx 580 XFX
PSU:600 watts Cougar
Chassis: Lian li 215
OS: Windows 10 22h2
Monitor: ViewSonic Elite 144Hz
I dont know what to do. If anyone has any ideas, feel free to share.
Thanks in Advance
Reply
Reply
O
Ob22007
10-31-2024, 04:55 PM #1

So I have been experiencing grey screens and driver timeout since 22/10/23 and idk what to do. I have been runing the same build for around 5 6 years and it never gave me any problems. Today I experienced a bsod and I am unable to find a solution. i have used ddu many times, reinstalled windows from iso file and ran mem test but no luck. I have stress tested my pc for hours and it didnt give any issue like flickering or crashes. Grey screen suddenly pops up while doing normal work and I am unable to do anything except to do a hard reset.
In Reliability Index, found hardware issue like livekernal 117. livekernal 141, livekernal 193, livekernal 1b0, Bluescreen 1a.
I have done ddu, reinstalled gpu drivers(old and new) millions of times, ran mem test, ran memory diagnostic, done basic cmd commands, and much more( cant remeber honestly, Did whatever I found but now i am exhausted).
I encountered a bsod which led me to believe that the issue lies with the ram(
Stop Code: Memory_Management)
. here is the minidump file for the bsod and grey screen
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : false
AllowNugetExeUpdate : false
AllowNugetMSCredentialProviderInstall : false
AllowParallelInitializationOfLocalRepositories : true
-- 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.031 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 36
Microsoft ® Windows Debugger Version 10.0.25877.1004 AMD64
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidumps\111123-8078-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 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff806`80e00000 PsLoadedModuleList = 0xfffff806`81a2a2b0
Debug session time: Sat Nov 11 12:57:41.484 2023 (UTC + 5:00)
System Uptime: 0 days 10:37:13.164
Loading Kernel Symbols
..
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.............................................................
................................................................
...................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000d4`b337b018). Type ".hh dbgerr001" for details
Loading unloaded module list
.................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`811fbca0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffbd8f`e159be60=000000000000001a
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000061948, The subtype of the BugCheck.
Arg2: 0000000000000000
Arg3: 0000000000000001
Arg4: 0000000000000000
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2436
Key : Analysis.Elapsed.mSec
Value: 4769
Key : Analysis.IO.Other.Mb
Value: 5
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 20
Key : Analysis.Init.CPU.mSec
Value: 515
Key : Analysis.Init.Elapsed.mSec
Value: 37739
Key : Analysis.Memory.CommitPeak.Mb
Value: 84
Key : Bugcheck.Code.LegacyAPI
Value: 0x1a
Key : Dump.Attributes.AsUlong
Value: 8
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Failure.Bucket
Value: 0x1a_61948_dxgmms2!VIDMM_RECYCLE_MULTIRANGE::Rotate
Key : Failure.Hash
Value: {ec362d5e-ccbe-e8ef-00c8-b53907af7897}
BUGCHECK_CODE: 1a
BUGCHECK_P1: 61948
BUGCHECK_P2: 0
BUGCHECK_P3: 1
BUGCHECK_P4: 0
FILE_IN_CAB: 111123-8078-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: RadeonSoftware
STACK_TEXT:
ffffbd8f`e159be58 fffff806`8123c050 : 00000000`0000001a 00000000`00061948 00000000`00000000 00000000`00000001 : nt!KeBugCheckEx
ffffbd8f`e159be60 fffff806`8105e6d4 : 00000000`00000002 00000000`00000001 00000000`00000001 00000000`00000000 : nt!MiDereferenceIoPages+0x1daa48
ffffbd8f`e159bef0 fffff806`8145ce4f : ffffbd8f`e159c4b8 00000000`00000003 ffffe304`ed2b1990 00000238`211d0000 : nt!MiReplaceRotateWithDemandZero+0x224
ffffbd8f`e159c1a0 fffff806`8c87309a : ffffe304`eb777a60 ffffd201`54e30b80 00000000`00000003 ffffbd8f`e159c580 : nt!MmRotatePhysicalView+0x40f
ffffbd8f`e159c440 fffff806`8c872d81 : ffffd201`648c4310 00000000`746c6644 ffffbd8f`00000003 00000000`00000000 : dxgmms2!VIDMM_RECYCLE_MULTIRANGE::Rotate+0x2c2
ffffbd8f`e159c500 fffff806`8c8646f7 : ffffe304`e8e6a900 ffffd201`652bed60 ffffe304`eb7f3040 fffff806`8103eef4 : dxgmms2!VIDMM_RECYCLE_HEAP_MGR::Rotate+0xb1
ffffbd8f`e159c590 fffff806`8c84e51a : 00000000`00000000 ffffd201`652bed60 ffffd201`00000000 ffffd201`5c37ae90 : dxgmms2!VIDMM_GLOBAL::Rotate+0x7b
ffffbd8f`e159c600 fffff806`8c81f2a1 : ffffd201`652bed60 fffff806`00000001 ffffe304`00000000 ffffe304`ee77b000 : dxgmms2!VIDMM_MEMORY_SEGMENT::TransferToSystem+0x30fba
ffffbd8f`e159c790 fffff806`8c8260bb : ffffe304`ee784c20 ffffbd8f`e159c8e0 ffffe304`ee77b000 00000000`00000000 : dxgmms2!VIDMM_MEMORY_SEGMENT::EvictResource+0xb1
ffffbd8f`e159c7e0 fffff806`8c83c3a8 : ffffe304`ee77b000 ffffe304`ee784c10 ffffe304`ee77b000 ffffe304`ee77b000 : dxgmms2!VIDMM_GLOBAL:
😛
rocessDeferredCommand+0xa9b
ffffbd8f`e159ca00 fffff806`8c846839 : ffffd201`553be500 ffffe304`e3cc5000 00000000`00000000 fffff806`81b27a00 : dxgmms2!VIDMM_WORKER_THREAD::Run+0xb78
ffffbd8f`e159cbe0 fffff806`811265f5 : ffffe304`eb7f3040 fffff806`8c846830 ffffd201`553be500 00000000`00000000 : dxgmms2!VidMmWorkerThreadProc+0x9
ffffbd8f`e159cc10 fffff806`812048d8 : fffff806`7be07180 ffffe304`eb7f3040 fffff806`811265a0 00000000`00000246 : nt!PspSystemThreadStartup+0x55
ffffbd8f`e159cc60 00000000`00000000 : ffffbd8f`e159d000 ffffbd8f`e1597000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: dxgmms2!VIDMM_RECYCLE_MULTIRANGE::Rotate+2c2
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.19041.3205
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 2c2
FAILURE_BUCKET_ID: 0x1a_61948_dxgmms2!VIDMM_RECYCLE_MULTIRANGE::Rotate
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {ec362d5e-ccbe-e8ef-00c8-b53907af7897}
Followup: MachineOwner
---------
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000061948, The subtype of the BugCheck.
Arg2: 0000000000000000
Arg3: 0000000000000001
Arg4: 0000000000000000
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2281
Key : Analysis.Elapsed.mSec
Value: 2275
Key : Analysis.IO.Other.Mb
Value: 5
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 20
Key : Analysis.Init.CPU.mSec
Value: 2953
Key : Analysis.Init.Elapsed.mSec
Value: 42511
Key : Analysis.Memory.CommitPeak.Mb
Value: 85
Key : Bugcheck.Code.LegacyAPI
Value: 0x1a
Key : Dump.Attributes.AsUlong
Value: 8
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Failure.Bucket
Value: 0x1a_61948_dxgmms2!VIDMM_RECYCLE_MULTIRANGE::Rotate
Key : Failure.Hash
Value: {ec362d5e-ccbe-e8ef-00c8-b53907af7897}
BUGCHECK_CODE: 1a
BUGCHECK_P1: 61948
BUGCHECK_P2: 0
BUGCHECK_P3: 1
BUGCHECK_P4: 0
FILE_IN_CAB: 111123-8078-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: RadeonSoftware
STACK_TEXT:
ffffbd8f`e159be58 fffff806`8123c050 : 00000000`0000001a 00000000`00061948 00000000`00000000 00000000`00000001 : nt!KeBugCheckEx
ffffbd8f`e159be60 fffff806`8105e6d4 : 00000000`00000002 00000000`00000001 00000000`00000001 00000000`00000000 : nt!MiDereferenceIoPages+0x1daa48
ffffbd8f`e159bef0 fffff806`8145ce4f : ffffbd8f`e159c4b8 00000000`00000003 ffffe304`ed2b1990 00000238`211d0000 : nt!MiReplaceRotateWithDemandZero+0x224
ffffbd8f`e159c1a0 fffff806`8c87309a : ffffe304`eb777a60 ffffd201`54e30b80 00000000`00000003 ffffbd8f`e159c580 : nt!MmRotatePhysicalView+0x40f
ffffbd8f`e159c440 fffff806`8c872d81 : ffffd201`648c4310 00000000`746c6644 ffffbd8f`00000003 00000000`00000000 : dxgmms2!VIDMM_RECYCLE_MULTIRANGE::Rotate+0x2c2
ffffbd8f`e159c500 fffff806`8c8646f7 : ffffe304`e8e6a900 ffffd201`652bed60 ffffe304`eb7f3040 fffff806`8103eef4 : dxgmms2!VIDMM_RECYCLE_HEAP_MGR::Rotate+0xb1
ffffbd8f`e159c590 fffff806`8c84e51a : 00000000`00000000 ffffd201`652bed60 ffffd201`00000000 ffffd201`5c37ae90 : dxgmms2!VIDMM_GLOBAL::Rotate+0x7b
ffffbd8f`e159c600 fffff806`8c81f2a1 : ffffd201`652bed60 fffff806`00000001 ffffe304`00000000 ffffe304`ee77b000 : dxgmms2!VIDMM_MEMORY_SEGMENT::TransferToSystem+0x30fba
ffffbd8f`e159c790 fffff806`8c8260bb : ffffe304`ee784c20 ffffbd8f`e159c8e0 ffffe304`ee77b000 00000000`00000000 : dxgmms2!VIDMM_MEMORY_SEGMENT::EvictResource+0xb1
ffffbd8f`e159c7e0 fffff806`8c83c3a8 : ffffe304`ee77b000 ffffe304`ee784c10 ffffe304`ee77b000 ffffe304`ee77b000 : dxgmms2!VIDMM_GLOBAL:
😛
rocessDeferredCommand+0xa9b
ffffbd8f`e159ca00 fffff806`8c846839 : ffffd201`553be500 ffffe304`e3cc5000 00000000`00000000 fffff806`81b27a00 : dxgmms2!VIDMM_WORKER_THREAD::Run+0xb78
ffffbd8f`e159cbe0 fffff806`811265f5 : ffffe304`eb7f3040 fffff806`8c846830 ffffd201`553be500 00000000`00000000 : dxgmms2!VidMmWorkerThreadProc+0x9
ffffbd8f`e159cc10 fffff806`812048d8 : fffff806`7be07180 ffffe304`eb7f3040 fffff806`811265a0 00000000`00000246 : nt!PspSystemThreadStartup+0x55
ffffbd8f`e159cc60 00000000`00000000 : ffffbd8f`e159d000 ffffbd8f`e1597000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: dxgmms2!VIDMM_RECYCLE_MULTIRANGE::Rotate+2c2
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.19041.3205
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 2c2
FAILURE_BUCKET_ID: 0x1a_61948_dxgmms2!VIDMM_RECYCLE_MULTIRANGE::Rotate
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {ec362d5e-ccbe-e8ef-00c8-b53907af7897}
Followup: MachineOwner
---------
6: kd> !blackboxpnp
PnpActivityId : {00000000-0000-0000-0000-000000000000}
PnpActivityTime : 133441627482246196
PnpEventInformation: 3
PnpEventInProgress : 0
PnpProblemCode : 24
PnpVetoType : 0
DeviceId : DISPLAY\VSC5A37\1&8713bca&0&UID0
VetoString :
6: kd> lmvm dxgmms2
Browse full module list
start end module name
fffff806`8c7b0000 fffff806`8c891000 dxgmms2 # (pdb symbols) C:\ProgramData\Dbg\sym\dxgmms2.pdb\4195ABCFBDAE22D6532698212FC99B081\dxgmms2.pdb
Loaded symbol image file: dxgmms2.sys
Mapped memory image file: C:\ProgramData\Dbg\sym\dxgmms2.sys\4C1E73FAe1000\dxgmms2.sys
Image path: dxgmms2.sys
Image name: dxgmms2.sys
Browse all global symbols functions data
Image was built with /Brepro flag.
Timestamp: 4C1E73FA (This is a reproducible build file hash, not a timestamp)
CheckSum: 000DD17D
ImageSize: 000E1000
File version: 10.0.19041.3205
Product version: 10.0.19041.3205
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: dxgmms2.sys
OriginalFilename: dxgmms2.sys
ProductVersion: 10.0.19041.3205
FileVersion: 10.0.19041.3205 (WinBuild.160101.0800)
FileDescription: DirectX Graphics MMS
LegalCopyright: © Microsoft Corporation. All rights reserved.
6: kd> lmvm dxgmms2
Browse full module list
start end module name
fffff806`8c7b0000 fffff806`8c891000 dxgmms2 # (pdb symbols) C:\ProgramData\Dbg\sym\dxgmms2.pdb\4195ABCFBDAE22D6532698212FC99B081\dxgmms2.pdb
Loaded symbol image file: dxgmms2.sys
Mapped memory image file: C:\ProgramData\Dbg\sym\dxgmms2.sys\4C1E73FAe1000\dxgmms2.sys
Image path: dxgmms2.sys
Image name: dxgmms2.sys
Browse all global symbols functions data
Image was built with /Brepro flag.
Timestamp: 4C1E73FA (This is a reproducible build file hash, not a timestamp)
CheckSum: 000DD17D
ImageSize: 000E1000
File version: 10.0.19041.3205
Product version: 10.0.19041.3205
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: dxgmms2.sys
OriginalFilename: dxgmms2.sys
ProductVersion: 10.0.19041.3205
FileVersion: 10.0.19041.3205 (WinBuild.160101.0800)
FileDescription: DirectX Graphics MMS
LegalCopyright: © Microsoft Corporation. All rights reserved.
My Build: ( I know the build is old)
CPU: I7-4770
CPU cooler: CoolerMaster
Motherboard: Intel Desktop Board DH87RL
Ram: 1600 mhz ddr3 16gb
SSD/HDD: Samsung Evo 1tb. hdd 500gb. ssd 128 gb
GPU: Rx 580 XFX
PSU:600 watts Cougar
Chassis: Lian li 215
OS: Windows 10 22h2
Monitor: ViewSonic Elite 144Hz
I dont know what to do. If anyone has any ideas, feel free to share.
Thanks in Advance

Reply
Reply
K
Kevin_Davidoff
Junior Member
Find
11
10-31-2024, 04:55 PM
#2
What's the exact model?
Reply
Reply
K
Kevin_Davidoff
10-31-2024, 04:55 PM #2

What's the exact model?

Reply
Reply
F
facianoir
Junior Member
Find
41
10-31-2024, 04:55 PM
#3
Cougar XTC600
Reply
Reply
F
facianoir
10-31-2024, 04:55 PM #3

Cougar XTC600

Reply
Reply
M
Mr_Ragez
Junior Member
Find
18
10-31-2024, 04:55 PM
#4
It isn't the worst, but it's not great either. I don't believe the PSU is the cause. Have you checked the RAM overnight using memtest86? Is the motherboard's BIOS current?
Reply
Reply
M
Mr_Ragez
10-31-2024, 04:55 PM #4

It isn't the worst, but it's not great either. I don't believe the PSU is the cause. Have you checked the RAM overnight using memtest86? Is the motherboard's BIOS current?

Reply
Reply
Z
zahmbie1227
Member
Find
55
10-31-2024, 04:55 PM
#5
All systems are current and have successfully run mem86. No problems found.
Reply
Reply
Z
zahmbie1227
10-31-2024, 04:55 PM #5

All systems are current and have successfully run mem86. No problems found.

Reply
Reply