Fast boot and Memory Management Issue Acer Predator ph315-52 laptop

SAIRISAN
SAIRISAN Member Posts: 12

Tinkerer

edited September 12 in Predator Laptops

I am using acer predator ph315-52 laptop. I removed my two ram (2 × 8GB ) and reseated it. when I started again. this issue comes. But it after reaching 100%. device restarted and open successfully. I have note following. (Note that I have my dual boot Ubuntu on other SSD)

  1. This is not come for restarting.
  2. Only for shutdown and start with fast boot enable.
  3. Sleep mode not working as previous. Devices go sleep. But when I press any key it shutdown and restarting automatically.

I have done following test and repairs but no fix.

  1. Upgrade new Ram with 32 GB (2 × 16GB).
  2. Memory diagnostic 2 test.
  3. Clean install windows 10. (remove ubuntu on other disk as well)
  4. system & security upgrade.

what will be issue?

[Edited the thread to add model name to the title]

Best Answer

  • SAIRISAN
    SAIRISAN Member Posts: 12

    Tinkerer

    Answer ✓

    I solved my issue by installing this driver. Thank you for the time.

Answers

  • StevenGen
    StevenGen ACE Posts: 11,428 Trailblazer

    A Windows 10 MEMORY MANAGEMENT BSOD ERROR can be caused by faulty hardware, often a broken memory bank. The error message can also be triggered by the installation of incorrect drivers or existing drivers that need to be updated.

    How to Fix a Memory Management Error

    There are various ways to fix the common memory management error on a Windows 10 computer, laptop, or tablet. Here are the most effective solutions.

    1. Restart the computer. If the memory management error was caused by a temporary glitch, a basic Windows restart might fix it.
    2. Perform a Windows update. A Windows update can correct a variety of errors and can also increase the stability of a Windows 10 device. To manually check for an update, go to Settings > Update & Security > Check for updates.

    Note: When updating your device, make sure it's plugged into a power source. A flat battery during an update can cause a variety of problems.

    3. Update the drivers. An old or incorrect device driver can cause the memory management error on a Windows 10 device.

    Tips: It's recommended to stay connected to the internet when updating drivers so new ones can be downloaded.

    4. Scan the drives. Performing a basic scan of your hard drives for errors can fix a variety of problems.

    5. Run Windows Memory Diagnostic. The Windows Memory Diagnostic is a Windows 10 repair tool that detects and fixes memory errors. To activate it, select the search bar or Cortana in the Windows 10 taskbar and type Windows Memory Diagnostic, then choose Open > Restart now and check for problems (recommended). Your device restarts and automatically scans for memory problems.

    6. Replace the memory moduleIf a test shows that the memory management error is the result of faulty hardware, remove the current memory, and replace it with a new one. Replacing memory on a Windows 10 computer or laptop usually takes around 15 minutes once the correct components are obtained.

    Good luck and hope this helps you out.

    If this answers your question and solved your query please "Click on Yes" or "Click on Like" if you find my answer useful👍

  • SAIRISAN
    SAIRISAN Member Posts: 12

    Tinkerer

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

    -- Configuring repositories
    ----> Repository : LocalInstalled, Enabled: true
    ----> Repository : UserExtensions, Enabled: true

    Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

    ************* Waiting for Debugger Extensions Gallery to Initialize **************

    Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.062 seconds
    ----> Repository : UserExtensions, Enabled: true, Packages count: 0
    ----> Repository : LocalInstalled, Enabled: true, Packages count: 42

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

    Loading Dump File [C:\Users\Rajaretnam Sairisan\Desktop\091124-19578-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 (12 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
    Kernel base = 0xfffff80244c00000 PsLoadedModuleList = 0xfffff8024582a820
    Debug session time: Wed Sep 11 23:46:02.221 2024 (UTC + 5:30)
    System Uptime: 0 days 0:02:37.014
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    ................................
    Loading User Symbols

    Loading unloaded module list
    ...........
    For analysis of this file, run !analyze -v
    nt!KeBugCheckEx:
    fffff80244ffe350 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff8024a475230=000000000000001a
    0: kd> !analyze -v

    • *
    • Bugcheck Analysis *
    • *

    MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000061941, The subtype of the BugCheck.
    Arg2: ffffca00e68d71c2
    Arg3: 000000000000000b
    Arg4: fffff8024a4753d0

    Debugging Details:

    *** WARNING: Check Image - Checksum mismatch - Dump: 0x3f5b5, File: 0x3fda3 - C:\ProgramData\Dbg\sym\intelppm.sys\3E03C5E841000\intelppm.sys

    KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4999

    Key : Analysis.Elapsed.mSec
    Value: 20930

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

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

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

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

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

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

    Key : Bugcheck.Code.LegacyAPI
    Value: 0x1a

    Key : Bugcheck.Code.TargetModel
    Value: 0x1a

    Key : Failure.Bucket
    Value: 0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram

    Key : Failure.Hash
    Value: {c6e5c6cf-692e-7852-5dc5-b74944540fc0}

    Key : WER.OS.Branch
    Value: vb_release

    Key : WER.OS.Version
    Value: 10.0.19041.1

    BUGCHECK_CODE: 1a

    BUGCHECK_P1: 61941

    BUGCHECK_P2: ffffca00e68d71c2

    BUGCHECK_P3: b

    BUGCHECK_P4: fffff8024a4753d0

    FILE_IN_CAB: 091124-19578-01.dmp

    FAULTING_THREAD: fffff80245927a00

    BLACKBOXBSD: 1 (!blackboxbsd)

    BLACKBOXNTFS: 1 (!blackboxntfs)

    BLACKBOXPNP: 1 (!blackboxpnp)

    BLACKBOXWINLOGON: 1

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: System

    STACK_TEXT:fffff8024a475228 fffff8024503367a : 000000000000001a 0000000000061941 ffffca00e68d71c2 000000000000000b : nt!KeBugCheckEx
    fffff8024a475230 fffff8024500e46d : ffffee65007346b0 ffffee77328039a0 ffffee773b994018 ffffee773b9dcca0 : nt!MmAccessFault+0x1fa2ea
    fffff8024a4753d0 fffff80248cad1f0 : fffff80248d2a5be ffffb303d5b834b0 fffff80200000000 0000000000000000 : nt!KiPageFault+0x36d
    fffff8024a475568 fffff80248d2a5be : ffffb303d5b834b0 fffff80200000000 0000000000000000 0000000000000004 : iaStorAVC!VpiWriteRegisterUlong
    fffff8024a475570 fffff80248d28bfa : 0000002d00210001 0000000000000001 0000000000000001 fffff8024881232b : iaStorAVC!RemapPort::readSptConfig+0x29e
    fffff8024a4755e0 fffff80248cc43e0 : ffffb303d5b0bd78 fffff8024a475a10 ffffb303d5b0bd78 ffffb303d7bcf000 : iaStorAVC!RemapPort::buildIo+0x14e
    fffff8024a475660 fffff80248cc4548 : ffffb303d7bcf0b0 ffffb303d5b0be10 0000000013431025 ffff5f4f15f2000c : iaStorAVC!TransportTarget::dispatch+0xa8
    fffff8024a4756b0 fffff80248cbcddd : ffffb303d5b0ba20 fffff8024a475860 ffffb303d5b0bd78 ffffb303d5b0bc20 : iaStorAVC!TransportTarget::dispatchIo+0x104
    fffff8024a475710 fffff80244e1f4de : fffff80241815240 fffff8024a475a60 0000000000000000 0000000000000000 : iaStorAVC!Transport::dispatchIo+0x95
    fffff8024a475760 fffff80244e1e7c4 : 0000000000000000 0000000000000000 0000000000000009 0000000000000000 : nt!KiExecuteAllDpcs+0x30e
    fffff8024a4758d0 fffff80245002e4e : 0000000000000000 fffff80241812180 fffff80245927a00 ffffb303e4c9e080 : nt!KiRetireDpcList+0x1f4
    fffff8024a475b60 0000000000000000 : fffff8024a476000 fffff8024a46f000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x9e

    MODULE_NAME: hardware

    IMAGE_NAME: hardware_ram

    STACK_COMMAND: .process /r /p 0xfffff80245924a00; .thread 0xfffff80245927a00 ; kb

    FAILURE_BUCKET_ID: 0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram

    OS_VERSION: 10.0.19041.1

    BUILDLAB_STR: vb_release

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {c6e5c6cf-692e-7852-5dc5-b74944540fc0}

    Followup: MachineOwner

  • SAIRISAN
    SAIRISAN Member Posts: 12

    Tinkerer

    what may be the exact issue here this is .dmp file I spot memory management issue here as well

  • SAIRISAN
    SAIRISAN Member Posts: 12

    Tinkerer

    ************* Preparing the environment for Debugger Extensions Gallery repositories **************   ExtensionRepository : Implicit   UseExperimentalFeatureForNugetShare : true   AllowNugetExeUpdate : true   NonInteractiveNuget : true   AllowNugetMSCredentialProviderInstall : true   AllowParallelInitializationOfLocalRepositories : true   EnableRedirectToChakraJsProvider : false   -- Configuring repositories      ----> Repository : LocalInstalled, Enabled: true      ----> Repository : UserExtensions, Enabled: true>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds************* Waiting for Debugger Extensions Gallery to Initialize **************>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.062 seconds   ----> Repository : UserExtensions, Enabled: true, Packages count: 0   ----> Repository : LocalInstalled, Enabled: true, Packages count: 42Microsoft (R) Windows Debugger Version 10.0.27668.1000 AMD64Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Users\Rajaretnam Sairisan\Desktop\091124-19578-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: srv*Executable search path is: Windows 10 Kernel Version 19041 MP (12 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalEdition build lab: 19041.1.amd64fre.vb_release.191206-1406Kernel base = 0xfffff802`44c00000 PsLoadedModuleList = 0xfffff802`4582a820Debug session time: Wed Sep 11 23:46:02.221 2024 (UTC + 5:30)System Uptime: 0 days 0:02:37.014Loading Kernel Symbols...............................................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list...........For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff802`44ffe350 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff802`4a475230=000000000000001a0: kd> !analyze -v********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************MEMORY_MANAGEMENT (1a)    # Any other values for parameter 1 must be individually examined.Arguments:Arg1: 0000000000061941, The subtype of the BugCheck.Arg2: ffffca00e68d71c2Arg3: 000000000000000bArg4: fffff8024a4753d0Debugging Details:------------------*** WARNING: Check Image - Checksum mismatch - Dump: 0x3f5b5, File: 0x3fda3 - C:\ProgramData\Dbg\sym\intelppm.sys\3E03C5E841000\intelppm.sysKEY_VALUES_STRING: 1    Key  : Analysis.CPU.mSec    Value: 4999    Key  : Analysis.Elapsed.mSec    Value: 20930    Key  : Analysis.IO.Other.Mb    Value: 8    Key  : Analysis.IO.Read.Mb    Value: 0    Key  : Analysis.IO.Write.Mb    Value: 21    Key  : Analysis.Init.CPU.mSec    Value: 1968    Key  : Analysis.Init.Elapsed.mSec    Value: 63069    Key  : Analysis.Memory.CommitPeak.Mb    Value: 95    Key  : Bugcheck.Code.LegacyAPI    Value: 0x1a    Key  : Bugcheck.Code.TargetModel    Value: 0x1a    Key  : Failure.Bucket    Value: 0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram    Key  : Failure.Hash    Value: {c6e5c6cf-692e-7852-5dc5-b74944540fc0}    Key  : WER.OS.Branch    Value: vb_release    Key  : WER.OS.Version    Value: 10.0.19041.1BUGCHECK_CODE:  1aBUGCHECK_P1: 61941BUGCHECK_P2: ffffca00e68d71c2BUGCHECK_P3: bBUGCHECK_P4: fffff8024a4753d0FILE_IN_CAB:  091124-19578-01.dmpFAULTING_THREAD:  fffff80245927a00BLACKBOXBSD: 1 (!blackboxbsd)BLACKBOXNTFS: 1 (!blackboxntfs)BLACKBOXPNP: 1 (!blackboxpnp)BLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT:  1PROCESS_NAME:  SystemSTACK_TEXT:  fffff802`4a475228 fffff802`4503367a     : 00000000`0000001a 00000000`00061941 ffffca00`e68d71c2 00000000`0000000b : nt!KeBugCheckExfffff802`4a475230 fffff802`4500e46d     : ffffee65`007346b0 ffffee77`328039a0 ffffee77`3b994018 ffffee77`3b9dcca0 : nt!MmAccessFault+0x1fa2eafffff802`4a4753d0 fffff802`48cad1f0     : fffff802`48d2a5be ffffb303`d5b834b0 fffff802`00000000 00000000`00000000 : nt!KiPageFault+0x36dfffff802`4a475568 fffff802`48d2a5be     : ffffb303`d5b834b0 fffff802`00000000 00000000`00000000 00000000`00000004 : iaStorAVC!VpiWriteRegisterUlongfffff802`4a475570 fffff802`48d28bfa     : 0000002d`00210001 00000000`00000001 00000000`00000001 fffff802`4881232b : iaStorAVC!RemapPort::readSptConfig+0x29efffff802`4a4755e0 fffff802`48cc43e0     : ffffb303`d5b0bd78 fffff802`4a475a10 ffffb303`d5b0bd78 ffffb303`d7bcf000 : iaStorAVC!RemapPort::buildIo+0x14efffff802`4a475660 fffff802`48cc4548     : ffffb303`d7bcf0b0 ffffb303`d5b0be10 00000000`13431025 ffff5f4f`15f2000c : iaStorAVC!TransportTarget::dispatch+0xa8fffff802`4a4756b0 fffff802`48cbcddd     : ffffb303`d5b0ba20 fffff802`4a475860 ffffb303`d5b0bd78 ffffb303`d5b0bc20 : iaStorAVC!TransportTarget::dispatchIo+0x104fffff802`4a475710 fffff802`44e1f4de     : fffff802`41815240 fffff802`4a475a60 00000000`00000000 00000000`00000000 : iaStorAVC!Transport::dispatchIo+0x95fffff802`4a475760 fffff802`44e1e7c4     : 00000000`00000000 00000000`00000000 00000000`00000009 00000000`00000000 : nt!KiExecuteAllDpcs+0x30efffff802`4a4758d0 fffff802`45002e4e     : 00000000`00000000 fffff802`41812180 fffff802`45927a00 ffffb303`e4c9e080 : nt!KiRetireDpcList+0x1f4fffff802`4a475b60 00000000`00000000     : fffff802`4a476000 fffff802`4a46f000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9eMODULE_NAME: hardwareIMAGE_NAME:  hardware_ramSTACK_COMMAND:  .process /r /p 0xfffff80245924a00; .thread 0xfffff80245927a00 ; kbFAILURE_BUCKET_ID:  0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ramOS_VERSION:  10.0.19041.1BUILDLAB_STR:  vb_releaseOSPLATFORM_TYPE:  x64OSNAME:  Windows 10FAILURE_ID_HASH:  {c6e5c6cf-692e-7852-5dc5-b74944540fc0}Followup:     MachineOwner---------
    

  • SAIRISAN
    SAIRISAN Member Posts: 12

    Tinkerer

    Answer ✓

    I solved my issue by installing this driver. Thank you for the time.