boot up problem 0x24 in vista

hello,

I have been searching for answers for weeks but cannot find any. I finally
decided to post my problem, hoping that any of you can help me. When reading
this consider I am a noob and would appreciate any serious help.

I am running a dual boot system with vista/ubuntu7.04 that until recently
worked fine. But all of a sudden I lost acces to my vista partition while
using ubuntu. When I later rebooted and tried to boot vista I just got an
endless loop of reboots. The last file to load before rebooting is the
crcdisk.sys. Manually preventing reboots I got this Blue Screen message:

A problem has been detected and windows has been shutdown to prevent damage
to your computer.

If this is the first time you have seen this stop error screen, restart your
computer. If this screen appears again, follow these steps:

Disable or uninstall any anti-virus, disk defragmentation or backup
utilities. Check your hard drive configuration, and check for any update
drivers. Run CHKDSK /F to check for hard drive corruption, and then restart
your computer.

Technical information:

*** STOP: 0x00000024 (0x00190445,0x860A2150,0xc0000102,0x00000000)

I tried chkdsk. It finds no errors and corrects nothing. My ubuntu
instalation complains that the ntfs-logfile is unclean.
I can mount it as readonly in ubuntu though. I can that way access all the
files, but I cannot change anything in them from there.
The MBR and partition tables are ok according to testdisk.
I've tried bootrec /scanos from the vista disks the factory sent me (vista
was preinstalled), but it doesn't find any windows os on the hard drive. I've
tried activating the partiotion using supergrubdisk, but I still recieve the
same error message?

Is there anyone that know something about this particular scenario? I am not
very experienced so I might ask some dumb cuestion. But I rather be safe then
sorry.

I can reinstall Vista, but I'd rather not since it reformats the whole
harddisk to its original state. All files are still there and no search tool
I have used can find any hardware problem either, so I believe this could be
solved somehow.

Any help greatly appreciated.