Question Gaming Laptop restarts randomly ?

tomazo-be · Nov 24, 2023

I checked the event viewer and it shows

''The computer has rebooted from a bugcheck. The bugcheck was: 0x0000010e (0x000000000000001d, 0xffffa487125e8770, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: d80f19f2-eba4-4456-bb4d-22ae03ab7eee.''

then i opened the dump file and it says :

************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
AllowNugetMSCredentialProviderInstall : true
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.265 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 36

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

Loading Dump File [C:\Windows\MEMORY.DMP]
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 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff807`1a800000 PsLoadedModuleList = 0xfffff807`1b42a6d0
Debug session time: Fri Nov 24 13:51:52.759 2023 (UTC + 0:00)
System Uptime: 0 days 5:31:01.509
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.....................
Loading User Symbols

Loading unloaded module list
......................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`1abfd730 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffe00b`5c27ee00=000000000000010e
5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 000000000000001d, The subtype of the BugCheck:
Arg2: ffffa487125e8770
Arg3: 0000000000000000
Arg4: 0000000000000000

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

*** WARNING: Check Image - Checksum mismatch - Dump: 0x15d0a, File: 0x15d70 - C:\ProgramData\Dbg\sym\watchdog.sys\28AF795D18000\watchdog.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4733

Key : Analysis.Elapsed.mSec
Value: 4780

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

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

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

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

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

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

Key : Bugcheck.Code.KiBugCheckData
Value: 0x10e

Key : Bugcheck.Code.LegacyAPI
Value: 0x10e

Key : Failure.Bucket
Value: 0x10e_1d_dxgmms2!VIDMM_GLOBAL::UpdatePageTable

Key : Failure.Hash
Value: {71cfaed7-afd6-912e-e10e-336c7c7acd87}

Key : Hypervisor.Enlightenments.Value
Value: 0

Key : Hypervisor.Enlightenments.ValueHex
Value: 0

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 0

Key : Hypervisor.Flags.ApicEnlightened
Value: 0

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 0

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 0

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 0

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 0

Key : Hypervisor.Flags.Phase0InitDone
Value: 0

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 0

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 16908288

Key : Hypervisor.Flags.ValueHex
Value: 1020000

Key : Hypervisor.Flags.VpAssistPage
Value: 0

Key : Hypervisor.Flags.VsmAvailable
Value: 0

Key : Hypervisor.RootFlags.AccessStats
Value: 0

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 0

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 0

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 0

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 0

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 0

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 0

Key : Hypervisor.RootFlags.MceEnlightened
Value: 0

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 0

Key : Hypervisor.RootFlags.Value
Value: 0

Key : Hypervisor.RootFlags.ValueHex
Value: 0

Key : SecureKernel.HalpHvciEnabled
Value: 0

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1

BUGCHECK_CODE: 10e

BUGCHECK_P1: 1d

BUGCHECK_P2: ffffa487125e8770

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB: MEMORY.DMP

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffffe00b`5c27edf8 fffff807`30f23ad0 : 00000000`0000010e 00000000`0000001d ffffa487`125e8770 00000000`00000000 : nt!KeBugCheckEx
ffffe00b`5c27ee00 fffff807`54820ff8 : 00000000`00000000 ffffa487`1906e000 00000000`00000000 00000000`00000000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffe00b`5c27ee40 fffff807`5481f606 : 00000000`00000000 fffff807`1aa3ea76 ffffba8f`006e0880 ffffa487`0bde9300 : dxgmms2!VIDMM_GLOBAL::UpdatePageTable+0x188
ffffe00b`5c27f0d0 fffff807`548220cd : 00000000`00000000 00000000`00000002 00000000`00040484 ffffe00b`5c27f640 : dxgmms2!VIDMM_PAGE_TABLE::UpdatePageTable+0x13a
ffffe00b`5c27f190 fffff807`54820092 : 00000000`00000000 ffffe00b`5c27f340 ffffba8e`d090a2f0 00000000`00000000 : dxgmms2!VIDMM_PAGE_TABLE::CommitVirtualAddressRange+0x1e5
ffffe00b`5c27f230 fffff807`54820226 : 00000000`00000000 ffffba8e`d0914810 ffffe00b`5c27f640 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x872
ffffe00b`5c27f3d0 fffff807`5481f24e : 00000000`00000007 ffffba8e`d0914810 ffffe00b`5c27f640 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0xa06
ffffe00b`5c27f570 fffff807`548224fc : 00000000`00000000 ffffe00b`5c27f800 00000000`00000000 00000000`00000000 : dxgmms2!CVirtualAddressAllocator::CommitVirtualAddressRange+0x2f6
ffffe00b`5c27f6f0 fffff807`5484b5a9 : 00000000`00000000 00000000`00000071 ffffe00b`5c27f880 ffffba8e`d0914160 : dxgmms2!VIDMM_GLOBAL::CommitVirtualAddressRangeSystemCommand+0x188
ffffe00b`5c27f780 fffff807`5483d622 : ffffba8e`d0914130 ffffe00b`00000001 00000000`00000001 ffffba8e`d08fec00 : dxgmms2!VIDMM_GLOBAL:😛rocessSystemCommand+0x340f9
ffffe00b`5c27f900 fffff807`548471c9 : ffffba8e`d08feb90 ffffa487`16ac5001 00000000`00000000 00000000`06f76300 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x1462
ffffe00b`5c27fae0 fffff807`1ab078e5 : ffffa487`16ac5080 fffff807`548471c0 ffffba8e`d08feb90 000fa4ef`bd9bbfff : dxgmms2!VidMmWorkerThreadProc+0x9
ffffe00b`5c27fb10 fffff807`1ac06368 : ffff9081`65e79180 ffffa487`16ac5080 fffff807`1ab07890 00500053`0041005c : nt!PspSystemThreadStartup+0x55
ffffe00b`5c27fb60 00000000`00000000 : ffffe00b`5c280000 ffffe00b`5c279000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME: dxgmms2!VIDMM_GLOBAL::UpdatePageTable+188

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.3636

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 188

FAILURE_BUCKET_ID: 0x10e_1d_dxgmms2!VIDMM_GLOBAL::UpdatePageTable

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {71cfaed7-afd6-912e-e10e-336c7c7acd87}

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

If someone can help me to solve the issue i will greatly appreciate it . Thanks !

tomazo-be · Nov 24, 2023

The temperatures are stuck on 55c CPU and 49c GPU so its definetly not overheating...fans are barely moving, the device is cold.

ubuysa · Nov 25, 2023

Please upload the actual dump file to the cloud with a (public) link to it here. There is way more to dump analysis than running analyze -v...

tomazo-be · Nov 25, 2023

ubuysa said:
Please upload the actual dump file to the cloud with a (public) link to it here. There is way more to dump analysis than running analyze -v...

https://1drv.ms/u/s!AixNp7Va8POrhl_IGxM0O_vrZj4U?e=55GBbp Hi , i uploaded the file here

ubuysa · Nov 25, 2023

From the dump* the BSOD happened because the graphics driver was attempting to use a paging buffer in video memory that had been unmapped. This is going to be either a graphics driver error (most likely) or possibly a graphics card problem in the video memory.

The version of the graphics driver (nvlddmkm.sys) that you have installed may not be current...

Code:

5: kd> lmDvm nvlddmkm
Browse full module list
start             end                 module name
fffff807`43550000 fffff807`46de8000   nvlddmkm   (export symbols)       nvlddmkm.sys
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\System32\DriverStore\FileRepository\nvamig.inf_amd64_59b5390a2716d77e\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        Thu Apr 13 22:19:25 2023 (643855BD)
    CheckSum:         03792E03
    ImageSize:        03898000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

However, I can see from the dump that this is an ASUS TUF Gaming F15 laptop and laptops are often very fussy about their drivers. Graphics drivers in particular are often customised for operational or power-saving reasons on laptops and the generic drivers from Nvidia sometimes don't function properly (because they don't contain the necessary customisation). The latest driver available from the Asus website for your laptop is dated 7th June 2022 and I would suggest that you consider uninstalling the current driver with DDU and installing that Asus driver. That is guaranteed to work with your laptop, so if it BSODs then the problem lies with the graphics card.

There is also a BIOS update available for your laptop dated 30th August 2022, the version you have installed is dated 26th November 2021. You should consider updating to this BIOS version.

*In the future please don't upload the full kernel dump (C:\Windows\Memory.dmp) unless we ask for it. Instead upload the minidumps in the folder C:\Windows\Minidump.

tomazo-be · Nov 25, 2023

ubuysa said:
From the dump* the BSOD happened because the graphics driver was attempting to use a paging buffer in video memory that had been unmapped. This is going to be either a graphics driver error (most likely) or possibly a graphics card problem in the video memory.

The version of the graphics driver (nvlddmkm.sys) that you have installed may not be current...

Code:

5: kd> lmDvm nvlddmkm Browse full module list start end module name fffff807`43550000 fffff807`46de8000 nvlddmkm (export symbols) nvlddmkm.sys Loaded symbol image file: nvlddmkm.sys Image path: \SystemRoot\System32\DriverStore\FileRepository\nvamig.inf_amd64_59b5390a2716d77e\nvlddmkm.sys Image name: nvlddmkm.sys Browse all global symbols functions data Timestamp: Thu Apr 13 22:19:25 2023 (643855BD) CheckSum: 03792E03 ImageSize: 03898000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 Information from resource tables:

However, I can see from the dump that this is an ASUS TUF Gaming F15 laptop and laptops are often very fussy about their drivers. Graphics drivers in particular are often customised for operational or power-saving reasons on laptops and the generic drivers from Nvidia sometimes don't function properly (because they don't contain the necessary customisation). The latest driver available from the Asus website for your laptop is dated 7th June 2022 and I would suggest that you consider uninstalling the current driver with DDU and installing that Asus driver. That is guaranteed to work with your laptop, so if it BSODs then the problem lies with the graphics card.

There is also a BIOS update available for your laptop dated 30th August 2022, the version you have installed is dated 26th November 2021. You should consider updating to this BIOS version.

*In the future please don't upload the full kernel dump (C:\Windows\Memory.dmp) unless we ask for it. Instead upload the minidumps in the folder C:\Windows\Minidump.

Hi , thank you very much ! I agree with you ! I actually did a clean install of the GPU drivers with DDU and NVCleanInstall yesterday .. and the laptop did not restart for ...27 hours already , so i think the issue is fixed.

However...

I want to update my BIOS but, isn't this the right place for the bios drivers for my laptop ? https://www.asus.com/laptops/for-ga...f-gaming-f15/helpdesk_bios?model2Name=FX506LU i always downloaded the stuff from here, did i do it wrong ? Or it has to be from the link that you gave me ?

thanks !

tomazo-be · Nov 25, 2023

I installed both bios updates from the both websites ... and it still shows ...
BIOS Version/Date American Megatrends Inc. FX506LU.310, 26/11/2021
in the system information tab ...

it shows my bios is version 310 in the BIOS itself tho ..

ubuysa · Nov 26, 2023

Use your site. I just looked at the laptop model name in the dump and did a web search on drivers for that model. I've since gone back to the dump and the model name you have in your link is correct...

Code:

 Family                        ASUS TUF Gaming F15
[BaseBoard Information (Type 2) - Length 15 - Handle 0002h]
  Manufacturer                  ASUSTeK COMPUTER INC.
  Product                       FX506LU

Apologies.

Search

Question Gaming Laptop restarts randomly ?

tomazo-be

Commendable

tomazo-be

Commendable

ubuysa

Distinguished

tomazo-be

Commendable

ubuysa

Distinguished

tomazo-be

Commendable

tomazo-be

Commendable

ubuysa

Distinguished

TRENDING THREADS

Latest posts

Moderators online

Share this page