It's a limitation of how the grid displays datetime values. I just ran into this a few weeks back
DateTime fields are internally tracked using a very large integer value. Each programming language and database treats things a bit differently, but they all define a date that represents an internal value of zero, and increase time according to the size of that internal value. The result is that you get this confusing date when you didn't define one.
If you are using a database query, you can try to convert the sql output from a datetime field to a text output (nvarchar for example). For null values, substitute an empty string.
Another option could be to define a custom datatype (in workflow) with the same fields as your original array, but swap text fields for the datetime fields. Create a model that is responsible for doing the translation and outputing the array with the swapped datetime to text fields. Within the model, compare the datetime values to see if they are greater than 1/1/2001 12:00:00 AM and set the output string accordingly. I believe there is also a checkbox on the time comparision components like "Minimum value" that is the same datetime value discussed earlier.