200519 14:27:55 [ERROR] Table .\bitrix_57\b_admin_notify has no primary key in

Question

200519 14:27:55 [ERROR] Table .\bitrix_57\b_admin_notify has no primary key in

InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.
200519 14:27:55 [Warning] Table .\bitrix_57\b_admin_notify key_used_on_scan is 0 even though there is no primary key inside InnoDB.
200519 14:27:55 [ERROR] Innodb could not find key n:o 0 with name PRIMARY from dict cache for table bitrix_57/b_admin_notify
11:27:56 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=26214400
read_buffer_size=2097152
max_used_connections=1
max_threads=30
thread_count=1
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 117953 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0xe28eea0
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...
5cec94 mysqld.exe!?check_next_symbol@Gis_read_stream@@QAE_ND@Z()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (e2c7af8): SHOW TABLE STATUS FROM `bitrix_57`Connection ID (thread ID): 3
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.

c:\openserver\ospanel\modules\database\MySQL-5.1>PAUSE