Skip to main content

Benchmarking Your Own PC: Free Tools and What the Numbers Mean

Media Benchmarking Your Own PC Free Tools and What the Numbers Mean

A computer can feel slow for many different reasons.

The processor may be overheating, the SSD might be performing below specification, the graphics card could be throttling, or the system may simply lack enough memory for the workload. At other times, the hardware is working correctly and the perceived slowdown is caused by software, background tasks, or unrealistic expectations.

Benchmarking helps replace guesswork with measurable results.

A benchmark runs a controlled workload and produces a score, speed, temperature, frame rate, or completion time. You can then compare that result with previous tests, similar systems, or the expected performance of your hardware.

However, benchmark numbers are useful only when you understand what they measure. A high score in one test does not guarantee that every application will be fast, and one low result does not automatically mean a component is faulty.

What Is a PC Benchmark?

A benchmark is a repeatable test designed to measure one or more aspects of computer performance.

It may test:

  • Processor performance
  • Graphics performance
  • Storage speed
  • Memory behaviour
  • Cooling and sustained performance
  • System stability
  • Gaming frame rates
  • General productivity
  • Battery performance

Some benchmarks produce a single score. Others report practical measurements such as megabytes per second, frames per second, latency, temperature, or the time required to complete a task.

The most useful result is not always the largest number. It is the result that answers a specific question about the computer.

What Are You Trying to Find Out?

Choose the benchmark according to the problem.

You may want to know:

  • Whether the processor performs as expected
  • Whether the graphics card is suitable for a game
  • Whether a new SSD is running at the correct speed
  • Whether the computer overheats under sustained load
  • Whether performance drops after several minutes
  • Whether a memory upgrade helped
  • Whether a laptop is slower on battery
  • Whether a driver update improved or reduced performance
  • Whether an overclock is stable
  • Whether a replacement computer is actually faster

Running every available benchmark without a clear purpose can produce a lot of numbers without a useful conclusion.

Benchmarking Is Not the Same as Stress Testing

A benchmark measures performance during a defined workload.

A stress test deliberately places sustained or extreme load on components to expose instability, overheating, power problems, or throttling.

For example:

  • A short CPU benchmark may show excellent performance
  • A longer stress test may reveal that the processor overheats and slows down
  • A graphics benchmark may complete successfully
  • A stability test may expose memory or GPU errors after 20 minutes

OCCT describes itself as an all-in-one stability, stress-testing, benchmarking, and monitoring tool, making it useful when the question is not merely “How fast is this PC?” but also “Can it remain stable under load?” 

Before You Run Any Benchmark

For meaningful comparisons, test under consistent conditions.

Before starting:

  • Restart the computer
  • Connect a laptop to its correct charger
  • Select the intended Windows power mode
  • Allow pending updates to finish
  • Close unnecessary applications
  • Pause large downloads and cloud synchronisation
  • Record the room temperature where relevant
  • Use the same benchmark version and settings
  • Confirm that cooling vents are not obstructed
  • Record driver and BIOS versions
  • Run the same test more than once

Do not compare a laptop running on battery with the same laptop connected to power and expect identical results.

Many laptops reduce CPU and GPU power substantially when unplugged.

Keep the Test Conditions Consistent

Benchmark results can change because of:

  • Background antivirus scanning
  • Windows Update
  • Browser tabs
  • Cloud backup
  • Room temperature
  • Fan profile
  • Battery level
  • Power plan
  • Driver version
  • Benchmark version
  • Thermal state before the test

UL states that its benchmark precision is usually better than 3% under ideal testing conditions. Small variations between runs are therefore normal and should not be treated as evidence of a fault. 

A difference of 1% or 2% may mean very little. A repeatable difference of 15% or 20% deserves investigation.

Run More Than Once

One benchmark run can be affected by a temporary background task.

A useful method is:

  1. Run the test three times
  2. Allow the system to cool briefly between tests where appropriate
  3. Record each result
  4. Use the middle result rather than the single highest score
  5. Investigate unusually large variation

If the first run is strong but later runs become progressively slower, thermal throttling may be involved.

If the results vary wildly with no clear pattern, check background activity, power delivery, temperatures, memory stability, and driver behaviour.

Free Tool 1: Cinebench for CPU and Rendering Performance

Cinebench is a free Maxon benchmark based on rendering workloads. The current Cinebench 2026 release provides CPU and supported GPU testing using a consistent scene and Maxon’s Redshift rendering technology. 

It is particularly useful for evaluating:

  • Multi-core CPU performance
  • Single-core or individual-core performance
  • Sustained rendering performance
  • Workstation and content-creation capability
  • Cooling performance during CPU load
  • Performance before and after a hardware change

What a Cinebench Score Means

Cinebench produces scores for specific test modes.

In general:

  • A higher score means the test completed more work within the benchmark’s scoring model
  • Multi-core results reflect performance when many processor cores are used
  • Single-core or individual-core results reflect performance that depends more heavily on one execution thread
  • CPU and GPU scores measure different devices and should not be compared directly

The result is most useful when compared with:

  • The same processor in similar systems
  • Your own earlier result
  • The same computer before and after a change
  • Multiple runs under identical settings

Do not compare Cinebench 2026 scores directly with scores from earlier Cinebench generations. Benchmark engines and scoring systems can change between releases, so results are meaningful only within the same benchmark version. 

Why Multi-Core and Single-Core Scores Both Matter

A processor with many cores may perform extremely well in:

  • 3D rendering
  • Video encoding
  • Code compilation
  • Scientific workloads
  • Heavy multitasking

Single-core performance remains important for:

  • General interface responsiveness
  • Older applications
  • Some games
  • Light office work
  • Tasks that cannot use many cores efficiently

A high multi-core score does not guarantee that every application will feel proportionally faster.

Software must be designed to use the available cores.

What a Low Cinebench Result Can Mean

A score below similar systems may be caused by:

  • High CPU temperature
  • Restricted laptop power mode
  • Incorrect charger
  • Background activity
  • Low processor power limits
  • Dust or blocked cooling
  • BIOS settings
  • Memory configuration
  • Outdated firmware
  • Manufacturer-specific thermal limits

It does not immediately prove the processor is defective.

Check the system’s temperature, clock speed, power draw, and whether performance drops during repeated runs.

Free Tool 2: 3DMark for Graphics and Gaming Performance

3DMark is designed to test and compare gaming-related CPU and graphics performance. UL offers free access to selected tests, with additional tests available in paid editions. 

It is useful for checking:

  • Graphics-card performance
  • Gaming-oriented CPU performance
  • Driver changes
  • GPU cooling
  • Laptop graphics modes
  • Performance before and after upgrades
  • Whether a system matches similar hardware

Choose the Correct 3DMark Test

Different 3DMark tests target different generations and levels of hardware.

Do not compare scores from two different tests as though they use the same scale.

A result from one benchmark workload cannot be directly compared with a score from another workload.

Use:

  • The same test
  • The same preset
  • The same benchmark version
  • Comparable hardware and operating conditions

When comparing results, confirm whether you are looking at:

  • Overall score
  • Graphics score
  • CPU score
  • Frame rate
  • Stress-test stability

What the Overall 3DMark Score Means

The overall score combines multiple test results according to the benchmark’s scoring method.

For example, UL explains that the Time Spy overall score uses a weighted harmonic mean of the Graphics and CPU scores, with the graphics component carrying the larger weighting. 

That means:

  • The overall score is not a simple average
  • A gaming-focused test may be influenced more heavily by GPU performance
  • The graphics score is often more useful when isolating the graphics card
  • The CPU score is more useful when investigating processor performance

When diagnosing a low result, inspect the separate component scores rather than focusing only on the headline figure.

Is Your 3DMark Score “Good”?

A higher score indicates stronger performance within that test, but the most useful comparison is against other systems using the same CPU and GPU.

3DMark’s result screen can show how the score compares with other results from the same hardware, and its online database allows scores to be searched and compared across compatible tests. 

A score labelled average may be perfectly normal.

A top-ranking result may involve:

  • Overclocking
  • Enhanced cooling
  • Higher power limits
  • Carefully tuned memory
  • Minimal background software
  • Conditions unlike an ordinary office or gaming PC

Do not chase leaderboard scores unless competitive benchmarking is the goal.

Watch the Frame Rates

The overall score is useful for comparison, but frame-rate figures are often easier to interpret.

For example:

  • 30 frames per second may feel acceptable for some slower-paced games
  • 60 frames per second generally feels smoother
  • Higher-refresh monitors can benefit from substantially higher frame rates
  • Minimum and low-percentile frame rates affect smoothness and stutter

A synthetic benchmark does not predict the exact frame rate in every game. Different games use different engines, effects, processors, and graphics features.

Use built-in game benchmarks when deciding how a particular game performs.

Free Tool 3: CrystalDiskMark for Storage Performance

CrystalDiskMark is a free Windows storage benchmark that measures sequential and random read, write, and mixed performance. 

It can test:

  • NVMe SSDs
  • SATA SSDs
  • Hard disk drives
  • USB drives
  • External SSDs
  • Memory cards
  • Network-mounted storage in some configurations

It is useful for checking whether a new drive or connection is performing in the expected range.

What Sequential Read and Write Mean

Sequential tests use larger, continuous blocks of data.

They are most relevant to tasks such as:

  • Copying large video files
  • Moving disk images
  • Reading large archives
  • Editing high-bitrate media
  • Backing up large files

Manufacturers often advertise the best sequential speed because it produces the largest and most marketable figure.

A very high sequential result does not necessarily mean that Windows will start or applications will open proportionally faster.

What Random Read and Write Mean

Random tests access smaller pieces of data from different locations.

They are often more relevant to:

  • Windows startup
  • Application launches
  • Installing software
  • Loading many small files
  • Browser cache
  • Databases
  • General desktop responsiveness

Random performance is usually much lower numerically than sequential performance.

That is normal.

Do not compare a random 4K figure directly with a large sequential figure and conclude that the drive is failing.

They are different workloads.

What Queue Depth and Threads Mean

Storage benchmarks may show settings involving queues and threads.

These represent how many storage requests are waiting and how many processing threads generate them.

High queue-depth results can demonstrate the maximum capability of a modern SSD under heavy parallel workloads.

A normal desktop user may spend much of the time at lower queue depths.

For everyday responsiveness, low-queue random performance may be more representative than the highest headline sequential figure.

Why an SSD May Test Below Its Advertised Speed

Possible causes include:

  • Testing a nearly full drive
  • Thermal throttling
  • Slow motherboard slot
  • PCIe link operating at fewer lanes
  • Older PCIe generation
  • External USB bottleneck
  • Enclosure limitation
  • SATA instead of NVMe
  • Background disk activity
  • Encryption overhead
  • Power-saving mode
  • Small test settings
  • Drive cache becoming exhausted

Advertised speeds are usually maximum figures achieved under controlled conditions.

A lower result is not automatically evidence of a fault.

Be Careful Benchmarking Storage

Storage benchmarks write data to the drive.

A few normal tests are unlikely to cause meaningful harm to a healthy modern SSD, but repeated large write tests create unnecessary writes and can fill caches or consume time.

Avoid:

  • Running continuous storage benchmarks for entertainment
  • Testing a drive that is already failing
  • Benchmarking during an important backup
  • Filling a nearly full system drive
  • Testing removable media containing irreplaceable data
  • Running aggressive tests on a drive making mechanical noises

Benchmarking is not a data-recovery method.

Free Tool 4: OCCT for Stability, Temperatures, and Sustained Load

OCCT provides monitoring, benchmarking, stability, and stress-testing functions for components such as the processor, graphics card, memory, and power-related workloads. 

It is useful when you want to know:

  • Whether the PC remains stable under load
  • Whether temperatures become excessive
  • Whether an overclock produces errors
  • Whether performance falls over time
  • Whether the CPU, GPU, or memory causes crashes
  • Whether cooling is adequate

Stress testing creates much more heat and power demand than ordinary browsing or office work.

Monitor the system closely.

Stop a Stress Test When Something Looks Wrong

End the test when you notice:

  • Temperatures rising beyond safe operating behaviour
  • Burning smell
  • Smoke
  • Crackling
  • Fan failure
  • Severe graphical corruption
  • Repeated hardware errors
  • Unexpected shutdowns
  • Grinding or clicking
  • Power instability

Do not use a stress test to force a visibly faulty computer to fail completely.

Laptops may run hot under load by design, but repeated thermal throttling or emergency shutdowns should still be investigated.

Temperature Is Not the Whole Story

A temperature reading needs context.

A processor may safely operate at a high temperature while maintaining its intended clock speed.

Another processor may show a lower temperature because it has already reduced speed and power.

Look at:

  • Temperature
  • Clock frequency
  • Power draw
  • Fan speed
  • Benchmark score
  • Whether the score falls over repeated runs
  • Whether the system reports thermal throttling

Performance and thermal behaviour should be interpreted together.

What Is Thermal Throttling?

Thermal throttling occurs when a component reduces its speed or power to control temperature.

It protects the hardware.

Signs include:

  • Strong score on the first run
  • Lower scores on later runs
  • Clock speed falling during sustained load
  • Fans running at maximum speed
  • Performance returning after cooling
  • Laptop performance changing with surface or airflow

Possible causes include:

  • Dust
  • Blocked vents
  • Failed fan
  • Poor case airflow
  • Dried thermal material
  • Undersized cooling
  • Very high room temperature
  • Aggressive power settings

Throttling is not always a fault. Many thin laptops are designed around brief boost performance followed by lower sustained power.

Built-In Game Benchmarks

Many games include their own benchmark mode.

These are often more useful than synthetic tests when the question is:

How well does this computer run this particular game?

Record:

  • Average frame rate
  • Minimum frame rate
  • Low-percentile frame rate where available
  • Resolution
  • Graphics preset
  • Upscaling setting
  • Ray-tracing setting
  • Frame-generation setting
  • Driver version

Do not compare two gaming results unless the graphics settings match.

A result at 1080p Low cannot be fairly compared with a result at 4K Ultra.

Benchmark at the Resolution You Actually Use

Graphics performance changes dramatically with resolution.

Test at:

  • 1920 × 1080 for a 1080p display
  • 2560 × 1440 for a 1440p display
  • 3840 × 2160 for a 4K display

Upscaling technologies can alter both image quality and frame rate.

Record whether the result used:

  • Native resolution
  • Quality upscaling
  • Balanced upscaling
  • Performance upscaling
  • Frame generation

Without these details, the frame-rate figure has little meaning.

Windows Task Manager Is Useful but Not a Benchmark

Task Manager shows real-time utilisation, memory, disk, network, and GPU activity.

It can help identify:

  • A process using the CPU
  • Memory pressure
  • High disk activity
  • GPU engine use
  • Background applications

However, 100% utilisation does not tell you whether the component is performing correctly.

A slow and fast processor can both reach 100%.

Task Manager is best used alongside a controlled benchmark and temperature-monitoring data.

Benchmark Scores Are Relative

A benchmark score usually has no universal meaning by itself.

A score of 10,000 may be excellent in one test and meaningless in another.

Always record:

  • Tool name
  • Benchmark name
  • Version
  • Preset
  • Resolution
  • Hardware
  • Driver
  • Power mode
  • Date
  • Temperature conditions

Without this context, the number cannot be interpreted reliably.

Do Not Compare Different Benchmark Versions

Benchmark developers update:

  • Workloads
  • Render engines
  • scoring models
  • Hardware support
  • APIs
  • test duration
  • error handling

Scores from different generations may not share the same scale.

Keep the installer or note the exact version when tracking performance over time.

An apparent improvement or regression may simply be caused by a changed benchmark.

Compare Like With Like

For a fair comparison, use systems with:

  • The same CPU model
  • The same GPU model
  • Similar memory configuration
  • Similar power limits
  • Similar cooling
  • The same test version
  • The same test preset
  • Similar driver versions

A laptop GPU and desktop GPU with the same marketing name may have very different power limits and performance.

Two laptops using the same processor can also perform differently because of cooling and manufacturer configuration.

Percentages Are More Useful Than Raw Differences

Suppose your earlier score was 10,000 and the new score is 9,800.

That is a 2% reduction and may be normal test variation.

If the new score is 8,000, the 20% reduction is more significant.

Use percentage change:

Difference ÷ original result × 100

Focus on repeatable percentage changes rather than small raw-number differences.

What Counts as a Meaningful Difference?

As a practical guide:

  • Under 3% may be ordinary variation
  • Around 5% may be worth retesting
  • 10% or more is usually noticeable in a controlled benchmark
  • 20% or more suggests a major configuration, thermal, driver, or hardware difference

These are not universal fault thresholds.

Some workloads naturally vary more than others.

Always repeat the test and confirm that conditions match.

Watch for the Average, Not the Best Internet Result

Online result databases often contain systems with:

  • Overclocked components
  • Modified cooling
  • Increased power limits
  • Tuned memory
  • Fresh Windows installations
  • Benchmark-specific optimisations

Compare against the average or typical result for your hardware rather than the record.

UL’s own guidance encourages comparing the score with other systems using the same hardware, while its Hall of Fame represents highly competitive top results rather than normal expectations. 

Why Your New PC May Score Lower Than a Review

Professional reviews may use:

  • Faster memory
  • Better cooling
  • High-performance motherboard
  • Latest drivers
  • Clean operating system
  • Higher power limits
  • Open test bench
  • Different benchmark version
  • Different ambient temperature

Your computer may also contain background security and management software that a review machine does not.

A moderate difference does not necessarily indicate faulty hardware.

Laptops Need Special Interpretation

Laptop performance depends heavily on:

  • Charger wattage
  • Battery state
  • Performance profile
  • Fan mode
  • Surface and airflow
  • CPU and GPU power limits
  • Shared cooling
  • Manufacturer firmware
  • Whether the discrete GPU is active
  • Docking configuration

Test the laptop:

  1. Connected to the correct charger
  2. On a hard, flat surface
  3. In the intended performance mode
  4. With the battery sufficiently charged
  5. Without blocking the vents

A universal USB-C charger may power the laptop but provide insufficient wattage for full benchmark performance.

Check Which GPU Is Running the Test

Many laptops include:

  • Integrated graphics
  • Dedicated NVIDIA or AMD graphics

A benchmark may accidentally run on the integrated GPU.

Check:

  • Benchmark settings
  • Windows graphics settings
  • GPU activity in Task Manager
  • Laptop performance mode
  • Docking and display connection

An external monitor connected to a particular port may also route through a different GPU.

Memory Configuration Can Affect Scores

System memory performance can be influenced by:

  • Capacity
  • Speed
  • Timings
  • Single-channel or dual-channel configuration
  • Number of modules
  • Integrated GPU usage
  • XMP or EXPO profile
  • Laptop power design

A system with one memory module may perform below an otherwise similar system using two matched modules.

This is especially noticeable for integrated graphics, which share system memory.

Do not assume that total RAM capacity is the only memory specification that matters.

Storage Capacity Affects SSD Performance

Some SSDs perform differently at different capacities.

Larger versions may have:

  • More NAND channels
  • More parallelism
  • Larger cache
  • Different controller behaviour

A 2 TB model and 500 GB model from the same product family may not deliver identical results.

Compare against the same capacity where possible.

Free Space Matters

An SSD that is almost full may perform worse because it has less room for:

  • Cache
  • Wear levelling
  • Background cleanup
  • Temporary files
  • Windows updates

Keep a reasonable amount of free space before testing.

Do not delete important data merely to improve a benchmark number.

Benchmarking Before and After an Upgrade

For a useful comparison:

  1. Record the original hardware and settings
  2. Run the same tests three times
  3. Save the results
  4. Install one upgrade
  5. Confirm drivers and firmware
  6. Repeat the same tests
  7. Compare percentage change
  8. Test real applications as well

Changing memory, SSD, graphics driver, BIOS, and Windows settings together makes it impossible to know which change produced the difference.

Benchmarking Before Buying a Replacement PC

Benchmark the existing computer using tasks relevant to the user.

For example:

  • CPU rendering test for creative work
  • Game benchmark for gaming
  • Storage test for large file workflows
  • Real Excel or application timing for office work
  • Video export time for editing
  • Software build time for development

A replacement may score twice as high in a synthetic test but deliver only a modest improvement in the application that matters.

Real-World Tests Matter Most

Useful real-world measurements include:

  • Time to export a video
  • Time to compile a project
  • Time to open a large spreadsheet
  • Time to generate a report
  • Time to copy a known data set
  • Frame rate in the intended game
  • Time to render an actual scene
  • Battery life during normal work

Synthetic benchmarks make comparison easier.

Real workflows show whether the improvement changes your day-to-day experience.

Use both.

Avoid Downloading Benchmark Tools From Random Websites

Benchmark utilities are popular enough that fake or modified installers exist.

Download tools from:

  • The developer’s official website
  • An official app store
  • A company-approved software portal

Maxon, UL, CrystalMark and OCCT all provide official download or product pages for their tools. 

Avoid websites that:

  • Bundle extra software
  • Demand unrelated browser extensions
  • Offer “cracked” versions
  • Require disabling security
  • Present several misleading download buttons

Do Not Benchmark a Visibly Failing Computer Aggressively

Avoid heavy testing when the computer shows:

  • Clicking or grinding drive
  • Burning smell
  • Swollen battery
  • Fan failure
  • Repeated sudden shutdowns
  • Liquid damage
  • Power-supply instability
  • Severe graphical corruption
  • Important data with no backup

Benchmarking adds load.

Protect the data and diagnose the physical fault first.

A Simple Free Benchmarking Toolkit

For many Windows users, a useful basic toolkit is:

  • Cinebench for processor and rendering performance
  • 3DMark for graphics and gaming-oriented comparison
  • CrystalDiskMark for storage speed
  • OCCT for monitoring, sustained load and stability testing
  • Built-in game benchmarks for actual gaming performance
  • Task Manager for identifying background activity

You do not need to install dozens of utilities.

Use the smallest set that answers the question.

A Practical Benchmarking Routine

A balanced test process could be:

  1. Restart the computer
  2. Record the specifications and power mode
  3. Check idle temperatures and background usage
  4. Run a CPU benchmark three times
  5. Run an appropriate graphics benchmark
  6. Test storage once using sensible settings
  7. Monitor temperatures and clock speeds
  8. Run a short stability test when required
  9. Record all results
  10. Compare with the same hardware and benchmark version
  11. Test one real application or game
  12. Investigate repeatable gaps greater than normal variation

Do not run every stress test simultaneously.

How to Record the Results

Create a simple table containing:

Item

Result

Date

Test date

Computer

Model or build

CPU

Exact processor

GPU

Exact graphics adapter

RAM

Capacity, speed and configuration

Storage

Drive model and capacity

BIOS

Version

Graphics driver

Version

Power mode

Balanced or Performance

Benchmark

Tool, version and preset

Score

Result

Maximum temperature

CPU or GPU

Notes

Throttling, errors or unusual behaviour

This turns benchmarking into useful evidence rather than a collection of screenshots.

When a Low Score Needs Investigation

Investigate further when:

  • The result is repeatedly far below similar systems
  • Performance declines significantly during repeated runs
  • Temperatures are excessive
  • The benchmark reports errors
  • The computer crashes
  • The expected dedicated GPU is not being used
  • Storage is negotiating through the wrong interface
  • The laptop does not recognise its charger
  • CPU or GPU clocks remain unusually low
  • A recent driver or firmware change caused a clear regression

Start with settings, cooling, power, drivers, and background activity before assuming hardware failure.

When a High Score Does Not Mean the PC Is Healthy

A computer may produce a strong short benchmark score while still suffering from:

  • Intermittent crashes
  • Memory errors
  • Failing storage
  • Poor sustained cooling
  • Power-supply instability
  • Driver faults
  • Overclocking errors

Performance and reliability are separate questions.

A stable PC with a slightly lower score is usually more valuable than a faster system that crashes under real workloads.

When to Contact an IT Professional

Professional assistance is recommended when:

  • Scores remain far below comparable hardware
  • The system overheats or shuts down
  • Storage performance is unexpectedly poor
  • Memory or hardware errors appear
  • Benchmarking causes crashes
  • Business computers need standardised testing
  • An upgrade needs to be justified
  • Performance fell after a BIOS or driver update
  • Power and cooling limits need investigation
  • A computer must be assessed without risking business data

An IT technician can test under controlled conditions, check temperatures and clock speeds, verify drivers and firmware, identify bottlenecks, and explain whether an upgrade, repair, or replacement offers worthwhile value.

Benchmark the Workload, Not Just the Specification

Benchmarking is most useful when it answers a practical question.

A single score cannot describe the entire computer. CPU, GPU, memory, storage, cooling, power limits, and software all affect different workloads.

Use the correct test, repeat it under consistent conditions, and compare like with like. Then confirm the result with the applications or games you actually use.

Hamilton Group can assess slow computers, identify performance bottlenecks, test upgrades, investigate thermal and stability problems, and help businesses decide whether equipment should be optimised, upgraded, or replaced.

Call 0330 043 0069 or visit hgmssp.com to book a meeting with one of our IT experts.