Driver security interface frozen

Driver B can read the parameter values that driver A provided and make choices, based on those values, about which information to supply to driver A. When the framework receives driver A's request for an interface that supports two-way communication, the framework calls driver B's EvtDeviceProcessQueryInterfaceRequest callback function so that it can examine received values and supply output values.

For two-way communication, the callback function is required because the framework does not copy any interface values to driver A's interface structure.

Each interface must include a reference function and a dereference function, which increment and decrement a reference count for the interface. When driver A asks driver B for an interface, the framework calls the interface's reference function before making the interface available to driver A. When driver A has finished using the interface, it must call the interface's dereference function.

The reference and dereference functions for most interfaces can be no-op functions that do nothing. In this case, driver B in a different stack must implement a reference count so that it can prevent its device from being removed while driver A is using driver B's interface.

If you are designing driver B, which defines an interface, you must decide whether your driver's interface will be accessed from a different driver stack. Driver B cannot determine if a request for its interface is from the local driver stack or from a remote stack. If your driver will support interface requests from a remote stack, the driver must implement a reference count.

Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Unplug and plug in the SSD. Click OK. Once the drive is detected, continue with the Secure Erase. If the Security warning message displays again, repeat the power-cycling process. Quickly remove and reconnect the SATA power cable. Click Device Manager, right-click Disk drives , and click Scan for hardware changes. Click Refresh. Try the Secure Erase procedure again.

Discontinued Products. Show all Show less. Get answers from your peers along with millions of IT pros who visit Spiceworks. Thank you for the assistance! Best Answer. Pure Capsaicin.

Google says this was something your other machines BIOS enabled. The logic in this method is to prevent the drives detection in BIOS, which is when the freeze lock command is issued Intel also claims to have a tool, but it says it is for their drives. View this "Best Answer" in the replies below ». Popular Topics in Data Storage. Spiceworks Help Desk. The help desk software for IT.