A couple of possibilities, not sure if any of them will help you

**Force recovery**

    [mysqld]
    innodb_force_recovery = 4

If you run Force Recovery, your database will still be in an incoherent state. This will however allow you to make a backup of the data that you do have access to.

> Usually, most of the data obtained in this way is intact. Serious
> corruption might cause SELECT * FROM tbl_name statements or InnoDB
> background operations to crash or assert, or even cause InnoDB
> roll-forward recovery to crash. In such cases, use the
> innodb_force_recovery option to force the InnoDB storage engine to
> start up while preventing background operations from running, so that
> you can dump your tables

[Force InnoDB recovery][1]

**Permissions**

Make sure the MySQL service user has full permissions on C:\wamp\bin\mysql\mysql5.6.12\data

![enter image description here][2]

The service that runs MySQL needs full control for the directory where you are storing your data files



**Restore from backup to another server**

Make sure you have a recent backup

Drop the database

Restore from backup

    cd C:\wamp\bin\mysql\mysql5.6.12\bin
    mysql -u root -psomepassword mydatabase < backupofdatabase.sql

**Install MySQL somewhere else and copy the data files**

[Download MySQL for Windows][3]

Stop your actual server 

Install MySQL on another location

Restore your database to the new server or perform an in-place upgrade by copying the data directory to the new server data directory location.

Be careful to backup your mysql database on the old server so that you have all of your users and their permissions 


  [1]: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  [2]: https://i.sstatic.net/jKZ4z.png
  [3]: http://dev.mysql.com/downloads/mysql/