Apache 2.2.4 + SSPI + SVN 1.4.3: Problems with Committing word docs & jsp file

I met with this really strange problems that I was hoping that someone can
help to give some
suggestions on how can I resolve it.
(1) I have setup subversion 1.4.3 with apache 2.2.4 with SSPI module for
windows domain authentication
(2) I have a repository that is being accessed by a team for developer

Everyone in the team except me have problems with committing word docs & jsp
file into the
repository. The client that we used is TortoriseSVN 1.4.3. I can checkout,
update, commit other files,
just not word docs and jsp file. The error that I get when I commit word
file or jsp file from TortoriseSVN
is as follow:

Error: Commit failed (details follow):
Error: PUT of
'/svn/!svn/wrk/8f8ec37f-90d5-174b-8529-c755bd6e931a/cors/trunk/Documents/Project%20Management/CORS-
Registration-Bidding-Schedule-for-2007-2008-Sem-2.doc': Could not read
status line: An existing connection was forcibly closed by the remote
host. (http://cors-xenon)

Here is a snapshots of my apache log when I tried to commit the same word
file:
access.log:
[10/Apr/2007:14:08:55 +0800] "OPTIONS
/svn/cors/trunk/Documents/Project%20Management HTTP/1.1" 200 183
[10/Apr/2007:14:08:55 +0800] "MKACTIVITY
/svn/!svn/act/bfcb46b6-cdad-7640-ba7a-dc2c47416f7b HTTP/1.1" 201 222
[10/Apr/2007:14:08:55 +0800] "PROPFIND
/svn/cors/trunk/Documents/Project%20Management HTTP/1.1" 207 464
[10/Apr/2007:14:08:55 +0800] "PROPFIND /svn/!svn/vcc/default HTTP/1.1" 207
389
[10/Apr/2007:14:08:55 +0800] "CHECKOUT /svn/!svn/bln/71 HTTP/1.1" 201 237
[10/Apr/2007:14:08:55 +0800] "PROPPATCH
/svn/!svn/wbl/bfcb46b6-cdad-7640-ba7a-dc2c47416f7b/71 HTTP/1.1" 207 349
[10/Apr/2007:14:08:55 +0800] "PROPFIND
/svn/cors/trunk/Documents/Project%20Management HTTP/1.1" 207 457
[10/Apr/2007:14:08:55 +0800] "CHECKOUT
/svn/!svn/ver/1/cors/trunk/Documents/Project%20Management/CORS-
Registration-Bidding-Schedule-for-2007-2008-Sem-2.doc HTTP/1.1" 201 335
[10/Apr/2007:14:08:55 +0800] "PUT
/svn/!svn/wrk/bfcb46b6-cdad-7640-ba7a-dc2c47416f7b/cors/trunk/Documents/Project%20Management/CORS-
Registration-Bidding-Schedule-for-2007-2008-Sem-2.doc HTTP/1.1" 204 -
[10/Apr/2007:14:08:55 +0800] "PUT
/svn/!svn/wrk/bfcb46b6-cdad-7640-ba7a-dc2c47416f7b/cors/trunk/Documents/Project%20Management/CORS-
Registration-Bidding-Schedule-for-2007-2008-Sem-2.doc HTTP/1.1" 500 419
[10/Apr/2007:14:08:56 +0800] "DELETE
/svn/!svn/act/bfcb46b6-cdad-7640-ba7a-dc2c47416f7b HTTP/1.1" 204 -

error.log:
[Tue Apr 10 14:08:55 2007] [error] [client 172.20.166.69] Unable to PUT new
contents for
/svn/!svn/wrk/bfcb46b6-cdad-7640-ba7a-dc2c47416f7b/cors/trunk/Documents/Project
Management/CORS-Registration-Bidding-Schedule-for-2007-2008-Sem-2.doc.
[403, #0]
[Tue Apr 10 14:08:55 2007] [error] [client 172.20.166.69] Could not prepare
to write the file [500, #200014]
[Tue Apr 10 14:08:55 2007] [error] [client 172.20.166.69] Base checksum
mismatch on '/cors/trunk/Documents/Project Management/CORS-
Registration-Bidding-Schedule-for-2007-2008-Sem-2.doc':\n expected:
50a51fbc5d898cf359189fa30c5002ce\n actual:
f8266d3702779d33d09a8ce540740ce6\n [500, #200014]

My apache configuration file:
<Location /svn>
  DAV svn
  SVNPath "D:/svnRepo"
  AuthName "NUS CORS Subversion Login [Please use your NUSNET id
(NUSSTF\XXXXX) & password]"
  AuthType SSPI
  SSPIAuth On
  SSPIAuthoritative On
  SSPIOfferBasic On
  SSPIOmitDomain Off
  SSPIUsernameCase lower
  require group nusstf\CCECORSDevelopmentTeam
</Location>

The same thing goes when I did a commit on jsp file. I tried setting up the
SVN on another machine
and experience the same problem despite it being a clean setup. What really
puzzled me is everyone else
in my team is not affected but me.

I also tried to download another SVN client to try but in vain.
As a last resort, I deleted all my working copy, uninstall all my SVN
clients and
did a reinstallation and recheckout again but the same problem still
persisted.

I spend almost for the last 3 days looking for solutions via SVN users
mailing list and googling
but in vain.

Really like to find out what is the cause of this problem. Anyone can give
me some suggestions on
what to do next would be much appreciated. Thanks in advance.

-- 
  Jenson Goh