What is happening is your file is somewhat "corrupted".  There is an illegal sequence of CRLF in the file, causing GenoPro to miss 0 GLOBAL root tag and therefore interpret the TAGS keyword as a root keyword.  Since I wanted GenoPro to be robust, I wrote some special code for this. Unfortunately this code had never been tested and crashed on you. I am taking this opportunity to kill two birds with one stone, by 1) fixing the crash in case of another misplaced TAGS keyword, and 2) by writing additional code to detect and correct any illegal sequence of CRLF.

0 @source00001@ SOUR 1 TITLE FamilySearch.org 1 PUBL 1910 Census 1 CHAN 2 DATE 24 Aug 2005 3 TIME 9:31:12 0 GLOBAL 1 NAME 2 FULL 3 FORMAT %T %F (%N) %M %L (%L2) %S 2 DISPLAY 3 FORMAT %F %M %L (%L2) 3 LINES 3 1 FONT Arial 1 TAGS 2 ID Individual 2 TAGDATA 3 NAME SSN 3 DISPLAYNAME SSN 3 DESCRIPTION Social Security Number 2 DIALOGLAYOUT 3 NAME Custom Tags 3 DESCRIPTION A custom tag is a generic placeholder to record additional information 4 CONC . 4 CONT You can customize those tags by clicking on the Customize button. 3 TAGS SSN

What to do:

In the meantime, use Notepad and open your .ged file.  Locate the GLOBAL keyword (use the F3 key).  You will see a long line as below

0 @source00001@ SOUR 1 TITLE FamilySearch.org 1 PUBL 1910 Census 1 CHAN 2 DATE 24 Aug 2005 3 TIME 9:31:12 0 GLOBAL

 
 and replace it by the following (split the long lines into smaller, valid Gedcom lines)

0 @source00001@ SOUR 1 TITLE FamilySearch.org 1 PUBL 1910 Census 1 CHAN 2 DATE 24 Aug 2005 3 TIME 9:31:12 0 GLOBAL