MySQL Crash (1 reply)

I simply tried to download phpMyAdminon and tried to start Apache and mySQL servers, however I was unable to start mySQL (Apache runs). I downloaded Currports to try to clear any application that would use the same ports, like Skype. However, I am still running into issues- here are my logs. I'd appreciate any help!


2018-11-12 21:42:40 8396 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-11-12 21:42:40 8396 [Note] InnoDB: The InnoDB memory heap is disabled
2018-11-12 21:42:40 8396 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-11-12 21:42:40 8396 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-11-12 21:42:40 8396 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-11-12 21:42:40 8396 [Note] InnoDB: Using generic crc32 instructions
2018-11-12 21:42:40 8396 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-11-12 21:42:40 8396 [Note] InnoDB: Completed initialization of buffer pool
2018-11-12 21:42:40 8396 [Note] InnoDB: Restoring page 0 of tablespace 0
2018-11-12 21:42:40 8396 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2018-11-12 21:42:40 8396 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\xampp\mysql\data\ibdata1
2018-11-12 21:42:40 8396 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2018-11-12 21:42:40 8396 [ERROR] Plugin 'InnoDB' init function returned error.
2018-11-12 21:42:40 8396 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2018-11-12 21:42:40 8396 [Note] Plugin 'FEEDBACK' is disabled.
2018-11-12 21:42:40 8396 [ERROR] Unknown/unsupported storage engine: InnoDB
2018-11-12 21:42:40 8396 [ERROR] Aborting