nvlddmkm event id 153, 13 and a warning

Question

nvlddmkm event id 153, 13 and a warning

Anonymous

So, i've been having quite a few issues with my games and pc. I've been having this error nonstop and aswell a bsod. I had a faulty_hardware_corrupted_page error due to the reason of ntkrnlmp.exe. After my game crashed i immediately checked the event viewer and saw these errors :

The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\Video5

Graphics Exception: MISSING_MACRO_DATA

The message resource is present but the message was not found in the message table

The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\Video5

Graphics Exception: ESR 0x404490=0x80000001

The message resource is present but the message was not found in the message table

3.

The description for Event ID 153 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\Video5

Error occurred on GPUID: 100

The message resource is present but the message was not found in the message table

And 4.

Display driver nvlddmkm stopped responding and has successfully recovered.

I've tried reinstalling windows, reinstalling drivers by ddu and nvcleanstall, i tried swapping memory, replaced the psu, took full control of the nvlddmkm.sys file and giving it a 140mm instead of a 120mm it had in there to not let it overheat and even ran memory diagnostic tool, which found no errors whatsoever. I'm out of options and dont know what to do anymore.

My PC specs :

Asus PRIME Z370-P

Intel core i5 9600K

GTX 1060 6GB

HyperX Fury 16 GB 3600 mhz RAM

Corsair CX 550W PSU (Originally there was a Be Quiet 600W psu, but that was throwing issues, so i replaced it with the 550W)

NVME Apacer 1TB

And Windows 11 Pro

THIS IS THE LOG FROM WINDBG :

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

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: 0000000000000993, physical page number
Arg3: 000001c3c60ca0f0, zero
Arg4: ffff9a8175779000, zero

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2124

    Key  : Analysis.Elapsed.mSec
    Value: 5449

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

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

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

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

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

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

    Key  : BlackBox.SmDecompressionFailure.CompressedSize
    Value: 0x993

    Key  : BlackBox.SmDecompressionFailure.CompressionFormat
    Value: 0x3

    Key  : BlackBox.SmDecompressionFailure.SourceDataHash
    Value: 0x6227df8d

    Key  : BlackBox.SmDecompressionFailure.SourceDataOffset
    Value: 0xa0f0

    Key  : BlackBox.SmDecompressionFailure.SourcePFN1
    Value: 0x1018d8

    Key  : BlackBox.SmDecompressionFailure.SourcePFN2
    Value: 0xffffffffffffffff

    Key  : BlackBox.SmDecompressionFailure.TargetPFN
    Value: 0x30bf5d

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x12b

    Key  : Bugcheck.Code.TargetModel
    Value: 0x12b

    Key  : Dump.Attributes.AsUlong
    Value: 1008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x12B_c00002c4_StCtDecompressFailed_nt!ST_STORE_SM_TRAITS_::StDmPageError

    Key  : Failure.Hash
    Value: {c6a6bb4d-3b77-dff6-2d9b-75f5d0f61a50}

BUGCHECK_CODE:  12b

BUGCHECK_P1: ffffffffc00002c4

BUGCHECK_P2: 993

BUGCHECK_P3: 1c3c60ca0f0

BUGCHECK_P4: ffff9a8175779000

FILE_IN_CAB:  090124-5828-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffd082fbc7d080

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  MemCompression

STACK_TEXT:  
fffffe8d`3d972168 fffff803`157c418f     : 00000000`0000012b ffffffff`c00002c4 00000000`00000993 000001c3`c60ca0f0 : nt!KeBugCheckEx
fffffe8d`3d972170 fffff803`1565d30b     : 00000000`00000200 00000000`00000003 ffffd082`f5348050 000001c3`c60ca0f0 : nt!ST_STORE<SM_TRAITS>::StDmPageError+0xfb
fffffe8d`3d9721c0 fffff803`157c5168     : 00000000`00000004 fffff803`157be8f2 00000000`00000000 00000000`00000001 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x2c5
fffffe8d`3d972290 fffff803`157c5dc8     : 00000000`00000001 00000000`00000138 00000000`00000000 ffffd082`00010000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xa0
fffffe8d`3d9722e0 fffff803`157c4955     : ffffffff`ffffffff ffffd082`f5eb4000 fffffe8d`3d9723c0 ffffd082`f536d7d0 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x1c4
fffffe8d`3d972380 fffff803`157be3eb     : fffffe8d`3d9725b9 fffff803`00000001 fffff803`15e69500 ffffd082`f50f1850 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xc9
fffffe8d`3d972430 fffff803`157be2c1     : ffffd082`f5348000 ffffd082`f536d7d0 ffffd082`f5eb4000 ffffd082`f53499c0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x93
fffffe8d`3d9724b0 fffff803`1551565a     : ffffd082`fbc7d0f4 ffffd082`f5348000 ffffd082`00000000 ffffd082`f5eb4000 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
fffffe8d`3d9724e0 fffff803`1565cd9c     : fffff803`157be2a0 fffffe8d`3d972580 00000000`00000002 ffffd083`00000004 : nt!KeExpandKernelStackAndCalloutInternal+0x7a
fffffe8d`3d972550 fffff803`157c01c8     : fffffe8d`00000000 ffffd082`ee54d1d8 00000000`000003ff ffffd082`f536d7d0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xd4
fffffe8d`3d972620 fffff803`157bdad3     : 00000000`000003ff 00000000`000003ff fffffe8d`3d9726d0 ffffd082`f536d7d0 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x48
fffffe8d`3d972670 fffff803`1565c832     : 00000000`0000000c ffffd082`f536d7d0 00000000`00000010 00000000`00000010 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0x1d7
fffffe8d`3d972700 fffff803`157c7442     : ffffd082`f50f1910 fffffe8d`3d9727c0 00000000`00000010 fffffe8d`00000000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x1cc
fffffe8d`3d972780 fffff803`1564e1f8     : ffffd083`203e3891 00000000`00000001 ffffd083`04595740 fffff803`1545c249 : nt!SmPageRead+0x42
fffffe8d`3d9727c0 fffff803`155430c7     : 00000000`00000002 fffffe8d`3d972900 ffffd082`f50f1800 ffffd082`f50f1800 : nt!MiIssueHardFaultIo+0x10ac48
fffffe8d`3d972810 fffff803`15468071     : 00000000`c0033333 00000000`00000001 000001bf`03c50000 00000000`00000000 : nt!MiIssueHardFault+0x207
fffffe8d`3d9728c0 fffff803`15626f7e     : 00000000`00000000 fffffe8d`3d972a60 00004d70`032b3800 ffffd083`00000000 : nt!MmAccessFault+0x331
fffffe8d`3d9729e0 00007fff`0b1075cd     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x37e
00000002`fc9ff070 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`0b1075cd

SYMBOL_NAME:  nt!ST_STORE<SM_TRAITS>::StDmPageError+fb

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.4036

STACK_COMMAND:  .process /r /p 0xffffd083045950c0; .thread 0xffffd082fbc7d080 ; kb

BUCKET_ID_FUNC_OFFSET:  fb

FAILURE_BUCKET_ID:  0x12B_c00002c4_StCtDecompressFailed_nt!ST_STORE_SM_TRAITS_::StDmPageError

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c6a6bb4d-3b77-dff6-2d9b-75f5d0f61a50}

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

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

6 answers

Answer 1

Anonymous

Nevermind, it got fixed, It couldnt handle xmp, so i just turned it to the max ram speed, that the cpu supports

0 comments

Answer 2

Hi, thanks for the reply, i have the newest drivers for the gpu, i did the check the memory and no problems were found and virtual memory is set to automatic. Im thinking that it is probably the gpu dying, because the system is 7 or 8 years old. I'll try playing some games till i get some kind of error or anything, and i'll report it straight here for you if any error or BSOD occurs.

Answer 3

Hi PavelEU.

Thank you for your reply. I understand that you set the RAM to the maximum running speed supported by the CPU and this issue seems to be resolved.

May I ask if you are still having problems now?

Thank you for your understanding and support.

Best regards,

Zev - MSFT | Microsoft Community Support Specialist

Answer 4

well, another bsod happened, here's the log

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff8003b2dc8aa, Address of the instruction which caused the BugCheck
Arg3: ffffe301771b2900, 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: 3453

    Key  : Analysis.Elapsed.mSec
    Value: 18806

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x3b

    Key  : Bugcheck.Code.TargetModel
    Value: 0x3b

    Key  : Dump.Attributes.AsUlong
    Value: 808

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: AV_nt!MiRewriteTrimPteAsDemandZero

    Key  : Failure.Hash
    Value: {2c833668-2175-f37c-3033-39f0ad4130a6}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1417cf94

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    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: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 4853999

    Key  : Hypervisor.Flags.ValueHex
    Value: 4a10ef

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7

BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8003b2dc8aa

BUGCHECK_P3: ffffe301771b2900

BUGCHECK_P4: 0

FILE_IN_CAB:  090224-5687-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b

DUMP_FILE_ATTRIBUTES: 0x808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffbc8da51e90c0

CONTEXT:  ffffe301771b2900 -- (.cxr 0xffffe301771b2900)
rax=00726b3000374eb3 rbx=8a000002ca5d1863 rcx=ffffbc8da382e740
rdx=ffff9600085f1730 rsi=ffff9600085f1730 rdi=0000000000000000
rip=fffff8003b2dc8aa rsp=ffffe188b2358570 rbp=ffffbc8da382e740
 r8=0000000000000800  r9=0000000000000800 r10=0000000300002080
r11=ffffe188b2358580 r12=ffffbc8da382e740 r13=0000000000000000
r14=0000000000000001 r15=fffff5011d172170
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050202
nt!MiRewriteTrimPteAsDemandZero+0x186:
fffff800`3b2dc8aa 038b5c244849    add     ecx,dword ptr [rbx+4948245Ch] ds:002b:8a000003`13a53cbf=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  RobloxPlayerBe

STACK_TEXT:  
ffffe188`b2358570 fffff800`3b32bd48     : 8a000002`ca5d1863 00000003`00002080 00000000`00000000 ffff9600`085f1730 : nt!MiRewriteTrimPteAsDemandZero+0x186
ffffe188`b23585b0 fffff800`3b32b421     : 00000000`00000000 00000000`085f1730 ffffffff`00000000 80000002`ca5d1863 : nt!MiWsleFree+0x358
ffffe188`b2358620 fffff800`3b3480a3     : ffffe188`b2358a60 fffff501`1d172170 ffffbc8d`a382e740 00000000`00000000 : nt!MiFreeWsleList+0x1b1
ffffe188`b23587f0 fffff800`3b42b305     : ffffbc8d`a51e90c0 ffffbc8d`a51e90c0 00000000`00000020 00000000`00001693 : nt!NtUnlockVirtualMemory+0x723
ffffe188`b23589e0 00007ffc`ef7dfa62     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
0000006b`8a9fe720 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`ef7dfa62

SYMBOL_NAME:  nt!MiRewriteTrimPteAsDemandZero+186

MODULE_NAME: nt

IMAGE_VERSION:  10.0.22621.4036

STACK_COMMAND:  .cxr 0xffffe301771b2900 ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  186

FAILURE_BUCKET_ID:  AV_nt!MiRewriteTrimPteAsDemandZero

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {2c833668-2175-f37c-3033-39f0ad4130a6}

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

this was in the event viewer :

The driver \Driver\WUDFRd failed to load for the device ROOT\CAMERA\0000.

The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff8003b2dc8aa, 0xffffe301771b2900, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\090224-5687-01.dmp. Report Id: 6f1e23df-8658-4cb0-aeb6-07192de4ae2e.

Answer 5

Hi PavelEU.

Welcome to Microsoft Community.

In your description, you are experiencing a number of issues with your computer including a blue screen.

I note that you have provided us with a couple of Event Viewer logs along with the blue screen logs, thank you for your efforts in trying to resolve this issue, your efforts deserve to be recognized. I do understand the frustration of not being able to use your computer correctly with the current problem.Based on the contents of your event viewer, this is most likely a failure of your graphics card or graphics driver that is causing problems with kernel calls.

Please download and install the appropriate driver for your graphics card, depending on its model or serial number, via the following link

https://www.nvidia.com/en-us/geforce/drivers/

Disclaimer: This is a non-Microsoft website. The page appears to be providing accurate and safe information. Watch out for ads on the site that may advertise products frequently classified as PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

Meanwhile, according to the blue screen logs you provided, it is very likely that there is some fault in your memory, causing ntkrnlmp.exe (kernel) to not be able to call or run correctly, resulting in a blue screen.

Please refer to the following steps to check your memory

Tap Windows+R, type MdSched and tap Enter to open the memory diagnostic tool

Tap Restart Now and check the problem

Follow the prompts to check, wait for it to complete, and check the report to see if there is any problem detected.

Then, refer to the following steps to set the virtual memory to automatic

1 Right-click the Start button and select Settings>System>About (System Information)>Advanced System Settings

2 Click the Advanced tab, and in the Performance section, click the Settings button

3 Click the Advanced tab in the new window, find the Virtual Memory section and click Change

4 Check Automatically manage paging file sizes for all drives.

5 Click OK

If you are still having problems with the above steps, please refer to the following link to enter Safe Mode

Windows startup settings - Microsoft Support

In Safe Mode, install the previously downloaded video card driver again and see if you have the same problem in Safe Mode after this.

If the problem still exists, then this is most likely a hardware failure in your RAM, please contact ASUS support via the link below so that they can perform further checks on your hardware.

https://www.asus.com/us/support/callus/

Disclaimer: Microsoft provides no assurances and/or warranties, implied or otherwise, and is not responsible for the information you receive from the third-party linked sites or any support related to technology.

Thank you for your understanding and support.

Best regards,

Zev - MSFT | Microsoft Community Support Specialist