Custom Resolution Utility (CRU) and Open Hardware Monitor are both useful Windows utilities, but they address very different aspects of PC configuration and maintenance. CRU focuses on customizing display modes and monitor configurations, while Open Hardware Monitor concentrates on monitoring hardware temperatures, voltages, fan speeds, clock speeds, load, and other system sensors.
Understanding the distinction between these tools makes it easier to determine which type of task each one is designed to handle.
Custom Resolution Utility vs Open Hardware Monitor at a Glance
| Category | Custom Resolution Utility (CRU) | Open Hardware Monitor |
| Primary purpose | Customize monitor resolutions and refresh rates | Monitor PC hardware sensors |
| Main focus | Display configuration | Hardware monitoring |
| Custom resolutions | Yes | No |
| Custom refresh rates | Yes | No |
| Temperature monitoring | No | Yes |
| Fan-speed monitoring | No | Yes, when supported |
| Voltage monitoring | No | Yes, when supported |
| CPU/GPU load | No | Yes |
| Clock-speed monitoring | No | Yes |
| Display identification | EDID configuration | No |
| Portable utility | Yes | Yes |
| Windows support | Windows-focused | Windows-focused |
| Typical users | Gamers, display enthusiasts, troubleshooting users | PC builders, enthusiasts, technicians |
| Main requirement | Compatible Windows display hardware/driver | Supported hardware sensors |
What Is Custom Resolution Utility?
Custom Resolution Utility, commonly known as CRU, is a Windows utility designed to modify the display information reported by a monitor or television. It primarily works with Extended Display Identification Data (EDID), allowing users to create or edit display resolutions, refresh rates, timings, and related configuration information.
CRU is particularly associated with users who want more control over display modes than the standard Windows display settings provide.
Key CRU Features
- Create custom resolutions
- Add custom refresh rates
- Modify display timings
- Edit detailed and standard resolutions
- Configure display ranges
- Modify extension blocks
- Work with EDID-related display information
- Create display configurations that Windows and the graphics driver can recognize
- Reset changes when necessary
CRU can be useful when a monitor does not expose a desired resolution or refresh rate through its normal driver configuration.
What Is Open Hardware Monitor?
Open Hardware Monitor is an open-source hardware monitoring utility designed to display information collected from a computer’s sensors.
Depending on the hardware and available sensor support, it can report information such as:
- CPU temperature
- GPU temperature
- Fan speeds
- CPU and GPU load
- Clock speeds
- Voltage readings
- Memory-related information
- Storage temperatures
- Power-related readings on supported hardware
The program is particularly useful for observing how a computer behaves during normal operation, gaming, benchmarking, or troubleshooting.
Feature Comparison
Display Configuration
CRU is specifically designed for display configuration. Users can create or modify resolutions and refresh rates that are not normally presented through Windows or the graphics driver’s standard interface.
Open Hardware Monitor does not provide comparable display configuration functionality. Its purpose is monitoring rather than changing display modes.
Hardware Monitoring
Open Hardware Monitor has a substantially different feature set. It reads available hardware sensors and presents information about the computer’s operating condition.
CRU does not function as a general-purpose hardware-monitoring application.
Custom Resolutions and Refresh Rates
Custom resolutions are one of CRU’s defining functions. This can be useful for users experimenting with non-standard resolutions, alternative refresh rates, or custom timing configurations.
Open Hardware Monitor does not create display modes.
Sensor Information
Open Hardware Monitor can expose multiple hardware measurements through a hierarchical interface. The exact sensors available depend on the motherboard, processor, graphics card, storage devices, and sensor controllers installed in the system.
CRU does not provide this type of sensor monitoring.
Performance Considerations
CRU is generally used as a configuration utility rather than something that continuously monitors the computer. Its purpose is to modify display configuration information, so it does not need to maintain a large background monitoring workload.
Open Hardware Monitor is designed to collect sensor information while running. Monitoring overhead is generally small, although the exact resource usage depends on the hardware, polling behavior, and configuration.
Neither application is primarily a benchmarking tool:
- CRU: changes display configuration rather than measuring system performance.
- Open Hardware Monitor: observes hardware behavior rather than directly benchmarking it.
Open Hardware Monitor can, however, be useful alongside a benchmark or stress test because temperatures, clocks, loads, and other sensor readings can help explain performance changes.
Compatibility
CRU Compatibility
CRU is designed primarily for Windows systems and works by interacting with the display configuration and graphics-driver environment.
Its usefulness depends on factors such as:
- Windows version
- Graphics driver
- GPU manufacturer
- Monitor or television
- Display connection
- Display’s supported timing characteristics
Changes made with CRU may not behave identically across different GPUs, drivers, displays, adapters, or connection standards.
Users should also be aware that creating an invalid or unsupported display mode can result in display problems. CRU therefore includes utilities for restarting the graphics driver and resetting configuration changes.
Open Hardware Monitor Compatibility
Open Hardware Monitor’s compatibility is primarily determined by whether it can access the sensors used by a particular hardware component.
Commonly monitored components include:
- Intel and AMD processors
- NVIDIA and AMD graphics hardware
- Motherboards
- Storage devices
- Memory-related sensors where available
- Fan controllers
- Temperature sensors
However, sensor availability varies between hardware generations and manufacturers. A computer may therefore expose some measurements while leaving others unavailable.
System Requirements
CRU
CRU is a relatively lightweight utility. Its main requirement is a compatible Windows environment with a display and graphics-driver configuration that allows the desired EDID-related changes to be applied.
Because CRU modifies display configuration rather than installing a large software framework, it is generally portable and can be run without a conventional installation process.
Open Hardware Monitor
Open Hardware Monitor is also lightweight and can be used as a portable application.
Its requirements are primarily related to:
- A supported Windows operating system
- Compatible hardware
- Appropriate access to hardware sensors
Administrative access may be useful or necessary for certain hardware-monitoring functions, depending on the system and configuration.
Use Cases
When CRU Is Typically Used
CRU can be useful for:
- Creating custom gaming resolutions
- Adding refresh rates not exposed by default
- Experimenting with display timings
- Configuring high-refresh-rate displays
- Adjusting monitor EDID information
- Troubleshooting missing display modes
- Fine-tuning monitor configurations
For example, someone using a high-refresh-rate gaming monitor might use CRU to experiment with a particular resolution and refresh-rate combination that is not listed by default.
When Open Hardware Monitor Is Typically Used
Open Hardware Monitor is suited to:
- Monitoring CPU temperatures
- Checking GPU temperatures
- Watching fan speeds
- Observing CPU/GPU utilization
- Monitoring clock speeds
- Troubleshooting overheating
- Checking system behavior during gaming
- Observing hardware while running stress tests
- Diagnosing unusual thermal or performance behavior
It can therefore be useful as a companion to CPU or GPU stress-testing applications.
Pros and Limitations of CRU
Pros
- Provides detailed display configuration controls
- Supports custom resolutions
- Supports custom refresh rates
- Allows advanced timing configuration
- Useful for display troubleshooting
- Portable and relatively lightweight
- Gives users more control than standard Windows display settings
Limitations
- Intended primarily for Windows
- Requires some understanding of display timings and refresh rates
- Incorrect settings can cause display problems
- Hardware and graphics-driver compatibility can affect results
- It is not a hardware-monitoring utility
- It is not intended to benchmark CPU or GPU performance
Pros and Limitations of Open Hardware Monitor
Pros
- Open-source
- Free to use
- Lightweight
- Provides a broad range of hardware measurements
- Useful for thermal monitoring
- Can monitor CPU and GPU activity
- Useful during gaming and stress testing
- Portable operation is available
Limitations
- Sensor availability varies by hardware
- Some newer components may have incomplete monitoring support
- It does not configure custom monitor resolutions
- It does not replace dedicated benchmarking applications
- Sensor readings can depend on hardware-controller support and driver access
CRU vs Open Hardware Monitor for Gaming PCs
The two utilities can serve different roles on the same gaming computer.
CRU can be relevant when the objective is to modify the display configuration—for example, experimenting with a custom resolution or refresh rate.
Open Hardware Monitor becomes relevant when the objective is to observe what the computer is doing while gaming. A user can monitor CPU and GPU temperatures, utilization, clocks, and fan speeds while playing a demanding game.
This makes their roles complementary rather than directly competitive.
CRU vs Open Hardware Monitor for Troubleshooting
For display-related troubleshooting, CRU can provide more detailed control over the display configuration and EDID information.
For thermal or hardware-related troubleshooting, Open Hardware Monitor provides the relevant sensor information.
Examples include:
- Missing refresh rate: CRU may be relevant.
- Custom resolution: CRU may be relevant.
- High CPU temperature: Open Hardware Monitor may be relevant.
- GPU overheating: Open Hardware Monitor may be relevant.
- Unexpected fan behavior: Open Hardware Monitor can help inspect fan readings where supported.
- Display timing experimentation: CRU is designed for this purpose.
Ease of Use
CRU has a more specialized interface because display timing and EDID configuration involve concepts that are not normally exposed to everyday Windows users. Beginners may need to understand resolutions, refresh rates, timing standards, and display ranges before making advanced changes.
Open Hardware Monitor is generally more straightforward for basic monitoring. Its sensor tree presents measurements in categories, making it relatively easy to locate temperatures, clocks, loads, and fan readings when the hardware is supported.
The learning curve for both programs therefore depends on the task: CRU requires display-configuration knowledge, while Open Hardware Monitor primarily requires familiarity with PC hardware readings.
Key Differences
The most important distinction between the two utilities is their purpose:
Custom Resolution Utility
- Focuses on displays.
- Modifies EDID-related configuration.
- Creates custom resolutions and refresh rates.
- Useful for advanced monitor configuration.
Open Hardware Monitor
- Focuses on PC hardware.
- Reads available sensors.
- Displays temperatures, loads, clocks, fans, and other measurements.
- Useful for monitoring and troubleshooting.
Neither is designed to replace the other because they solve different problems.
Final Comparison
Custom Resolution Utility and Open Hardware Monitor are specialized tools aimed at different areas of PC management.
CRU is centered on advanced display configuration, giving users greater control over resolutions, refresh rates, timings, and EDID-related settings. It is particularly relevant to monitor customization and display troubleshooting.
Open Hardware Monitor is centered on hardware visibility, providing sensor readings that can help users understand CPU, GPU, motherboard, storage, and cooling behavior where supported.
The choice between them therefore depends primarily on the task rather than overall software quality. Users working with display modes and custom refresh rates are dealing with the area CRU targets, while users interested in temperatures, utilization, clocks, and hardware sensors are dealing with the area Open Hardware Monitor targets.