MySQL Workbench -- How to efficiently review large database tables?
The first suggestion was to use the "pager less" command - but as pointed out, even at 10 pages a second, it would take 25 hours to get through 900,000 records. 

Unfortunately, the "pager" command doesn't work on Windows. It was then suggested to send the output to a file and scroll through that - looking for a disconnect between the .csv input and the final table.

Then, this was proposed

    Or!! You could save your table as a .csv (with a different name  
to your original file) and then do a diff on the files - that might 
immediately show up problems? 


This appears to have resolved the issue for the OP.