New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mortal Combat X: Driver Crash/GPU hangs after dxgi changes #342

Closed
pingubot opened this Issue May 4, 2018 · 3 comments

Comments

Projects
None yet
2 participants
@pingubot

pingubot commented May 4, 2018

MKX crashes the gpu when loading a map. Simply start a singleplayer 1vs1 match. The following messages are shown in dmesg:

[13498.656207] NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception on GPC 0: WIDTH CT Violation. Coordinates: (0x3c0, 0x0)
[13498.656213] NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x500420=0x80000010 0x500434=0x3c0 0x500438=0xc00 0x50043c=0x0
[13498.656221] NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception on GPC 1: WIDTH CT Violation. Coordinates: (0x3e0, 0x10)
[13498.656225] NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x508420=0x80000010 0x508434=0x1003e0 0x508438=0xc00 0x50843c=0x0
[13498.656232] NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception on GPC 2: WIDTH CT Violation. Coordinates: (0x3d0, 0x0)
[13498.656236] NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x510420=0x80000010 0x510434=0x3d0 0x510438=0xc00 0x51043c=0x0
[13498.656243] NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception on GPC 3: WIDTH CT Violation. Coordinates: (0x3e0, 0x0)
[13498.656246] NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x518420=0x80000010 0x518434=0x3e0 0x518438=0xc00 0x51843c=0x0
[13498.656255] NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ChID 002b, Class 0000b197, Offset 00000a10, Data 44070000

Works fine up to commit: commit 4c298d4
Commit: commit 4c298d4 seems to break it.

System information

  • GPU: GTX 970
  • Driver: 396.18.07
  • Wine version: 3.7

Apitrace file(s)

https://drive.google.com/open?id=1WWLek6-MamG-kMVy_ZUuPreGosCFXDCv

Vulkan Validation file:

mkx.log

@pingubot

This comment has been minimized.

pingubot commented May 4, 2018

@pdaniell-nv, @jeffbolznv:

As those crashes are impossible to debug for @doitsujin , it would be fantastic if you could bring in some light what could cause that crashes and, if technically possible, how the dev could debug that on his own.
Many thanks in advance !!

@jeffbolznv

This comment has been minimized.

jeffbolznv commented May 4, 2018

Hi @pingubot,

It's very likely that GPU exception is caused by this error in the validation log:

DS(ERROR / SPEC): object: 0x0 type: 0 msgNum: 155191012 - vkCreateFramebuffer(): VkFramebufferCreateInfo attachment #0 mip level 0 has dimensions smaller than the corresponding framebuffer dimensions. Here are the respective dimensions for attachment #0, framebuffer:
width: 960, 1920
height: 540, 1080
layerCount: 1, 1
The spec valid usage text states 'Each element of pAttachments must have dimensions at least as large as the corresponding framebuffer dimension' (https://www.khronos.org/registry/vulkan/specs/1.0/html/vkspec.html#VUID-VkFramebufferCreateInfo-pAttachments-00882)
@pingubot

This comment has been minimized.

pingubot commented May 5, 2018

@jeffbolznv : Many thanks for your help !

@doitsujin : fixed in fb3dbd8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment