*** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys

ubuysa said:
Try this one: 091724-7125-01.dmp
Click to expand...
This one not getting that error:

Code: 
************* 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.016 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 42

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


Loading Dump File [C:\Users\User\Desktop\091724-7125-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Deferred                                       symsrv*symsrv.dll*C:\WindowsSymbols*https://msdl.microsoft.com/download/symbols
Symbol search path is: srv*;symsrv*symsrv.dll*C:\WindowsSymbols*https://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 22621 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff807`5aa00000 PsLoadedModuleList = 0xfffff807`5b6134f0
Debug session time: Tue Sep 17 21:00:48.649 2024 (UTC - 7:00)
System Uptime: 0 days 0:01:01.285
Loading Kernel Symbols
...............................................................
................................................................
............................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000076`7f619018).  Type ".hh dbgerr001" for details
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`5ae16000 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff807`59936f40=0000000000000119
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000005, The subtype of the BugCheck:
Arg2: ffff9a010ef65000
Arg3: ffff9a010f0467a0
Arg4: 000000000000440f

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

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** WARNING: Check Image - Checksum mismatch - Dump: 0x4921ae, File: 0x48c0a4 - C:\ProgramData\Dbg\sym\dxgkrnl.sys\AC042CE6486000\dxgkrnl.sys
*** WARNING: Check Image - Checksum mismatch - Dump: 0x4921ae, File: 0x48c0a4 - C:\WindowsSymbols\dxgkrnl.sys\AC042CE6486000\dxgkrnl.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2765

    Key  : Analysis.Elapsed.mSec
    Value: 7846

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27704.1001

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x119

    Key  : Bugcheck.Code.TargetModel
    Value: 0x119

    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: 0x119_5_DRIVER_FAULTED_SYSTEM_COMMAND_nvlddmkm!unknown_function

    Key  : Failure.Hash
    Value: {55a61c3c-91b1-e527-dcff-f2f0d7348227}

    Key  : Stack.Pointer
    Value: NMI


BUGCHECK_CODE:  119

BUGCHECK_P1: 5

BUGCHECK_P2: ffff9a010ef65000

BUGCHECK_P3: ffff9a010f0467a0

BUGCHECK_P4: 440f

FILE_IN_CAB:  091724-7125-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffff9a01153060c0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  MsMpEng.exe

DPC_STACK_BASE:  FFFFF80759938FB0

STACK_TEXT:  
fffff807`59936f38 fffff807`76fc5745     : 00000000`00000119 00000000`00000005 ffff9a01`0ef65000 ffff9a01`0f0467a0 : nt!KeBugCheckEx
fffff807`59936f40 fffff807`9281b0bb     : fffff807`59937007 ffff9a01`08e30310 ffff9a01`08e30318 ffff9a01`08e30320 : watchdog!WdLogSingleEntry5+0x3c05
fffff807`59936ff0 fffff807`92803c2d     : ffff9a01`0ef3f000 ffff9a01`0ef65000 fffff807`599372b0 ffff9a01`0ef65000 : dxgmms2!VidSchiProcessIsrFaultedPacket+0x25f
fffff807`59937070 fffff807`927eae9d     : 00000000`0000440f fffff807`8a855c80 ffff9a01`0ef3f000 fffff807`89d3fd06 : dxgmms2!VidSchDdiNotifyInterruptWorker+0x18bed
fffff807`599370f0 fffff807`6b20f784     : ffff9a01`082ad030 ffff9a01`08232000 00000000`00000000 fffff807`8aacbd58 : dxgmms2!VidSchDdiNotifyInterrupt+0xcd
fffff807`59937150 fffff807`8a87496f     : ffff9a01`082ad030 ffff9a01`08413000 fffff807`0000000e fffff807`00000000 : dxgkrnl!DxgNotifyInterruptCB+0x94
fffff807`599371c0 ffff9a01`082ad030     : ffff9a01`08413000 fffff807`0000000e fffff807`00000000 fffff807`8a8748f1 : nvlddmkm+0xbf496f
fffff807`599371c8 ffff9a01`08413000     : fffff807`0000000e fffff807`00000000 fffff807`8a8748f1 ffff9a01`08413000 : 0xffff9a01`082ad030
fffff807`599371d0 fffff807`0000000e     : fffff807`00000000 fffff807`8a8748f1 ffff9a01`08413000 00000000`00000000 : 0xffff9a01`08413000
fffff807`599371d8 fffff807`00000000     : fffff807`8a8748f1 ffff9a01`08413000 00000000`00000000 00000000`00000000 : 0xfffff807`0000000e
fffff807`599371e0 fffff807`8a8748f1     : ffff9a01`08413000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff807`00000000
fffff807`599371e8 ffff9a01`08413000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0xbf48f1
fffff807`599371f0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 ffff9a01`082ad030 : 0xffff9a01`08413000


SYMBOL_NAME:  nvlddmkm+bf496f

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .process /r /p 0xffff9a01125cc080; .thread 0xffff9a01153060c0 ; kb

BUCKET_ID_FUNC_OFFSET:  bf496f

FAILURE_BUCKET_ID:  0x119_5_DRIVER_FAULTED_SYSTEM_COMMAND_nvlddmkm!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {55a61c3c-91b1-e527-dcff-f2f0d7348227}

Followup:     MachineOwner
 
Is there perhaps a problem with the dump you were attempting to analyse? If you upload that dump we can see whether we can read it properly.
 
alotta said:
here reloaded
Click to expand...
Why have you attached the output as a .txt file? Please just enter any relevant WinDbg output wrapped in [code][/code] tags as you did before.

You were meant to run !sym noisy; .reload /f win32k.sys with the dump file you were originally trying to analyse. Could you please provide us with the original dump file which was having the issue?

I suspect that the issue was like the following:

Code: 
DBGENG:  RTCore64.sys - Partial symbol image load missing image info
DBGHELP: No header for RTCore64.sys.  Searching for dbg file
DBGHELP: .\RTCore64.dbg - file not found
DBGHELP: .\sys\RTCore64.dbg - path not found
DBGHELP: .\symbols\sys\RTCore64.dbg - path not found
DBGHELP: RTCore64.sys missing debug info.  Searching for pdb anyway
DBGHELP: Can't use symbol server for RTCore64.pdb - no header information available
DBGHELP: RTCore64.pdb - file not found
*** WARNING: Unable to verify timestamp for RTCore64.sys
DBGHELP: RTCore64 - no symbols loaded
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top