A philips remote service engineer (rse) received email from a philips field service engineer (fse) on the behalf of the customer.In the email, the customer confirmed that the central monitoring was down for approximately one hour.The customer informed that the system big server was updated to 4.2 on (b)(6) 2022.On (b)(6) 2024 there was a failure in the cardio system and this time, it was on station w43a which was installed approx.3 to 4 weeks ago.At around 11:40 am, the customer tried to log in to the configuration but it did not work.The mouse clicks were unsuccessful followed by screen freeze.The customer waited for about 2 minutes and then did a hard reset.The customer requested to look in the logs to see if anything stood out.The customer had about 500 beds on the system so far, and another 200 would be added.The logs were checked and failure confirmed.The information collected about the outage was provided to the factory for further investigation and the case was escalated.A philips product specialist engineer (pse) identified the unhandled exception, which caused philips.Ix.Databridgehost to fail and subsequently also philips.Pmp.Dbenginehost.Exe to fail.The system was not able to recover and was restarted forcefully at 2:24.The logs were provided to philips r&d for further investigation and to identify cause of the fail.Based on the investigation by philips research and development team (r&d), the issue was caused due to memory corruption either at the operating system (os) or in the memory hardware.There was also a less likely chance that it could be the cpu registers.The points of failure for the various processes were all in hash code generation, which was not something that philips control for most objects in memory.Philips had a similar case last year, where finally a cpu replacement solved the reported issue.The pse recommended the customer to monitor the box.If the error or similar issue occurred again, the pse requested the customer to replace the hardware which would be cpu & memory.The cause of the reported problem was due to memory corruption either at the operating system (os) or in the memory hardware.The reported problem was confirmed.The engineer provided information to the customer to resolve the reported issue.510 k is corrected to k211900.
|