Failure of openSSH service (windows)

[MICHOUX Emmanuel]

Hello,
I have a problem with the OpenSsh services which fails, but I don't find the reasons of these regular failuresI need help for reading the logs inserted below

I have several SSH connexions between :- a File Server in which the Ssh server based on OpenSsh 6.6.1p1-3(Windows 2008 SP2 64bits)  has been installed,- a Ssh client OpenSsh 4.3P2, installed on a SANTOS Linux distribution, 
- others Ssh clients based on OpenSsh 6.2p2-1(Windows 2008 SP2 64bits)
Note : The problem was also present with the version setupssh-6.2p2-1-v1.exe, which have been 
firstly installed on my File server
my configuration is based on RSA authentification (sshd_config attached)
I have also changed the following parameters, but without any successLoginGraceTimeThe server disconnects after this time if the user hasnotsuccessfully logged in. If the value is 0, there is no time limit.Thedefault is 600 (seconds).LoginGraceTime 30  KeepAliveSpecifies whether the system should send keepalive messages to theotherside. If they are sent, death of the connection or crash of oneof the machineswill be properly noticed. However, this means thatconnections will die if theroute is down temporarily, and some peoplefind it annoying. On the other hand,if keepalives are not send,sessions may hang indefinitely on the server,leaving "ghost" usersand consuming server resources.               he default is"yes" (to send keepalives), and the server will noticeif the networkgoes down or the client host reboots. This avoidsinfinitely hangingsessions.KeepAlive yes  ClientAliveCountMax – This indicates the total number of checkalive message sent by the sshserver without getting any response from the ssh client. Default is 3.ClientAliveCountMax  0  ·  ClientAliveInterval – This indicates the timeout in seconds. After x numberof seconds, ssh server will send a message to the client asking for response.Deafult is 0 (server will not send message to client to check.).ClientAliveInterval10 
It's seems it's the linux client (IP : 192.168.32.30 ) which provokes the failure of the OpenSsh service on my File Server?

In my EventViewer, I have the logs : 

(PRESENT)
sshd: PID 5236: debug1: attempt 1 failures 0
sshd: PID 5236: debug2: input_userauth_request: try method publickey
sshd: PID 5236: debug3: userauth_finish: failure partial=0 next methods="publickey,password,keyboard-interactive
sshd: PID 5236: debug1: userauth_send_banner: sent
sshd: PID 5236: debug2: input_userauth_request: try method none
sshd: PID 5236: debug1: userauth-request for user operateur service ssh-connection method publickey
sshd: PID 5236: debug1: test whether pkalg/pkblob are acceptable
sshd: PID 5236: debug1: temporarily_use_uid: 1000/513 (e=500/513)
sshd: PID 4604: debug3: session_unused: session id 0 unused
sshd: PID 4604: debug1: do_cleanup
sshd: PID 4604: debug3: channel 0: status: The following connections are open:\r\n  #0 server-session (t4 r619955 i3/0 o3/0 fd -1/-1 cc -1)\r\n
sshd: PID 4604: debug1: session_close: session 0 pid 3864
sshd: PID 4604: Transferred: sent 5328, received 687736 bytes
sshd: PID 5236: debug2: parse_server_config: config reprocess config len 442
sshd: PID 5236: debug2: input_userauth_request: setting up authctxt for operateur
sshd: PID 4604: Closing connection to 10.101.8.2 port 2388

OpenSSHd: PID 2340: service `OpenSSHd' failed: signal 11 raised

sshd: PID 5248: debug2: channel 0: close_read
sshd: PID 5248: debug2: channel 0: input open -> drain
sshd: PID 5248: debug2: channel 0: read failed
sshd: PID 5248: debug2: notify_done: reading
sshd: PID 5248: debug2: channel 0: read<=0 rfd 8 len 0
sshd: PID 5248: debug2: channel 0: ibuf empty
sshd: PID 5248: debug3: channel 0: will not send data after close
sshd: PID 5248: debug2: channel 0: rcvd close
sshd: PID 5248: debug2: channel 0: send close
sshd: PID 5248: debug2: channel 0: send eof
sshd: PID 5248: debug2: channel 0: input drain -> closed
sshd: PID 5248: debug2: channel 0: request exit-status confirm 0
sshd: PID 5248: debug1: session_exit_message: release channel 0
sshd: PID 5248: debug1: session_exit_message: session 0 channel 0 pid 3080
sshd: PID 5248: debug1: Received SIGCHLD.
sshd: PID 5248: debug1: session_by_pid: pid 3080
sshd: PID 5248: debug2: channel 0: write failed
sshd: PID 5248: debug2: channel 0: read 0 from efd 10
sshd: PID 5248: debug2: channel 0: closing read-efd 10
sshd: PID 5248: debug2: channel 0: output open -> closed
sshd: PID 5248: debug2: channel 0: close_write
sshd: PID 5248: debug2: channel 0: send eow
sshd: PID 5248: Transferred: sent 430056, received 2368 bytes
sshd: PID 5248: Closing connection to 192.168.32.30 port 56963
sshd: PID 5248: debug1: do_cleanup
sshd: PID 5248: debug3: channel 0: status: The following connections are open:\r\n  #0 server-session (t4 r0 i3/0 o3/0 fd -1/-1 cc -1)\r\n
sshd: PID 5248: Connection closed by 192.168.32.30
sshd: PID 4604: debug2: channel 0: window 1998376 sent adjust 98776
sshd: PID 4604: debug2: channel 0: window 1966472 sent adjust 130680
sshd: PID 4604: debug2: channel 0: rcvd close
sshd: PID 4604: debug2: channel 0: window 1966472 sent adjust 98010
sshd: PID 4604: debug2: channel 0: window 1966472 sent adjust 130680(PAST)
regardsEmmanuel