Error in kernel data page issue detected
Error in kernel data page issue detected
Hey everyone! I've been facing some frustrating blue screens lately, especially when gaming or running demanding tasks. I've checked everything suggested online—updating drivers, updating Windows, fixing corrupted files, scanning for faulty RAM, boosting RAM from 16 to 32 GB, looking for viruses, checking SSDs, running SFC and CHKDSK, and verifying the pagefile. Did I miss anything? Any tips or steps you recommend? Just sharing my specs: Ryzen 3600xt RTX 2060, 32 GB RAM, 500 GB SSD, 1 TB M.2 SSD, 60 GB SSD. Thanks!
The kernel page data error indicates corruption in the page file, which acts like additional RAM and is refreshed each time the system restarts. Persistent crashes suggest a serious storage issue. Look for firmware updates, keep an eye on SSD temperature, and re-seat the M.2 drive if needed. For NVMe drives, SMART checks via tools like CrystalDiskInfo are ineffective. With SATA drives, focus on reading the relevant parameters in the bottom section. Understanding these details is crucial for troubleshooting. If you need further assistance, provide a screenshot with all parameters included.
I assume that's what the " pagefile.sys" file is? Then is that an indicator that the SSD (that one is not the NVME) that has the pagefile.sys is the faulty storage, or can any of them be guilty? I'll send a screenshot of the bottom half of the CrystalDiskInfo from the SSD with the pagefile.sys
It's a straightforward fix, but have you thought about turning off the pagefile or resizing the drive manually to test performance? I'm curious to know what you tried and how it affected things. Also, the SMART data looks mostly normal for me. No crashes or issues, though your hard drive has been running about 4 years straight—definitely not too bad, but I’d probably check a new drive to see if it helps.
Pagefile.sys refers to the designated page file. The storage device shows multiple CRC errors. This indicates data alterations during transport between the computer and the drive, often caused by a faulty SATA cable. The issue might stem from the SATA controller itself, though CRC errors also appear on other connected drives. Rarely, the drive itself could be the culprit. While SMART monitoring isn't foolproof, it can help detect problems; however, it may miss some errors. SMART data from BackBlaze revealed that 20% of their failing drives showed no SMART indicators, all involving SATA interfaces. This document aims to assist in relocating the page file to another drive. Some recommendations include manual sizing or completely disabling it, which I generally avoid unless RAM is extremely limited. Certain systems operate without Windows involvement, writing directly to the page file and potentially leading to complications. I prefer letting Windows manage this process. Insufficient space on the drive can also disrupt the page file functionality. Previously, a common guideline was to allocate twice the amount of RAM, but with modern systems supporting up to 20GB, this is usually sufficient. Creating a dump file might encounter problems if RAM is less than the recommended amount plus an additional 3-4GB. Confirm that the page file resides on a single drive, as it can be spread across multiple ones. If it’s confined to one drive, that drive is likely the primary concern.