It appears this question was asked in a similar manner in the "What is the range of dates that windows explorer can display?" and the answer on that post gives some good resources offering a clue explaining.
I've dug into those resources and others a bit and will reference quote the parts which I think are relevant and important your question since you posted a bounty it must be important for you to get a verifiable answer.
Note: I believe this is a Windows Explorer/File Explorer limitation and not that of the underlying file system.
As per the "Interpretation of NTFS Timestamps" post and the results of extensive testing. . .
Windows Explorer GUI:
- 1980-01-01 00:00:00 - 2107-12-31 23:59:57
- 2107-12-31 23:59:58 and :59 are shown as (blank)
Remaining timestamps outside the range are translated as (blank)
Interpretation of results
In terms of coverage, none of the tools presented above is perfect:
all are affected by some kind of restriction to the time period they
translate correctly. The tools that comes off best are, in order of
the time range they support:
- Windows Explorer GUI (1980–2107)
As per the Why do my file creation, access, or modified time disappear if I set it to midnight on January 1, 1980? here relevant information. . .
A customer discovered that if their program used the
function to set a network file's creation, access, or modified time to
the specific value of "midnight on January 1, 1980", then the
corresponding timestamp is removed.
Some time ago, I discussed several timestamp formats you might run into. Today we'll take a logical step from that information and develop a list of special values you might encounter. Note that if you apply time zone adjustments, the actual timestamp may shift by up to a day.
- Date: December 31, 1969 - January 1, 1970
- Interpretation: The value -1 or 0 as a time_t.
All of these special values have one thing in common: If you see them, it's probably a bug. Typically they will arise when somebody fails to do proper error checking and ends up treating an error code as if it were a valid return value. (The special values 0, -1, and 0xFFFFFFFF are often used as error codes.)