Running any application result in unhandled page fault on execute access

[K3ssl3r5yndr0m3]

I can't run any program. When I tried to run winecfg, this is outputted "wine: Unhandled page fault on execute access to 00007F9E9634C9F0 at address 00007F9E9634C9F0 (thread 0080), starting debugger...".

[binarynoise]

Having the same issue.
arch linux, Wine 7.1

[K3ssl3r5yndr0m3]

I'm also on Arch. My version of wine is 7.0 though

[jkfloris]

What is the output of:

Code: Select all

WINEPREFIX=${HOME}/wine-test wine winecfg

[binarynoise]

That shouldn't have worked, I created a test-prefix with winetricks and it gave the same result.
But I continued researching and found this: https://bbs.archlinux.org/viewtopic.php?id=272856
It's an incompatibility with the nvidia-drivers (probably introduced with version 5xx).
I downgraded to the latest 495 version and wine works again.

[binarynoise]

What is the output of:

Code: Select all

WINEPREFIX=${HOME}/wine-test wine winecfg

Code: Select all

wine: created the configuration directory '~/wine-test'
002c:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
0048:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
0050:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
wine: Unhandled page fault on execute access to 00007FE4A5FE79F0 at address 00007FE4A5FE79F0 (thread 0048), starting debugger...
0048:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 68 88" (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
wine: Unhandled page fault on execute access to 00007FE7863FD8A0 at address 00007FE7863FD8A0 (thread 0050), starting debugger...
0050:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 76 88" (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
002c:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
002c:err:winediag:nodrv_CreateWindow The explorer process failed to start.
0040:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
0040:err:winediag:nodrv_CreateWindow The explorer process failed to start.
0080:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
0080:err:winediag:nodrv_CreateWindow The explorer process failed to start.
0080:fixme:file:NtLockFile I/O completion on lock not implemented yet
0080:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
0080:err:mscoree:LoadLibraryShim error reading registry key for installroot
0080:err:mscoree:LoadLibraryShim error reading registry key for installroot
0080:err:mscoree:LoadLibraryShim error reading registry key for installroot
0080:err:mscoree:LoadLibraryShim error reading registry key for installroot
0080:err:mscoree:LoadLibraryShim error reading registry key for installroot
0080:err:mscoree:LoadLibraryShim error reading registry key for installroot
0080:err:mscoree:LoadLibraryShim error reading registry key for installroot
0080:err:mscoree:LoadLibraryShim error reading registry key for installroot
0080:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 1)
0080:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 1)
00d4:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
00d4:err:winediag:nodrv_CreateWindow The explorer process failed to start.
00d4:err:winediag:gnutls_process_attach failed to load libgnutls, no support for encryption
00d4:err:winediag:process_attach failed to load libgnutls, no support for pfx import/export
wine: configuration in L"/tmp/Download/wine-test" has been updated.
wine: Unhandled page fault on execute access to 00007FC33F0099F0 at address 00007FC33F0099F0 (thread 0134), starting debugger...

[jkfloris]

Thank you for the information. Personally, I have not been able to test version 5xx yet.
Is there a bug report about this at NVIDIA or Wine?

The link it is about an Optimus system with NVidia version 495 where the 32-bit drivers were not configured properly.
Perhaps you mean a different page?

[binarynoise]

Yes, I did mean that link, but you're right, the core problem is a different one.
Still, the problem arises from the NVIDIA 5xx drivers. I had to upgrade to 5xx again, because they wouldn't work otherwise , so I could debug it with you (fortunately I don't depend on the windows programs atm)

[jkfloris]

It might be this bug: https://bugs.winehq.org/show_bug.cgi?id=51210
Do you have a multi GPU system?
Can you run wine with the VK_ICD_FILENAMES variabele?

Code: Select all

# For example:
VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json wine winecfg

[K3ssl3r5yndr0m3]

I have intel intergrated graphics and nvidia, and I use optimus manager. I tried running wine with VK_ICD_FILENAMES but it resulted in the same error. Even after I disable optimus manager, it was still the same

[binarynoise]

Same for me, I use Nvidia Prime (so intel as default and nvidia for games), but running the above command yields the same error

[jkfloris]

Version 510 is now also available for Debian Sid, and so far I have no problems with it.
Unfortunately, I don't have the opportunity to test out a Nvidia Prime/ Optimus setup.

[binarynoise]

So I kept digging, looking for changes to graphics configuration and it seems, I found the culprit.
It was

Code: Select all

/usr/share/X11/xorg.conf.d/20-intel.conf

created by https://github.com/dianariyanto/virtual-display-linux

Code: Select all

Section "Device"
    Identifier "intelgpu0"
    Driver "intel"
    Option "VirtualHeads" "2"
EndSection

When I remove that file, wine starts working again.
From hindsight, it doesn't seem at all related to a specific wine or nvidia version, all wine versions didn't work and I'm back on 510 and it still works.

[Eocene]

Interesting, I'm running into this bug as well (using Manjaro with dual Intel/Nvidia setup).

However this file is not present on my system.

[K3ssl3r5yndr0m3]

Wine just started working for me after I update my system.

[Eocene]

I managed to find a fix.

When I installed Manjaro, it offered me to install Nvidia's proprietary drivers. I assumed I was using Nvidia's gpu.

But I wanted to be able to switch to integrated, to conserve battery. So I installed optimus-manager, and commented the lines starting with DisplayCommand and DisplayStopCommand in /etc/sddm.conf (I use SDDM as the display manager).

Upon reboot, optimus-manager now worked, however the --switch parameter wouldn't.

So I created the file /etc/optimus-manager/optimus-manager.conf (https://github.com/Askannz/optimus-mana ... nager.conf) and changed startup_mode to nvidia.

After rebooting again, optimus-manager --status now reported the nvidia GPU as being active, and Wine now works fine.

[mario156090]

Same problem here, any solution instead use only dedicated graphic card?

[SSUPII]

So I kept digging, looking for changes to graphics configuration and it seems, I found the culprit.
It was

Code: Select all

/usr/share/X11/xorg.conf.d/20-intel.conf

created by https://github.com/dianariyanto/virtual-display-linux

Code: Select all

Section "Device"
    Identifier "intelgpu0"
    Driver "intel"
    Option "VirtualHeads" "2"
EndSection

When I remove that file, wine starts working again.
From hindsight, it doesn't seem at all related to a specific wine or nvidia version, all wine versions didn't work and I'm back on 510 and it still works.

By removing it also fixed it for me, but I really wish this wasn't the case. The secondary virtual monitor is extremely useful

[binarynoise]

The secondary virtual monitor is extremely useful

As it turns out, I can also use any of the physical outputs as virtual.
I created a gist of the script I created.

Just replace the name of your main screen and its frame rate

[pancutan]

Arch, Lenovo Ideapad with Radeon integrated and Nvidia 3050:

In my case the behavior was after second run of any exe (example winbox.exe). If I changed it to another monitor, the exe crashed.
And when trying a second run, a not starting debugger hangs forever:

Code: Select all

wine: Unhandled page fault on execute access to 00007F36A6B287D0 at address 00007F36A6B287D0 (thread 00a0), starting debugger

Temporal solution was to throw a

Code: Select all

sudo pkill -9 -f wine, and rm -rf ~/.wine

How I was able to resolve permanently by installing optimus-manager-qt (AUR) and from the tray bar switching to Hybrid. Now the problem is gone.