PUBG Crash Doctor read-only diagnostic

Verdict

What your logs & event viewer show

Fix the launch block first (anti-cheat)

This is not a hardware fault — PUBG Shield stopped the game from starting because something looked like it was hooking into it. Reinstalling rarely helps; removing the conflict does.

    Fix the file-integrity problem (BattlEye / corrupted data)

    Errors like “[25] BattlEye: Corrupted Data” mean a checksum failed — the files being verified weren’t what they should be. That’s not a crash and not a hardware fault by itself. Antivirus interference and interrupted downloads are the usual causes.

      Do this, in order

      Steps highlighted in gold are the ones your scan specifically points to. Work top-to-bottom and test after each.

        Show raw evidence
        
            

        A tiny, open-source tool that reads your PUBG logs, anti-cheat records and Windows crash events, then tells you the likely cause — and what to try, cheapest first. It changes nothing on your PC and uploads nothing.

        Why this exists
        That “Out of video memory” error is usually lying. On an 8 GB+ card at 1080p you aren’t actually out of VRAM — the real cause is normally an unstable RAM/XMP profile, a shaky overclock, a starved pagefile, a bad driver, or a tired PSU. This tool finds which.

        Run it in 3 steps (Windows)

        1. Download this repo (green Code ▾ → Download ZIP) and unzip it anywhere.
        2. Double-click Run-Diagnostic.bat  — or right-click diagnose.ps1 → Run with PowerShell.
        3. Your browser opens this page with your results: a verdict, the evidence, and an ordered fix list.

        Prefer the command line? powershell -ExecutionPolicy Bypass -File diagnose.ps1

        It tells the three kinds of PUBG failure apart

        💥 Instability
        “Out of video memory”, crash mid-game, freezes, PC powers off → RAM/XMP, overclock, pagefile, driver, PSU
        🛡️ Anti-cheat block
        “Interrupted by external program”, PUBG Shield, pubg_fail.log, [MHV] → overlays, RGB/macro suites, injectors, hypervisor
        🧩 File integrity
        “[25] BattlEye: Corrupted Data”, failed checksums → antivirus quarantine, interrupted download, damaged BattlEye install

        Getting this wrong wastes days — people replace RAM over an anti-cheat conflict, reinstall Windows over unstable memory, or reinstall the game ten times when their antivirus is eating BattlEye. The tool tells you which you have (or several at once).

        What it checks

        PUBG logs
        GPU-crash, “out of video memory”, render-thread hangs
        Anti-cheat
        pubg_fail.log code & diagnostic, injected modules, overlay apps, hypervisor
        File integrity
        BattlEye files & service, antivirus detections on game files, Steam install state
        Event Viewer
        Kernel-Power 41, WHEA hardware faults, driver TDRs
        Memory
        XMP/EXPO state & actual vs rated speed
        System
        Pagefile, GPU driver & date, VRAM, disk health

        This is a community troubleshooting aid, not official PUBG/KRAFTON software. It is read-only and open source — inspect diagnose.ps1 before running if you like. No warranty; hardware changes are at your own risk.

        Copied ✔