The only difference was the day and time and the user ID used for the Remote desktop session.Īny insight would be greatly appreciated. It is interesting to note that I had run this on the same server for 3.5 hours without issue as a test. I use Sysinternals ProcMon quite a bit, and its a great tool, but Id like to be able to run it silently - no UI. Process Monitor is started with this command from a bat file in a remote desktop session: start E:\ProcessMonitor\Procmon64.exe /BackingFile G:\ProcMonLogs\\%logdir%\CS-DLY-LS-SUNDAY.PML /AcceptEula /Profiling /Quiet /NoFilter Hey folks, looking for some special Powershell help, if possible. Click yes on prompt 'A log of boot-time activity was created by a previous instance of Process Monitor. From the resulting Dialog box, Select 'Generate profiling events' 'every 100 milliseconds'. It appears that it had passed the 199 event limit as the first 5 PML files had been overwritten Navigate to Options > Click Enable Boot Logging. Report Id: 4e4549af-41a1-4778-8957-98c9fa24c033įaulting package-relative application ID:Ī minidump file does not get produced. Process Monitor seems to crash after about 90 minutes with teh following info:įaulting application name: Procmon64.exe, version: 3.60.0.0, time stamp: 0x5f6395d1įaulting module name: ntdll.dll, version: 3.3630, time stamp: 0x5e8d4386įaulting application start time: 0x01d6a031aa85c566įaulting application path: E:\ProcessMonitor\Procmon64.exeįaulting module path: C:\windows\SYSTEM32\ntdll.dll This report is generated from a file or URL submitted to this webservice on July 16th 2019 19:42:13 (UTC) Guest System: Windows 7 64 bit. I am trying to capture data to solve an app issue.
0 Comments
Leave a Reply. |