Yes, its possible for there to be more than one valid hash. I don't know what the mathematical probability of this is, but if you were to exhaust the entire nonce spectrum, there are likely to be several valid blocks. Most blocks, however, stop when they get a valid hash, so it seldom is an issue. Though occasionally, two miners might come up with different valid hashes at the same time, and this results in one of them being rejected.
As for a collision, well, that's effectively impossible. First, yes, it's possible that the same hash could be found for two different blocks, but that's not a collision. It's also highly unlikely. Unlikely to the point of there being no point in dealing with it.
Yes, it could screw up certain software that assumes hashes are indexable and unique, but it shouldn't really be an issue for the blockchain itself to have duplicate hashes.
The only real "collision" would be if an attacker were trying to come up with his own block of transactions, with the same parent that would somehow hash to the same value and trying to "take over" the other block, and that is astronomically unlikely to the point of absurdity.
What do you mean by "for the same block"? A block has one, and only one, hash, which is the hash of that block. – David Schwartz – 2017-07-11T00:18:54.480
related: How can we be sure that a new block will be found?
– Murch – 2017-07-11T04:15:26.567There is slight confusion in the question. The nonce is a part of the block. So, a given block will have only 1 hash. If you mean, can there be different nonces such that block hash is different but still meets the difficulty, then yes. – sanket1729 – 2017-07-11T05:41:44.613