120925  8:35:05 [Note] Plugin 'FEDERATED' is disabled.
120925  8:35:05 InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!!
120925  8:35:05 InnoDB: !!!!!!!! UNIV_SYNC_DEBUG switched on !!!!!!!!!
120925  8:35:05 InnoDB: The InnoDB memory heap is disabled
120925  8:35:05 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120925  8:35:05 InnoDB: Compressed tables use zlib 1.2.3
120925  8:35:05 InnoDB: CPU does not support crc32 instructions
120925  8:35:05 InnoDB: Initializing buffer pool, size = 128.0M
120925  8:35:05 InnoDB: Completed initialization of buffer pool
120925  8:35:05 InnoDB: highest supported file format is Barracuda.
120925  8:36:01 InnoDB: 128 rollback segment(s) are active.
120925  8:36:01 [Note] InnoDB: Creating tablespace and datafile system tables.

120925  8:36:01 [Note] InnoDB: Tablespace and datafile system tables created

120925  8:36:01 InnoDB: Waiting for the background threads to start
120925  8:36:01 InnoDB: 1.2.6 started; log sequence number 105218975104
120925  8:36:01 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 46296ed7-06db-11e2-aa3b-c860005a3177.
120925  8:36:01 [Note] Server hostname (bind-address): '*'; port: 3356
120925  8:36:01 [Note]   - '::' resolves to '::';
120925  8:36:01 [Note] Server socket created on IP: '::'.
06:36:01 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=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=200
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 = 87454 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x16e9e9a0
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...
13fc1b28d    mysqld-debug.exe!Field::val_str()[field.h:634]
13fd7f312    mysqld-debug.exe!get_field()[table.cc:2898]
13fcaf566    mysqld-debug.exe!acl_load()[sql_acl.cc:1193]
13fcae822    mysqld-debug.exe!acl_reload()[sql_acl.cc:1607]
13fcae015    mysqld-debug.exe!acl_init()[sql_acl.cc:970]
13fb67ad1    mysqld-debug.exe!win_main()[mysqld.cc:5292]
13fb6b627    mysqld-debug.exe!mysql_service()[mysqld.cc:5479]
13fb6bab0    mysqld-debug.exe!mysqld_main()[mysqld.cc:5672]
13fb61034    mysqld-debug.exe!main()[main.cc:26]
1406538e7    mysqld-debug.exe!__tmainCRTStartup()[crt0.c:266]
1406537ee    mysqld-debug.exe!mainCRTStartup()[crt0.c:182]
76d4652d    kernel32.dll!BaseThreadInitThunk()
76e7c521    ntdll.dll!RtlUserThreadStart()

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.