> For the complete documentation index, see [llms.txt](https://docs.hyperdbg.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperdbg.org/commands/scripting-language/functions/events/event_inject_error_code.md).

# event\_inject\_error\_code

### Function

> event\_inject\_error\_code

### Syntax

> event\_inject\_error\_code( InterruptionType, Vector, ErrorCode);

### Parameters

**\[ Expression (InterruptionType)]**

Type of the target interrupt/exception/fault (see the **Remarks** section for more information). Can be selected from the following table:

<table><thead><tr><th width="217">Interruption Type</th><th>Description</th></tr></thead><tbody><tr><td>0</td><td>External interrupt</td></tr><tr><td>1</td><td>Reserved</td></tr><tr><td>2</td><td>Non-maskable interrupt (NMI)</td></tr><tr><td>3</td><td>Hardware exception (e.g,. #PF)</td></tr><tr><td>4</td><td>Software interrupt (INT n)</td></tr><tr><td>5</td><td>Privileged software exception (INT1)</td></tr><tr><td>6</td><td>Software exception (INT3 or INTO)</td></tr><tr><td>7</td><td>Other event</td></tr></tbody></table>

**\[ Expression (Vector)]**

The vector number (interrupt IDT vector number) of the target interrupt/exception/fault. Can be selected from the following table:

<table><thead><tr><th width="228">Name</th><th>Vector nr.</th><th>Type</th><th>Mnemonic</th><th>Error code?</th></tr></thead><tbody><tr><td>Divide-by-zero Error</td><td>0 (0x0)</td><td>Fault</td><td>#DE</td><td>No</td></tr><tr><td>Debug</td><td>1 (0x1)</td><td>Fault/Trap</td><td>#DB</td><td>No</td></tr><tr><td>Non-maskable Interrupt</td><td>2 (0x2)</td><td>Interrupt</td><td>-</td><td>No</td></tr><tr><td>Breakpoint</td><td>3 (0x3)</td><td>Trap</td><td>#BP</td><td>No</td></tr><tr><td>Overflow</td><td>4 (0x4)</td><td>Trap</td><td>#OF</td><td>No</td></tr><tr><td>Bound Range Exceeded</td><td>5 (0x5)</td><td>Fault</td><td>#BR</td><td>No</td></tr><tr><td>Invalid Opcode</td><td>6 (0x6)</td><td>Fault</td><td>#UD</td><td>No</td></tr><tr><td>Device Not Available</td><td>7 (0x7)</td><td>Fault</td><td>#NM</td><td>No</td></tr><tr><td>Double Fault</td><td>8 (0x8)</td><td>Abort</td><td>#DF</td><td>Yes (Zero)</td></tr><tr><td>Coprocessor Segment Overrun</td><td>9 (0x9)</td><td>Fault</td><td>-</td><td>No</td></tr><tr><td>Invalid TSS</td><td>10 (0xA)</td><td>Fault</td><td>#TS</td><td>Yes</td></tr><tr><td>Segment Not Present</td><td>11 (0xB)</td><td>Fault</td><td>#NP</td><td>Yes</td></tr><tr><td>Stack-Segment Fault</td><td>12 (0xC)</td><td>Fault</td><td>#SS</td><td>Yes</td></tr><tr><td>General Protection Fault</td><td>13 (0xD)</td><td>Fault</td><td>#GP</td><td>Yes</td></tr><tr><td>Page Fault</td><td>14 (0xE)</td><td>Fault</td><td>#PF</td><td>Yes</td></tr><tr><td>Reserved</td><td>15 (0xF)</td><td>-</td><td>-</td><td>No</td></tr><tr><td>x87 Floating-Point Exception</td><td>16 (0x10)</td><td>Fault</td><td>#MF</td><td>No</td></tr><tr><td>Alignment Check</td><td>17 (0x11)</td><td>Fault</td><td>#AC</td><td>Yes</td></tr><tr><td>Machine Check</td><td>18 (0x12)</td><td>Abort</td><td>#MC</td><td>No</td></tr><tr><td>SIMD Floating-Point Exception</td><td>19 (0x13)</td><td>Fault</td><td>#XM/#XF</td><td>No</td></tr><tr><td>Virtualization Exception</td><td>20 (0x14)</td><td>Fault</td><td>#VE</td><td>No</td></tr><tr><td>Reserved</td><td>21-29 (0x15-0x1D)</td><td>-</td><td>-</td><td>No</td></tr><tr><td>Security Exception</td><td>30 (0x1E)</td><td>-</td><td>#SX</td><td>Yes</td></tr><tr><td>Reserved</td><td>31 (0x1F)</td><td>-</td><td>-</td><td>No</td></tr><tr><td>Triple Fault</td><td>-</td><td>-</td><td>-</td><td>No</td></tr><tr><td>FPU Error Interrupt</td><td>IRQ 13</td><td>Interrupt</td><td>#FERR</td><td>No</td></tr></tbody></table>

**\[ Expression (ErrorCode)]**

The target error code number of the interrupt/exception/fault.

### Description

Injects an interrupt/exception/fault with an error code which will be delivered once you continue the debuggee.

### Examples

`event_inject_error_code(3, e, 2);`

Injects a page-fault (**Hardware Exception = 3** and Vector equal to **Page-fault = 0xe**, and [Error code](https://docs.hyperdbg.org/commands/meta-commands/.pagein#page-fault-error-codes) equal to **Write Access = 2**) to the target debuggee.

### Remarks

This function will set the error code. If the target interrupt/exception/fault doesn't need an error code (see the table above), you should use the [event\_inject](https://docs.hyperdbg.org/commands/scripting-language/functions/events/event_inject).

The interruption type determines the details of how the injection is performed. In general, you should use the type **hardware exception** for all exceptions other than the following:

* breakpoint exceptions (#BP; a VMM should use the type software exception);
* overflow exceptions (#OF a VMM should use the use type software exception); and
* those debug exceptions (#DB) that are generated by INT1 (a VMM should use the use type privileged software exception).
* The type of other event is used for the injection of events that are not delivered through the IDT.

Starting from **v0.6**, this function was added to the HyperDbg debugger.

### Related

[event\_inject](https://docs.hyperdbg.org/commands/scripting-language/functions/events/event_inject)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hyperdbg.org/commands/scripting-language/functions/events/event_inject_error_code.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.