dpc watchdog violation debuged

Question

Bug：

==========

just after i install a new windows insider:

24H22024/6/1826120.961Windows Feature Experience Pack 1000.26100.8.0 and then the error just happened

I always have this error, can anyone help?

debug:

STACK_COMMAND:  .cxr; .ecxr ; kb

EXCEPTION_CODE_STR:  FBC9A4EE

EXCEPTION_STR:  WRONG_SYMBOLS

PROCESS_NAME:  ntoskrnl.wrong.symbols.exe

IMAGE_NAME:  ntoskrnl.wrong.symbols.exe

MODULE_NAME: nt_wrong_symbols

SYMBOL_NAME:  nt_wrong_symbols!FBC9A4EE144F000

FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X64_10.0.26100.961_(WinBuild.160101.0800)_TIMESTAMP_FBC9A4EE_nt_wrong_symbols!FBC9A4EE144F000

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {2a6b33a1-e00f-b2b7-e69c-4d94104b4d5e}

Followup:     MachineOwner

dump file:
https://ufile.io/pkit3n49

Answer 1

hi, i've fallow the article and rolled back into the normal version and still got the same problem, but this time my PC tell me that it can't generate the dump file, but the error is still dpc watchdog error, how can i fix this?

Answer 2

Hello mochacha Rancho,

Welcome to Microsoft Community.

Looks like you're having blue screen problems. That is very annoying. I will do my best to help you. Here are some of my suggestions:

Based on the information you have provided, this is due to a driver anomaly due to the fact that you are using Windows Insider. Drivers may not be able to keep up with the compatibility of the Windows version.

According to the dump file you provided, the blue screen is caused by igdkmdn64.sys. This is Intel's core graphics driver.

You can fix it according to the official article provided by intel: 

https://www.intel.com/content/www/us/en/support/articles/000094672/graphics.html

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.

If the problem persists and affects your daily use, try exiting Windows Insider and rolling back to a normal Windows version.

Hope this helps.

Thank you for your patience and cooperation.

Best Regards,

William.S - MSFT