MySQL startet nicht

[felix2014]

Hallo zusammen,
vielleicht kann mir jemand helfen.
Ich habe xampp-portable-win32-1.8.3-5-VC11.7z heruntergeladen und auf der Festplatte installiert.
Danach die Datei setup_xampp aufgerufen.
Danach xampp_control Panel gestartet und die Module Apache und MySQL gestartet, welches ohne Fehlermeldung geschah (grüne Hintergrundfarbe).
Apache: PID (6768/6492) Port (80/443);
MySQL: PID 5716 Port 3306;

Beim Aufruf des XAMPP - Status erscheint MySQL-Datenbank deaktiviert.
(leider kein Zugriff )
Wie Ihr aus der Beschreibung ersehen könnt, bin ich kein Profi
Ich hoffe, dass die Informationen ausreichten.
(Betriebssystem Windows 8.1)

Die log-Datei hat folgenden Inhalt (ähnlich wie einige andere):
2014-10-08 10:39:07 7372 [Note] Plugin 'FEDERATED' is disabled.
2014-10-08 10:39:07 1138 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.
2014-10-08 10:39:07 7372 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-10-08 10:39:07 7372 [Note] InnoDB: The InnoDB memory heap is disabled
2014-10-08 10:39:07 7372 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-10-08 10:39:07 7372 [Note] InnoDB: Memory barrier is not used
2014-10-08 10:39:07 7372 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-10-08 10:39:07 7372 [Note] InnoDB: Not using CPU crc32 instructions
2014-10-08 10:39:07 7372 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-10-08 10:39:07 7372 [Note] InnoDB: Completed initialization of buffer pool
2014-10-08 10:39:07 7372 [Note] InnoDB: Highest supported file format is Barracuda.
2014-10-08 10:39:07 7372 [Note] InnoDB: 128 rollback segment(s) are active.
2014-10-08 10:39:07 7372 [Note] InnoDB: Waiting for purge to start
2014-10-08 10:39:07 7372 [Note] InnoDB: 5.6.20 started; log sequence number 1665234
2014-10-08 10:39:07 7372 [Note] Server hostname (bind-address): '*'; port: 3306
2014-10-08 10:39:07 7372 [Note] IPv6 is available.
2014-10-08 10:39:07 7372 [Note] - '::' resolves to '::';
2014-10-08 10:39:07 7372 [Note] Server socket created on IP: '::'.
Vielen Dank für Eure Mühe

[xcipx]

I have also a problem while starting MySQL:

InnoDB: Doing recovery: scanned up to log sequence number 1595924
2014-10-09 07:46:43 6436 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
2014-10-09 07:46:43 6436 [Note] InnoDB: 128 rollback segment(s) are active.
2014-10-09 07:46:43 6436 [Note] InnoDB: Waiting for purge to start
2014-10-09 07:46:43 6436 [Note] InnoDB: 5.6.20 started; log sequence number 1595924
2014-10-09 07:46:43 6436 [Note] Server hostname (bind-address): '*'; port: 3306
2014-10-09 07:46:43 6436 [Note] IPv6 is available.
2014-10-09 07:46:43 6436 [Note] - '::' resolves to '::';
2014-10-09 07:46:43 6436 [Note] Server socket created on IP: '::'.
04:46:43 UTC - mysqld got exception 0xc0000005 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133778 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x1b420dc8
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
111eaa3 mysqld.exe!?get_field@@YAPADPAUst_mem_root@@PAVField@@@Z()
10caef9 mysqld.exe!?init@ACL_PROXY_USER@@QAEXPAUTABLE@@PAUst_mem_root@@@Z()
10cbbda mysqld.exe!?acl_reload@@YADPAVTHD@@@Z()
10cf69f mysqld.exe!?acl_init@@YAD_N@Z()
10226f8 mysqld.exe!?win_main@@YAHHPAPAD@Z()
1022a37 mysqld.exe!?mysql_service@@YAHPAX@Z()
14ae48a mysqld.exe!my_mb_ctype_mb()
75ae338a kernel32.dll!BaseThreadInitThunk()
77de9f72 ntdll.dll!RtlInitializeExceptionChain()
77de9f45 ntdll.dll!RtlInitializeExceptionChain()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 0
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.


can someone assist?