This post has 2 parts: 1) How to disable Fast Startup in Windows 10, and 2) What is Fast Startup and why is it causing a problem.

AMENDED
I have tested Hibernation several times and seen results that vary from benign but incomplete to one GSOD.
So, I am striking out the statements below that Hibernation can be kept enabled.

1) Disable Hibernation and Fast Startup
Hibernation is not the problem, so you can keep it enabled or disable it.
If you disable Hibernation, then Fast Startup is also disabled and not available.

To disable Hibernation and Fast Startup from a Command Prompt
- Open a Command Prompt (Run as Administrator).
- At the prompt, type: "powercfg /h off' (without the quotes).
- Exit Command Prompt

OR:
To disable Hibernation and Fast Startup from the Control Panel
- goto Control Panel (there are several ways to launch the Control Panel... so, below is one way)
- Click on the Windows Start icon (lower left), scroll down to Windows System click on its folder and select Control Panel.
- Copy and paste "Control Panel\All Control Panel Items\Power Options" into the address bar (without the quotes).
- Select "Choose what the power buttons do"
- Click on "Change settings that are currently unavailable"
- De-select "Hibernate" from "Power and sleep buttons and lid settings" and from "Shutdown Settings"
- De-select "Turn on fast startup (recommended)" from "Shutdown Settings"


2) What is Fast Startup and why is it causing a problem.
Fast startup is a hybrid form of Hibernation, where the user is logged off before the hibernation file is created. So, it saves an image of just the Windows kernel and loaded drivers, rather than the user's complete session state. This allows for a smaller hibernation file (hiberfil.sys), which is faster to restore than performing a cold startup.

From:
https://docs.microsoft.com/en-us/windows-hardware/drivers/kernel/distinguishing-fast-startup-from-wake-from-hibernation

"To prepare for a fast startup, Windows performs a hybrid shutdown sequence that combines elements of a full shutdown sequence and a prepare-for-hibernation sequence. First, as in a full shutdown, Windows closes all applications and logs off all user sessions. At this stage, the system state is similar to that of a computer that has just started up—no applications are running, but the Windows kernel is loaded and the system session is running. Next, the power manager sends system power IRPs to device drivers to tell them to prepare their devices to enter hibernation. Finally, Windows saves the kernel memory image (including the loaded kernel-mode drivers) in Hiberfil.sys and shuts down the computer."

This sentence in BOLD above reveals the most likely cause of the OFA driver failure when Fast Startup is enabled.
I suspect that the OFA device driver receives the IRP and powers down... unfortunately, the Fast Startup process then tries to write its hiberfil.sys to the OFA driven SSD that has shutdown and the system hangs.

The 'docs.microsoft.com' link above addresses the steps that drivers need to take to handle Fast Startup shutdowns.

meanwhile I made another (casual) discovery:
with the OFA drivers the userbenchmark suite detects a different firmware for the drive (from EXA7 to 301Q)

Hello,

using Windows 7. Since OFA driver does not work (bootloop) i would like to try the generic Intel RST Driver. Downloaded it from https://downloadcenter.intel.com/downloa...n-Platforms?v=t
However when trying to import it in device manager by pointing to folder which contains iaStorAC.cat/inf/sys Windows just shows a message "there is no compatible driver. if folder contains a driver make sure that it can be used with Windows for x64-based systems"

Where can I download and How can I use a universal Intel NVME driver for win 7??

Zitat von Fernando im Beitrag #95

---

@godmodeUser23:
This is the way how you get any generic Intel RST NVMe driver v16.x.x.xxxx installed:

---

error from first posting happens:

Zitat von godmodeUser23 im Beitrag #94

---

---

is there any possibility to get it intel driver to run under windows 7?

Any explanation or solution why NVMe drive is detected with Microsoft Driver/Hotfix but S.M.A.R.T. and temperature data is not shown under Windows 7?
Its interesting to say that even smartmontools under Linux do not show this data, but when using terminal under linux it shows it.

Zitat von Fernando im Beitrag #104

---

there are tools available, which show the related data.

---