It's possible there is corrupt data in the images - so maybe saving to different file format would help.
However, tiff or psd are just fine for InDesign.
I don't really see what the problem is with 2.
And with 3 - is that with InDesign? As InDesign only shows a lo-res proxy of the image.
If it's PDF - what were your PDF settings?
And InDesign check the Window>Info and select a problem image - see what it says for Actual and Effective - effective is the resolution it is when scaled.
It could be a hardware failure, most likely the RAM or the drive or the connection to it. Does it happen on different computers?
If it happens on different computer, are the files saved on the same place in the network?
In Issue 2, horizontal green color shading is crossing above the play/pause icon in right hand side of the image.
In Issue 3, I have displayed the screenshot of the image placed in InDesign to show the original view of the image. But the problem shows in right hand side that is pdf output view. You can see the horizontal green color shading in 1st image and light grey color shading (at the top of "NO" text) in 2nd image.
Actual & Effective PPi of top of the image --> 597
Actual & Eff. PPI of bottom of the image --> 477
PS to pdf creation:
Crops & bleeds ON, Composite CMYK color output, Image data: All, Postscript: Level3, Data format: Binary, Printer profile: Document CYMK-US. web coated
If you need more details, I'm ready to give you. Please let me know.
@Willi: Recently we migrated the Mac os to 10.7.5 version. It happens in different computers and the files are saved in different place in a server.
Did you experience the same kind of issue due to network problem?
Do you mean you migrated the software from one Mac to another one? YOu should install it instead.
But if you save the images on the same server (doesn't matter if they are on different places), you should check the server and its connection to the network.
Does the same issue happen if you save everything locally?
@Willi: We upgraded the Mac os to higher version. Sorry for the word used migration.
We could test in different cases if the error is reproducible. It happens in different titles but in rare cases. Still we don't know when it will happen again. The cases were happened in thrice for the past two months.
We really need a permanent solution for this. Please suggest.
I am pretty sure that we have here a hardware problem. That is why I would ask, if you encounter the problem also, if you work locally. (But check if none of the file used locally has the problem inherited.)
Did you get the same problem in export pdf?