Common IssuesBSOD Recovery

BSOD Recovery

Getting blue screens after running the spoofer? Work through every section below in order. Most BSODs are caused by driver conflicts or Secure Boot interference and are fully recoverable.

If your PC is stuck in a boot loop, skip to Step 1 — Boot into Safe Mode first, then work through the rest from there.

Step 1 — Boot into Safe Mode

If the spoofer caused a BSOD and Windows won't boot normally, you need to enter Safe Mode first to undo the spoofer's driver changes.

1Restart your PC and hold F8 or Shift + F8 during boot. On newer systems you may need to force-shutdown 3 times to trigger the recovery menu.

2Select Troubleshoot → Advanced Options → Startup Settings → Restart.

3Press 4 or F4 to boot into Safe Mode (or 5 / F5 for Safe Mode with Networking).

4Once in Safe Mode, open File Explorer, navigate to your spoofer folder, and run the cleanup or restore tool included with the spoofer.

5Restart normally. If Windows boots cleanly, continue to Step 2 before using the spoofer again.

Step 2 — Disable Secure Boot & TPM in BIOS

Secure Boot and TPM can actively block driver injection and cause BSODs. Both must be disabled before running the spoofer.

1Restart and enter your BIOS — usually Del, F2, or F10 at the manufacturer splash screen.

2Find Secure Boot (usually under Security or Boot tab) and set it to Disabled.

3Find TPM / PTT / fTPM and disable it as well.

4Find Fast Startup or Fast Boot and disable it.

5Save and exit (F10 on most boards), then boot normally and try spoofing again.

Note: BIOS menus vary by manufacturer (ASUS, MSI, Gigabyte, etc.). If you cannot find Secure Boot, search for your motherboard model + "disable secure boot".

Step 3 — Update GPU & Chipset Drivers

Outdated or conflicting GPU drivers are the #1 cause of spoofer-related BSODs. This must be done before retrying.

1Uninstall your current GPU driver using DDU (Display Driver Uninstaller) — run it in Safe Mode for a clean removal.

2Download the latest driver directly from NVIDIA.com or AMD.com (do not use Windows Update drivers).

3Also update your chipset drivers from your motherboard manufacturer's website.

4Completely uninstall any VPN client software — VPN drivers can interfere with the spoofer at the kernel level.

Step 4 — NVIDIA Drivers Already Up to Date? Roll Back

If your NVIDIA drivers are already on the latest version and you're still getting BSODs, the latest driver itself is likely the cause. NVIDIA occasionally releases updates that conflict with kernel-level software like the spoofer. Rolling back to a previous version often resolves this immediately.

Method 1Device Manager Quick RollbackEasiest

Only works if you did not fully uninstall the previous driver before updating. If the Roll Back button is greyed out, use Method 2.

1Right-click Start → Device Manager

2Expand Display Adapters → right-click your NVIDIA GPU → Properties

3Click the Driver tab → click Roll Back Driver

4Select a reason when prompted, confirm, and restart your PC

Method 2DDU + Manual Older Driver InstallIf Method 1 unavailable

Use this if the Roll Back Driver button was greyed out, or if you want to install a specific known-good version.

1Boot into Safe Mode (see Step 1 above)

2Run DDU (Display Driver Uninstaller) to fully clean-remove your current NVIDIA driver

3Visit nvidia.com/en-gb/drivers → Manual Driver Search → select your GPU model and Windows version

4In the results list, pick a Game Ready Driver that is 2–3 months older than the current release — these are more stable and widely tested

5Install normally (do not use Express install — choose Custom and uncheck GeForce Experience if unwanted), then restart

Which version to pick?Drivers from 2–3 months ago are typically the most stable for kernel-level software. Avoid the newest release and anything marked "Beta".

AMD users:Same approach applies. Use DDU to clean-remove, then download an older version from amd.com/en/support.

NVIDIA Official Driver Rollback Guide

nvidia.com/en-gb/drivers/driver-rollback/

Step 5 — Run System Repair Commands

Open Command Prompt as Administrator (Win + X → Terminal (Admin)) and run both commands. Wait for each to complete fully.

sfc /scannow

DISM /Online /Cleanup-Image /RestoreHealth

What these do:

sfc /scannowScans and repairs corrupted Windows system files.

DISM /RestoreHealthRepairs the Windows component store, fixing deeper corruption that SFC can't touch.

If BSODs persist after these commands: A clean Windows reinstall via USB (with full partition deletion) is the only reliable fix. System repair cannot resolve all kernel-level driver conflicts.

→ Windows Reinstall Guide

Step 6 — Locate the Crash Dump File (.dmp)

If you still get BSODs, capture the crash dump to send to support. This file tells us exactly what driver caused the crash.

1Open File Explorer (Win + E) and paste this path in the address bar:

2Look for .dmp files inside. If the folder is empty or missing, enable hidden files via View → Show → Hidden items.

3If the Minidump folder is still empty, open sysdm.cpl → Advanced → Startup and Recovery → set dump type to Small memory dump (256 KB), click OK, and trigger the crash again.

C:\Windows\Minidump

Step 7 — Submit a Support Ticket

Still crashing after completing steps 1–6? Open a ticket on our Discord. Attach your .dmp file and include the following:

Screenshot proof you completed steps 1–5

When exactly the crash occurs (during spoof load / on game launch / mid-game)

Your Windows version (Win + Pause or Settings → System → About)

Your GPU model and driver version

The .dmp file from C:\Windows\Minidump

Submit DMP via Discord

~10 min response