Thanks for sharing your thought, SQLRNNR.

While we will do a IO/memory check on the weekend, I cannot do too many things at the moment I believe.

Through the research the affected object is not a fatal error so at the moment all services and client databases are running smoothly.

But since it is a abrand new instance, we prefer to set it up with 0 error.

I may need to try some other methods to narrow down the error causes.