dxvk: [d3d9] : GTA San Andreas Crash
@doitsujin Hey, GTA San Andreas Crash (d3d9) sins commit bbe851f6a25b57f320362c97b12afc52bfa99da1
I check two of this commit artifacts
https://github.com/doitsujin/dxvk/actions/runs/9804878804
https://github.com/doitsujin/dxvk/actions/runs/9804865813
. . . .
hare is ultimate asi loader crash log
Unhandled exception at 0x6C8C3CC0 in igvk32.dll (+0x1a3cc0): 0xC0000005: Access violation reading location 0x0000049C.
Register dump:
EAX: 0x205C5290 EBX: 0x0D7CF0AC ECX: 0x00000000 EDX: 0x00000001
EDI: 0x205C4DD0 ESI: 0x0D7CF138 EBP: 0x0D7CEF30 EIP: 0x6C8C3CC0
ESP: 0x0D7CEE90 EFL: 0x00010293
CS: 0x00000023 SS: 0x0000002B
GS: 0x0000002B FS: 0x00000053
ES: 0x0000002B DS: 0x0000002B
ST00: 0x00000000 0x00000000 0x00000000 0x00000000 [ 0.000000 0.000000 0.000000 0.000000 ]
ST01: 0x00000000 0x00000000 0x00000000 0x00000000 [ 0.000000 0.000000 0.000000 0.000000 ]
ST02: 0x00000000 0x00000000 0x00000000 0x00000000 [ 0.000000 0.000000 0.000000 0.000000 ]
ST03: 0x00000000 0x00000000 0x00000000 0x00000000 [ 0.000000 0.000000 0.000000 0.000000 ]
ST04: 0x00000000 0x00000000 0x00000000 0x00000000 [ 0.000000 0.000000 0.000000 0.000000 ]
ST05: 0x00000000 0xB0000000 0x00004002 0x00000000 [ 0.000000 -0.000000 0.000000 0.000000 ]
ST06: 0x00000000 0xB0000000 0x00004002 0x00000000 [ 0.000000 -0.000000 0.000000 0.000000 ]
ST07: 0x00000000 0x00000000 0x00000000 0x002B0000 [ 0.000000 0.000000 0.000000 0.000000 ]
XMM00: 0x00000000 0x00000000 0x00000000 0x00000000 [ 0.000000 0.000000 0.000000 0.000000 ]
XMM01: 0x00000000 0x00000000 0x00000000 0x00000000 [ 0.000000 0.000000 0.000000 0.000000 ]
XMM02: 0x00000000 0x00000000 0x00000000 0x00000000 [ 0.000000 0.000000 0.000000 0.000000 ]
XMM03: 0x00000000 0x00000000 0x00000000 0x00000000 [ 0.000000 0.000000 0.000000 0.000000 ]
XMM04: 0x00000000 0x00000000 0x00000000 0x00000000 [ 0.000000 0.000000 0.000000 0.000000 ]
XMM05: 0x00000000 0x00000000 0x00000000 0x00000000 [ 0.000000 0.000000 0.000000 0.000000 ]
XMM06: 0x00000000 0x00000000 0x00000000 0x00000000 [ 0.000000 0.000000 0.000000 0.000000 ]
XMM07: 0x00000000 0x00000000 0x00000000 0x00000000 [ 0.000000 0.000000 0.000000 0.000000 ]
Stack dump:
0x0D7CEE90: 00000100 205C4DD0 AA5C0CB8 0D7CEEAC 0D7CED3C 0D7CEEE4
0x0D7CEEA8: 00000001 FFFFFFFF 0D7CEEF0 6C8AA13C 205C6F80 205C4DD0
0x0D7CEEC0: 205C5290 AA5C0CF8 205C6FA4 20915808 0D7CF0AC 205C6FA4
0x0D7CEED8: 20915C70 20915C70 00000000 0D7CEF24 6D024B0D 00000000
0x0D7CEEF0: 0D7CEF30 6C890FDE 20915808 205C6F80 0D7CEF1C 0D7CEF20
0x0D7CEF08: AA5C0D38 00000100 205C4DD0 0D7CF0AC 205C6F80 00000000
0x0D7CEF20: 00001000 0D7CEFA4 6D024730 FFFFFFFF 0D7CEFB0 6C8BD8BD
0x0D7CEF38: 0D7CF180 00000100 00000000 00000000 00000000 0D7CEF60
0x0D7CEF50: AA5C0DB8 00000000 205C4DD0 0D7CF0AC 00000000 018B0000
0x0D7CEF68: 000D3E88 00000000 0D7CEF90 77955F00 00000000 77955F2E
base: 0x0D6D0000 top: 0x0D7CEE90 bottom: 0x0D7D0000
Backtrace (may be wrong):
=>0x6C8C3CC0 SetDriverStoreDir+0x19b6b0 in igvk32.dll (+0x1a3cc0) (0x0D7CEF30)
0x6C8BD8BD SetDriverStoreDir+0x1952ad in igvk32.dll (+0x19d8bd) (0x0D7CEFB0)
0x6C83F5CF SetDriverStoreDir+0x116fbf in igvk32.dll (+0x11f5cf) (0x0D7CF00C)
0x6C74896C SetDriverStoreDir+0x2035c in igvk32.dll (+0x2896c) (0x0D7CF0A0)
0x6C735040 SetDriverStoreDir+0xca30 in igvk32.dll (+0x15040) (0x0D7CF0C8)
0x6EE0B11B Direct3DCreate9On12Ex+0xb98db in d3d9.dll (+0xbb11b) (0x0D7CF2C8)
0x6EE0B766 Direct3DCreate9On12Ex+0xb9f26 in d3d9.dll (+0xbb766) (0x0D7CF9B8)
0x6EE0E0B9 Direct3DCreate9On12Ex+0xbc879 in d3d9.dll (+0xbe0b9) (0x0D7CFD18)
0x6EE0E3CF Direct3DCreate9On12Ex+0xbcb8f in d3d9.dll (+0xbe3cf) (0x0D7CFD98)
0x6EDDA93E Direct3DCreate9On12Ex+0x890fe in d3d9.dll (+0x8a93e) (0x0D7CFDA8)
0x6EDDA93E Direct3DCreate9On12Ex+0x890fe in d3d9.dll (+0x8a93e)
```
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 26
Yea thank you for the bisect. The reason we were very much suspecting a Intel driver issue is that we don’t have a GPU to test on ourselves and it worked with other drivers seemingly. The Intel Windows driver also don’t always have a great history with this dxvk and the backtrace was looking weird. Just one of those extra annoying bugs heh.
Thanks for staying persistent and for the excellent work on the bisect!
To be fair, working with D3D9On12 bugs is usually more pleasant than the average because it’s completely open source.
Hey @K0bin …Now It’s working… Great👍👍