IP Library Granted Patent US 9,606,853
Granted Patent B2
US 9,606,853 · App. 14/229,345 · Granted Mar 28, 2017

Protecting a memory device from becoming unusable

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,606,853
App. No.
14/229,345
Granted
Mar 28, 2017
Kind
B2
Abstract

In an embodiment, a computing device may include a memory device that may be rendered unusable after a certain number of operations are performed on the memory device. The computing device may incorporate one or more techniques for protecting the memory device. Processing logic contained in the computing device may be configured to implement the techniques. The techniques may include, for example, acquiring a request to write or erase information stored in a memory device contained in a first computing device, saving the request for execution after a user visible event has been generated on the first computing device, generating the user visible event on the first computing device, and executing the saved request after the user visible event has been generated. In addition, the techniques may include reporting the request. The request may be reported to, for example, an anti-malware agent.

Claims (43)

1. A method comprising:

acquiring a request, the request associated with writing information to a memory device or erasing information stored in the memory device, the memory device being contained in a first computing device;

saving the request for execution by the first computing device after a user visible event has been generated on the first computing device, the user visible event being generated after the first computing device has been reset;

resetting the first computing device;

generating the user visible event on the first computing device; and

executing the saved request after the user visible event has been generated.

2. The method of claim 1 , wherein the user visible event includes a reset of the first computing device.

3. The method of claim 1 , further comprising:

reporting the request.

4. The method of claim 3 , wherein the request is reported to an anti-malware agent.

5. The method of claim 4 , wherein the anti-malware agent is executed by the first computing device.

6. The method of claim 4 , wherein the anti-malware agent is executed on a second computing device that communicates with the first computing device.

7. The method of claim 6 , wherein the second computing device communicates with the first computing device via a communications network.

8. The method of claim 1 , wherein the memory device is contained in a storage that stores computer-executable instructions that are executed by the first computing device when the first computing device is booting.

9. The method of claim 8 , wherein the request includes a request to write or erase information in a code region of the storage.

10. The method of claim 8 , wherein the request includes a request to write or erase information contained in a data region of the storage.

11. The method of claim 1 , wherein the request is acquired by a basic input/output system (BIOS) contained in the first computing device.

12. A computing device comprising:

a memory device;

processing logic to:

acquire a request, the request associated with writing information to the memory device or erasing information stored in the memory device,

save the request for execution by the computing device after a user visible event has been generated on the computing device, the user visible event being generated after the computing device has been reset,

reset the computing device,

generate the user visible event on the computing device, and

execute the saved request after the user visible event has been generated.

13. The computing device of claim 12 , wherein the user visible event includes resetting the computing device.

14. The computing device of claim 12 , wherein the processing logic is further to:

report the request.

15. The computing device of claim 14 , wherein the request is reported to an anti-malware agent.

16. The computing device of claim 12 , wherein the memory device is contained in a storage that stores computer-executable instructions that are executed by the computing device when the computing device is booting.

17. The computing device of claim 16 , wherein the request includes a request to write or erase information in a code region or a data region of the storage.

18. One or more tangible non-transitory computer-readable media storing one or more computer-executable instructions that when executed by processing logic causes the processing logic to:

acquire a request, the request associated with writing information to a memory device or erasing information stored in the memory device, the memory device being contained in a computing device;

save the request for execution by the computing device after a user visible event has been generated on the computing device, the user visible event being generated after the computing device has been reset;

reset the computing device;

generate the user visible event on the computing device; and

execute the saved request after the user visible event has been generated.

19. The computer-readable media of claim 18 , wherein the user visible event includes a reset of the computing device.

20. The computer-readable media of claim 18 , further storing one or more computer-executable instructions that when executed by the processing logic cause the processing logic to:

report the request.

21. The computer-readable medium of claim 20 , wherein the request is reported to an anti-malware agent.

22. The computer-readable medium of claim 18 , wherein the memory device is contained in a storage that stores computer-executable instructions that are executed by the computing device when the computing device is booting.

23. The computer-readable medium of claim 22 , wherein the request includes a request to write or erase information in a code region or a data region of the storage.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 10, 2023
From: INTEL CORPORATION
To: SK HYNIX NAND PRODUCT SOLUTIONS CORP.
Reel/Frame 062702/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 15, 2014
From: SARANGDHAR, NITIN V.; OTTURU, SUDHAKAR
To: INTEL CORPORATION
Reel/Frame 032891/0331 →