Gaming on Intel® Processors with Intel® Graphics
Ask questions and get answers, tips/tweaks, and techniques from product and technology experts

Driver causing crashes in CS2

Rafa3
Beginner
34 Views

- CPU: 1215U

- RAM: 16GB DDR4 @3200Mhz

- OS: Windows 11

- iGPU's drivers: the latest (32.0.101.7088)

 

Hello. CS2 crashed after opening it. I attached here the dump file that CS2 generated. After analysing it with WinDbg, it says that  igd10umt64xe.DLL is to blame. Specifically:

 

*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************


KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 671

    Key  : Analysis.Elapsed.mSec
    Value: 2363

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29617.1000

    Key  : Analysis.Version.Description
    Value: 10.2604.29.1 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2604.29.1

    Key  : Failure.Bucket
    Value: INVALID_POINTER_READ_c0000005_igd10umt64xe.DLL!Unknown

    Key  : Failure.Exception.Code
    Value: 0xc0000005

    Key  : Failure.Exception.IP.Address
    Value: 0x7fff10334496

    Key  : Failure.Exception.IP.Module
    Value: igd10umt64xe

    Key  : Failure.Exception.IP.Offset
    Value: 0xa4496

    Key  : Failure.Hash
    Value: {50f3037f-17d3-fd14-0052-46e3d505301c}

    Key  : Failure.ProblemClass.Primary
    Value: INVALID_POINTER_READ

    Key  : Faulting.IP.Type
    Value: Paged

    Key  : Timeline.Process.Start.DeltaSec
    Value: 51


FILE_IN_CAB:  cs2_2026_0721_222401_0_accessviolation.mdmp

NTGLOBALFLAG:  0

CONTEXT:  (.ecxr)rax=0000000000000000 rbx=000002ad81734bc0 rcx=000000000000001a
rdx=0000000000000003 rsi=0000000000000000 rdi=000002acb677e600
rip=00007fff10334496 rsp=000000d280baebf0 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000001 r10=000002acb677e600
r11=000000d280baee40 r12=000002acaf036610 r13=0000000000000044
r14=000000d280baef20 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
igd10umt64xe!QueryDesiredMode1+0x50c76:
00007fff`10334496 4883780800      cmp     qword ptr [rax+8],0 ds:00000000`00000008=????????????????
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)ExceptionAddress: 00007fff10334496 (igd10umt64xe!QueryDesiredMode1+0x0000000000050c76)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000008
Attempt to read from address 0000000000000008

PROCESS_NAME:  cs2.exe

READ_ADDRESS:  0000000000000008 

ERROR_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en 0x%p hace referencia a la memoria en 0x%p. La memoria no se pudo %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000008

STACK_TEXT:  
000000d2`80baebf0 00007fff`10339a2a     : 000002ad`81734bc0 000002ac`b677e600 00000000`00000000 000002ad`81734bc0 : igd10umt64xe!QueryDesiredMode1+0x50c76
000000d2`80baec60 00007fff`102e85ee     : 000002ad`5d736478 00000000`00000000 000002ad`5d736320 000002ac`c17e0460 : igd10umt64xe!QueryDesiredMode1+0x5620a
000000d2`80baecc0 00007fff`102efb03     : 00000000`00000000 000002ac`b677e600 000002ac`00000001 000002ac`bf2fe7c8 : igd10umt64xe!QueryDesiredMode1+0x4dce
000000d2`80baed10 00007fff`102e83cc     : 00000000`00000000 000000d2`80baedd0 00000000`00000000 00007fff`102ea37d : igd10umt64xe!QueryDesiredMode1+0xc2e3
000000d2`80baed50 00007fff`74022e7b     : 000002ad`5d736320 00000000`00000000 00000000`00000000 000002ac`c17e0460 : igd10umt64xe!QueryDesiredMode1+0x4bac
000000d2`80baedb0 00007fff`16cddc6d     : 00007fff`170e54a0 00000000`00000000 00000000`00000000 00000000`00000011 : d3d11!CContext::TID3D11DeviceContext_UpdateSubresource_<1>+0x47b
000000d2`80baeeb0 00007fff`16d1ea07     : 000002ad`5d736320 000002ac`af036018 00000222`00000001 000000d2`ffffffff : rendersystemdx11+0x1dc6d
000000d2`80baef90 00007fff`16d1c117     : 00000000`00000000 00000222`14356af0 00000222`2c030000 00007fff`16cfaad0 : rendersystemdx11+0x5ea07
000000d2`80baf670 00007fff`16d1c694     : 00000000`ffffffff 00000222`14462238 00000222`14462200 00000222`14462200 : rendersystemdx11+0x5c117
000000d2`80baf6d0 00007fff`16cfaad9     : 00000222`14356af0 00007fff`16cfaad0 00000222`2c0300c0 00000222`14356af0 : rendersystemdx11+0x5c694
000000d2`80baf710 00007fff`30fc0324     : 00000000`00000148 00000000`00000000 00000222`14462200 00007fff`3104be32 : rendersystemdx11+0x3aad9
000000d2`80baf740 00007fff`30fc04e2     : 00000222`16030348 00000222`14356af0 00000222`14356af0 00000000`00000000 : tier0!ThreadInitOnceCall_Finish+0x34
000000d2`80baf790 00007fff`7d03e957     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tier0!ThreadInitOnceCall_Finish+0x1f2
000000d2`80baf800 00007fff`7db8ad6c     : 00000000`00000000 00000000`00000000 000004f0`fffffb30 000004d0`fffffb30 : kernel32!BaseThreadInitThunk+0x17
000000d2`80baf830 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x2c


IP_IN_PAGED_CODE: 
igd10umt64xe!QueryDesiredMode1+50c76
00007fff`10334496 4883780800      cmp     qword ptr [rax+8],0

SYMBOL_NAME:  igd10umt64xe+a4496

MODULE_NAME: igd10umt64xe

IMAGE_NAME:  igd10umt64xe.DLL

STACK_COMMAND: ~13s; .ecxr ; kb

FAILURE_BUCKET_ID:  INVALID_POINTER_READ_c0000005_igd10umt64xe.DLL!Unknown

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

IMAGE_VERSION:  32.0.101.7088

FAILURE_ID_HASH:  {50f3037f-17d3-fd14-0052-46e3d505301c}

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

 

0 Kudos
1 Reply
Jay_Intel
Moderator
15 Views

Hi Rafa3, 

  

Thank you for reaching out to the Intel Community Forum. To assist us in investigating the issue, please provide the following details: 

  

When did the issue start? Was it after a specific driver update or game patch? 

What are the troubleshooting steps that you tried so far?  

Have you used Display Driver Uninstaller (DDU) to completely remove all residual drivers and installed a new one? 

Have you tried adjusting the graphics settings? 

Which gaming platform did you use to download the game? 

Have you tried rolling back to older drivers to see if the issue persists?

  

Additionally, to gain a comprehensive understanding of your system, please use the System Support Utility (SSU). This tool will generate a text file compiling all your system information, additionally kindly uncheck the networking field to avoid exposing your network information. You can follow the instructions at this link and send the text file here. Help Guide for the Intel® System Support Utility

  

If you have any questions, please let us know. Thank you. 

  

Best regards, 

  

Louie Jay J. 

Intel Customer Support Technician 


0 Kudos
Reply