Hi, I got back to the problem yesterday and solved it today. I wanted to share the solution hoping it will inspire improvements on DVT.

Short story: pixel data on disk had a different size than advertised in the Frame Data tag (7FE0,0010).

Long story: We save our images, in DICOM format, to disk, twice. First, we save the full original image. Then, we apply enhancement filters which may involve cropping. Thing is, due to a subtle bug, the second time we saved the image, we opened the existing file in a mode which didn't write the file from scratch. Therefore, when we cropped the image, the header and cropped pixel data overwrote the original, but there was garbage left upto the end of the file. And this is what seemed to confuse DVT and the others.

A great tool which helped me diagnose this: David Clunie's dicom3tools.

The exact error message is:



I can load the image without errors using ImageJ and Sante DICOM Viewer FREE, but not using MicroDicom, so there must be something wrong with my image. I counted on DVT to tell me what...

I also tried to look at the DICOM header using DCMEditor, but it crashed similarly. I could look at the header using Sante DICOM Hexadecimal Viewer, but it's quite gruesome to find the error manually.

I'm using the latest version (2.6.6), on Windows XP SP3, 32 bits, with all the latest updates.

I tried to attach the image, but even compressed with .7z, it exceeds the 1000 K limit (it's a little over 4 MB). So I uploaded it to Mediafire, here:

http://www.mediafire.com/?p3denwo4c905iub