EASYPHP Mysql ne démarre pas

Bonjour à tous,

J'ai installé EASYPHP 13.1 depuis 3 mois sur mon PC.
Jusqu'ici aucun souci.

Je développe donc des sites en local: 127.0.0.1/blabla/monsite1

Hier soir tout était nickel.
Ce matin je démarre easyphp pour m'y remettre et là ... Mysql ne démarre plus.
Quand je clic sur démarrer, il passe à en attente ... puis 2 sec après repasse en arrêté.
Apache quand à lui fonctionne bien.

Je n'ai plus accès à phpmyadmin et du coup (comme Mysql est arrêté) plus accès à mes site (qui utilisent un CMS).

Comment faire pour redémarrer MYSQL ?

Plz Help et merci d'avance.

PS: J'ai trouvé 1 million de solution sur google même certaines sur commentçamarche cependant aucune ne fonctionne! :(

voici les logs pour easy php:

ServerBase::TimerProc : GetProcessVersion MySQL (pid: 6520) error 5

Voici les logs pour Mysql:

2013-11-15 10:06:00 5908 [Note] Plugin 'FEDERATED' is disabled.

2013-11-15 10:06:00 9a4 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.

2013-11-15 10:06:00 5908 [Note] InnoDB: The InnoDB memory heap is disabled

2013-11-15 10:06:00 5908 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions

2013-11-15 10:06:00 5908 [Note] InnoDB: Compressed tables use zlib 1.2.3

2013-11-15 10:06:00 5908 [Note] InnoDB: Not using CPU crc32 instructions

2013-11-15 10:06:00 5908 [Note] InnoDB: Initializing buffer pool, size = 16.0M

2013-11-15 10:06:00 5908 [Note] InnoDB: Completed initialization of buffer pool

2013-11-15 10:06:00 5908 [Note] InnoDB: Highest supported file format is Barracuda.

2013-11-15 10:06:00 5908 [Note] InnoDB: The log sequence numbers 20769754 and 20769754 in ibdata files do not match the log sequence number 20889365 in the ib_logfiles!

2013-11-15 10:06:00 5908 [Note] InnoDB: Database was not shutdown normally!

2013-11-15 10:06:00 5908 [Note] InnoDB: Starting crash recovery.

2013-11-15 10:06:00 5908 [Note] InnoDB: Reading tablespace information from the .ibd files...

2013-11-15 10:06:00 5908 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace boutique/ps2_scene_lang uses space ID: 533 at filepath: .\boutique\ps2_scene_lang.ibd. Cannot open tablespace boutique/ps_badge which uses space ID: 533 at filepath: .\boutique\ps_badge.ibd

InnoDB: Error: could not open single-table tablespace file .\boutique\ps_badge.ibd

InnoDB: We do not continue the crash recovery, because the table may become

InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.

InnoDB: To fix the problem and start mysqld:

InnoDB: 1) If there is a permission problem in the file and mysqld cannot

InnoDB: open the file, you should modify the permissions.

InnoDB: 2) If the table is not needed, or you can restore it from a backup,

InnoDB: then you can remove the .ibd file, and InnoDB will do a normal

InnoDB: crash recovery and ignore that table.

InnoDB: 3) If the file system or the disk is broken, and you cannot remove

InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf

InnoDB: and force InnoDB to continue crash recovery here.