# Image corruption when loading single DICOM CT slice as Scalar Volume

**URL:** <https://discourse.slicer.org/t/image-corruption-when-loading-single-dicom-ct-slice-as-scalar-volume/47388>\
**Category:** Support\
**Tags:** segmentation, dicom, visualization, lungctanalyzer\
**Created:** [June 19, 2026, 12:32pm UTC](https://discourse.slicer.org/t/image-corruption-when-loading-single-dicom-ct-slice-as-scalar-volume/47388 "2026-06-19T12:32:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Martina\_Caro95](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/martina_caro95/32/82497_2.png) [@Martina\_Caro95](https://discourse.slicer.org/u/Martina_Caro95)\
**Post date:** [June 19, 2026, 12:32pm UTC](https://discourse.slicer.org/t/image-corruption-when-loading-single-dicom-ct-slice-as-scalar-volume/47388/1 "2026-06-19T12:32:18Z")

</div>

Hi everyone,

I am currently working on building a retrospective clinical database, extracting body composition and radiomic data from thoracic CT scans specifically at the T4 level. Our historical workflow involved exporting these single, targeted CT slices directly from our hospital PACS and importing them into 3D Slicer. In the past, this worked seamlessly. However, with the latest batch of extracted single slices, the images appear completely corrupted upon loading.

What happens is that I import the single DICOM file via the DICOM Browser. Slicer correctly indexes the patient but highlights that there is only “1 image” in the series.

1. Because standard loading fails or triggers missing-image warnings, I force the load via the `Advanced` tab → `Examine` → selecting `Scalar Volume` and clicking Load.
2. The volume loads without explicit error pop-ups, but the visualization shows a severe shearing/scrambling artifact. The pixel matrix appears completely misaligned and oblique.
3. I have already ruled out basic display issues (I applied the “Fit to window” centering and standard CT Window/Level presets, but the structural distortion remains).

Has anyone encountered this specific artifact when working with isolated single slices? Are there any recommended workarounds (e.g., switching from GDCM to DCMTK reader), or can the `DICOM Patcher` module be configured to rebuild the matrix for these orphaned slices?

Thank you in advance for your time and expertise.

 ![Screenshot of the slice viewer in the main interface. It displays the final loaded volume, showing the severe shearing/scrambling artifact where the pixel matrix appears completely oblique and unreadable.](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/1/c/1cb5c3d506253d5878c5f48024bff832f031dfe9.png)

 ![Screenshot of the Advanced "Examine" dialog box. It shows the forced loading attempt by selecting the "Scalar Volume" plugin to bypass the missing images warning.](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/2/c/2c62a2a7932372ec4d2d560e840b45bab32b20e7.png)

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [June 20, 2026, 8:01pm UTC](https://discourse.slicer.org/t/image-corruption-when-loading-single-dicom-ct-slice-as-scalar-volume/47388/2 "2026-06-20T20:01:17Z")

</div>

Looks like compressed data not being uncompressed. Did you check the logs (see Help-\>Report a bug menu).

Also you might try the latest Preview version of slicer, since it has some newer dicom codec support.