[SOLVED - FS error] Wine can't load kernel32.dll and c0000135

okbzl · 2024-09-17 15:26:32

Wine version: staging 9.10 and wine 9.16 (aka whatever is in the main repository) with gecko and mono installed.
CPU: Intel(R) Core(TM) i3-2330M (4) @ 2.20 GHz
GPU: Intel 2nd Generation Core Processor Family Integrated Graphics Controller @ 1.10 GHz [Integrated]

Log (idk how to quote this like the posts on here, sorry bout that):

[chutienbinh@ASUS ~]$ winecfg
002c:fixme:winediag:loader_init wine-staging 9.10 is a testing version containing experimental patches.
002c:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org.
0050:err:ntoskrnl:ServiceMain Failed to load L"C:\\windows\\system32\\win32k.sys"
0050:err:ntoskrnl:ServiceMain Failed to load L"C:\\windows\\system32\\drivers\\dxgkrnl.sys"
0050:err:ntoskrnl:ServiceMain Failed to load L"C:\\windows\\system32\\drivers\\dxgmms1.sys"
0024:err:environ:run_wineboot boot event wait timed out
wine: could not load kernel32.dll, status c0000135
0058:fixme:gdi:get_default_fonts unhandled charset 0x000000a3 - use ANSI_CHARSET for default stock objects
006c:fixme:gdi:get_default_fonts unhandled charset 0x000000a3 - use ANSI_CHARSET for default stock objects
002c:fixme:gdi:get_default_fonts unhandled charset 0x000000a3 - use ANSI_CHARSET for default stock objects
006c:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
006c:err:winediag:nodrv_CreateWindow L"The explorer process failed to start."
002c:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
002c:err:winediag:nodrv_CreateWindow L"The explorer process failed to start."
008c:fixme:gdi:get_default_fonts unhandled charset 0x000000a3 - use ANSI_CHARSET for default stock objects
0074:fixme:gdi:get_default_fonts unhandled charset 0x000000a3 - use ANSI_CHARSET for default stock objects
007c:fixme:gdi:get_default_fonts unhandled charset 0x000000a3 - use ANSI_CHARSET for default stock objects
008c:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
008c:err:winediag:nodrv_CreateWindow L"The explorer process failed to start."
0074:err:ole:start_rpcss Failed to open RpcSs service
007c:err:ole:start_rpcss Failed to open RpcSs service
0074:err:ole:start_rpcss Failed to open RpcSs service
007c:err:ole:start_rpcss Failed to open RpcSs service

I already tried some of the fixes that people post on here, nothing work for me. Yes, I've exported WINEPREFIX, WINEARCH, WINEPATH, delete the wine prefix itself, run wine as root, etc. Oh, and for some reason, though the process should end by now, it's somehow still output logs.

Last edited by okbzl (2024-09-21 11:56:08)

V1del · 2024-09-17 15:55:19

What do you get from

glxinfo -B

? Chances are you're running normal mesa with xf86-video-intel installed. Try installing mesa-amber in case or uninstall xf86-video-intel, though this GPU is old enough that running xf86-video-intel might still be beneficial.

okbzl · 2024-09-17 22:16:13

[chutienbinh@ASUS ~]$ glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel (0x8086)
    Device: Mesa Intel(R) HD Graphics 3000 (SNB GT2) (0x116)
    Version: 24.2.2
    Accelerated: yes
    Video memory: 1536MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 3.3
    Max compat profile version: 3.3
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.0
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) HD Graphics 3000 (SNB GT2)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 24.2.2-arch1.1
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 3.3 (Compatibility Profile) Mesa 24.2.2-arch1.1
OpenGL shading language version string: 3.30
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.0 Mesa 24.2.2-arch1.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00

Last edited by okbzl (2024-09-18 08:14:00)

okbzl · 2024-09-17 22:25:50

Info after install mesa-amber (I haven't install xf86-video-intel yet)

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel Open Source Technology Center (0x8086)
    Device: Mesa DRI Intel(R) HD Graphics 3000 (SNB GT2) (0x116)
    Version: 21.3.9
    Accelerated: yes
    Video memory: 1536MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 3.3
    Max compat profile version: 3.0
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.0
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 3000 (SNB GT2)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 21.3.9-arch.6 Amber
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 3.0 Mesa 21.3.9-arch.6 Amber
OpenGL shading language version string: 1.30
OpenGL context flags: (none)

OpenGL ES profile version string: OpenGL ES 3.0 Mesa 21.3.9-arch.6 Amber
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00

Last edited by okbzl (2024-09-18 08:14:38)

okbzl · 2024-09-17 22:32:22

And yeah, wine still gave the same error, mesa-amber with xf86-video-intel or not

seth · 2024-09-18 07:20:28

Please use [code][/code] tags. Edit your posts in this regard.

I've exported WINEPREFIX, WINEARCH, WINEPATH

Stop that.
Unset all variables, run "wineserver -k", move away ~/.wine and try again to run "winecfg" - the errors there say that various dll's could not be loaded and the most likely explanation is that wine is looking at a path where they don't exist and cannot be copied.

okbzl · 2024-09-18 08:32:53

Yep, I've tried that. It doesn't work, same error as before. Strange thing is, all important files are at /usr/lib/wine/x86_64-windows, and I don't find all those files at the prefix, Maybe the problem is that wineprefix creation don't copy all (not any, some stuff are in those files) system32 and syswow64 files (so maybe that's why this also affected Lutris and Proton). I don't have a Debian/Ubuntu-based distro installed, but I don't get this error from either Mint and Pop.

Also, sorry about those untagged log, fixed now

okbzl · 2024-09-18 10:23:33

Oh wait, I see now. It's prefix creation took too long. So to describe my prefix ~1h and a half ago, practically just system32 and syswow64 folder and files are being copied. Now it looks like a normal C: drive on Windows.

Last edited by okbzl (2024-09-18 10:23:50)

okbzl · 2024-09-18 11:03:07

So I got curious and tried to boot winecfg from this prefix. Here's the log:

[chutienbinh@ASUS x86_64-windows]$ WINEPREFIX=~/wine winecfg
002c:fixme:winediag:loader_init wine-staging 9.10 is a testing version containing experimental patches.
002c:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org.
0090:err:sync:RtlpWaitForCriticalSection section 00006FFFFFFAD440 "../wine-staging/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0090, blocked by 0084, retrying (60 sec)
003c:err:service:process_send_command receiving command result timed out
003c:fixme:service:scmdatabase_autostart_services Auto-start service L"winebus" failed to start: 1053
003c:err:service:process_send_start_message service L"PlugPlay" failed to start
003c:fixme:service:scmdatabase_autostart_services Auto-start service L"PlugPlay" failed to start: 1053
0054:err:sync:RtlpWaitForCriticalSection section 00006FFFFFFAD440 "../wine-staging/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0054, blocked by 0064, retrying (60 sec)
003c:err:service:process_send_command receiving command result timed out
003c:fixme:service:scmdatabase_autostart_services Auto-start service L"nsiproxy" failed to start: 1053
003c:err:service:process_send_command receiving command result timed out
003c:fixme:service:scmdatabase_autostart_services Auto-start service L"NDIS" failed to start: 1053
0090:err:sync:RtlpWaitForCriticalSection section 00006FFFFFFAD440 "../wine-staging/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0090, blocked by 0084, retrying (60 sec)
0054:err:sync:RtlpWaitForCriticalSection section 00006FFFFFFAD440 "../wine-staging/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0054, blocked by 0064, retrying (60 sec)
0090:err:sync:RtlpWaitForCriticalSection section 00006FFFFFFAD440 "../wine-staging/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0090, blocked by 0084, retrying (60 sec)
0054:err:sync:RtlpWaitForCriticalSection section 00006FFFFFFAD440 "../wine-staging/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0054, blocked by 0064, retrying (60 sec)
0090:err:sync:RtlpWaitForCriticalSection section 00006FFFFFFAD440 "../wine-staging/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0090, blocked by 0084, retrying (60 sec)
0054:err:sync:RtlpWaitForCriticalSection section 00006FFFFFFAD440 "../wine-staging/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0054, blocked by 0064, retrying (60 sec)
0090:err:sync:RtlpWaitForCriticalSection section 00006FFFFFFAD440 "../wine-staging/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0090, blocked by 0084, retrying (60 sec)
0054:err:sync:RtlpWaitForCriticalSection section 00006FFFFFFAD440 "../wine-staging/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0054, blocked by 0064, retrying (60 sec)
0024:err:environ:run_wineboot boot event wait timed out
0090:err:sync:RtlpWaitForCriticalSection section 00006FFFFFFAD440 "../wine-staging/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0090, blocked by 0084, retrying (60 sec)
0054:err:sync:RtlpWaitForCriticalSection section 00006FFFFFFAD440 "../wine-staging/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0054, blocked by 0064, retrying (60 sec)
0090:err:sync:RtlpWaitForCriticalSection section 00006FFFFFFAD440 "../wine-staging/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0090, blocked by 0084, retrying (60 sec)
0054:err:sync:RtlpWaitForCriticalSection section 00006FFFFFFAD440 "../wine-staging/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0054, blocked by 0064, retrying (60 sec)
0090:err:sync:RtlpWaitForCriticalSection section 00006FFFFFFAD440 "../wine-staging/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0090, blocked by 0084, retrying (60 sec)
0054:err:sync:RtlpWaitForCriticalSection section 00006FFFFFFAD440 "../wine-staging/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0054, blocked by 0064, retrying (60 sec)
0090:err:sync:RtlpWaitForCriticalSection section 00006FFFFFFAD440 "../wine-staging/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0090, blocked by 0084, retrying (60 sec)
0054:err:sync:RtlpWaitForCriticalSection section 00006FFFFFFAD440 "../wine-staging/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0054, blocked by 0064, retrying (60 sec)
0090:err:sync:RtlpWaitForCriticalSection section 00006FFFFFFAD440 "../wine-staging/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0090, blocked by 0084, retrying (60 sec)
0054:err:sync:RtlpWaitForCriticalSection section 00006FFFFFFAD440 "../wine-staging/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0054, blocked by 0064, retrying (60 sec)
0090:err:sync:RtlpWaitForCriticalSection section 00006FFFFFFAD440 "../wine-staging/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0090, blocked by 0084, retrying (60 sec)
0054:err:sync:RtlpWaitForCriticalSection section 00006FFFFFFAD440 "../wine-staging/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0054, blocked by 0064, retrying (60 sec)
0064:fixme:gdi:get_default_fonts unhandled charset 0x000000a3 - use ANSI_CHARSET for default stock objects
002c:fixme:gdi:get_default_fonts unhandled charset 0x000000a3 - use ANSI_CHARSET for default stock objects
0084:fixme:gdi:get_default_fonts unhandled charset 0x000000a3 - use ANSI_CHARSET for default stock objects
0034:fixme:gdi:get_default_fonts unhandled charset 0x000000a3 - use ANSI_CHARSET for default stock objects
00d0:err:sync:RtlpWaitForCriticalSection section 00006FFFFFFAD440 "../wine-staging/dlls/ntdll/loader.c: loader_section" wait timed out in thread 00d0, blocked by 0084, retrying (60 sec)
00bc:fixme:gdi:get_default_fonts unhandled charset 0x000000a3 - use ANSI_CHARSET for default stock objects
0024:fixme:gdi:get_default_fonts unhandled charset 0x000000a3 - use ANSI_CHARSET for default stock objects
00cc:fixme:gdi:get_default_fonts unhandled charset 0x000000a3 - use ANSI_CHARSET for default stock objects
00c4:fixme:gdi:get_default_fonts unhandled charset 0x000000a3 - use ANSI_CHARSET for default stock objects
00ec:fixme:gdi:get_default_fonts unhandled charset 0x000000a3 - use ANSI_CHARSET for default stock objects
00ec:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
00ec:err:winediag:nodrv_CreateWindow L"The explorer process failed to start."
Killed

seth · 2024-09-18 13:09:01

So the dll errors are gone.
But there're lots of timeouts and it took 90 minutes to initialize the wine drive???

What kind of session is this, X11 or wayland?
Same issue w/ the non-staging wine (and a fresh prefix)?
What what partition is your $HOME on?

findmnt -T ~

Are there IO errors in dmesg?

okbzl · 2024-09-18 23:40:07

First question:

[chutienbinh@ASUS plex-desktop]$ findmnt -T ~
TARGET SOURCE            FSTYPE OPTIONS
/home  /dev/sda2[/@home] btrfs  rw,relatime,compress=zstd:3,space_cache=v2,subvolid=257,subvol=/@home

Second question: No mention of IO errors
Also, X11, but I wouldn't be suprised if this also happen on Wayland

seth · 2024-09-19 06:52:31

Ok, the compression probably explains why writing data there is slow.
Maybe also the timeouts.

What if you move the WINEPREFIX to some ext4 or tmpfs?

okbzl · 2024-09-19 10:24:39

I don't have the time to find and format a drive to ext4 rn, but quick question: What compression and format does Mint and Pop use by default, cuz wine seems to always work on them?

Last edited by okbzl (2024-09-19 10:25:37)

seth · 2024-09-19 14:46:36

What makes you sure "Mint" and "Pop!OS" *default* to any btrfs itfp?
Idk what FS you're using on them, but the findmnt command will work there, too.

Try a tmpfs WINEPREFIX, if you've enough RAM, /tmp/wine or so will do.

okbzl · 2024-09-21 05:47:38

Sorry for the long response, but after reinstalling Arch with ext4 for root and no compression, wine finally works again. Thanks for your help

okbzl · 2024-09-21 11:38:30

Okay, never bloody mind, problem arise after reboot already

seth · 2024-09-21 11:50:14

What exact error?
What did you do after the re-installation? Notably: to your wine setup?

okbzl · 2024-09-21 11:55:31

After another reboot, wine works again. I'm gonna chalk it up to the fact that I have too many process running at once (LO Writer, Firefox, Lutris, TeraBox, Dolphin at the same time). Will update the title to solved again

Arch Linux

#1 2024-09-17 15:26:32

[SOLVED - FS error] Wine can't load kernel32.dll and c0000135

#2 2024-09-17 15:55:19

Re: [SOLVED - FS error] Wine can't load kernel32.dll and c0000135

#3 2024-09-17 22:16:13

Re: [SOLVED - FS error] Wine can't load kernel32.dll and c0000135

#4 2024-09-17 22:25:50

Re: [SOLVED - FS error] Wine can't load kernel32.dll and c0000135

#5 2024-09-17 22:32:22

Re: [SOLVED - FS error] Wine can't load kernel32.dll and c0000135

#6 2024-09-18 07:20:28

Re: [SOLVED - FS error] Wine can't load kernel32.dll and c0000135

#7 2024-09-18 08:32:53

Re: [SOLVED - FS error] Wine can't load kernel32.dll and c0000135

#8 2024-09-18 10:23:33

Re: [SOLVED - FS error] Wine can't load kernel32.dll and c0000135

#9 2024-09-18 11:03:07

Re: [SOLVED - FS error] Wine can't load kernel32.dll and c0000135

#10 2024-09-18 13:09:01

Re: [SOLVED - FS error] Wine can't load kernel32.dll and c0000135

#11 2024-09-18 23:40:07

Re: [SOLVED - FS error] Wine can't load kernel32.dll and c0000135

#12 2024-09-19 06:52:31

Re: [SOLVED - FS error] Wine can't load kernel32.dll and c0000135

#13 2024-09-19 10:24:39

Re: [SOLVED - FS error] Wine can't load kernel32.dll and c0000135

#14 2024-09-19 14:46:36

Re: [SOLVED - FS error] Wine can't load kernel32.dll and c0000135

#15 2024-09-21 05:47:38

Re: [SOLVED - FS error] Wine can't load kernel32.dll and c0000135

#16 2024-09-21 11:38:30

Re: [SOLVED - FS error] Wine can't load kernel32.dll and c0000135

#17 2024-09-21 11:50:14

Re: [SOLVED - FS error] Wine can't load kernel32.dll and c0000135

#18 2024-09-21 11:55:31

Re: [SOLVED - FS error] Wine can't load kernel32.dll and c0000135

Board footer