Hello @Babar_Qayyum ,
based on the screenshot it looks you are looking at method hotspots. There are two important points here for an interpretation of the results:
In other words - the code was waiting for input from a disk. You will need to look for the hotspots classes and methods in Method hotspots view to figure out what is really going on.
It's load test - it's fine you see purepaths errors and it's expected.
The hotspots are obvious, the code is getting file information (attributes/last modifications). You will need to browse the code to identify it. You will need to understand what the application should do and maybe the application is inefficiently doing some operations on filesystem. It's not possible to tell from the the screenshot you pasted, but definitely it's filesystem operations. It's for example possible there are just many files and the code is looping through them.
This is a screenshot from a single PurePath in Code-Level tab. Here it only shows "instrumentation points". Thus this is not visible here and you can only see the GAP.
You must look the calling code in the method hotspots. Either for this single PurePath or for a set of requests. If you have enough samples in the method hotspots, you can clearly see the stackframes and the class/method responsible for the issue.