[SOLVED] New build Crashing on various games (dump file included)

Status
Not open for further replies.

kGius

Distinguished
Apr 4, 2013
44
1
18,545
2
Hi everyone,

I very recently built a new PC. All is running good, but I have some issues in various games where the game will just close, no error message. Games this has happened with are:

  • DOOM Eternal
  • Ori and the WIllof the Wisps
  • Wasteland 3
  • Horzon - Zero Dawn
  • CS:GO
The system:
MOBO: GIGABYTE Aorus B550 Elite
CPU: Rysen 5 3600
GPU: GIGABYTE Aorus Radeon RX5700XT
RAM: G.Skill Ripjaws 2x16GB 3600Mhz DDR4
Win 10 x86

As CS:GO is a game I ran on my previous build with no issues, I checked the crash dump file, not very experienced with this though, seems there is an issue with the shaders?
The dump file is located below. Any help on what's going on here exactly and what I could do to fix this would be much appreciated.

Some added info that might be useful:
I made an exact clone of my old SSD to a new M.2 SSD. My old system booted to the new rig with no issues except re-authenticating windows (legal copy). No non-game programs have caused any issues (Adobe package, audio DAW's etc). I know it's advised to make a clean win install for a new system but in my specific case this is very unpractical, mainly due to this also being a music production rig where there are a LOT of plugins involved in a lot of big projects. Doing a clean windows install would mean a buttload of re-installing and re-linking audio files and plugins, so I really would love to avoid this. Still, if this is causing these issues in any way I would of course be open to that solution.

Thanks so much in advance for having a look at this, if needed I can provide more crash dumps for other games, wouldn't be surprised to find them pointing to the same issue though as the crashes seem very identical (game loads, plays for while, like say between 15 and 40mins, then just blips out to windows screen with no error message, with exception of Wasteland 3 that occasionaly does give a "Wasteland 3 has crashed" message, but I've read that game is littered with bugs and crashes, so not my main focus at this moment).

Kind regards,
kGius

***
  • Exception Analysis
***


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4421

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on SKY_BEAST_MKII

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 260744

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

Key : Analysis.System
Value: CreateObject

Key : Timeline.OS.Boot.DeltaSec
Value: 34344

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

Key : WER.OS.Branch
Value: 19h1_release

Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z

Key : WER.OS.Version
Value: 10.0.18362.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

APPLICATION_VERIFIER_FLAGS: 0

CONTEXT: (.ecxr)
eax=57fad920 ebx=03b2f4e0 ecx=2a30f9e0 edx=03b8f014 esi=57fe6aac edi=00000000
eip=57925fef esp=2a30f8c0 ebp=2a30fa24 iopl=0 nv up ei pl zr na pe nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010246
stdshader_dx9+0x75fef:
57925fef 8bce mov ecx,esi
Resetting default scope

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 57925fef (stdshader_dx9+0x00075fef)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0

PROCESS_NAME: csgo.exe

ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

EXCEPTION_CODE_STR: c000001d

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
2a30fa24 57944d19 03b2f4e0 00000000 57fe6aac stdshader_dx9+0x75fef
2a30fa50 5a913367 03b2f4e0 00000000 00000000 stdshader_dx9!ftol3+0x1c49
2a30fa80 5a8ce59f 579ae9cc 00000000 131dd86c materialsystem+0x53367
2a30faa4 57f55c80 00000000 2a30fb00 00000000 materialsystem+0xe59f
2a30fad0 57f55a96 57fe5c00 00000249 2a30fb00 shaderapidx9+0x15c80
2a30faf8 57f49cb6 57fe5cd0 00000001 2a30fb20 shaderapidx9+0x15a96
2a30fb8c 57f4c2a7 164fdc4c 164fdc48 08838320 shaderapidx9+0x9cb6
2a30fc68 5a8f1996 164fdc4c ffffffff 00000000 shaderapidx9+0xc2a7
2a30fc84 5a8e3e21 164fdc48 5a8f0eca 5a9a14f8 materialsystem+0x31996
2a30fcb4 5a8f2b51 5a9a3d80 5a9a3d80 5a8f28aa materialsystem+0x23e21
2a30fce8 5a8e2180 5a9a3d80 5a8d3488 60038fff materialsystem+0x32b51
2a30fd2c 600942be 2a30fd84 2a30fd70 6008dc30 materialsystem+0x22180
2a30fd38 6008dc30 1cd5ded8 600942d0 6008de22 tier0!CThread::ThreadProcRunWithMinidumpHandler+0xe
2a30fd70 60094412 600942d0 600942d0 1cd5ded8 tier0!CatchAndWriteMiniDump+0x90
2a30fdb4 74a16359 1cd5ded8 74a16340 2a30fe20 tier0!CThread::ThreadProc+0x142
2a30fdc4 77007c24 1cd5ded8 a7f9eb36 00000000 kernel32!BaseThreadInitThunk+0x19
2a30fe20 77007bf4 ffffffff 77028feb 00000000 ntdll!__RtlUserThreadStart+0x2f
2a30fe30 00000000 600942d0 1cd5ded8 00000000 ntdll!_RtlUserThreadStart+0x1b


FAILED_INSTRUCTION_ADDRESS:
stdshader_dx9+75fef
57925fef 8bce mov ecx,esi

SYMBOL_NAME: stdshader_dx9+75fef

MODULE_NAME: stdshader_dx9

IMAGE_NAME: stdshader_dx9.dll

STACK_COMMAND: ~40s ; .ecxr ; kb

FAILURE_BUCKET_ID: ILLEGAL_INSTRUCTION_c000001d_stdshader_dx9.dll!Unknown

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x86

OSNAME: Windows 10

FAILURE_ID_HASH: {0f893c26-b8b1-f268-bf0e-2b1ed0179e2e}

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

kGius

Distinguished
Apr 4, 2013
44
1
18,545
2
  • Deleted by kGius
  • Reason: double
Re-installing DirectX seems to have fixed this particular issue, so i'll close this thread and make a new specific one if problems occur again.
 
Status
Not open for further replies.

ASK THE COMMUNITY

TRENDING THREADS