When CPU-Z freezes: cpuz.ini Sensor, DMI, SMBus

You double-click cpuz.exe, the splash screen appears, and then... nothing. The window stops responding, your cursor spins, and CPU-Z never reaches the familiar tabbed interface. This is one of the most common complaints from users, and the good news is that it is almost always fixable. The root cause is nearly always a hardware probe that gets stuck while trying to talk to a component on your motherboard.

This guide walks you through exactly why CPU-Z freezes, how to use the cpuz.ini configuration file to isolate the problem, and what to do once you have found the culprit.

Why does CPU-Z freeze?

When CPU-Z starts, it performs a series of low-level hardware scans to populate every tab with accurate data. These probes include:

• Sensor probing — CPU-Z queries sensor integrated circuits (ICs) on the motherboard to read temperatures, voltages, and fan speeds. Some sensor chips, especially older Winbond or ITE Super I/O controllers, can lock up when accessed in unexpected ways.
• DMI (Desktop Management Interface) — This probe reads SMBIOS tables from your BIOS/UEFI firmware to extract motherboard name, manufacturer, BIOS version, and serial numbers. Malformed or non-standard DMI tables can cause the read to hang indefinitely.
• SMBus (System Management Bus) — CPU-Z communicates over the SMBus to read SPD (Serial Presence Detect) data from your RAM modules. Certain chipset or memory controller combinations respond slowly or not at all.
• PCI enumeration — The PCI scan walks every device on the bus to identify your graphics card, storage controllers, and other peripherals. Exotic or poorly documented PCI devices can stall this scan.
• Display detection — GPU-specific queries that gather driver and adapter information may conflict with certain display drivers.

If any single probe gets stuck waiting for a hardware response that never comes, the entire application freezes. The solution is to selectively disable probes until CPU-Z can launch, then narrow down the offender.

The fix: cpuz.ini

CPU-Z reads an optional configuration file called cpuz.ini at startup. By setting specific keys to 0, you tell CPU-Z to skip certain hardware probes entirely. Create a plain text file named cpuz.ini and place it in the same folder as cpuz.exe. The file contents should look like this:

With every probe set to 0, CPU-Z will skip all potentially problematic hardware reads. It will still show basic CPU information (gathered through the CPUID instruction), but tabs like Mainboard, Memory SPD, and Graphics will be empty or incomplete. That is expected — the goal at this stage is simply to confirm that CPU-Z can launch without freezing.

Step-by-step troubleshooting

Follow these steps methodically to pinpoint which probe causes the hang:

1. Disable ALL probes — Create cpuz.ini with every key set to 0 as shown above. Save the file and launch CPU-Z.
2. Verify CPU-Z launches — If the program opens successfully, the freeze is confirmed to be probe-related. If it still freezes, the issue may lie elsewhere (corrupted install, antivirus interference, or driver conflicts).
3. Re-enable one probe at a time — Change Sensor=0 to Sensor=1, save, and launch CPU-Z again. If it works, close CPU-Z, then re-enable DMI=1. Continue in this order: Sensor, DMI, SMBus, PCI, Display.
4. Identify the culprit — When CPU-Z freezes again after re-enabling a specific probe, you have found the problematic one. Set that key back to 0 and leave all others at 1. You will lose the data that probe provides, but CPU-Z will work reliably.

Common culprits

Based on years of user reports, certain hardware configurations are more prone to probe-related freezes:

• Older sensor ICs — Winbond W83627, ITE IT8712, and similar Super I/O chips from the mid-2000s era are frequent offenders when Sensor=1.
• Exotic or server chipsets — Workstation boards with Intel C-series or AMD EPYC chipsets sometimes have non-standard SMBus implementations that stall the SPD read.
• Virtual machines — Running CPU-Z inside VMware, VirtualBox, or Hyper-V can trigger DMI or PCI freezes because the virtualized hardware does not respond like real silicon.
• Laptops with embedded controllers — Some laptop EC firmware handles sensor queries differently, causing Sensor probes to time out.
• Multi-GPU setups — Systems with SLI, CrossFire, or mixed GPU configurations may freeze during the Display probe.

Other solutions

If editing cpuz.ini does not fully resolve the issue, try these additional approaches:

• Run as Administrator — Right-click cpuz.exe and select "Run as administrator." Some hardware probes require elevated privileges to complete properly, and running without them can cause partial hangs.
• Update CPU-Z — Newer versions include updated probe routines and hardware compatibility fixes. If you are running an older build, download the latest version and try again.
• Try the portable (ZIP) version — The portable version does not install a kernel driver at setup time, which can help isolate whether the issue is driver-related or probe-related.
• Check your antivirus — Security software sometimes intercepts the low-level hardware access that CPU-Z requires. Temporarily whitelist or disable your antivirus to test.

For more detailed configuration options and advanced troubleshooting, visit the Help and Troubleshooting section. You can also consult the install and cpuz.ini guide for a full list of available configuration keys. Ready to grab the latest build? Head to the Download page.