Techniques for performing memory diagnostics

• US 7,818,625 B2
• Filed: 08/17/2005
• Issued: 10/19/2010
• Est. Priority Date: 08/17/2005
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Greenberg, Steven M., LeBlanc, David C., Coon, Thomas S.
• Primary Examiner(s): Baderman; Scott T
• Assistant Examiner(s): PATEL, KAMINI B
• Application Number:
  US11/206,386
• Publication Number:
  US 20070043974A1
• Time in Patent Office: 1,889 Days
• Field of Search: 714/42, 714/40
• US Class Current: 714/40
• CPC Class Codes: G06F 11/2268 Logging of test results

Abstract

Techniques are provided for performing memory diagnostics. A portion of physical memory is locked using functionality included in an operating system. At least one memory diagnostic test is executed on the portion producing a result. It is determined, in accordance with the result, whether a memory problem exists for the portion of physical memory.

Claims

1. A method for performing memory diagnostics comprising:

based upon examination of program termination data, initiating memory diagnostics from a first program having user level privileges;

locking a portion of physical memory to be tested using functionality included in an operating system by a second program having system level privileges, the system level privileges provide for a privileged execution state in comparison to the first program having user level privileges, wherein said second program is a system service that can only be executed from an account having administrative privileges;

executing at least one memory diagnostic test on said portion locked by the second program having system privileges producing a result by the second program; and

determining, in accordance with said result, whether a memory problem exists for said portion by the second program.

2. The method of claim 1, wherein said locking includes making at least one call using an application programming interface.

3. The method of claim 1, further comprising:

communicating at least one of said result or testing progress information from said second program to said first program.

4. The method of claim 1, wherein execution of said first program is manually initiated by a user.

5. The method of claim 1, wherein execution of said first program is automatically initiated in accordance with at least one heuristic associated with a memory failure.

6. The method of claim 5, wherein said at least one heuristic includes a threshold value indicating a number of abnormal program terminations.

7. The method of claim 5, wherein said at least one heuristic includes at least one characteristic associated with an abnormal program termination.

8. The method of claim 5, further comprising:

examining termination data associated with at least one previous program execution in accordance with said at least one heuristic.

9. The method of claim 1, wherein execution of said first program is automatically initiated by an exception handler handling an abnormal termination of a third program executing in said first execution mode.

10. The method of claim 1, wherein said first program executes as a background task.

11. The method of claim 1, wherein said system service performs only processing associated with performing memory diagnostics.

12. The method of claim 1, wherein execution of said system service cannot be initiated remotely by an unauthorized user.

13. The method of claim 1, wherein the portion of physical memory comprises random access memory.

14. A computer storage medium having computer executable instructions stored thereon for performing steps comprising:

invoking a system service executing in a first execution mode with a first set of privileges, said system service locking a portion of physical memory to be tested using functionality included in an operating system, and executing at least one memory diagnostic test on said portion locked by said system service producing a result, wherein said first execution mode comprises system level privileges, the system level privileges provide for a privileged execution state in comparison to a second execution mode having user level privileges; and

determining, in accordance with said result, whether a memory problem exists for said portion.

15. The computer storage medium of claim 14, wherein said system service is initiated by a program executing in the second execution mode that is different from said first execution mode and has insufficient privileges to perform said locking.

16. The computer storage medium of claim 15, wherein said system service is installed and architected in accordance with at least one security measure.

17. A system for performing memory diagnostics comprising:

a user computer upon which said memory diagnostics are performed, said user computer operative to;

lock a portion of physical memory to be tested using functionality included in an operating system by a program having system level privileges;

execute at least one memory diagnostic test on said locked portion producing a result; and

determine, in accordance with said result, whether a memory problem exists for said portion; and

wherein said user computer communicates information related to said memory diagnostics to a reporting computer.

18. The system of claim 17, wherein said user computer includes computer executable components comprising:

a service manager component that manages services;

a memory diagnostic service component which locks said portion of physical memory, initiates execution of said at least one memory diagnostic, and communicates said result to said service manager component;

a diagnostics application component which communicates with said service manager component to initiate said memory diagnostic service component; and

an operating system component which includes functionality utilized by said memory diagnostic service component in locking said portion of physical memory.