120602 11:21:07 InnoDB: The InnoDB memory heap is disabled
120602 11:21:07 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120602 11:21:07 InnoDB: Compressed tables use zlib 1.2.3
120602 11:21:07 InnoDB: Initializing buffer pool, size = 1019.0M
120602 11:21:08 InnoDB: Completed initialization of buffer pool
120602 11:21:08 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120602 11:21:08 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
120602 11:21:08 InnoDB: Assertion failure in thread 34164 in file fsp0fsp.c line 2874
InnoDB: Failing assertion: space != 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
120602 11:21:08 [ERROR] mysqld got exception 0x80000003 ;
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.

To report this bug, see http://kb.askmonty.org/en/reporting-bugs

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.

Server version: 5.5.24-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
max_threads=501
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1223068 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x0
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...
0x13fbe28e3 mysqld.exe!fsp_reserve_free_pages()[fsp0fsp.c:2874]
0x13fbe2bdd mysqld.exe!fsp_reserve_free_extents()[fsp0fsp.c:3026]
0x13fbe6045 mysqld.exe!fseg_create_general()[fsp0fsp.c:2241]
0x13fbe6291 mysqld.exe!fseg_create()[fsp0fsp.c:2328]
0x13fbdfc04 mysqld.exe!btr_create()[btr0btr.c:1356]
0x13fc099d8 mysqld.exe!dict_boot()[dict0boot.c:277]
0x13fb8b987 mysqld.exe!innobase_start_or_create_for_mysql()[srv0start.c:1890]
0x13fb7fab6 mysqld.exe!innobase_init()[ha_innodb.cc:2958]
0x13f8c3166 mysqld.exe!ha_initialize_handlerton()[handler.cc:469]
0x13f8bcae2 mysqld.exe!plugin_initialize()[sql_plugin.cc:1354]
0x13f8c1c0f mysqld.exe!plugin_init()[sql_plugin.cc:1596]
0x13f8aaf82 mysqld.exe!init_server_components()[mysqld.cc:4256]
0x13f8abbaa mysqld.exe!win_main()[mysqld.cc:4812]
0x13f8ac020 mysqld.exe!mysql_service()[mysqld.cc:5020]
0x13f8ac343 mysqld.exe!mysqld_main()[mysqld.cc:5213]
0x13fca6003 mysqld.exe!__tmainCRTStartup()[crt0.c:278]
0x76eef33d kernel32.dll!BaseThreadInitThunk()
0x77392ca1 ntdll.dll!RtlUserThreadStart()
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.