Chkdsk detects errors when online, but doesn't when offline

Question

I've been getting a lot of BSOD's recently, most of them being PFN list corrupted, System service exception and attempt to write read only memory. I ran DISM and SFC but they dont seem to have done anything, when I ran CHKDSK it came back with this:

497 new analysis records processed.
Error detected in index $I30 of file 2BDCE.
Error detected in index $I30 of file 2BDCE.
Error detected in index $I30 of file 2BE26.
Error detected in index $I30 of file 2BE26.
Error detected in index $I30 of file 2BE50.
Error detected in index $I30 of file 2BE50.
Error detected in index $I30 of file 2C340.
Error detected in index $I30 of file 2C340.
Error detected in index $I30 of file 2C35E.
Error detected in index $I30 of file 2C35E.
Error detected in index $I30 of file 2C388.
Error detected in index $I30 of file 2C388.
Error detected in index $I30 of file 2C3CE.
Error detected in index $I30 of file 2C3CE.
Error detected in index $I30 of file 2C442.
Error detected in index $I30 of file 2C442.
Error detected in index $I30 of file 2C47F.
Error detected in index $I30 of file 2C47F.
Error detected in index $I30 of file 2C490.
Error detected in index $I30 of file 2C490.
Error detected in index $I30 of file 67279.
Error detected in index $I30 of file 67279.
Error detected in index $I30 of file 6727E.
Error detected in index $I30 of file 6727E.
Error detected in index $I30 of file 70298.
Error detected in index $I30 of file 70298.
Error detected in index $I30 of file 7029C.
Error detected in index $I30 of file 7029C.

Error detected in index $I30 of file 702A1.

Error detected in index $I30 of file 702A1.

Error detected in index $I30 of file 702A4.

Error detected in index $I30 of file 702A4.

Error detected in index $I30 of file 702A7.

Error detected in index $I30 of file 702A7.

Error detected in index $I30 of file 702AA.

Error detected in index $I30 of file 702AA.

Error detected in index $I30 of file 702AD.

Error detected in index $I30 of file 702AD.

Error detected in index $I30 of file 702B2.

Error detected in index $I30 of file 702B2.

Error detected in index $I30 of file 702B5.

Error detected in index $I30 of file 702B5.

Error detected in index $I30 of file 702BC.

Error detected in index $I30 of file 702BC.

Error detected in index $I30 of file 702BF.

Error detected in index $I30 of file 702BF.

Error detected in index $I30 of file 702C4.

Error detected in index $I30 of file 702C4.

Error detected in index $I30 of file 702C7.

Error detected in index $I30 of file 702C7.

Error detected in index $I30 of file 702CB.

Error detected in index $I30 of file 702CB.

1112370 index entries processed.

Index check completed.

Phase duration (Index check): 13.64 seconds.

Errors found. CHKDSK cannot continue in read-only mode.

So I ran it offline, using CHKDSK C: /f /r so it could repair, but it did not found any of these errors and they continue unfixed. How can I solve this?

Answer 1

Your minidump files just indicate memory (RAM) corruption no specific driver is listed

The best option is to download the widely available free utility MemTest86, then run a full 4 pass scan with that to test your RAM for physical errors

Answer 2

This is the Minidump folder

Answer 3

This is the Minidump folder

Answer 4

Hi, I am Dave, I will help you with this.

Please check to see if your PC is producing any minidump files, I will check those to see if they provide any insight into a potential cause of the system crashes.

Open Windows File Explorer.

Navigate to C:\Windows\Minidump

Copy any minidump files onto your Desktop, then zip those up.

Upload the zip file to the Cloud (OneDrive, DropBox... etc.), then choose to share those and get a share link.

Then post the link here to the zip file, so we can take a look for you.

Answer 5

Hello Gabriel Zorzan,

Thanks for reaching out here in the Microsoft Answers Community.

Based on the description, it seems that either the check is performed when there is a lot of activity, or the errors are considered not fatal by the system.

Please try checking the filesystem in the recovery environment, and see whether there are any errors detected. Since the filesystem could have already been corrupted, please back up your personal files to offline storage (like USB sticks, external hard disks, and memory cards) beforehand to prevent data loss.

Then, right-click Start->Terminal (Admin), and enter the following command to enter the recovery environment:

shutdown /r /o /f /t 0

You should see a "Choose an option" screen. From there, please select Troubleshoot->Advanced options->Command prompt, and enter the following command to perform the check:

chkdsk C: /F /X

If there are multiple drives (like drives D, E, and others), please check all of them, as the drive ordering is different in the recovery environment.

Disclaimer: Running "CHKDSK" can check the file system and file system metadata of a volume for logical and physical errors.

To avoid any trouble for you, do not cancel or interrupt CHKDSK, and back up important data.

After checking, see whether the blue screens continue. If so, please go to file explorer->This PC->C drive->Windows->minidump, and upload the DMP files there to a file-sharing service for our analysis.

We look forward to your response.

Best Regards,

Sheng G. - MSFT | Microsoft Community Support Specialist