Semi-reproducible weird freezes

Running /home/rabcor/.local/share/lutris/runners/wine/tkg-4.0-x86_64/bin/wine /run/media/rabcor/Storage/Lutris/overwatch/drive_c/Program Files (x86)/Battle.net/Battle.net.exe --exec=launch Pro
wine: cannot find L"C:\\windows\\system32\\winemenubuilder.exe"
[0322/192714.129:ERROR:network_change_notifier_win.cc(157)] WSALookupServiceBegin failed with: 8
[0322/192714.148:ERROR:gpu_process_transport_factory.cc(1031)] Lost UI shared context.
[2019-03-22T19:27:14Z][..\source\main.cpp:475][INFO]: System Survey 2.4.1.48, Data Version 3, Git Revision v2.4.0.47-7-g0e76705e, Copyright (C) 2013 Blizzard Entertainment. All rights reserved.
[2019-03-22T19:27:14Z][..\source\main.cpp:549][INFO]: Exit value: 0
info:  Game: Battle.net.exe
info:  DXVK: v0.96
warn:  OpenVR: Failed to locate module
info:  Enabled instance extensions:
info:    VK_KHR_get_physical_device_properties2
info:    VK_KHR_surface
info:    VK_KHR_win32_surface
info:  GeForce RTX 2060:
info:    Driver: 418.43.0
info:    Vulkan: 1.1.95
info:    Memory Heap[0]: 
info:      Size: 6144 MiB
info:      Flags: 0x1
info:      Memory Type[7]: Property Flags = 0x1
info:      Memory Type[8]: Property Flags = 0x1
info:    Memory Heap[1]: 
info:      Size: 11910 MiB
info:      Flags: 0x0
info:      Memory Type[0]: Property Flags = 0x0
info:      Memory Type[1]: Property Flags = 0x0
info:      Memory Type[2]: Property Flags = 0x0
info:      Memory Type[3]: Property Flags = 0x0
info:      Memory Type[4]: Property Flags = 0x0
info:      Memory Type[5]: Property Flags = 0x0
info:      Memory Type[6]: Property Flags = 0x0
info:      Memory Type[9]: Property Flags = 0x6
info:      Memory Type[10]: Property Flags = 0xe
info:  GeForce RTX 2060:
info:    Driver: 418.43.0
info:    Vulkan: 1.1.95
info:    Memory Heap[0]: 
info:      Size: 6144 MiB
info:      Flags: 0x1
info:      Memory Type[7]: Property Flags = 0x1
info:      Memory Type[8]: Property Flags = 0x1
info:    Memory Heap[1]: 
info:      Size: 11910 MiB
info:      Flags: 0x0
info:      Memory Type[0]: Property Flags = 0x0
info:      Memory Type[1]: Property Flags = 0x0
info:      Memory Type[2]: Property Flags = 0x0
info:      Memory Type[3]: Property Flags = 0x0
info:      Memory Type[4]: Property Flags = 0x0
info:      Memory Type[5]: Property Flags = 0x0
info:      Memory Type[6]: Property Flags = 0x0
info:      Memory Type[9]: Property Flags = 0x6
info:      Memory Type[10]: Property Flags = 0xe
info:  D3D11CoreCreateDevice: Probing D3D_FEATURE_LEVEL_11_1
info:  D3D11CoreCreateDevice: Using feature level D3D_FEATURE_LEVEL_11_1
info:  Enabled device extensions:
info:    VK_EXT_shader_viewport_index_layer
info:    VK_EXT_transform_feedback
info:    VK_EXT_vertex_attribute_divisor
info:    VK_KHR_dedicated_allocation
info:    VK_KHR_descriptor_update_template
info:    VK_KHR_driver_properties
info:    VK_KHR_get_memory_requirements2
info:    VK_KHR_image_format_list
info:    VK_KHR_maintenance1
info:    VK_KHR_maintenance2
info:    VK_KHR_sampler_mirror_clamp_to_edge
info:    VK_KHR_shader_draw_parameters
info:    VK_KHR_swapchain
info:  DXVK: Read 29 valid state cache entries
info:  DXVK: Using 9 compiler threads
warn:  D3D11DeviceContext::QueryInterface: Unknown interface query
warn:  b4e3c01d-e79e-4637-91b2-510e9f4c9b8f
info:  DXGI: NvAPI workaround enabled, reporting AMD GPU
err:   DXGI: CheckInterfaceSupport: Unsupported interface
err:   54ec77fa-1377-44e6-8c32-88fd5f44c84c
info:  DXGI: NvAPI workaround enabled, reporting AMD GPU
warn:  D3D11Device::GetDeviceRemovedReason: Stub
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  035f3ab4-482e-4e50-b41f-8a7f8bd8960b
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  9d8e1289-d7b3-465f-8126-250e349af85d
info:  Presenter: Actual swap chain properties:
  Format:       VK_FORMAT_B8G8R8A8_UNORM
  Present mode: VK_PRESENT_MODE_IMMEDIATE_KHR
  Buffer size:  104x1
  Image count:  2
warn:  DXGI: MakeWindowAssociation: Ignoring flags
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  9d8e1289-d7b3-465f-8126-250e349af85d
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  035f3ab4-482e-4e50-b41f-8a7f8bd8960b
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  9d8e1289-d7b3-465f-8126-250e349af85d
info:  Presenter: Actual swap chain properties:
  Format:       VK_FORMAT_B8G8R8A8_UNORM
  Present mode: VK_PRESENT_MODE_IMMEDIATE_KHR
  Buffer size:  1200x780
  Image count:  2
warn:  DXGI: MakeWindowAssociation: Ignoring flags
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  9d8e1289-d7b3-465f-8126-250e349af85d
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
info:  Presenter: Actual swap chain properties:
  Format:       VK_FORMAT_B8G8R8A8_UNORM
  Present mode: VK_PRESENT_MODE_FIFO_KHR
  Buffer size:  1200x780
  Image count:  3
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
warn:  D3D11Texture2D::QueryInterface: Unknown interface query
warn:  f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
[0322/192727.339:ERROR:mf_audio_decoder.cc(713)] Unsupported codec by MfAudioDecoder: 4
[0322/192727.340:ERROR:mf_video_decoder.cc(747)] Unsupported codec by MfVideoDecoder: 6

That's all I got. (For battle.net when things would 'soft' freeze for several seconds nonstop) Unless the unsupported codec caused it... There's no info in there.

I'm using optimus-manager, I'm running X with the nvidia gpu so the integrated graphics are completely unused (theoretically it should function just like a desktop)

thats not exactly true, your nvidia is doing all the work, but the intel iGPU is still used to display it. i dont know if its related (i dont think so, but who knows) but right now im helping 2 other users of optimus-manager who couldnt boot at all in intel mode and it just started happening for them too. but again, i dont think this is your issue.

to be honest, wine is not something i've played with much, but amd gpu? thats doesnt seem right.
how is directx and d3d handled? is there a way or re-installing it in wine/lutris?

anyway, D3D seems like the main contributor to your issues judging by the amount of errors it's producing right before it reaches the endpoint of:

Ah the amdgpu workaround thing is something proton does because some games have problems with nvidia cards, it shouldn't have any side effects really. it was something about games trying to use nvapi or physx or some ■■■■ when it's not available, causing problems. It's supposed to do that, in other words.

It could be that dxvk is leading to graphics driver freezes or something like that I suppose. It's a long shot, otherwise it could be an issue with vulkan. Worth looking into at least, since I don't have these freezes when I'm not doing something game related.

maybe wine forums? lutris? or post an issue and include that log you posted and maybe someone will know whats going on but i really dont have the slightest clue when it comes to wine/lutris/proton/etc..

best of luck, hope you get it figured out.

But not all games, right ? Specifically wine/lutris/windoze ?

I have an update. I was trying to launch overwatch and like mentioned in the OP; Battle net made my system go crazy, constantly freezing (as it was updating itself this time). It restarted once done and started updating overwatch, only this timeI waited for a while and my system actually crashed, like turned itself off.

When it rebooted I got this error on bootup:

[    0.228879] mce: [Hardware Error]: Machine check events logged
[    0.228880] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 4: be00000000800400
[    0.228883] mce: [Hardware Error]: TSC 0 ADDR 5513ed MISC 5513ed 
[    0.228886] mce: [Hardware Error]: PROCESSOR 0:906ea TIME 1555749709 SOCKET 0 APIC 0 microcode aa
[    0.392178] mce: [Hardware Error]: Machine check events logged
[    0.392185] mce: [Hardware Error]: CPU 3: Machine Check: 0 Bank 3: be00000000800400
[    0.392205] mce: [Hardware Error]: TSC 0 ADDR 5513ed MISC 5513ed 
[    0.392208] mce: [Hardware Error]: PROCESSOR 0:906ea TIME 1555749709 SOCKET 0 APIC 6 microcode aa

So now we have some kind of lead (I'm not entirely certain, but I think the hard crash was caused by the CPU overheating)

I cannot update the game.

A weird thing I noticed when the system freezes is that my Caps Lock LED starts constantly blinking.

Update: Brainstorming a solution for this problem, I tried switching to the igpu.

Doing so made battle.net not crash everything, this way i was ablle to successfully update overwatch lol. So the problem has to lay somewhere with the nvidia driver or optimus-manager.

Another update: Playing hearthstone will consistently create the same kinds of freezes as battle net (e.g. suddenly the screen freezes and no input will be taken, sound still plays as normal) however it doesn't seem to overheat my cpu and crash my system this time... So there's that.

A bit of a shame I can't check if the issue is just with optimus-manager since the games I'm crashing on all use dxvk and optimus manager (or maybe nvidia xrun) are my only options for this.

you have other options like prime and optimus-switch that both work great.

if you decide to get rid of optimus-manager, be sure to remove it properly.

You're right I should probably test the alternatives, it's just a bit of a pain in the ass.

My point however was that it only happens (so far) when DXVK is in use, and I can't use that with bumblebee.

I'll give optimus-switch a try, but I have not followed Jonathon's guide to enable PRIME so I imagine I should do that too. Like I said tho, pain in the ass.

The problem seems to have been noticably mitigated by following Jonathon's guide to use Prime. I can't be certain to what extent yet though.

I got another freeze while updating origin, this is the terminal output at the time.

9:104:0501/072413:ERROR:tcp_socket_win.cc(786)] connect failed: 10049
[59:104:0501/072413:ERROR:tcp_socket_win.cc(786)] connect failed: 10049
[59:104:0501/072413:ERROR:tcp_socket_win.cc(786)] connect failed: 10049
[59:104:0501/072413:ERROR:tcp_socket_win.cc(786)] connect failed: 10049
[59:104:0501/072413:ERROR:tcp_socket_win.cc(786)] connect failed: 10049
[59:104:0501/072414:ERROR:tcp_socket_win.cc(786)] connect faWaiting on children
iled: 10049
[59:104:0501/072414:ERROR:tcp_socket_win.cc(786)] connect failed: 10049
2019-05-01 07:24:14,011: Unable to read stat for process 16373
2019-05-01 07:24:14,011: Unable to read stat for process 16373
Waiting on children
[59:104:0501/072414:ERROR:tcp_socket_win.cc(786)] connect failed: 10049
2019-05-01 07:24:58,610: Unable to read stat for process 15974
2019-05-01 07:24:58,610: Unable to read stat for process 15974
Waiting on children
2019-05-01 07:24:58,629: Unable to read stat for process 16163
2019-05-01 07:24:58,629: Unable to read stat for process 16163
Waiting on children
Waiting on children
2019-05-01 07:25:00,624: Unable to read stat for process 21263
2019-05-01 07:25:00,625: Unable to read stat for process 21263
Waiting on children

I was able to successfully play Hearthstone without freezes, and Battle Net did not cause any freezes either when idle (but I've seen this problem mostly when it's downloading/installing/updating things so I can't be sure it's fixed on that end)

Edit: Don't think I'll test optimus-switch, I may try optimus-manager again tho seeing as I have a different setup right now it might not break things again if I reinstall it. It's better than optimus-switch because it doesn't require a reboot.

next time when it happens, use top or htop and see what processes are causing issues.

it's purposely made like that for stability. i found trying to properly unload and load the appropriate modules without a reboot to be less stable and have issues with lockups. by powering down the nvidia gpu and then removing it sysfs and also making it so the nvidia modules cant be loaded everything works as intended. not to mention logging out and back in again loses your current session anyway so why not just take the few extra seconds to reboot.

some folks just like the idea of having a long uptime and dont reboot for long periods and for them maybe this isnt the way, or those that have abnormally long boot times.

Personal preference, I didn't have any stability issues with optimus manager besides these crashes (but they're even happening on just prime, only less, haven't had a full crash yet but we'll see)

Granted I rarely switched between the cards, the only reason I had to go to intel was for when using the nvidia gpu would lead to a crash (e.g. when updating ■■■■ on battle net or playing hearthstone, guess Idon't need it for the latter now tho)

How exactly though od I use top or htop to find a specific process? I've never really understood how to use top.

htop has more functionality and shows more processes, you can also kill process from htop whereas with top you would veiw what the process is and use a command like kill 21263 to kill the process.

so next time you run into that error, run top or htop or any process manager, find the process number and see what program it is, at least then you get an idea of where to look for issues.

though i dont think the new errors have anything to do with the old ones you mentioned earlier in the thread. these look like something it not allowing origin to connect. are you using a vpn? check firewall rules/logs and see if it's being blocked.

I am using a vpn yes, now that you mention it. I tried disabling it and I didn't run into the same problems with origin... Which also means I didn't get the freezes of course, but it's strange...

I guess i'll have to run the laptop for a while like it is now until I encounter another freeze, or don't.

1 Like

if that all works out, you can likely make it work with the vpn by adding/removing a rule/permission. origin probably uses a port that is blocked by default by either your vpn or vpn client.

But... but, @dglt dont you know that every time you reboot a Linux computer a new born kitten dies???

Kill a kitten, or have a stable computing experience. Cmon, that's a no brainer. :wink:

up times for me couldnt be any less important. most times at night i just close the lid and the following day i wake and then reboot (and most of the time for no good reason other than habit)

I actually turn it off at night you know...

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by