-
We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
I did not manage to attach more than 1 file, so the remaining files are attached here
In that exceptions log the crash is in your Nvidia driver.
Please uninstall it with this tool https://developer.nvidia.com/cleanup-tool
Reboot, then update that Nvidia driver to mid-May 2025 https://www.nvidia.com/Download/index.aspx?lang=en-us
Then reboot again. If GeForce Experience or the Nvidia app are running after doing that, exit them before starting the game.
Good luck!
Please uninstall it with this tool https://developer.nvidia.com/cleanup-tool
Reboot, then update that Nvidia driver to mid-May 2025 https://www.nvidia.com/Download/index.aspx?lang=en-us
Then reboot again. If GeForce Experience or the Nvidia app are running after doing that, exit them before starting the game.
Good luck!
Thank you it seems to have worked. However I did not write down my GPU version beforehand, so downloading the right driver was not straightforward. It seems Windows auto-update still found the driver.
Just to add the following general information about the IN_PAGE_ERROR
This exception is actually triggered by the storage device from which the application is run (or any of it's associated DLL libraries) when it becomes temporary unavailable. When this happens while the Windows kernel is resolving a page-in/loading request for a page of code or data from any of these files, this exception gets triggered.
It's part of how the Windows kernel deals with virtual memory. For data, you have the actual pagefile. But for application code, the .exe and associated .dll files are also treated as page files. Code gets loaded on a need-to-use basis, instead of loading everything in memory before the application starts running. Which means that the storage device on which any of these files is stored needs to be accessible constantly.
If there is any interruption while the kernel is servicing a page fault exception from the CPU (and thus can't provide the chunk of memory the CPU needs to continue), the entire application stalls. But instead of waiting, the kernel just aborts with this IN_PAGE_ERROR exception.
The formal description from Microsoft for this exception is:
The instruction at 0x%08lx referenced memory at 0x%08lx. The required data was not placed into memory because of an I/O error status of 0x%08lx.
The most frequent cause of this exception is when the application is run from a networked resource (a file server or NAS or something), and the network card or server isn't responding (fast enough).
A video card/driver can also be responsible (although this is the first case I've heard about). In order to facilitate high performance memory transfers for the video card, the card is able to lock the PCI bus during these transfers. The local hard drive is also connected via the PCI bus. So, when the video card locks the bus, the hard drive is inaccessible. When the lock is held for too long (by the video card/driver) and the CPU needs a chunk of memory from the page file, the kernel can run into the device inaccessible problem, and thus the IN_PAGE_EXCEPTION gets triggered.
This exception is actually triggered by the storage device from which the application is run (or any of it's associated DLL libraries) when it becomes temporary unavailable. When this happens while the Windows kernel is resolving a page-in/loading request for a page of code or data from any of these files, this exception gets triggered.
It's part of how the Windows kernel deals with virtual memory. For data, you have the actual pagefile. But for application code, the .exe and associated .dll files are also treated as page files. Code gets loaded on a need-to-use basis, instead of loading everything in memory before the application starts running. Which means that the storage device on which any of these files is stored needs to be accessible constantly.
If there is any interruption while the kernel is servicing a page fault exception from the CPU (and thus can't provide the chunk of memory the CPU needs to continue), the entire application stalls. But instead of waiting, the kernel just aborts with this IN_PAGE_ERROR exception.
The formal description from Microsoft for this exception is:
The instruction at 0x%08lx referenced memory at 0x%08lx. The required data was not placed into memory because of an I/O error status of 0x%08lx.
The most frequent cause of this exception is when the application is run from a networked resource (a file server or NAS or something), and the network card or server isn't responding (fast enough).
A video card/driver can also be responsible (although this is the first case I've heard about). In order to facilitate high performance memory transfers for the video card, the card is able to lock the PCI bus during these transfers. The local hard drive is also connected via the PCI bus. So, when the video card locks the bus, the hard drive is inaccessible. When the lock is held for too long (by the video card/driver) and the CPU needs a chunk of memory from the page file, the kernel can run into the device inaccessible problem, and thus the IN_PAGE_EXCEPTION gets triggered.
FYI it is shown in the system.log file you attached above:
Make sure Windows installed the latest version of the driver; which yesterday was mid-May - although a new one just came out last night!