HowToFixMe
WINDOWS · 0xC0040037 STATUS_PNP_IRQ_TRANSLATION_FAILED

How to Fix Windows Error 0xC0040037

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-25

⚡ At a glance
Error code0xC0040037
Symbolic nameSTATUS_PNP_IRQ_TRANSLATION_FAILED
PlatformWindows
Error classNTSTATUS
Official messageAn IRQ translator failed to translate resources.
SourceMicrosoft MS-ERREF (NTSTATUS)

What is 0xC0040037?

Real-world context. Cost envelope: ~Rs 0 INR (configuration fix in most cases). Time at the keyboard: ~10 to 30 minutes triage. Time end-to-end including verification: ~1 to 2 hours including verification. Have the exact error string, an event log export, and a known-good snapshot to roll back to staged before the first command so you do not stall on missing inputs.

0xC0040037 is a Windows NTSTATUS value returned by the kernel or by a driver running in kernel mode. NTSTATUS codes are 32-bit values that the user-mode layer normally converts to a Win32 error before showing it, but tools that call into the native API directly (debuggers, kernel tracers, file-system filter drivers) surface the raw status. In plain English, this code says: pnp irq translation failed. The official reference describes it like this: "An IRQ translator failed to translate resources.". That description is the contract; the actual fix depends on which subsystem produced the value, which is what the rest of this guide walks through.

When does 0xC0040037 appear?

The same status code can come from very different code paths. Here are the scenarios I see most often when STATUS_PNP_IRQ_TRANSLATION_FAILED shows up on a real machine:

If your environment matches more than one of these, work the fix steps in order: cheap diagnostics first, system repair second, in-place reinstall as the last resort.

How to fix 0xC0040037

Run an elevated PowerShell prompt (right-click Start, then Windows Terminal (Admin) or PowerShell (Admin)). Each block below is a copy-paste recipe; adapt the placeholders in angle brackets to your environment before running.

Rescan device manager for hardware changes (PowerShell, run as administrator)

pnputil /scan-devices
Get-PnpDevice -Status Error

Restart the Plug and Play service (PowerShell, run as administrator)

Get-Service -Name PlugPlay | Format-Table -AutoSize
Restart-Service -Name 'PlugPlay' -Force

Remove and reinstall the misbehaving driver (PowerShell, run as administrator)

pnputil /enum-drivers
pnputil /delete-driver oem##.inf /uninstall /force
pnputil /add-driver 'C:\Drivers\new\driver.inf' /install

CMD fallback (run as administrator)

pnputil /scan-devices
pnputil /enum-drivers

Pull the matching event-log entry

$code = '0xC0040037'
Get-WinEvent -LogName System -MaxEvents 1000 | Where-Object { $_.Message -match $code } | Select-Object -First 10 TimeCreated, Id, ProviderName, Message | Format-List
Get-WinEvent -LogName Application -MaxEvents 1000 | Where-Object { $_.Message -match $code } | Select-Object -First 10 TimeCreated, Id, ProviderName, Message | Format-List

Back the registry up before any edit

$stamp = Get-Date -Format yyyyMMdd-HHmm
New-Item -ItemType Directory -Force -Path 'C:\Backup' | Out-Null
reg export 'HKLM\SOFTWARE' "C:\Backup\HKLM-Software-pre-windows-error-0xc0040037-$stamp.reg" /y
reg export 'HKLM\SYSTEM'   "C:\Backup\HKLM-System-pre-windows-error-0xc0040037-$stamp.reg" /y

If you can't fix immediately

Reduce the blast radius until the change window opens: stop the service that raises the error, isolate the host from production traffic, or fall back to a known-good snapshot. A short workaround beats a rushed change on a Friday night.

# Pause the affected service and capture state before changing anything.
Get-Service | Where-Object Status -eq 'Running' | Where-Object Name -match '<service-keyword>' | Stop-Service -Force -PassThru
Get-ScheduledTask | Where-Object State -ne 'Disabled' | Where-Object TaskName -match '<task-keyword>' | Disable-ScheduledTask

How to verify the fix worked

Work through these checks in order. If any one fails, repeat the matching fix step before moving on.

Frequently asked questions

What does 0xC0040037 mean exactly?

The Windows documentation defines it as a ntstatus that signals pnp irq translation failed. In day-to-day terms, it is the operating system telling a calling program that the request cannot complete in the current state. The fix is almost always about restoring the state the caller expected, not about removing the code itself.

Is 0xC0040037 dangerous?

In isolation it is mostly an indicator, not a vulnerability. The status code is a symptom, not the disease. The danger is in what produced it: a corrupted driver, a flaky disk, an exhausted resource, or a permission boundary that is wrong. Read the event-log context around the code before assuming the worst.

Will reinstalling Windows fix it?

Usually no, and it is the wrong first move. A clean install removes the entire configuration that produced the error, which makes it look fixed for a few days while you reinstall apps and drivers. The same condition tends to come back the moment the original workload is restored. Work the fix steps above before you reach for the install media.

What is the difference between 0xC0040037 and the symbolic name STATUS_PNP_IRQ_TRANSLATION_FAILED?

They are the same value. 0xC0040037 is the numeric form a developer prints, and STATUS_PNP_IRQ_TRANSLATION_FAILED is the C/C++ constant defined in the Windows headers. Tooling that consumes one will accept the other; the lookup is deterministic.

Where can I look up other NTSTATUS codes?

Microsoft maintains the full reference at MS-ERREF. For Win32 error names there is the System Error Codes index. Both are searchable by hex value and by the symbolic name.

Related guides worth a look while you sort this one out:

References

Field notes from real Windows incidents

When I work on the 0xC0040037 symptom the rhythm I lean on is the one I have built over years of these tickets, not a stack of generic advice. Windows error codes come in a handful of families; once you recognise the family, the doc page is one search away. Reliability Monitor is the single most underused triage surface in Windows — it gives 30 days of crash history without writing a query.

DISM RestoreHealth needs network or a known-good source image; the most common cause of a failed RestoreHealth is a blocked Windows Update endpoint. STOP codes look terrifying but the first DWORD almost always points directly at the responsible driver.

Tools I actually reach for

For the 0xC0040037 symptom on Windows the cheapest signal I can land usually comes from DISM and sfc, then Process Monitor (procmon), Windows Performance Recorder when DISM and sfc cannot see the layer the fault sits in, and PowerShell Get-WinEvent for the cases where neither of those answers cleanly. That ordering is not academic. It matches the layers the failure tends to surface through, so the cheap signal lands first and the heavier tooling only comes out when the simpler answer does not hold up under scrutiny.

Verification I run before I close the ticket

Before I mark the 0xC0040037 symptom resolved on a Windows unit, the verification loop below is what I actually run. Each step proves a different layer is green, and the order matters - the cheap checks gate the more expensive ones.

sfc /scannow

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

err.exe 0xXXXXXXXX  # symbolic decode

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

Get-WinEvent -FilterHashtable @{LogName='System'; Level=1,2; StartTime=(Get-Date).AddDays(-7)}

Only when every line above runs clean do I close the ticket and update the runbook with the timestamps.

Where I check first when the docs disagree

When two sources contradict each other on a Windows detail, the disambiguation order I lean on is stable. I usually start at support.microsoft.com for the ground-truth view on Windows. I usually start at learn.microsoft.com/windows/win32/debug/system-error-codes for the ground-truth view on Windows. I usually start at techcommunity.microsoft.com/category/windows for the ground-truth view on Windows. I usually start at github.com/microsoft/Windows-Driver-Frameworks for the ground-truth view on Windows. Random blog posts and reseller wikis are signal, not ground truth, and I treat them as such until the references above either confirm or contradict the claim.

Pitfalls I have walked into on this exact path

The shortcuts that look smart on the 0xC0040037 symptom have a habit of biting back. The pitfalls below are the ones I have personally walked into on a Windows unit, not things I read about. Reliability Monitor is the single most underused triage surface in Windows — it gives 30 days of crash history without writing a query. Windows error codes come in a handful of families; once you recognise the family, the doc page is one search away. STOP codes look terrifying but the first DWORD almost always points directly at the responsible driver. When in doubt I revert to the slower path that the manual prescribes - the time I save by skipping it is always smaller than the time I spend cleaning up afterwards.

What I tell the next on-call

When I hand the 0xC0040037 symptom off to the next person on rotation, the three lines I leave in the runbook are these. First, the symptom signature for Windows on the Windows family - not a paraphrase, the exact string that surfaces. Second, the diagnostic that gave the highest signal in the least time. Third, the exact verification command whose green output justified closing the ticket. That trio is what turns a one-off fix into a runbook entry the next engineer can use without paging me at three in the morning.

I also add a one-line note on the cost of getting this wrong. For the 0xC0040037 symptom on a Windows unit, the cost is rarely the replacement part. It is the downtime, the second site visit, and the trust deficit you spend with whoever owns the asset when the fix does not hold. That framing keeps the next on-call from choosing the cheap-looking shortcut that ends up costing the most in elapsed hours and goodwill.