Diagnostic interrupt

Available in Classic

This document describes diagnostic interrupts on NAVER Cloud Platform that can collect memory dumps according to the OS settings. Diagnostic interrupts can be performed through the user CLI and API. The conditions for using the diagnostic interrupt are as follows:

• Server-related services using the Windows-based OS
• When you can use API and CLI of NAVER Cloud Platform from outside the server

Required situations

Diagnostic interrupts are required in the following situations:

• When a user application requires a memory dump analysis
• When other OS issues require analysis

Windows full memory dump presets

The default setting is "automatic memory dump," which makes it difficult to check the application memory because the full memory dump is missing. Therefore, you must enable dumping of a full memory in the event of a BSOD in Windows and set it for the page file.
Enabling a full memory dump should not have a significant impact on operating system performance, but it can be reverted if the issue is resolved. However, if you revert it, a full memory dump is not collected when a diagnostic interrupt (or BSOD) occurs.

Set Windows memory dump

The following describes how to enable a full memory dump when a BSOD occurs in Windows.

1. Click > > System > Advanced system settings > [Advanced], in that order.
   
2. Click to select the Automatically restart check box under System failure.
3. Click [Settings] in Startup and Recovery and select Complete memory dump from the drop-down menu in Write debugging information.
   
4. Click the [OK] button in the pop-up window.
5. Click to select the Overwrite any existing file check box in the Write debugging information.
6. Click the [OK] button.

Set paging file

The following describes how to set a paging file.

1. Click > > System > Advanced system settings > [Advanced], in that order.

2. Click the [Settings] button for Performance, click the [Advanced] tab, and then click the [Change] button for Virtual memory.
   

3. Click to deselect the Automatically manage paging file size for all drives check box.

4. Click to select Custom size and set the paging file size to be under C:\, larger than RAM.

   • The following image shows an example setting with 8 GB of physical memory.
     

   • The size of the paging file must be at least 257 MB larger than the physical memory.

     Amount of RAM on the server	Recommended paging file size
     4 GB	4353 MB or above
     8 GB	8449 MB or above
     16 GB	16,641 MB or above
     32 GB	33,025 MB or above
     64 GB	65,793 MB or above

5. Click the [Set] > [OK] buttons, in that order.

Apply

The settings will not apply until Windows is rebooted. When the settings are applied, a BSOD is generated when a diagnostic interrupt occurs, at which point a dump of the entire memory is collected.

How to use the API/CLI

You can use diagnostic interrupts through API and CLI as follows:

1. Check if you are in a required situation to run diagnostic interrupts.
2. See the following guides and run API and CLI.
   • API Guide
   • CLI Guide
3. Click the Services > Compute > Server menu in NAVER Cloud Platform's console and check the Configuring status of the server.
4. Check the Restart status of the server.
5. Try to access when the server status changes to Running.