REFERENCE_BY_POINTER is a Windows Blue Screen of Death (BSOD) stop error associated with bug check 0x00000018.

The error indicates that Windows detected an inconsistency involving the reference count of a kernel object. In simplified terms, Windows and kernel-mode drivers use reference counting to keep track of objects that are currently being used. When a component incorrectly increments or decrements one of these reference counts, Windows may determine that continuing operation could corrupt memory or destabilize the operating system.

Windows therefore deliberately stops the system and displays a BSOD.

The error may appear as:

Stop code: REFERENCE_BY_POINTER

or during dump analysis as:

REFERENCE_BY_POINTER (18)

The problem is commonly related to a faulty kernel-mode driver, although damaged system files, security software, hardware instability, or memory corruption can sometimes contribute.

Understanding Bug Check 0x18

The REFERENCE_BY_POINTER bug check has the hexadecimal value:

0x00000018

Windows kernel objects maintain reference counts that indicate how many components currently hold references to them.

For example, when a driver obtains a reference to an object, the reference count may be increased. When the driver finishes using that object, the reference should be released.

A simplified example is:

Reference obtained → Reference count increases

Object used → Reference remains valid

Object released → Reference count decreases

When the count reaches the appropriate state, Windows can safely remove the object.

Problems occur when a driver performs operations such as:

• Dereferencing an object too many times
• Failing to dereference an object
• Incorrectly manipulating object handles
• Releasing an object that it does not properly own
• Using an invalid or stale object reference
• Corrupting memory containing object-management information

Because these operations occur in kernel mode, Windows normally cannot safely recover from the error.

Common Symptoms of REFERENCE_BY_POINTER

A computer affected by this error may experience:

• Sudden blue-screen crashes
• Automatic restart without warning
• REFERENCE_BY_POINTER displayed during startup
• Crashes while shutting down or restarting
• BSOD after installing a driver
• BSOD after installing Windows updates
• Crashes when connecting USB or other hardware
• BSOD when enabling Wi-Fi or Bluetooth
• Crashes while using VPN software
• Crashes when antivirus software is running
• BSOD during gaming or graphics-intensive operations
• Random crashes when the computer is idle
• Repeated crashes after waking from Sleep or Hibernate

The timing of the crash can provide an important clue about the responsible driver.

Most Common Causes

1. Faulty Device Drivers

Driver problems are among the most important causes of REFERENCE_BY_POINTER.

Possible problematic drivers include:

• Graphics drivers
• Network adapters
• Wi-Fi drivers
• Bluetooth drivers
• Storage controllers
• USB controllers
• Audio drivers
• Chipset drivers
• Printer drivers
• VPN drivers
• Antivirus filter drivers
• Backup software drivers
• Virtualization drivers

A recently installed or updated driver should therefore be one of the first areas investigated.

2. Incompatible Drivers

A driver does not necessarily need to be corrupted to cause a BSOD.

An older driver may work correctly on one Windows build but become unstable after a major Windows update.

This is particularly relevant to:

• Old printer software
• Legacy hardware utilities
• VPN clients
• Endpoint security software
• Disk encryption utilities
• Hardware monitoring programs
• Virtualization software
• Backup applications

3. Incorrect Driver Reference Counting

REFERENCE_BY_POINTER is closely associated with kernel object reference management.

Kernel-mode components frequently work with Windows objects and must correctly manage references to those objects.

A programming error inside a driver can create a mismatch such as:

Expected reference count: 1

Actual reference count: 0

or:

Expected reference count: 1

Actual reference count: 2

Windows may detect the inconsistency and issue bug check 0x18.

This is why identifying the responsible .sys driver from a crash dump can be much more useful than repeatedly reinstalling Windows.

4. Corrupted Windows System Files

Damage to Windows components may also contribute to instability.

Possible causes include:

• Interrupted Windows updates
• Unexpected shutdown
• Storage errors
• Malware
• Failed software installations
• File-system corruption

Windows includes built-in tools such as SFC and DISM that can repair many system-component problems.

5. Antivirus or Endpoint Security Software

Modern security applications install kernel-level components for functions such as:

• File-system monitoring
• Network inspection
• Web filtering
• Ransomware protection
• Device control
• Application monitoring

A defective or incompatible filter driver can potentially cause kernel crashes.

If REFERENCE_BY_POINTER started immediately after installing or upgrading security software, the security application should be investigated.

Do not permanently leave a production computer without appropriate security protection merely as a troubleshooting shortcut.

6. VPN and Network Filter Drivers

VPN software frequently installs virtual network adapters and filtering components.

Examples of relevant software categories include:

• Corporate VPN clients
• Remote-access software
• Network monitoring utilities
• Firewalls
• Packet capture utilities
• Endpoint network security

If the BSOD occurs primarily when connecting or disconnecting a VPN, update or temporarily remove the VPN software as part of controlled troubleshooting.

7. Virtualization Software

Virtualization applications can install low-level drivers for:

• Virtual networking
• Virtual storage
• Hypervisor integration
• USB redirection
• Network bridging

An incompatible virtualization driver may contribute to kernel crashes.

If the problem began after installing or upgrading virtualization software, update the software to a Windows-compatible release.

8. RAM or Memory Corruption

REFERENCE_BY_POINTER usually points toward software or driver behavior, but physical memory problems should not be ignored when crashes are random or multiple unrelated bug-check codes occur.

Possible causes include:

• Defective RAM
• Unstable memory timings
• Overclocking
• XMP/EXPO instability
• Motherboard problems
• CPU memory-controller instability

9. BIOS or Firmware Problems

Outdated BIOS/UEFI firmware can sometimes cause stability problems, especially after:

• CPU upgrades
• RAM upgrades
• Major Windows updates
• Storage upgrades
• Hardware changes

Firmware updates may contain compatibility and stability fixes.

10. Overclocking and System Instability

Temporarily disable:

• CPU overclocking
• GPU overclocking
• RAM overclocking
• Aggressive undervolting
• Non-default memory timings

If XMP or EXPO is enabled, temporarily testing at standard memory settings can help determine whether memory instability is contributing to crashes.

Step-by-Step Solutions for REFERENCE_BY_POINTER

Solution 1: Identify What Changed Before the BSOD Started

Before making major changes, determine when the problem began.

Ask:

• Was a driver recently installed?
• Was Windows recently updated?
• Was new hardware connected?
• Was antivirus software upgraded?
• Was VPN software installed?
• Was BIOS updated?
• Was RAM added?
• Was virtualization software installed?
• Did a graphics driver update occur?

If the BSOD started immediately after one specific change, investigate that change first.

This approach is generally faster than performing random repairs.

Solution 2: Update Windows

Install currently applicable Windows quality and security updates.

Open:

Settings → Windows Update

Select:

Check for updates

Install relevant updates and restart the computer.

Also review:

Settings → Windows Update → Advanced options → Optional updates

Driver updates may sometimes appear there.

However, on business-critical systems, evaluate driver and firmware updates carefully instead of installing every optional driver indiscriminately.

Solution 3: Update Device Drivers

Open Device Manager:

Press:

Windows + X

Select:

Device Manager

Pay particular attention to:

• Display adapters
• Network adapters
• Bluetooth
• Storage controllers
• Sound controllers
• USB controllers
• System devices

For important hardware, drivers obtained from the computer or hardware manufacturer's support channel are often preferable to random third-party driver-download websites.

Avoid automated "driver updater" utilities of uncertain origin.

Solution 4: Roll Back a Recently Updated Driver

If the BSOD began immediately after a driver update:

Open:

Device Manager

Right-click the affected device.

Select:

Properties → Driver → Roll Back Driver

Restart Windows.

This is especially useful for graphics, Wi-Fi, Bluetooth, chipset and storage drivers.

Solution 5: Reinstall the Suspected Driver

A driver installation can become corrupted even when the installed version is appropriate.

Open:

Device Manager

Right-click the device.

Choose:

Uninstall device

Restart the computer and install a known-good driver from the hardware or system manufacturer where appropriate.

For complex devices such as GPUs, VPN clients, endpoint-security products, or storage software, follow the vendor's recommended clean-installation procedure.

Solution 6: Repair Windows System Files with SFC

Open Command Prompt or Windows Terminal as Administrator.

Run:

sfc /scannow

Windows will scan protected system files and attempt to repair detected corruption.

Possible results include:

Windows Resource Protection did not find any integrity violations

or:

Windows Resource Protection found corrupt files and successfully repaired them

Restart the computer after repairs.

Solution 7: Repair Windows Component Store with DISM

If SFC reports problems or the system remains unstable, run:

DISM /Online /Cleanup-Image /ScanHealth

Then:

DISM /Online /Cleanup-Image /RestoreHealth

After DISM finishes, run:

sfc /scannow

again.

Restart Windows.

Solution 8: Check the File System and Storage

Storage corruption can indirectly contribute to system instability.

Open an elevated Command Prompt and run:

chkdsk C: /scan

For a deeper repair when justified, you may use:

chkdsk C: /f

Windows may request that the repair be scheduled for the next restart if the volume is in use.

If storage-related warnings, SMART problems, bad sectors, or I/O errors are present, back up important data promptly and investigate the SSD/HDD itself.

Solution 9: Test the RAM

Press:

Windows + R

Enter:

mdsched.exe

Choose:

Restart now and check for problems

Windows Memory Diagnostic will test the memory.

For intermittent or difficult memory problems, an extended bootable memory-testing utility may provide a more thorough test.

If memory errors are detected:

• Test RAM modules individually
• Reseat RAM
• Disable memory overclocking
• Restore standard timings
• Test different memory slots
• Verify module compatibility
• Replace defective memory

Solution 10: Use Reliability Monitor

Reliability Monitor provides a useful timeline of application failures, Windows failures and hardware errors.

Press:

Windows + R

Enter:

perfmon /rel

Look for critical events around the time REFERENCE_BY_POINTER occurred.

Check whether the crashes correlate with:

• Driver installations
• Application installations
• Windows updates
• Hardware failures
• Security software changes

Solution 11: Examine Event Viewer

Press:

Windows + X → Event Viewer

Navigate to:

Windows Logs → System

Look around the exact time of the crash.

Potentially useful events include:

• BugCheck
• Kernel-Power
• Disk
• Ntfs
• WHEA-Logger
• Driver-related warnings

Remember that Kernel-Power Event ID 41 often means Windows detected that the previous shutdown was unexpected. It does not, by itself, identify the root cause.

Solution 12: Boot Windows in Safe Mode

Safe Mode loads Windows with a reduced driver and service set.

If the computer remains stable in Safe Mode but crashes during normal operation, a third-party driver, service or startup component becomes more suspicious.

To access recovery options, use:

Settings → System → Recovery → Advanced startup

Then:

Troubleshoot → Advanced options → Startup Settings → Restart

Choose Safe Mode.

Solution 13: Perform a Clean Boot

A clean boot helps isolate third-party services and startup software.

Press:

Windows + R

Type:

msconfig

Open the Services tab.

Select:

Hide all Microsoft services

Then disable nonessential third-party services for testing.

Also open Task Manager and review startup applications.

Restart the computer.

If the BSOD disappears, re-enable items methodically until the problematic software is identified.

Do not indiscriminately disable essential security, backup, management, encryption, or business-critical services on production machines without understanding their purpose.

Solution 14: Check for Third-Party Kernel Software

Pay special attention to recently installed software that interacts deeply with Windows.

Examples include:

• Antivirus
• Endpoint protection
• VPN software
• Disk encryption
• Backup software
• Virtualization software
• Hardware monitoring
• RGB/control utilities
• Printer suites
• Network monitoring
• Remote-control software

Update the suspected application first.

If necessary, temporarily uninstall it and test system stability.

Simply closing an application may not be sufficient because its kernel driver can remain loaded.

Solution 15: Analyze Windows Minidump Files

When Windows crashes, it may create dump files in:

C:\Windows\Minidump

A full or kernel dump may also be stored as:

C:\Windows\MEMORY.DMP

Crash dumps are extremely useful when REFERENCE_BY_POINTER repeatedly occurs.

They may reveal:

• Suspected driver
• Faulting module
• Call stack
• Process active during the crash
• Bug-check parameters
• Kernel object involved
• Related drivers

Using WinDbg to Analyze REFERENCE_BY_POINTER

Microsoft's Windows debugger can be used for advanced BSOD investigation.

Open the dump file in WinDbg and run:

!analyze -v

Review fields such as:

BUGCHECK_CODE
MODULE_NAME
IMAGE_NAME
FAILURE_BUCKET_ID
PROCESS_NAME
STACK_TEXT

If the output repeatedly identifies the same third-party .sys driver across multiple crashes, that driver becomes a strong troubleshooting lead.

However, the module named in a crash dump is not automatically guilty. Memory corruption may cause Windows to crash later inside an otherwise legitimate component.

Therefore, examine the call stack and compare several dump files when possible.

Understanding the REFERENCE_BY_POINTER Bug-Check Parameters

Bug check 0x18 provides parameters that can assist kernel debugging.

Depending on the Windows version and debugging context, these values can provide information concerning the object and its reference state.

Advanced troubleshooting should rely on the debugger's interpretation of the actual dump rather than attempting to diagnose the crash solely from the BSOD screen.

Use:

!analyze -v

as the starting point.

Additional debugger commands may be useful depending on the object and stack involved.

Solution 16: Use Driver Verifier Carefully

Driver Verifier is a Windows debugging tool designed to stress drivers and expose incorrect behavior.

Run:

verifier

However, Driver Verifier should be used carefully.

It can intentionally trigger additional BSODs when it detects driver violations.

It is best suited to:

• Advanced users
• IT professionals
• Test systems
• Systems with working recovery access

Do not casually enable every verification option against every driver on a production computer.

Before enabling Driver Verifier, ensure that:

• Important data is backed up
• You know how to enter Safe Mode or Windows Recovery Environment
• You know how to disable Verifier

To reset Driver Verifier, use an elevated Command Prompt:

verifier /reset

Then restart Windows.

If Windows cannot boot normally, use Safe Mode or Windows Recovery Environment to disable it.

Solution 17: Uninstall a Problematic Windows Update

If REFERENCE_BY_POINTER started immediately after a Windows update, review:

Settings → Windows Update → Update history

Determine whether the crash timing corresponds with a recently installed update.

If strong evidence points to a specific update, uninstalling it temporarily may help isolate the issue.

Before doing this on managed or business computers, consider the security implications of removing updates.

Solution 18: Update BIOS/UEFI and Firmware

Check the computer or motherboard manufacturer's support resources for:

• BIOS/UEFI
• Chipset
• Intel/AMD platform drivers
• SSD firmware
• Thunderbolt firmware
• Docking-station firmware

Do not interrupt BIOS updates.

For laptops, keep AC power connected and ensure sufficient battery charge.

Only install firmware intended for the exact device or motherboard model.

Solution 19: Restore BIOS Defaults

If the computer is overclocked or has aggressive performance settings, load BIOS defaults for troubleshooting.

Temporarily disable:

• CPU overclocking
• GPU overclocking
• RAM overclocking
• XMP/EXPO
• Custom voltage settings

Test Windows stability again.

If the BSOD disappears, restore performance settings one at a time to identify the unstable configuration.

Solution 20: Use System Restore

If the problem began recently and an appropriate restore point exists:

Press:

Windows + R

Enter:

rstrui.exe

Choose a restore point created before the BSOD started.

System Restore can reverse certain:

• Driver changes
• Registry changes
• System configuration changes
• Application installations

Personal documents are generally not the target of System Restore, but important data should still be backed up before major recovery operations.

Solution 21: Perform an In-Place Windows Repair

If drivers appear correct but Windows components remain damaged, an in-place repair installation can reinstall Windows system components while preserving supported applications and user data.

Before proceeding:

• Create a backup
• Verify sufficient free disk space
• Record important application settings
• Ensure recovery keys are available where encryption is used
• Use Windows installation media matching the appropriate edition and architecture

An in-place repair should generally be considered before a destructive clean installation when the existing Windows installation remains bootable.

Solution 22: Reset or Clean Install Windows as a Last Resort

If extensive troubleshooting fails, Windows can be reset or clean-installed.

However, a clean installation should not be the first response to REFERENCE_BY_POINTER.

If defective RAM, unstable firmware, or a faulty third-party driver is responsible, reinstalling Windows without correcting the root cause may not permanently solve the problem.

Back up important data before performing any reset or clean installation.

Recommended Troubleshooting Order

For most computers, use the following order:

1. Determine what changed immediately before the first BSOD.
2. Review Reliability Monitor.
3. Check Windows Update history.
4. Update or roll back suspected drivers.
5. Install appropriate chipset and hardware drivers.
6. Run SFC.
7. Run DISM.
8. Check storage health and file-system errors.
9. Test RAM.
10. Review minidump files.
11. Investigate third-party security, VPN and virtualization drivers.
12. Perform a clean boot.
13. Check BIOS and firmware.
14. Disable overclocking/XMP temporarily.
15. Use Driver Verifier only when advanced driver diagnosis is necessary.
16. Consider System Restore.
17. Consider an in-place Windows repair.
18. Reset or clean-install Windows only when justified.

This order minimizes unnecessary destructive troubleshooting.

Troubleshooting REFERENCE_BY_POINTER on Business Computers

Business computers require additional caution.

Before removing software, determine whether the machine uses:

• Endpoint protection
• Disk encryption
• VPN
• Backup agents
• Remote-management software
• Domain policies
• Microsoft Entra ID management
• RMM tools
• Accounting applications
• Database software

Do not remove enterprise security or management software without understanding the consequences.

For repeated BSODs across several computers, compare:

• Computer model
• Windows build
• Driver versions
• Recently deployed updates
• Security-agent versions
• VPN versions
• Common applications

If several computers started experiencing REFERENCE_BY_POINTER immediately after the same software or driver deployment, a common driver should become a primary suspect.

How to Collect Useful Information Before Troubleshooting

Record the following:

Stop code:
REFERENCE_BY_POINTER

Bug check:
0x00000018

Windows version:
Run:

winver

System information:
Run:

msinfo32

Recent reliability history:
Run:

perfmon /rel

Dump location:

C:\Windows\Minidump

Also record:

• Computer make/model
• BIOS version
• CPU
• RAM
• GPU
• Storage model
• Antivirus/endpoint software
• VPN software
• Recent hardware changes
• Recent driver changes
• Date/time of each BSOD

This information makes advanced diagnosis significantly easier.

Important Warning About Random Online Fixes

Avoid troubleshooting methods that recommend:

• Downloading random DLL files
• Downloading unknown .sys drivers
• Installing generic driver-updater programs
• Running registry-cleaner software
• Deleting Windows system files
• Disabling security permanently
• Modifying random registry entries without understanding them
• Flashing BIOS from unofficial sources

These actions can create additional problems and may make the computer less secure or unbootable.

Frequently Asked Questions (FAQ)

1. What does REFERENCE_BY_POINTER mean?

REFERENCE_BY_POINTER is a Windows BSOD indicating that Windows detected an inconsistency involving references to a kernel object.

2. What is the bug-check code for REFERENCE_BY_POINTER?

The bug check is:

0x00000018

It may also be displayed as:

REFERENCE_BY_POINTER (18)

during crash-dump analysis.

3. Is REFERENCE_BY_POINTER usually caused by hardware?

Not necessarily.

A faulty or incompatible kernel-mode driver is an important suspect. However, RAM instability, firmware problems and memory corruption can also contribute.

4. Can a graphics driver cause REFERENCE_BY_POINTER?

Yes.

Graphics drivers operate at low levels of Windows and can cause BSODs if they contain bugs, become corrupted, or are incompatible with the current Windows environment.

5. Can Wi-Fi or network drivers cause this BSOD?

Yes.

Network, Wi-Fi, Bluetooth, VPN and network-filter drivers should be investigated, particularly if crashes occur during network activity.

6. Can antivirus software cause REFERENCE_BY_POINTER?

Potentially.

Security products frequently install kernel-level filter drivers. A defective or incompatible component can contribute to BSODs.

Update the product first and consult the vendor's support information when a specific driver is implicated.

7. Will SFC fix REFERENCE_BY_POINTER?

SFC can repair corrupted protected Windows system files, so it is useful when system-file corruption contributes to the problem.

It will not repair a programming bug inside a third-party driver.

8. What command should I use to repair Windows files?

Start with:

sfc /scannow

If necessary, use:

DISM /Online /Cleanup-Image /RestoreHealth

and then run SFC again.

9. Where are Windows BSOD dump files stored?

Small memory dumps are commonly stored in:

C:\Windows\Minidump

A larger dump may be stored at:

C:\Windows\MEMORY.DMP

depending on Windows crash-dump configuration.

10. How can I determine which driver caused the BSOD?

Analyze the crash dump with a debugger such as WinDbg.

Start with:

!analyze -v

Then review the module, image name, failure bucket and call stack.

Comparing several dumps is preferable to assuming the first named driver is definitely responsible.

11. Should I use Driver Verifier?

Only when necessary and with appropriate recovery preparation.

Driver Verifier intentionally stresses drivers and can cause additional BSODs when defective behavior is detected.

12. How do I disable Driver Verifier?

Open an elevated Command Prompt and run:

verifier /reset

Restart Windows.

If Windows cannot boot normally, perform the reset through Safe Mode or the recovery environment.

13. Can faulty RAM cause REFERENCE_BY_POINTER?

Yes, indirectly.

Defective or unstable RAM can corrupt kernel memory and create apparently driver-related crashes.

This becomes more suspicious when the computer produces several different BSOD stop codes rather than one consistent error.

14. Should I reinstall Windows immediately?

No.

First investigate:

• Recent drivers
• Windows updates
• Third-party kernel software
• Crash dumps
• RAM
• Storage
• BIOS/firmware

Reinstallation should normally be a later troubleshooting step.

15. Why does REFERENCE_BY_POINTER occur randomly?

Kernel-driver problems may only occur under specific conditions such as:

• Sleep/wake transitions
• Device connection/disconnection
• Network activity
• High system load
• Driver unload
• Shutdown
• Security scanning

Therefore, the responsible bug may appear intermittent.

16. Why does the BSOD occur when shutting down?

Shutdown causes drivers and services to release resources and objects.

A driver that incorrectly manages object references may expose the problem while unloading or releasing resources during shutdown.

17. Why does the error occur after Sleep or Hibernate?

Sleep and resume require hardware drivers to transition between power states.

Graphics, Wi-Fi, Bluetooth, storage and chipset drivers are particularly relevant when crashes consistently occur during resume.

18. Can BIOS updates fix REFERENCE_BY_POINTER?

Sometimes, depending on the root cause.

BIOS updates can contain fixes for hardware initialization, power management, memory compatibility and platform stability.

They will not directly repair a defective third-party Windows driver.

19. Can overclocking cause this error?

Yes.

An unstable CPU, GPU or memory configuration can corrupt data in memory and produce BSODs that appear to implicate software.

Return the computer to standard settings during diagnosis.

20. What should I do if REFERENCE_BY_POINTER keeps returning?

Collect several minidump files and compare them.

If the same third-party driver repeatedly appears in the relevant crash stacks, update, roll back, reinstall, or remove the associated software/device as appropriate.

If crashes implicate different unrelated modules each time, investigate RAM, system instability, firmware and broader memory corruption.

Conclusion

REFERENCE_BY_POINTER (Bug Check 0x00000018) is a Windows kernel-level BSOD involving incorrect object reference management.

The most productive troubleshooting strategy is usually not to reinstall Windows immediately, but to identify what changed and determine which low-level component is involved.

Pay particular attention to:

• Recently changed drivers
• Graphics and network drivers
• VPN clients
• Antivirus and endpoint software
• Virtualization software
• Storage and chipset drivers
• Windows system-file corruption
• RAM instability
• BIOS/firmware
• Overclocking

For recurring crashes, Windows crash dumps provide some of the most valuable diagnostic evidence. Analyzing multiple minidumps with WinDbg can help distinguish a consistently defective driver from broader memory or hardware instability.

A systematic approach—identify the trigger → inspect crash evidence → repair/update the responsible component → test stability—is considerably safer and more effective than applying random BSOD fixes.

#tags

#REFERENCE_BY_POINTER #ReferenceByPointer #BSOD #BlueScreen #BlueScreenOfDeath #WindowsBSOD #Windows11 #Windows10 #WindowsError #WindowsFix #WindowsTroubleshooting #WindowsRepair #BugCheck18 #BugCheck0x18 #StopCode #WindowsStopCode #KernelError #KernelCrash #KernelDriver #DriverError #DriverFix #DriverUpdate #DriverTroubleshooting #WindowsDrivers #MemoryCorruption #WindowsMemory #RAMTest #WindowsDiagnostic #SystemFileChecker #SFC #DISM #DISMRepair #CHKDSK #WindowsRecovery #SafeMode #CleanBoot #DriverVerifier #WinDbg #Minidump #CrashDump #DumpAnalysis #WindowsDebugging #DeviceManager #SystemRestore #WindowsUpdate #BIOSUpdate #ComputerRepair #LaptopRepair #PCRepair #WindowsSupport