Although I have googled this, I can't seemed to find any real explanation except that it is a know fault and it is fixed with SQL 2005 Service Pack 3.
I applied SQL SERVER 2003 SP2 and SQL 2005 SP3 over last weekend, however, this morning it ran away again.
I can get round it, short term, by first restarting the SQL service and then issuing the following command:
ALTER DATABASE [database name]MODIFY FILE ( NAME = N'[database name]_dat', FILEGROWTH = 100mb)
This gets round it as I said but after a while, off it goes.
The database is very large, some 350gb and when the problems occur it takes up all of the 750gb space made available for it.
Can anyone throw any more light on this please?