111230 14:10:47 [Note] Plugin 'FEDERATED' is disabled.
111230 14:10:47 InnoDB: The InnoDB memory heap is disabled
111230 14:10:47 InnoDB: Mutexes and rw_locks use Windows interlocked functions
111230 14:10:47 InnoDB: Compressed tables use zlib 1.2.3
111230 14:10:47 InnoDB: Initializing buffer pool, size = 47.0M
111230 14:10:47 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file .\ibdata1 did not exist:
InnoDB: a new database to be created!
111230 14:10:47  InnoDB: Setting file .\ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
111230 14:10:47  InnoDB: Log file .\ib_logfile0 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile0 size to 24 MB
InnoDB: Database physically writes the file full: wait...
111230 14:10:48  InnoDB: Log file .\ib_logfile1 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile1 size to 24 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: 127 rollback segment(s) active.
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
111230 14:10:49  InnoDB: Waiting for the background threads to start
111230 14:10:50 InnoDB: 1.1.8 started; log sequence number 0
111230 14:10:50 [Note] Event Scheduler: Loaded 0 events
111230 14:10:50 [Note] C:\Program Files (x86)\MySQL\MySQL Server 5.5\bin\mysqld: ready for connections.
Version: '5.5.19'  socket: ''  port: 3306  MySQL Community Server (GPL)
120112  2:17:35 [Warning] IP address '61.176.223.15' could not be resolved: No such host is known. 
120112  3:20:29 [Warning] IP address '159.33.68.88' could not be resolved: No such host is known. 
120116 17:31:36 [Warning] IP address '60.6.168.160' could not be resolved: No such host is known. 
120116 17:32:01 [Warning] IP address '1.82.47.220' could not be resolved: No such host is known. 
120116 17:32:01 [Warning] IP address '119.251.67.77' could not be resolved: No such host is known. 
120116 17:32:15 [Warning] IP address '121.30.187.189' has been resolved to the host name '189.187.30.121.adsl-pool.sx.cn', which resembles IPv4-address itself.
120116 17:32:31 [Warning] IP address '60.219.215.5' could not be resolved: No such host is known. 
120116 17:32:38 - 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=26214400
read_buffer_size=65536
max_used_connections=9
max_threads=100
thread_count=8
connection_count=8
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 58326 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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...
77180390    
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.
120131 12:23:13 [Note] Plugin 'FEDERATED' is disabled.
120131 12:23:13 InnoDB: The InnoDB memory heap is disabled
120131 12:23:13 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120131 12:23:13 InnoDB: Compressed tables use zlib 1.2.3
120131 12:23:13 InnoDB: Initializing buffer pool, size = 47.0M
120131 12:23:13 InnoDB: Completed initialization of buffer pool
120131 12:23:13 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 2133303
120131 12:23:13  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...
InnoDB: Doing recovery: scanned up to log sequence number 2271193
120131 12:23:13  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 15 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
120131 12:23:14  InnoDB: Waiting for the background threads to start
120131 12:23:15 InnoDB: 1.1.8 started; log sequence number 2271193
120131 12:23:16 [Note] Event Scheduler: Loaded 0 events
120131 12:23:16 [Note] C:\Program Files (x86)\MySQL\MySQL Server 5.5\bin\mysqld: ready for connections.
Version: '5.5.19'  socket: ''  port: 3306  MySQL Community Server (GPL)
120131 12:32:20 [Warning] IP address '116.114.72.192' could not be resolved: No such host is known. 
120131 12:32:31 [Warning] IP address '112.171.128.130' could not be resolved: No such host is known. 
120131 12:32:31 [Warning] IP address '175.16.111.234' has been resolved to the host name '234.111.16.175.adsl-pool.jlccptt.net.cn', which resembles IPv4-address itself.
120131 12:32:32 [Warning] IP address '112.251.59.184' could not be resolved: No such host is known. 
120131 12:32:33 [Warning] IP address '113.9.248.108' could not be resolved: No such host is known. 
120131 12:32:33 [Warning] IP address '110.252.179.102' could not be resolved: No such host is known. 
120131 12:32:38 - 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=26214400
read_buffer_size=65536
max_used_connections=8
max_threads=100
thread_count=8
connection_count=8
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 58326 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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...
77210390    
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.
120131 12:32:38 [Warning] IP address '213.139.60.87' could not be resolved: No such host is known. 
120131 12:32:40 [Warning] IP address '111.91.80.20' has been resolved to the host name '20.snat-111-91-80.hns.net.in', which resembles IPv4-address itself.
120201  9:46:46 [Note] Plugin 'FEDERATED' is disabled.
120201  9:46:46 InnoDB: The InnoDB memory heap is disabled
120201  9:46:46 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120201  9:46:46 InnoDB: Compressed tables use zlib 1.2.3
120201  9:46:46 InnoDB: Initializing buffer pool, size = 47.0M
120201  9:46:46 InnoDB: Completed initialization of buffer pool
120201  9:46:46 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 2407870
120201  9:46:46  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...
InnoDB: Doing recovery: scanned up to log sequence number 2680714
120201  9:46:46  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 15 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
120201  9:46:47  InnoDB: Waiting for the background threads to start
120201  9:46:48 InnoDB: 1.1.8 started; log sequence number 2680714
120201  9:46:49 [Note] Event Scheduler: Loaded 0 events
120201  9:46:49 [Note] C:\Program Files (x86)\MySQL\MySQL Server 5.5\bin\mysqld: ready for connections.
Version: '5.5.19'  socket: ''  port: 3306  MySQL Community Server (GPL)
120201  9:55:15 [Warning] IP address '116.116.135.85' could not be resolved: No such host is known. 
120201  9:55:23 [Warning] IP address '113.229.55.230' could not be resolved: No such host is known. 
120201  9:55:30 [Warning] IP address '113.218.164.222' could not be resolved: No such host is known. 
120201  9:55:58 [Warning] IP address '123.157.187.64' could not be resolved: No such host is known. 
120201  9:55:58 [Warning] IP address '14.221.24.124' could not be resolved: No such host is known. 
120201  9:56:00 - 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=26214400
read_buffer_size=65536
max_used_connections=6
max_threads=100
thread_count=5
connection_count=5
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 58326 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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...
00AE1C22    
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.
120201 10:31:00 [Note] Plugin 'FEDERATED' is disabled.
120201 10:31:01 InnoDB: The InnoDB memory heap is disabled
120201 10:31:01 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120201 10:31:01 InnoDB: Compressed tables use zlib 1.2.3
120201 10:31:01 InnoDB: Initializing buffer pool, size = 47.0M
120201 10:31:01 InnoDB: Completed initialization of buffer pool
120201 10:31:01 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 2817078
120201 10:31:01  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...
InnoDB: Doing recovery: scanned up to log sequence number 2950013
120201 10:31:01  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 15 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
120201 10:31:02  InnoDB: Waiting for the background threads to start
120201 10:31:03 InnoDB: 1.1.8 started; log sequence number 2950013
120201 10:31:04 [Note] Event Scheduler: Loaded 0 events
120201 10:31:04 [Note] C:\Program Files (x86)\MySQL\MySQL Server 5.5\bin\mysqld: ready for connections.
Version: '5.5.19'  socket: ''  port: 3306  MySQL Community Server (GPL)
120201 10:31:19 [Warning] IP address '122.175.164.81' could not be resolved: No such host is known. 
120201 10:31:23 [Warning] IP address '119.115.233.128' could not be resolved: No such host is known. 
120201 10:31:32 [Warning] IP address '117.92.109.234' could not be resolved: No such host is known. 
120201 10:31:39 [Warning] IP address '121.16.138.90' could not be resolved: No such host is known. 
120201 10:31:40 [Warning] IP address '124.166.94.226' has been resolved to the host name '226.94.166.124.adsl-pool.sx.cn', which resembles IPv4-address itself.
120201 10:31:48 [Warning] IP address '112.245.38.142' could not be resolved: No such host is known. 
120201 10:32:02 - 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=26214400
read_buffer_size=65536
max_used_connections=6
max_threads=100
thread_count=6
connection_count=6
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 58326 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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...
75DD0390    
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.
120201 11:27:59 [Note] Plugin 'FEDERATED' is disabled.
120201 11:27:59 InnoDB: The InnoDB memory heap is disabled
120201 11:27:59 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120201 11:27:59 InnoDB: Compressed tables use zlib 1.2.3
120201 11:27:59 InnoDB: Initializing buffer pool, size = 47.0M
120201 11:27:59 InnoDB: Completed initialization of buffer pool
120201 11:27:59 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 3084684
120201 11:27:59  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...
InnoDB: Doing recovery: scanned up to log sequence number 3491260
120201 11:28:00  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 15 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
120201 11:28:01  InnoDB: Waiting for the background threads to start
120201 11:28:02 InnoDB: 1.1.8 started; log sequence number 3491260
120201 11:28:02 [Note] Event Scheduler: Loaded 0 events
120201 11:28:02 [Note] C:\Program Files (x86)\MySQL\MySQL Server 5.5\bin\mysqld: ready for connections.
Version: '5.5.19'  socket: ''  port: 3306  MySQL Community Server (GPL)
120201 11:28:35 [Warning] IP address '180.126.63.209' could not be resolved: No such host is known. 
120201 11:28:51 [Warning] IP address '119.49.167.31' has been resolved to the host name '31.167.49.119.adsl-pool.jlccptt.net.cn', which resembles IPv4-address itself.
120201 11:29:00 [Warning] IP address '112.250.184.171' could not be resolved: No such host is known. 
120201 11:29:21 [Warning] IP address '115.242.201.139' could not be resolved: No such host is known. 
120201 11:29:25 [Warning] IP address '118.186.202.203' could not be resolved: No such host is known. 
120201 11:29:30 [Warning] IP address '180.126.26.122' could not be resolved: No such host is known. 
120201 11:29:34 [Warning] IP address '111.67.207.82' could not be resolved: The requested name is valid, but no data of the requested type was found. 
120201 11:29:41 - 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=26214400
read_buffer_size=65536
max_used_connections=11
max_threads=100
thread_count=10
connection_count=10
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 58326 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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...
100011CC    
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.
120201 11:48:47 [Note] Plugin 'FEDERATED' is disabled.
120201 11:48:47 InnoDB: The InnoDB memory heap is disabled
120201 11:48:47 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120201 11:48:47 InnoDB: Compressed tables use zlib 1.2.3
120201 11:48:47 InnoDB: Initializing buffer pool, size = 47.0M
120201 11:48:47 InnoDB: Completed initialization of buffer pool
120201 11:48:47 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 3625882
120201 11:48:47  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...
InnoDB: Doing recovery: scanned up to log sequence number 3896384
120201 11:48:48  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 15 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
120201 11:48:49  InnoDB: Waiting for the background threads to start
120201 11:48:50 InnoDB: 1.1.8 started; log sequence number 3896384
120201 11:48:50 [Note] Event Scheduler: Loaded 0 events
120201 11:48:50 [Note] C:\Program Files (x86)\MySQL\MySQL Server 5.5\bin\mysqld: ready for connections.
Version: '5.5.19'  socket: ''  port: 3306  MySQL Community Server (GPL)
120201 11:49:13 [Warning] IP address '124.116.105.216' has been resolved to the host name '216.105.116.124.broad.hz.sn.dynamic.163data.com.cn', which resembles IPv4-address itself.
120201 11:49:16 [Warning] IP address '113.125.233.9' could not be resolved: No such host is known. 
120201 11:49:23 [Warning] IP address '180.123.164.205' could not be resolved: No such host is known. 
120201 11:49:43 - 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=26214400
read_buffer_size=65536
max_used_connections=5
max_threads=100
thread_count=5
connection_count=5
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 58326 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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...
00000000    
76930D14    
76930807    
769302D9    
769290C7    
77110816    WaitForSingleObjectEx()
77110849    WaitForSingleObjectEx()
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.
120201 11:49:45 [Warning] IP address '219.129.237.71' could not be resolved: No such host is known. 
120210 15:56:53 [Note] Plugin 'FEDERATED' is disabled.
120210 15:56:54 InnoDB: The InnoDB memory heap is disabled
120210 15:56:54 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120210 15:56:54 InnoDB: Compressed tables use zlib 1.2.3
120210 15:56:54 InnoDB: Initializing buffer pool, size = 47.0M
120210 15:56:54 InnoDB: Completed initialization of buffer pool
120210 15:56:54 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!
120210 15:56:54  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...
120210 15:56:54  InnoDB: Waiting for the background threads to start
120210 15:56:55 InnoDB: 1.1.8 started; log sequence number 4165503
120210 15:56:56 [Note] Event Scheduler: Loaded 0 events
120210 15:56:56 [Note] C:\Program Files (x86)\MySQL\MySQL Server 5.5\bin\mysqld: ready for connections.
Version: '5.5.19'  socket: ''  port: 3306  MySQL Community Server (GPL)
120210 16:06:49 [Warning] IP address '110.73.165.34' could not be resolved: No such host is known. 
120210 16:06:56 [Warning] IP address '116.30.192.54' could not be resolved: No such host is known. 
120210 16:07:03 [Warning] IP address '110.242.130.173' could not be resolved: No such host is known. 
120210 16:07:07 [Note] Hostname 'OS1' does not resolve to '113.191.252.28'.
120210 16:07:07 [Note] Hostname 'OS1' has the following IP addresses:
120210 16:07:07 [Note]  - fe80::24c3:20d0:36c9:f357%14

120210 16:07:07 [Note]  - fe80::1c2a:2c31:8951:f184%12

120210 16:07:07 [Note]  - 2002:76ae:e7b::76ae:e7b

120210 16:07:07 [Note]  - 118.174.14.123

120210 16:07:07 [Note]  - 2001:0:4137:9e76:1c2a:2c31:8951:f184

120210 16:07:33 [Warning] IP address '221.208.32.12' could not be resolved: No such host is known. 
120210 16:08:21 [Warning] IP address '113.106.101.45' could not be resolved: No such host is known. 
120210 16:08:23 - 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=26214400
read_buffer_size=65536
max_used_connections=7
max_threads=100
thread_count=6
connection_count=6
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 58326 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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...
75C10390    
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.