Windows Driver Error 1275 Displayed When Running Epic Games Battleye Anti-Cheat. [Fortnite]

Windows driver error 1275 is displayed when trying to run a game using Epic Games Battleye Anti-Cheat Protection Software. [Necessary to run the game Fortnite.]

Epic is researching the issue related to the Windows Core Isolation [Hardware-Enforced Stack Protection] security protocol.

Enabling this option in Windows settings will not allow BEDaisy.sys [a core Battleye component] to run.

Currently the only [temporary] fix is to disable Core Islotation:

    - Click the "Disable" button in the Windows pop-up dialog window if displayed and reboot the system.

    - Click on the Windows "Start Menu" icon and type "core isolation" into the search box, click the "system setting" icon, this will open the related Windows Defender Security setting window.

    - Click to disable the Kernel-Mode Hardware-Enforced Stack Protection option.

[Windows 11 screenshot]

- Reboot the system and the issue should resolved until a patch is released where you can re-enable this option.

Epic Games notes that disabling this service the does not lower the security of the system, or expose it to greater risks as it was a feature that was previously disabled by default.

We hope this issue will be permanently resolved in the near future.

Epic Games Battleye FAQ

Getting Burnout Paradise: Remastered To Run On Windows 10 With Nvidia Graphic Cards:

Electronic Arts will gladly take your money while ignoring the fact Burnout Paradise: Remastered won't initially run on Windows 10.

 

The Problem:

The game crashes to desktop during startup.

The Issue:

The game is coded to recognize older/non supported graphic cards.

The Resolution:

Instructions for Nvidia; the instructions for AMD/Radeon should be similar.

1) Download, Install [if not already present], and Run the free Nvidia Control Panel (different from GeForce Experience).

Click the image below to download from Nvidia, or goto the Windows Store.

 

2) Select "Manage 3D Settings".  [Click the image below to enlarge.]

    Click the "Program Settings" tab.

    Click the box shown below the "Select a program to customize".

    Locate the game.  Note: I have Steam installed; the full path would be:

   C:\Program Files (x86)\Steam\steamapps\common\BurnoutPR

    (you would then select the BurnoutPR.exe) 

    (C:\Program Files (x86) is also common location usually within the game company's folder.)

 

 

    Click "Add".

    The option to run with the "High Performance Nvidia Processor" should already be selected.

Close the Nvidia Control Panel it will save the changes.

The game should run now.*

 

*It should be noted some people have mentioned having to initially run it twice; the game may crash immediately after making this change; but will run fine after that.

Worse comes to worst, restart the computer.
 

Fallout 4 Intermittent Crash To Desktop Under Windows 10

[edit to include the version of Fallout 4 running is 1.3 Beta.]


Problem:
Fallout 4 would launch fine one day, then crash after the launch menu on another.
Literally; nothing was changed (No Mods added/deleted, no updates whatsoever.)

Solution:
Right-clicking the Fallout.exe
[Usually in C:\Program Files (x86)\Steam\steamapps\common\Fallout 4]

Select "Properties".
Select the "Compatibility" tab.
Under "Compatibility Mode", choose "Windows 7":

Previous troubleshooting involved:
* Restarting the computer.

* Verifying the integrity of the local game files on Steam.
(Right-click Fallout 4 in your Steam Library, select "Properties", then "Local Files")

* Renaming or Moving the Fallout4.ini, Fallout4Prefs.ini, and the Fallout4Prefs_Custom.ini files to another folder. (The game creates new default ones if they are missing.) 

Note: The files are usually located in C:\Users\{username]\Documents\my games\Fallout4.


Note: The files may not have '.ini' after them, and 'Fallout4Prefs_Custom' may not exist for older versions.









* Disabling Mods [if installed].

* Updating Windows, video card drivers, Fallout 4 itself.


                          ....further help on Steam





CTD, No Error,