You will need to work with your application developers to figure out what their code is doing.
See this post.
https://learn.microsoft.com/en-us/answers/questions/1468684/high-cpu-usage-about-w3wp-exe
Look at the screen images for "On a running system. monitor currently executing requests". You will need to use the IIS management console to see if you have long running HTTP requests. Show that to your programmers and ask them to investigate the page.
You should also examine your IIS logs and look for errors and also at the Time-Taken field for long running requests.
If you can't find the root cause, then you next best bet is get a memory dump of the w3wp.exe process and analyze it with DebugDiag. You do not have to install DebugDiag on your web server, but it should be installed on a machine that has access to the internet so that the debug symbols can be downloaded from Microsoft.
https://www.bing.com/search?pglt=41&q=how+to+use+debug+diag+to+troubleshoot+a+memory+leak