C# DivideByZeroException — What It Means & How to Fix It

What Does This Error Mean?

DivideByZeroException is thrown when your code tries to divide a number by zero. In mathematics, dividing by zero is undefined — no number times zero equals a non-zero number. In C#, integer division by zero throws this exception. (Floating-point division by zero gives Infinity or NaN instead of throwing.) The fix is to check that the divisor is not zero before dividing.

Affected Models

.NET Framework
.NET Core
.NET 5+
All C# versions

Common Causes

Dividing an integer by a variable that happens to be zero at runtime
Using the modulo operator (%) with a zero divisor: x % 0
A calculation that was supposed to produce a non-zero result ends up as zero due to unexpected input
Reading a divisor from user input or a database without checking it is not zero
An off-by-one error or logic bug causes a counter or denominator to reach zero

How to Fix It

Add a check before dividing: if (denominator != 0) { result = numerator / denominator; } else { result = 0; /* or handle however is appropriate */ }

This is the simplest and most direct fix. Never divide without first confirming the denominator is safe.
Use a try/catch block to catch the exception if you cannot easily check beforehand — but this should be a last resort.

try { result = a / b; } catch (DivideByZeroException) { result = 0; Console.WriteLine('Cannot divide by zero'); } Checking beforehand is cleaner and more efficient.
If the divisor comes from user input, validate it when received: if (int.TryParse(input, out int value) && value != 0) — make sure it is both a valid number and not zero.

Validation should happen as early as possible — when you receive the input, not when you use it later.
For floating-point numbers (double, float), dividing by zero does NOT throw an exception in C# — it returns double.PositiveInfinity, double.NegativeInfinity, or double.NaN. Check for these after division if needed.

double.IsNaN(result) and double.IsInfinity(result) let you check for these special values.
Trace the code to find where the zero value comes from. Is it uninitialized (defaults to 0), a result of a calculation, or bad input? Fix the source of the zero.

Sometimes the real fix is upstream — the zero should never have been there in the first place.

When to Call a Professional

DivideByZeroException is always fixable yourself. Add a check before any division to ensure the denominator is not zero. Decide what the right behavior is when the denominator is zero — return zero, return a default, skip the calculation, or show an error.

Frequently Asked Questions

Why does integer division by zero throw but float division does not?

Integer types (int, long) have no way to represent Infinity or NaN — they only hold whole numbers. So when integer division by zero occurs, the only option is to throw an exception. Floating-point types (double, float) follow the IEEE 754 standard, which defines special values: Infinity, -Infinity, and NaN (Not a Number). So float/0.0 returns Infinity instead of throwing.

What is the difference between DivideByZeroException and ArithmeticException?

DivideByZeroException is a subclass of ArithmeticException. ArithmeticException is the general category for math errors. DivideByZeroException is the specific case of dividing by zero. Catching ArithmeticException will also catch DivideByZeroException.

What does double.NaN mean?

NaN stands for 'Not a Number' — it is the result of mathematically undefined floating-point operations like 0.0 / 0.0 or the square root of a negative number. NaN is unusual: NaN != NaN is true — NaN is not equal to itself. Use double.IsNaN(value) to check for it, not == double.NaN.