PFN_LIST_CORRUPT is a Windows Blue Screen of Death (BSOD) stop error associated with corruption of Windows' physical-memory management structures.

The official Microsoft bug check code is:

Bug Check: 0x0000004E
Stop Code: PFN_LIST_CORRUPT

Microsoft describes Bug Check 0x4E as indicating that the Page Frame Number (PFN) list has become corrupted.

A typical blue screen may display:

Your device ran into a problem and needs to restart.

Stop code: PFN_LIST_CORRUPT

The computer normally restarts after Windows creates crash-dump information.

Although the name appears to point directly toward defective RAM, PFN_LIST_CORRUPT does not automatically mean that the RAM is faulty. Drivers, memory corruption, DMA operations, unstable hardware, storage-related drivers, overclocking, or other kernel-level problems can corrupt PFN-related structures.

What Is PFN in Windows?

PFN stands for Page Frame Number.

Windows divides physical memory into fixed-size pages. Internally, the Windows Memory Manager maintains information describing physical memory pages and their current state.

Conceptually, Windows needs to know whether a physical page is:

• Available
• In use
• Modified
• Reserved
• Locked
• Referenced
• Assigned to a process or kernel component
• Available for reuse

The PFN database is therefore a critical component of Windows memory management.

If a kernel-mode component incorrectly manipulates memory, Windows may detect that the information describing physical pages is inconsistent.

Rather than continuing with potentially corrupted memory, Windows stops the operating system and generates:

PFN_LIST_CORRUPT

This protects the system from further corruption or possible data loss.

What Does Error 0x0000004E Mean?

The hexadecimal bug check code for PFN_LIST_CORRUPT is:

0x0000004E

Microsoft states that the first bug-check parameter identifies the particular type of PFN violation.

Some important Parameter 1 values include:

Parameter 1	General Meaning
0x01	PFN list head corruption
0x02	A PFN list entry was corrupted
0x06	Hardware/prototype PTE structures were corrupted
0x07	A driver unlocked a page more times than it locked it
0x8D	Page-free list corruption; hardware is a strong possibility
0x8F	Free or zeroed page list-head corruption
0x99	A PTE or PFN is corrupted
0x9A	Driver attempted to free a page still locked for I/O

Microsoft specifically notes that this bug check is commonly associated with a driver passing a bad Memory Descriptor List (MDL), such as incorrectly unlocking the same pages multiple times.

Therefore, the actual bug-check parameters in the crash dump can provide valuable clues about whether you should concentrate on drivers, memory, hardware, or I/O operations.

Common Symptoms of PFN_LIST_CORRUPT

You may experience one or more of the following:

• Random Blue Screen of Death
• PC suddenly restarting
• PFN_LIST_CORRUPT during startup
• BSOD while gaming
• BSOD during file transfers
• Crash while installing applications
• Crash after installing RAM
• Crash after changing XMP/EXPO settings
• Crash after installing a graphics driver
• Crash after a Windows update
• System freezing before the blue screen
• Applications crashing unexpectedly
• Windows becoming unstable after waking from sleep
• Multiple different BSOD stop codes appearing on the same computer

The last symptom is especially important.

If you receive different memory-related stop codes at different times, the possibility of unstable RAM, memory timings, motherboard problems, CPU memory-controller instability, or widespread driver memory corruption becomes more significant.

Major Causes of PFN_LIST_CORRUPT

1. Faulty or Unstable RAM

Memory problems are an important possibility.

Examples include:

• Defective RAM module
• Incorrect RAM timings
• Unstable XMP profile
• Unstable EXPO profile
• Mixed RAM modules
• Different memory capacities or specifications
• Poor DIMM contact
• Faulty motherboard RAM slot
• Excessive memory frequency
• Insufficient memory-controller stability

A computer can sometimes run apparently normally for hours before an intermittent RAM problem triggers a BSOD.

2. Faulty Kernel-Mode Drivers

Drivers operate with high privileges and can directly interact with memory.

A defective driver can damage structures that Windows later discovers are inconsistent.

Potential drivers include:

• Graphics drivers
• Storage/NVMe drivers
• RAID drivers
• Network drivers
• Wi-Fi drivers
• Bluetooth drivers
• USB drivers
• Chipset drivers
• VPN drivers
• Antivirus filter drivers
• Backup software drivers
• Virtualization drivers
• Hardware monitoring utilities
• RGB/control software
• Third-party system utilities

Microsoft specifically identifies incorrect memory-descriptor handling by drivers as a typical cause of Bug Check 0x4E.

3. Recently Installed Hardware

If the BSOD started after installing hardware, investigate the new component first.

Examples:

• RAM
• Graphics card
• NVMe SSD
• PCIe card
• Wi-Fi adapter
• USB device
• Capture card
• Storage controller

Temporarily removing the recently installed device can be a useful diagnostic test.

4. XMP, EXPO or Memory Overclocking

High-performance memory profiles can cause instability even when the RAM itself is not physically defective.

For troubleshooting, enter BIOS/UEFI and temporarily disable:

• XMP
• EXPO
• Manual RAM overclocking
• CPU overclocking
• Memory-controller overclocking
• Aggressive voltage/timing adjustments

Run the system using motherboard/CPU default settings.

If PFN_LIST_CORRUPT disappears, the problem may be memory-profile stability rather than damaged Windows files.

5. Corrupted Windows System Files

Damaged Windows system components can contribute to system instability.

Windows includes built-in tools such as:

• System File Checker (SFC)
• Deployment Image Servicing and Management (DISM)

These should be checked when the source of the BSOD is unknown.

6. Storage or File-System Problems

Storage problems can indirectly produce memory-related symptoms.

Possible causes include:

• SSD errors
• NVMe firmware problems
• File-system corruption
• Storage-controller driver problems
• RAID driver issues
• Unexpected shutdowns
• Corrupted pagefile data

Therefore, disk and storage health should also be checked during troubleshooting.

7. BIOS/UEFI or Chipset Problems

Outdated BIOS firmware or chipset drivers can sometimes contribute to memory-management instability, especially after:

• CPU upgrades
• RAM upgrades
• Installing high-speed memory
• Installing a new GPU
• Changing NVMe devices
• Major Windows upgrades

Obtain BIOS and chipset updates from the PC or motherboard manufacturer whenever possible.

8. Third-Party Security Software

Antivirus and endpoint-security products frequently install kernel-level components such as:

• File-system filters
• Network filters
• Behavioral monitoring drivers
• Anti-ransomware components

A defective or incompatible filter driver can potentially cause memory corruption.

If crashes began immediately after installing or updating security software, investigate that software carefully.

Do not permanently disable security protection merely as a general troubleshooting step.

Step-by-Step PFN_LIST_CORRUPT Troubleshooting

Step 1: Identify What Changed

Before running dozens of commands, determine whether anything changed shortly before the BSOD started.

Ask:

• Was RAM recently installed?
• Was the graphics driver updated?
• Was Windows updated?
• Was a new SSD installed?
• Was BIOS updated?
• Was XMP or EXPO enabled?
• Was antivirus software changed?
• Was a VPN installed?
• Was virtualization software installed?
• Was new hardware connected?

If PFN_LIST_CORRUPT started immediately afterward, investigate that change first.

Step 2: Install Windows Updates

Open:

Settings → Windows Update

Check for updates and install applicable stable updates.

Restart Windows afterward.

If the BSOD specifically started immediately after an update, however, troubleshooting may instead require investigating or rolling back the relevant driver/update.

Step 3: Update Critical Device Drivers

Concentrate on drivers that operate close to hardware.

Update:

1. Chipset driver
2. Graphics driver
3. Storage/NVMe driver
4. Network/Wi-Fi driver
5. Bluetooth driver
6. RAID/storage-controller driver where applicable
7. Laptop/system-specific drivers

Whenever possible, obtain drivers from:

• Computer manufacturer
• Motherboard manufacturer
• GPU manufacturer
• Device manufacturer

Avoid random third-party "driver updater" websites.

Step 4: Roll Back a Recently Updated Driver

Sometimes the newest driver is the problem.

Open:

Device Manager → Device → Properties → Driver

If available, select:

Roll Back Driver

This is particularly useful when the crashes started immediately after a GPU, storage, network, or chipset driver update.

Step 5: Run Windows Memory Diagnostic

Press:

Windows + R

Enter:

mdsched.exe

Select:

Restart now and check for problems

Windows will restart and test system memory.

If memory errors are detected, investigate:

• RAM modules
• RAM slots
• XMP/EXPO
• Memory timings
• Motherboard compatibility
• CPU memory controller

However, passing Windows Memory Diagnostic does not conclusively prove that RAM is healthy. Intermittent faults may require longer testing.

Step 6: Perform Extended RAM Testing

For persistent or unexplained PFN_LIST_CORRUPT crashes, use a dedicated bootable memory-testing utility and perform extended tests.

If errors appear, do not immediately assume every DIMM is defective.

Test modules individually.

For example, if the computer has:

RAM A + RAM B

Test:

RAM A only

Then:

RAM B only

You can also test a known-good module in different motherboard slots.

This helps distinguish among:

• Faulty RAM module
• Faulty DIMM slot
• Memory-profile instability
• Motherboard issue

Step 7: Disable XMP/EXPO Temporarily

Enter BIOS/UEFI and load default memory settings.

Disable:

Intel systems: XMP
AMD systems: EXPO, where applicable

Then use the computer normally.

If crashes stop, test memory settings carefully before re-enabling the performance profile.

Step 8: Run System File Checker

Open Command Prompt or Windows Terminal as Administrator.

Run:

SFC /scannow

Allow the scan to complete.

If corrupted protected system files are detected, SFC will attempt to repair them.

Restart Windows afterward.

Step 9: Repair the Windows Component Store with DISM

Open an elevated Command Prompt and run:

DISM /Online /Cleanup-Image /RestoreHealth

After DISM completes successfully, run:

SFC /scannow

again.

Restart the computer.

Step 10: Check the File System

Open Command Prompt as Administrator and run:

chkdsk C: /scan

For problems requiring offline repair, Windows may recommend a more extensive CHKDSK operation.

Before performing disk repairs, make sure important data is backed up.

Step 11: Check SSD/NVMe Health

Investigate:

• SMART status
• SSD health
• NVMe temperature
• SSD firmware
• Storage-controller driver
• Unexpected I/O errors

Also check:

Event Viewer → Windows Logs → System

Look for repeated storage-related events around the crash time.

Step 12: Perform a Clean Boot

A clean boot can help determine whether third-party background software contributes to the crashes.

Press:

Windows + R

Enter:

msconfig

Open:

Services

Select:

Hide all Microsoft services

Then disable appropriate third-party services for diagnostic testing.

Also review startup applications in Task Manager.

Restart Windows and test.

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

Step 13: Check Reliability Monitor

Reliability Monitor provides an easier chronological view of system failures.

Search Windows for:

View reliability history

Look for:

• Windows failures
• Hardware errors
• Application crashes
• Driver installations
• Update installations

Check what happened immediately before PFN_LIST_CORRUPT first appeared.

Step 14: Examine Windows Minidump Files

Windows commonly stores small crash dumps in:

C:\Windows\Minidump\

Typical files look like:

082926-12345-01.dmp

Crash dumps can provide information including:

• Bug-check code
• Bug-check parameters
• Faulting thread
• Loaded modules
• Call stack
• Suspected driver
• Memory-corruption indicators

For advanced diagnosis, analyze the dump using Microsoft's WinDbg debugger.

Step 15: Analyze PFN_LIST_CORRUPT with WinDbg

Open the crash dump in WinDbg and run:

!analyze -v

Microsoft specifically recommends examining the stack trace when debugging Bug Check 0x4E.

Review fields such as:

BUGCHECK_CODE

MODULE_NAME

IMAGE_NAME

FAILURE_BUCKET_ID

and the stack trace.

Do not automatically blame:

ntoskrnl.exe

just because it appears in a crash report.

ntoskrnl.exe is the Windows kernel and frequently appears because Windows detects the corruption while executing kernel code. The component that originally damaged memory may be another driver or unstable hardware.

Understanding Important 0x4E Parameters

The actual arguments can make PFN_LIST_CORRUPT analysis significantly more precise.

Parameter 1 = 0x07

Microsoft describes this condition as a driver unlocking a page more times than it previously locked it.

This makes driver behavior particularly important to investigate.

Parameter 1 = 0x8D

This represents page-free-list corruption, and Microsoft's documentation states that this code most likely indicates a hardware problem.

Prioritize:

• RAM testing
• XMP/EXPO testing
• DIMM slots
• Memory settings
• Motherboard/CPU stability

Parameter 1 = 0x99

This indicates that a Page Table Entry (PTE) or PFN is corrupted.

Both drivers and unstable hardware should be investigated.

Parameter 1 = 0x9A

Microsoft describes this as a driver attempting to free a page that is still locked for I/O.

Driver and I/O-path investigation therefore becomes particularly important.

Step 16: Use Driver Verifier Only for Advanced Troubleshooting

Windows includes Driver Verifier, which monitors kernel-mode and graphics drivers for illegal behavior.

Microsoft warns that Driver Verifier can intentionally stress drivers and may cause the computer to crash; Microsoft therefore recommends it primarily for testing and debugging systems.

For this reason, do not make Driver Verifier your first troubleshooting step on an important production computer.

Before using it:

• Back up important files.
• Make sure you know how to enter Safe Mode or Windows Recovery Environment.
• Ensure you can disable Driver Verifier if Windows enters a crash loop.

To check Driver Verifier:

verifier

To reset it from an elevated command prompt:

verifier /reset

Restart Windows afterward.

Driver Verifier is particularly useful when RAM testing passes but crash dumps continue to suggest memory corruption caused by an unidentified driver.

Step 17: Test Recently Installed RAM Individually

If PFN_LIST_CORRUPT started after a memory upgrade, this should be one of your highest-priority tests.

Suppose the machine originally had:

16 GB

and you upgraded it to:

32 GB

Temporarily return to the original configuration.

If the crashes disappear, investigate:

• New DIMM
• Compatibility
• Memory frequency
• XMP/EXPO
• DIMM placement
• Voltage/timing configuration

Also verify the motherboard manufacturer's recommended DIMM slots.

Step 18: Update BIOS/UEFI Carefully

Check the PC or motherboard manufacturer's support site.

Review BIOS release notes for references to:

• Memory compatibility
• System stability
• CPU microcode
• DDR compatibility
• PCIe compatibility
• NVMe compatibility

BIOS updates should be performed carefully. Interrupting firmware updates can render a motherboard unbootable.

If the computer is stable enough and the manufacturer recommends an applicable update, BIOS updating can be considered.

Step 19: Remove Overclocking During Diagnosis

Restore the system to stock settings.

Temporarily remove:

• CPU overclock
• GPU overclock
• RAM overclock
• XMP/EXPO
• Undervolting
• Custom memory timings

Even an overclock that worked for months can become unstable under different workloads, temperatures, firmware, or driver versions.

Step 20: Check Temperatures and Hardware Stability

Monitor:

• CPU temperature
• GPU temperature
• SSD/NVMe temperature
• Motherboard temperatures where available

Also inspect:

• RAM seating
• Power connections
• GPU seating
• Dust buildup
• Cooling fans

Persistent random memory corruption may ultimately require hardware isolation testing.

Recommended Troubleshooting Order

For most users, use this order:

1. Identify recent hardware/software changes

↓

2. Install appropriate Windows and manufacturer driver updates

↓

3. Roll back any suspicious recent driver

↓

4. Disable XMP/EXPO/overclocking

↓

5. Test RAM

↓

6. Run SFC and DISM

↓

7. Check SSD/file-system health

↓

8. Perform clean boot

↓

9. Analyze minidump

↓

10. Test RAM modules individually

↓

11. Investigate BIOS/chipset

↓

12. Use Driver Verifier if driver corruption remains strongly suspected

↓

13. Perform deeper hardware diagnostics

This approach is more effective than immediately reinstalling Windows.

PFN_LIST_CORRUPT After Installing New RAM

If the BSOD started immediately after a RAM upgrade:

1. Disable XMP/EXPO.
2. Reseat the DIMMs.
3. Confirm correct DIMM slots.
4. Test memory.
5. Test each module separately.
6. Return to the original RAM configuration.
7. Check motherboard memory compatibility.
8. Update BIOS if an applicable stability update exists.

If the original RAM works perfectly and crashes return with the new RAM installed, the new memory configuration becomes a strong suspect.

PFN_LIST_CORRUPT While Gaming

Gaming places heavy loads on:

• RAM
• VRAM
• GPU drivers
• CPU
• Storage
• Power delivery

If the error appears mainly during games:

• Update/reinstall GPU drivers.
• Remove GPU overclocking.
• Disable RAM overclocking/XMP/EXPO temporarily.
• Test system RAM.
• Monitor temperatures.
• Check whether crashes occur in multiple games.
• Examine the minidump.

A crash occurring in only one game may have a different cause from crashes occurring under every high-load application.

PFN_LIST_CORRUPT After Windows Update

If crashes started immediately after Windows Update:

Check:

Settings → Windows Update → Update history

Identify recently installed:

• Quality updates
• Driver updates
• Feature updates

Do not assume Windows itself is defective.

A Windows update can expose an existing incompatibility with an older third-party driver.

Analyze the timing and minidump before removing updates unnecessarily.

PFN_LIST_CORRUPT After Sleep or Wake

If the error mainly occurs during sleep, resume, or shutdown, investigate:

• GPU driver
• Chipset driver
• Storage driver
• BIOS/UEFI
• Power-management drivers
• USB devices
• Network adapters

Sleep/resume problems frequently involve hardware power-state transitions and drivers.

Is PFN_LIST_CORRUPT Always a RAM Problem?

No.

This is one of the most important points about this BSOD.

PFN_LIST_CORRUPT indicates that Windows detected corruption in memory-management structures. It does not identify the component that originally caused the corruption.

Possible causes include:

• Defective RAM
• Unstable RAM
• Faulty driver
• Incorrect driver memory handling
• Hardware/DMA problem
• Storage-related driver
• BIOS instability
• Motherboard problem
• Overclocking

The crash dump and bug-check parameters are therefore extremely valuable.

Should You Reinstall Windows?

Not initially.

A clean Windows installation will not repair:

• Defective RAM
• Faulty motherboard
• Unstable XMP/EXPO
• Hardware instability
• Defective SSD
• Firmware problems

Reinstallation should generally be considered only after hardware and driver troubleshooting has failed or when the operating system itself is known to be badly damaged.

Advanced Diagnostic Checklist for IT Engineers

When troubleshooting a business computer, collect the following information before changing multiple settings:

System Information

• PC/laptop model
• Motherboard model
• BIOS version
• CPU model
• RAM capacity
• RAM module configuration
• GPU
• SSD/NVMe model
• Windows version/build

Crash Information

• Stop code
• Bug-check code
• Bug-check parameters
• Date/time
• Minidump
• Frequency
• Activity being performed

Recent Changes

• Windows update
• Driver update
• BIOS update
• RAM upgrade
• SSD upgrade
• New application
• Security software update

This documentation prevents troubleshooting from becoming guesswork.

Frequently Asked Questions (FAQ)

1. What does PFN_LIST_CORRUPT mean?

PFN_LIST_CORRUPT means Windows detected corruption in data structures associated with physical-memory page management. Its bug-check code is 0x0000004E.

2. What does PFN stand for?

PFN stands for Page Frame Number.

3. Is PFN_LIST_CORRUPT a hardware error?

It can be, but not always. Faulty RAM and other hardware can cause it, while kernel-mode driver errors can also corrupt PFN-related structures.

4. Can bad RAM cause PFN_LIST_CORRUPT?

Yes. Defective or unstable RAM is an important cause to investigate, particularly when the system produces several different memory-related BSODs.

5. Can a driver cause PFN_LIST_CORRUPT?

Yes. Microsoft states that Bug Check 0x4E is typically associated with drivers passing bad memory descriptor lists.

6. Can a graphics driver cause this error?

Potentially. GPU drivers are kernel-mode components and should be investigated when crashes coincide with graphics-driver changes or GPU-heavy workloads.

7. Can an SSD cause PFN_LIST_CORRUPT?

Storage hardware, firmware, storage-controller drivers, or corrupted I/O operations can contribute to system instability, so storage should be checked when other diagnostics do not identify the cause.

8. Why did PFN_LIST_CORRUPT start after installing RAM?

The new module could be defective, incompatible, improperly seated, or unstable at the configured memory frequency/timings. Test the original configuration and each DIMM individually.

9. Can XMP cause PFN_LIST_CORRUPT?

Yes. An unstable memory profile can produce memory corruption and BSODs. Disable XMP temporarily and retest.

10. Can AMD EXPO cause PFN_LIST_CORRUPT?

An unstable EXPO configuration can contribute to memory instability. Temporarily return memory to default settings when diagnosing unexplained BSODs.

11. Should I replace my RAM immediately?

No. Test the memory first and also investigate drivers, memory settings, DIMM slots, and crash dumps.

12. Does Windows Memory Diagnostic detect every RAM problem?

No memory test can guarantee detection of every intermittent problem in a single run. Persistent unexplained crashes may require extended testing and individual DIMM testing.

13. Where are Windows BSOD minidumps stored?

They are commonly stored in:

C:\Windows\Minidump\

provided Windows is configured to create small memory dumps.

14. How do I analyze PFN_LIST_CORRUPT?

Use Microsoft WinDbg to open the dump and execute:

!analyze -v

Microsoft recommends examining the stack trace for Bug Check 0x4E.

15. Does ntoskrnl.exe mean Windows itself caused the BSOD?

Not necessarily. The Windows kernel can be the component that detects the corruption rather than the component that originally caused it.

16. Should I use Driver Verifier?

Only for advanced driver troubleshooting. Microsoft warns that Driver Verifier can cause the computer to crash and recommends it for testing/debugging scenarios.

17. How do I disable Driver Verifier?

Open an elevated Command Prompt and run:

verifier /reset

Then restart Windows.

18. Can antivirus software cause PFN_LIST_CORRUPT?

Potentially. Some security products install kernel-level filter drivers. If crashes began after installing or updating security software, investigate that software and its drivers.

19. Can BIOS cause PFN_LIST_CORRUPT?

BIOS/UEFI memory compatibility or stability issues can contribute, especially after hardware upgrades or when high-speed memory profiles are enabled.

20. Can overheating cause this BSOD?

Overheating can destabilize hardware and should be investigated when crashes happen mainly under heavy workloads.

21. Should I run SFC for PFN_LIST_CORRUPT?

Yes, as part of general Windows integrity checking. Run:

SFC /scannow

22. Should I run DISM?

If Windows component corruption is suspected, run:

DISM /Online /Cleanup-Image /RestoreHealth

and then run SFC again.

23. Should I run CHKDSK?

It can be useful when file-system or storage corruption is suspected. A non-disruptive initial check is:

chkdsk C: /scan

24. Why does my PC show different BSOD codes every time?

Different stop codes can occur when underlying memory corruption affects different kernel structures. RAM instability, hardware problems, or a defective kernel driver should be investigated.

25. What is the fastest way to diagnose recurring PFN_LIST_CORRUPT?

Collect the minidumps, identify recent changes, test RAM at default settings, update or roll back suspicious drivers, and analyze the dumps with WinDbg. Avoid changing many unrelated settings simultaneously because doing so makes the actual cause harder to identify.

Conclusion

PFN_LIST_CORRUPT (0x0000004E) is a serious Windows stop error indicating corruption of the Page Frame Number memory-management structures.

The most important mistake is assuming:

PFN_LIST_CORRUPT = bad RAM

RAM is certainly an important suspect, but it is only one possibility.

Microsoft's Bug Check 0x4E documentation specifically points to incorrect driver handling of memory descriptor lists as a typical cause, while certain bug-check parameter values can also indicate likely hardware corruption.

A systematic diagnosis should therefore investigate:

RAM → XMP/EXPO → Drivers → Minidumps → Storage → BIOS/Chipset → Hardware

For recurring crashes, analyzing the actual .dmp file with WinDbg is usually far more valuable than repeatedly applying generic BSOD fixes.

Tags

#PFN_LIST_CORRUPT #PFNLISTCORRUPT #BSOD #BlueScreen #BlueScreenOfDeath #Windows11 #Windows10 #WindowsError #WindowsTroubleshooting #WindowsSupport #StopCode #BugCheck #BugCheck0x4E #0x0000004E #MemoryError #MemoryCorruption #RAM #RAMError #RAMTesting #WindowsMemoryDiagnostic #MemTest86 #DriverError #WindowsDrivers #DriverVerifier #WinDbg #Minidump #CrashDump #DumpAnalysis #WindowsCrash #PCRepair #ComputerRepair #WindowsRepair #SystemCrash #KernelError #KernelDriver #MemoryManagement #PageFrameNumber #PFN #PTE #SFC #DISM #CHKDSK #SSD #NVMe #BIOS #XMP #EXPO #HardwareDiagnostics #WindowsBSOD #Troubleshooting