You are always welcome and I'm glad it is now all good.
PC keeps getting BSOD
Good day! I have been getting BSOD whenever I boot my PC. It keeps showing after minutes of turning on the PC. Here is the attached memory dump I saved. I hope someone can help me. Thank you! Here are some of the things that WinDBG showed. I am also attaching the dump file saved on my google drive.
https://drive.google.com/file/d/1yy9ojNOWFWmHX0vuLqDNfVO0fVP6ucLb/view?usp=sharing
0xc 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x10 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x14 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x18 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x1c 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x20 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x24 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x28 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x2c 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x30 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x34 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x38 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x3c 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x40 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x4c 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x50 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x54 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x58 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x5c 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x60 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x6c 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x70 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x74 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x78 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x7c 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x80 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x84 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x88 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x8c 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x90 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x94 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x98 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x9c 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0xa0 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0xa4 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0xa8 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0xac 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0xb0 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0xb4 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0xb8 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0xbc 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0xc0 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0xc4 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0xc8 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0xcc 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0xd0 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0xd4 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0xd8 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0xdc 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0xe0 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0xe4 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0xe8 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0xec 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0xf0 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0xf4 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0xf8 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0xfc 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x100 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x104 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x108 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x10c 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x110 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x114 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x118 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x11c 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x120 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x124 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x128 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x12c 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x130 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x134 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x138 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x13c 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x140 0x0 nt!KeBugCheckEx (fffff803`567fd5c0)
0x144 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x148 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x14c 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x150 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x154 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x158 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x15c 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x160 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x164 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x168 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x16c 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x170 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x174 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x178 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x17c 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x180 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x188 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x18c 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x190 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x194 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x198 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x19c 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x1a0 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x1a4 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x1a8 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
0x1b8 0x0 nt!KiSwapContext+0x76 (fffff803`56805bb6)
Windows for home | Windows 10 | Devices and drivers
5 answers
Sort by: Most helpful
-
Lester Bernard Reyes 84,700 Reputation points Independent Advisor
2026-08-30T04:46:44.88+00:00 -
Zyrus 0 Reputation points
2026-08-29T04:01:05.0533333+00:00 Hello everyone! After some time, I decided to just use the PC parts to migrate to my main PC. One thing I've find out is that the hard drive and RAM is fine. My final conclusion is that the CPU might be already failing or it is corrupted. It is a 3rd gen chip and I wouldn't be surprised if it is broken now. Thank you for all of your answers!
-
Lester Bernard Reyes 84,700 Reputation points Independent Advisor
2025-11-05T02:18:40.6966667+00:00 Hi, thank you for that information, as per checking and analyzing the new DMP files, it is still displaying the same error, in this case. Let us eliminate software-related issues on the PC. I suggest doing an in-place upgrade wherein it will upgrade the device to the latest version and repair all issues without deleting any files.
Note: before doing this make sure to create a restore point: https://support.microsoft.com/en-us/help/4027538/windows-create-a-system-restore-point
- Go to this link: https://www.microsoft.com/en-us/software-download/windows10
- Select Download Now, and select Run. You need to be an administrator to run this tool.
- On the License terms page, if you accept the license terms, select Accept.
- On the What do you want to do? page, select Upgrade this PC now, and then select Next.
- After downloading and installing, it should fix the issue.
Reference: https://www.microsoft.com/en-us/software-download/windows10
Note: If the issue persists, I suggest contacting a local technician to physically check the device for any hardware-related issues.
-
Lester Bernard Reyes 84,700 Reputation points Independent Advisor
2025-11-04T02:58:08.58+00:00 Hi, I'm Bernard, a fellow Windows user. I'm happy to help!
I understand the issue you have. There is nothing to worry about. I am here to assist. As per checking and analyzing the DMP files, there is an error rdyboost.sys, which is the ready boost on the PC that is having conflicts with the memory of the PC. To sort out the issue, kindly follow the steps below:
Method 1. Disable Ready Boost:
Open Notepad, then copy and paste the code below:
Windows Registry Editor Version 5.00 [-HKEY_CLASSES_ROOT\Drive\shellex\PropertySheetHandlers\{55B3A0BD-4D28-42fe-8CFB-FA3EDFF969B8}]Click File > Save as > File name: readyboost.reg > then on Save as type: All files
Once you save it double click the file then run.
Restart the PC and check.
Note: If the issue persists, kindly follow the "Method 4. Disable NTFS compression" from this link: https://windowsreport.com/wpprecorder-sys/
Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.
-
AI answer
2025-11-04T02:19:20.5566667+00:00 Experiencing Blue Screen of Death (BSOD) errors can be frustrating. The error messages you see are often related to hardware or driver issues. Here are some general troubleshooting steps you can take to address BSOD errors:
- Check for Faulty Drivers: If you have recently installed new drivers or system services, consider removing or updating them. You can use Windows Device Manager to check for any devices marked with an exclamation point (!), which indicates a problem.
- Review Hardware Changes: If you have added new hardware recently, try removing it to see if the BSOD persists. Ensure that all hardware components are compatible with your version of Windows.
- Run Hardware Diagnostics: Use the hardware diagnostics tools provided by your system manufacturer to check for any hardware issues.
- Check System Logs: Use the Event Viewer to check for critical errors in the system log that occurred around the same time as the BSOD. This can help identify the problematic device or driver.
- Memory Diagnostics: Run the Windows Memory Diagnostics tool to check for memory errors. You can find this tool by searching for "Memory" in the Control Panel.
- Virus Scan: Run a virus detection program to ensure that your system is not infected, as viruses can cause system instability and BSOD errors.
- Clean Boot: Perform a clean boot to start Windows with a minimal set of drivers and startup programs. This can help identify if background programs are causing the issue.
- Analyze the Memory Dump: If you have a memory dump file, you can analyze it using WinDbg. Make sure you have set up the symbol path correctly to get meaningful information from the dump.
If the problem persists after trying these steps, you may need to consider restoring your system to a previous state or reinstalling Windows as a last resort.
References:
AI-generated content may be incorrect. Read our transparency notes for more information.