http://bugs.winehq.org/show_bug.cgi?id=58086
Bug ID: 58086 Summary: Conflict during update of MingW has corrupted WINESYSTEMDLLPATH; and or Vulkantools SPIRV (more likely) has overwritten %SystemRoot% Product: Wine Version: 10.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: jorik.de.leeuw360@gmail.com Distribution: ---
Created attachment 78339 --> http://bugs.winehq.org/attachment.cgi?id=78339 Wine depending on MingW (dnf remove Mingw-*)
Conflict during update of MingW has corrupted WINESYSTEMDLLPATH; and or Vulkantools SPIRV (more likely) has overwritten %SystemRoot%
https://forum.winehq.org/viewtopic.php?t=40520
I have keeped track of this issue .... and i've broken the system completely.
Due to several leaks and several system bugs you should take a look at that. I ran DXDiag and Fedora core started 'two' updates of which the name are unavailable.
This is the very short version
" 0874:trace:file:nt_to_unix_file_name_no_root L"usr\x86_64-w64-mingw32\sys-root\mingw\bin\kernel32.dll" not found in "/home/[REDACTED]/.wine/dosdevices/z:" 0874:warn:file:NtCreateFile L"\??\Z:\usr\x86_64-w64-mingw32\sys-root\mingw\bin\kernel32.dll" not found (c0000034)"
Looking for Kernel32 in "/usr/x84_64-mingw32/sys-root/mingw/bin/".
I did ABNORMALLY ABRUPT a game while this was happening i saw a update running. I got back and none of the VulkanApplications 'but' vulkaninfo.exe and vkcube.exe did ran. The other applications primarily 3D Games that are not overridden by the Driver to Vulkan do run.
The others seemingly all corrupted.
I have tried troubleshooting this with AI and keeping AI up to date to relieve of having to ask Developers regarding a situation for Games that do not support them and vice versa.
This issue with Vulkan-Corruption also happens ALOT in Wink10. My other drive is accessible from Fedora Core but it has no bootmanager because it never got to repair itself. It takes about 52 minutes to boot it versus less than 30 seconds on fedora.
However it seems based on the development. You can delete the thread after you have seen it. The Linux Kernel seemingly got corrupted because it might be; when i ran Vulkaninfo.exe through BASH it did not stop running .........
-- > 013c:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFA, 0085FECC < --
Even after a complete 'powercycle' the problem remains.
I have seen such severe Vulkan crashes that i had to replace the CMOS because the Computer did not boot anymore.
Seemingly this spawns a Orphan Window and a lot more to take some time investigating this issue.