What does "Warning: Check Image" means?

Status
Not open for further replies.
G

goldencrixor

New member
Joined
Jun 16, 2023
Posts
3
Hello all,

Recently I was debugging a BSOD.

Literally, there was no clue to find out what was the source for it. I still didn't find.

Then I saw:

Code: 
WARNING: Check Image - Checksum mismatch - Dump: 0x127dc4, File: 0x127c0e - C:\ProgramData\Dbg\sym\dxgmms2.sys\FF1BB511117000\dxgmms2.sys

Does that mean corrupted/broken NVIDIA/AMD/Intel GPU drivers?

Or this sometimes happens randomly, due to Windows, debugging, and usual library download problems, etc...?

Thank you.
 
This appears to be an issue with your symbols, where have you set the symbol path to? You can find it by entering the following command in WinDbg while processing a dump file:

Code: 
.sympath

Please post the output of the command in your next post. Additionally, please enable debugging information for symbols and then reload them using the following command:

Code: 
!sym noisy; .reload /f /o

Please post the output of these two commands.
 
Hi @x BlueRobot, thank you for the response.


By the way, I've uploaded the relevant minidump if you need.

061623-4859-01.dmp



.sympath command output:

Code: 
8: kd> .sympath
Symbol search path is: srv*
Expanded Symbol search path is: cache*;SRV*https://msdl.microsoft.com/download/symbols

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*


I'm not sure how to "enable debugging information for symbols", but anyway I send you a screenshot from "Settings".


DbgX.Shell_wDnND2TZfp.png



For !sym noisy; .reload /f /o, I've entered it but it kept downloading for way too long. I've seen OK's, but I also saw "path not found" etc.

However, I usually don't have WARNINGS like that.


Is there any possibility that this WARNING: Check Image - Checksum dxgmms2.sys mismatch means corrupted/broken NVIDIA/AMD/Intel GPU drivers?
 
Last edited:
goldencrixor said:
I'm not sure how to "enable debugging information for symbols"
Click to expand...
I meant to have to set the "noisy" debugging prompts with !sym noisy and then do a reload so we can see what is happening while the symbols are being loaded. Your symbol path seems to be okay though.

I'm not getting any symbol warnings or errors with the dump file you've provided me with either. Was it the same one which you were looking at in your initial post?

Rich (BB code): 
8: kd> .exr ffffde0c464d19c8
ExceptionAddress: fffff80741e358bb (nt!SwapContext+0x00000000000000cb)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

It looks like the exception was thrown during a context switch so most of the information will be unable available which makes things more difficult to debug. For now, I would suggest following posting instructions and attaching the resultant .zip in your next post, as well as, running Driver Verifier using these instructions: Driver Verifier - BSOD related - Windows 11, 10, 8.1 and 8
 
x BlueRobot said:
Was it the same one which you were looking at in your initial post?
Click to expand...
Yes. I've opened it up again and saw the warning again.

Code: 
*** WARNING: Check Image - Checksum mismatch - Dump: 0x127dc4, File: 0x127c0e - C:\ProgramData\Dbg\sym\dxgmms2.sys\FF1BB511117000\dxgmms2.sys


And before that warning, there are bunch of symbol warnings.


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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ContextRecord                                 ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ContextRecord                                 ***
***                                                                   ***
*************************************************************************
*** WARNING: Check Image - Checksum mismatch - Dump: 0x127dc4, File: 0x127c0e - C:\ProgramData\Dbg\sym\dxgmms2.sys\FF1BB511117000\dxgmms2.sys



x BlueRobot said:
It looks like the exception was thrown during a context switch so most of the information will be unable available which makes things more difficult to debug. For now, I would suggest following posting instructions and attaching the resultant .zip in your next post, as well as, running Driver Verifier using these instructions: Driver Verifier - BSOD related - Windows 11, 10, 8.1 and 8
Click to expand...
Thank you.
 
goldencrixor said:
And before that warning, there are bunch of symbol warnings.
Click to expand...
It looks like you probably have a corrupted symbol cache, the command which I recommended earlier to you will clear the cache and download the symbols again.

Code: 
.reload /f /o

Yes, it will take some time to complete but please be patient and let it run.
 
Status
Not open for further replies.

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

Back
Top