Check the MySQL error log.  It looks like trying to read table 44 is actually crashing the server.

"Lost connection to MySQL server during query" is (or should be) heart-stopping time for a MySQL DBA because it often means that whatever your query just did has actually crashed the server.  

The subsequent messages seem to bear this out:

    mysqldump: Got error: 2003: Can't connect to MySQL server on 'localhost' (10061) when
    trying to connect
    Operation failed with exitcode 2

A quick test of mysqldump on Windows 7 against a MySQL server *that is not running* returns exactly that same error and exits with `%ERRORLEVEL%` set to 2.  The nature of error 10061 can be found with [the `perror` utility][1]. 

    C:\>perror 10061
    Win32 error code 10061: No connection could be made because the target machine actively refused it.

...so, check the MySQL error log.  What's likely happening is that you're hitting corruption severe enough that in spite of `innodb_force_recovery`, the MySQL Server is crashing.  I will then usually restart on its own, but this takes time so may not complete before mysqldump gets an IP connection refused on the subsequent connection attempts.  This should all show up in the error log.

> I assume that when the dump does not yield any error, the table's data is non-corrupted.

Incorrect assumption.  If the dump does not yield any error, it could also mean that that `innodb_force_recovery` allowed the server to retrieve *some* of the data.  A "successful" dump of a table only means it's not corrupted so severely that `innodb_force_recovery` can't survive it.

>`1 (SRV_FORCE_IGNORE_CORRUPT)`

>Let the server run even if it detects a corrupt page. Try to make `SELECT * FROM tbl_name` jump over corrupt index records and pages, which helps in dumping tables.

><sup>http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html</sup>

Again, you should see chatter from InnoDB in the MySQL error log.

Final suggestion, don't use workbench.  Use the `mysql` command line client to explore the server schemata and use `mysqldump` directly from the command line to try to restore individual schemas or individual databases.


  [1]: http://dev.mysql.com/doc/refman/5.5/en/perror.html