BUG #7595: terminate process in an unusual way

The following bug has been logged on the website:

Bug reference: 7595
Logged by: seowoong kim
Email address: hikkis21c(at)hotmail(dot)com
PostgreSQL version: 9.1.3
Operating system: windows 7 (x64)
Description:

hi

I'm using postgreSQL 9.1.3 version.

there's some problem with connect to database and I knew after process
recovery. this problem solved after restart computer
after I saw postgresql's log
postgresql.conf file was default

this is log file's information
at first

I got this error

2012-10-10 16:01:55 KST PANIC: could not write to log file 4, segment 232
at offset 15237120, length 16384: Invalid argument
this time it was doing usual operation

after this
This application has requested the Runtime to terminate it in an unusual
way.
Please contact the application's support team for more information.

2012-10-10 16:01:55 KST LOG: server process (PID 1870880) exited with exit
code 3
2012-10-10 16:01:55 KST LOG: terminating any other active server processes
this comment printed

and until database recovery
2012-10-10 16:01:57 KST FATAL: the database system is in recovery mode
this message printed continuously

recovery message is this

2012-10-10 16:37:35 KST LOG: database system was interrupted; last known up
at 2012-10-10 16:00:51 KST
2012-10-10 16:37:35 KST LOG: database system was not properly shut down;
automatic recovery in progress
2012-10-10 16:37:35 KST LOG: redo starts at 4/E8E1E868
2012-10-10 16:37:35 KST LOG: record with zero length at 4/E8E89EE0
2012-10-10 16:37:35 KST LOG: redo done at 4/E8E89EA0
2012-10-10 16:37:35 KST LOG: last completed transaction was at log time
2012-10-10 16:01:54.795+09
2012-10-10 16:37:35 KST LOG: database system is ready to accept
connections

I'm just wondering what kind of problem is this and if this problem happen
again how I recover process without restart computer.