DB snapshot goes into SUSPECT mode (SQL 2014 on WIN2K8R2) I was hoping someone here might have encountered this sort of issue and if so what did you do to fix it?

Here's some details:

DB server: SQL 2014 Enterprise (12.0.4100.1) 
OS: Windows 2008R2 Enterprise

Data drive: 800GB

Database to snapshot: 430GB

I can create multiple snapshots of this database and they function perfectly fine until the actual size on disk reaches 38.1GB. At this point there is still well over 150GB of free space on the drive. After that the SnapShot file encounters an IO error and the snapshot enters SUSPECT mode. Here's the error message in the SQL ERRORLOG:

The operating system returned: 


  error 665(The requested operation could not be completed due to a file
  system limitation) to SQL Server during a write at offset
  0x00002dc1520000 in file 'E:\SQL Data 1\devDB_seq1501_rba63692865.ss'.
  Additional messages in the SQL Server error log and system event log
  may provide more detail. This is a severe system-level error condition
  that threatens database integrity and must be corrected immediately.
  Complete a full database consistency check (DBCC CHECKDB). This error
  can be caused by many factors; for more information, see SQL Server
  Books Online.
  
  E:\SQL Data 1\devDB_seq1501_rba63692865.ss: Operating system error
  665(The requested operation could not be completed due to a file
  system limitation) encountered.
  
  Database snapshot 'devDB_seq1501_rba63692865' has failed an IO
  operation and is marked suspect. It must be dropped and recreated.


This article: https://support.microsoft.com/en-us/kb/2002606 mentions a similar sort of issue (the 665 error) on a heavily fragmented file system, but I'm not really sure how to approach this.

Any insight into what might be happening here would be greatly appreciated.
Did the drive the snapshot is on or the drive that the source DB is on run out of space? 

There's no way to repair a corrupt snapshot. The only thing you can do with it is drop it.