#Requires -Version 5.1
<#
    JbTecWiz Support Centre -- generated fix script

    Fault : STOP 0x00000139 -- KERNEL_SECURITY_CHECK_FAILURE
    Fix   : Rule out memory, then catch the driver
    Source: https://jbtecwiz.com/support/win-0x139

    Run as     : Elevated PowerShell and WinDbg
    Expect     : 1-2 days
    Risk       : medium
    Reversible : yes

    WHEN THIS IS THE RIGHT FIX
    Repeated 0x139 bugchecks. Do the cheap test first -- memory faults
    produce this readily and cost nothing to exclude.

    HOW TO UNDO IT
    Boot Safe Mode and run verifier /reset. If Safe Mode will not start
    either, run it from WinRE Command Prompt, or use System Restore.

    This script walks the fix one step at a time and asks before each
    one. Steps with no command are things you do yourself -- it prints
    those and waits. Run with -DryRun to print without executing.

    --------------------------------------------------------------------
    NO WARRANTY - USE AT YOUR OWN RISK

    This script is provided by JbTecWiz as-is and with no warranty of any
    kind, express or implied. You run it entirely at your own risk.

    JbTecWiz accepts no liability for any loss or damage arising from its
    use, including but not limited to data loss, downtime, or configuration
    changes that turn out to be wrong for your system.

    You are responsible for reading this script before running it, for
    satisfying yourself that it suits the machine in front of you, and for
    having a working backup first. Some steps cannot be undone.
    --------------------------------------------------------------------
#>

[CmdletBinding()]
param(
    # Print every step and command without running anything.
    [switch]$DryRun,
    # Do not ask before each step. Read the script first if you use this.
    [switch]$Unattended
)

$ErrorActionPreference = 'Stop'
$script:Failed = 0

function Write-Rule { param([string]$Text)
    Write-Host ''
    Write-Host ('-' * 70) -ForegroundColor DarkGray
    if ($Text) { Write-Host $Text -ForegroundColor Cyan }
}

function Show-Prose { param([string]$Text, [string]$Colour = "Gray")
    if (-not $Text) { return }
    $words = $Text -split "\s+"; $line = "  "
    foreach ($w in $words) {
        if (($line.Length + $w.Length) -gt 74) { Write-Host $line -ForegroundColor $Colour; $line = "  " }
        $line += "$w "
    }
    if ($line.Trim()) { Write-Host $line -ForegroundColor $Colour }
}

function Invoke-Step {
    param(
        [int]$Number, [string]$Do, [string]$Why,
        [scriptblock]$Command, [switch]$Manual, [string]$Shell = "powershell"
    )
    Write-Rule "  Step $Number of 6"
    Show-Prose $Do "White"
    if ($Why) { Write-Host ""; Show-Prose $Why "DarkGray" }

    if ($Manual) {
        Write-Host ''
        Write-Host '  -> Do this yourself, then press Enter to carry on.' -ForegroundColor Yellow
        if (-not $Unattended -and -not $DryRun) { [void](Read-Host) }
        return
    }

    Write-Host ''
    foreach ($l in ($Command.ToString().Trim() -split "`n")) {
        Write-Host ("    " + $l.Trim()) -ForegroundColor Green
    }
    Write-Host ''

    if ($DryRun) { Write-Host "  (dry run -- not executed)" -ForegroundColor DarkGray; return }
    if (-not $Unattended) {
        $a = Read-Host "  Run this step? [Y]es / [S]kip / [Q]uit"
        if ($a -match "^[Qq]") { Write-Host "  Stopped at your request."; exit 0 }
        if ($a -match "^[Ss]") { Write-Host "  Skipped." -ForegroundColor DarkGray; return }
    }
    try { & $Command }
    catch {
        $script:Failed++
        Write-Host ("  Step $Number failed: " + $_.Exception.Message) -ForegroundColor Red
        Show-Prose "The rest of the fix may depend on this. Read the write-up before carrying on." "Red"
        if (-not $Unattended) {
            $c = Read-Host "  Carry on anyway? [y/N]"
            if ($c -notmatch "^[Yy]") { exit 1 }
        }
    }
}

Write-Rule
Write-Host '  STOP 0x00000139 -- KERNEL_SECURITY_CHECK_FAILURE' -ForegroundColor White
Write-Host '  Rule out memory, then catch the driver' -ForegroundColor Cyan
Write-Host ''
Write-Host '  Risk: medium   Reversible   1-2 days'
Write-Host ''
Show-Prose 'No warranty. Use at your own risk - JbTecWiz accepts no liability. Read it before you run it, and have a backup.' 'DarkYellow'
Write-Rule

if (-not $Unattended -and -not $DryRun) {
    $go = Read-Host '  Ready? [y/N]'
    if ($go -notmatch "^[Yy]") { Write-Host "  Nothing was changed."; exit 0 }
}

Invoke-Step -Number 1 -Do 'Disable any memory overclock profile (XMP, DOCP, EXPO) and run at stock for a day.' -Why 'A factory overclock that is marginally unstable produces corrupted structures, which is exactly what this check is designed to catch.' -Manual

Invoke-Step -Number 2 -Do 'Run MemTest86 for four full passes from USB.' -Manual

Invoke-Step -Number 3 -Do 'If memory is clean, open the dump and read the analysis.' -Command {
    cmd.exe /c '!analyze -v'
}

Invoke-Step -Number 4 -Do 'Check parameter 1. For 3 (corrupt LIST_ENTRY), dump the call stack to see whose list it was.' -Command {
    cmd.exe /c '!analyze -v; kb'
}

Invoke-Step -Number 5 -Do 'Enable Driver Verifier against third-party drivers only, and be ready for the machine to bugcheck on purpose.' -Why 'Read the rollback step before running this -- Verifier can leave a machine unbootable and the way out is Safe Mode or WinRE.' -Command {
    cmd.exe /c 'verifier /standard /driver.exclude ntoskrnl.exe'
}

Invoke-Step -Number 6 -Do 'Use the machine until it crashes, analyse the new dump, then turn Verifier off.' -Command {
    cmd.exe /c 'verifier /reset'
}

Write-Rule "  Confirm it worked"
Show-Prose 'A named driver is updated or removed and the bugchecks stop.' 'White'

Write-Rule
if ($script:Failed -gt 0) {
    Write-Host ("  Finished with " + $script:Failed + " failed step(s).") -ForegroundColor Yellow
    Show-Prose 'Read the full write-up at https://jbtecwiz.com/support/win-0x139' 'Yellow'
} else {
    Write-Host '  Finished.' -ForegroundColor Green
}
Write-Host ''
Show-Prose 'To undo: Boot Safe Mode and run verifier /reset. If Safe Mode will not start either, run it from WinRE Command Prompt, or use System Restore.' 'DarkGray'
Write-Rule