Windows wants to check D partition at every boot

csabix

New Member
Local time
8:27 PM
Posts
6
Thread starter
Hi all


My problem started few weeks ago.
At every boot, Windows 10 wants to check drive D and I have to press a key to skip it since the check process doesn't solve anything (although it says it repairs stuff).
My setup:
1. On the SSD
Windows 10 20H2
Debian Linux 10

2. On the HDD
one NTFS partition that can be seen both by Win and Linux.

At first I thought Linux corrupted the NTFS volume. So I let autocheck run and correct things, then restarted and booted again in Windows, to exclude the possibility of another fs corruption. But it kept asking for disk check.

What could I do to solve the issue?
 
Windows Version
20H2

My Computer

System One

  • Operating System
    Windows 10 and Debian Linux 10

philc43

BSOD Analyst
MVP
Member
VIP
Local time
6:27 PM
Posts
64
Location
Cambridge, UK
It could be that the D drive is failing and so needs constant checks. Try running a disk diagnostic check on the drive such as HDTune and report back on the results. You can post screen shots of all the HDTune screens to do this.
 
Last edited:

My Computer

System One

  • Operating System
    Windows 10
    Computer type
    PC/Desktop
    Manufacturer/Model
    Self-Build
    CPU
    Intel Core i5 3570K 3.4GHz
    Motherboard
    ASUS P8Z77-V LX
    Memory
    16GB
    Graphics Card(s)
    NVidia Geforce GTX 750Ti
    Sound Card
    On-board Realtek HD Audio
    Monitor(s) Displays
    Samsung 226BW
    Hard Drives
    1TB SSD + 1TB HDD
    PSU
    Corsair TX550
    Case
    Gigabyte IF233
    Keyboard
    Microsoft wired Keyboard 600
    Mouse
    Microsoft wired Basic Optical
    Internet Speed
    900MB/s
    Browser
    MS Edge
    Antivirus
    Microsoft Defender

DTG1

Death to Gnomes!!!
VIP
Local time
1:27 PM
Posts
74
Location
SE MI
When this started what was going on? did just start out of the blue? the MBR might be corrupted

I found this for you, Method 1 is preferred since you dont have to install software you wont use that often.

 

My Computer

System One

  • Operating System
    Win10
    Computer type
    PC/Desktop
    Manufacturer/Model
    ME
    CPU
    AMD FX-9370
    Motherboard
    ASUS SABERTOOTH 990FX R2.0 +SB950
    Memory
    G.Skill Sniper 16gb DDR3 2400
    Graphics Card(s)
    Msi GTX1080 Gaming X
    Sound Card
    onboard (realtek?) -- SPKRS:Logitech Z623 200w 2.1
    Monitor(s) Displays
    2x Dell S2440L (16:9) 1 Nixeus NX-EDG27S
    Hard Drives
    C:\Samsung Evo (500GB)
    D:\Samsung Evo (1TB)
    F:\Seagate (2TB)
    PSU
    Corsair HX1000i
    Case
    Phanteks Enthoo Primo w/9 140mm fans
    Cooling
    CM Nepton 280L(CPU) (4 fan P/P)
    Keyboard
    Logitech 910s Orion Spark
    Mouse
    Logitech G604 LightSpeed
    Internet Speed
    faster than dialup
    Browser
    Waterfox
    Antivirus
    none
    Other Info
    potato image lighted > http://i.imgur.com/gYkHqxU.jpg

csabix

New Member
Local time
8:27 PM
Posts
6
Thread starter
When this started what was going on? did just start out of the blue? the MBR might be corrupted

I found this for you, Method 1 is preferred since you dont have to install software you wont use that often.

I suppose it started after an OS update. 99 % of the time I'm on Linux and enter Windows sporadically, to resolve some rare problems that need specific applications. Also, this is hen I update the OS.
MBR is not corrupted but modified by Linux. Windows "corrects" the "issue" by deleting the Linux entries. Anyways, that's not the problem. Drive D is on separate disk. Also, Windows can boot regardless if I skip or let AutoChk do its (useless) job.
At the moment I'm running HDTune just to make sure there aren't issues with the disk itself, as instructed by philc43.
 

My Computer

System One

  • Operating System
    Windows 10 and Debian Linux 10

csabix

New Member
Local time
8:27 PM
Posts
6
Thread starter
It could be that the D drive is failing and so needs constant checks. Try running a disk diagnostic check on the drive such as HDTune and report back on the results. You can post screen shots of all the HDTune screens to do this.
 

My Computer

System One

  • Operating System
    Windows 10 and Debian Linux 10

zbook

Junior Member
Member
VIP
Local time
12:27 PM
Posts
71
The logs displayed recurrent drive file system corruption.

Often this can be fixed.

If not, then replace the drive.

First test the hardware.

After completing HD Tune run the Sea Tools long generic test.


1) Run Sea Tools for Windows
long generic test
Post an image of the test result into the thread


If the hardware passes testing then run deep Chkdsk scans until all corruption is fixed.
Then an additional scan is ran to make sure that no corruption is detected.


2) Open administrative command prompt and type or copy and paste:
chkdsk /b /v
This may take hours to run so plan to run overnight.
Run on all drives using the syntax: chkdsk /b /v C: or chkdsk /b /v D: changing the drive letter to the applicable drive.

C:\Windows\system32>chkdsk /b /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y
reboot


3) Use the information in this link to find the chkdsk report in the event viewer.
Copy and paste into notepad > save to desktop > post into the thread using a one drive, drop box, or google drive share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials


Code:
Event[1828]:
  Log Name: System
  Source: Ntfs
  Date: 2021-02-14T11:48:18.3960000Z
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: MunkagepWin
  Description:
A corruption was discovered in the file system structure on volume D:.

The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x1000000000026.  The name of the file is "<unable to determine file name>".
 

My Computer

System One

  • Operating System
    Windows 10

zbook

Junior Member
Member
VIP
Local time
12:27 PM
Posts
71
Other notable findings seen in the logs:

a) insufficient free space on D:
b) absence of a page file
c) BSOD


See these tutorials:

(1) Manage Virtual Memory Pagefile in Windows 10 | Tutorials (tenforums.com)


Once the drive testing steps are completed steps can be made to troubleshoot the BSOS.

Increase the free space on the Windows drive so that there is > 30 GB free space

Make sure for virtual memory page file:
a) that the page file is on the Windows drive
b) the dot is in system managed
c) the box is checked to automatically manage paging file size for all drives
d) that the computer is rebooted after modifying page file settings






Code:
      Drive: C:
Free Space: 236.8 GB
Total Space: 309.6 GB
File System: NTFS
      Model: KINGSTON SA400S37480G

      Drive: D:
Free Space: 10.5 GB
Total Space: 953.9 GB
File System: NTFS
      Model: WDC WD10EZEX-22MFCA0


Code:
Installed Physical Memory (RAM)    10.0 GB
Total Physical Memory    9.50 GB
Available Physical Memory    1.85 GB
Total Virtual Memory    9.50 GB
Available Virtual Memory    1.00 GB
Page File Space    0 bytes


Code:
Event[1797]:
  Log Name: System
  Source: volmgr
  Date: 2021-02-14T11:47:27.8270000Z
  Event ID: 46
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: MunkagepWin
  Description:
Crash dump initialization failed!


Code:
Event[1724]:
  Log Name: System
  Source: volmgr
  Date: 2021-02-14T11:36:28.2060000Z
  Event ID: 46
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: MunkagepWin
  Description:
Crash dump initialization failed!
 

My Computer

System One

  • Operating System
    Windows 10

csabix

New Member
Local time
8:27 PM
Posts
6
Thread starter
Thank you for the effort taken.

Indeed, the pagefile was on drive D: and this prevented checkdisk from completing the repair (Windows automatically locked the fs before chkdsk could be run).
Moved pagefile back to C:, rebooted and completed the repair from GUI.
Did another reboot and everything is fine.
Since I found anomalies in one of the folders (deleted subfolders returning there), I could spot the culprit: the video editor from Linux (KDEnlive) was corrupting the fs when it crashed. Luckily it is cross-platform and the Win version seems more stable. Also, the kernel driver for the filesystem is way better than the open source one since it's native.

As a bonus issue/question: what can I do with the found.000 folders that were created? They contain gigabytes of data with unknown relevance.
 

My Computer

System One

  • Operating System
    Windows 10 and Debian Linux 10

zbook

Junior Member
Member
VIP
Local time
12:27 PM
Posts
71
I've seen reports where end users attempt to recover found.000.

Long ago on one of my drives there was corruption in the EFI partition.
The partition was labeled and fixed with chkdsk.
The found.000 remained in this partition as non usable files.


These files are most often metadata.

I've not seen end users reporting regular success with third party software.
This one has a cost: How to Recover Data from FOUND.000 Folder - Best Three Solutions (systoolsgroup.com)


Please run:

Tuneup.bat - Click here to go to the BSOD batch repository to download and run this batch file.
LOGS.bat - Click here to go to the BSOD batch repository to download and run this batch file.
DiskParInfo.bat - Click here to go to the BSOD batch repository to download and run this batch file.
 

My Computer

System One

  • Operating System
    Windows 10

csabix

New Member
Local time
8:27 PM
Posts
6
Thread starter
Thanks!
Did try UnCHK in the past and it helped on a different computer but not this one. EaseUS is shady business. At least I didn't like something about their policy back in the day.
 

My Computer

System One

  • Operating System
    Windows 10 and Debian Linux 10
Top