Jump to content

Terry Nixon

Members
  • Posts

    8
  • Joined

  • Last visited

Everything posted by Terry Nixon

  1. So the client is working however according to my logs it seems to experience a crash and then restarts itself successfully. Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: PCMonitorSrv.exe P2: 4.1.1.0 P3: 527d2d13 P4: ntdll.dll P5: 6.3.9600.16408 P6: 523d5305 P7: c0000005 P8: 000000000005b459 P9: P10: Attached files: These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_PCMonitorSrv.exe_a5e5112b1a7c7d7e992382fea2c9fb048cc5e_1878e40f_08fc3345 Analysis symbol: Rechecking for solution: 0 Report Id: b62cc163-4bda-11e3-bf9c-94de806b51c4 Report Status: 4100 Hashed bucket: Faulting application name: PCMonitorSrv.exe, version: 4.1.1.0, time stamp: 0x527d2d13 Faulting module name: ntdll.dll, version: 6.3.9600.16408, time stamp: 0x523d5305 Exception code: 0xc0000005 Fault offset: 0x000000000005b459 Faulting process id: 0x6fc Faulting application start time: 0x01cedfe7752cc046 Faulting application path: C:\Program Files\PC Monitor\PCMonitorSrv.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: b62cc163-4bda-11e3-bf9c-94de806b51c4 Faulting package full name: Faulting package-relative application ID: Application: PCMonitorSrv.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException Stack: at System.Net.UnsafeNclNativeMethods+SafeNetHandles_SECURITY.EnumerateSecurityPackagesW(Int32 ByRef, System.Net.SafeFreeContextBuffer_SECURITY ByRef) at System.Net.SafeFreeContextBuffer.EnumeratePackages(System.Net.SecurDll, Int32 ByRef, System.Net.SafeFreeContextBuffer ByRef) at System.Net.SSPIWrapper.EnumerateSecurityPackages(System.Net.SSPIInterface) at System.Net.SSPIWrapper.GetVerifyPackageInfo(System.Net.SSPIInterface, System.String, Boolean) at System.Net.Security.SecureChannel..ctor(System.String, Boolean, System.Net.SchProtocols, System.Security.Cryptography.X509Certificates.X509Certificate, System.Security.Cryptography.X509Certificates.X509CertificateCollection, Boolean, Boolean, Boolean, System.Net.Security.EncryptionPolicy, System.Net.Security.LocalCertSelectionCallback) at System.Net.Security.SslState.ValidateCreateContext(Boolean, System.String, System.Security.Authentication.SslProtocols, System.Security.Cryptography.X509Certificates.X509Certificate, System.Security.Cryptography.X509Certificates.X509CertificateCollection, Boolean, Boolean, Boolean) at System.Net.TlsStream.ProcessAuthentication(System.Net.LazyAsyncResult) at System.Net.TlsStream.Write(Byte[], Int32, Int32) at System.Net.ConnectStream.WriteHeaders(Boolean) at System.Net.HttpWebRequest.EndSubmitRequest() at System.Net.HttpWebRequest.GetResponse() at System.ServiceModel.Channels.HttpChannelFactory`1+HttpRequestChannel+HttpChannelRequest[[system.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].WaitForReply(System.TimeSpan) at System.ServiceModel.Channels.RequestChannel.Request(System.ServiceModel.Channels.Message, System.TimeSpan) at System.ServiceModel.Channels.ServiceChannel.Call(System.String, Boolean, System.ServiceModel.Dispatcher.ProxyOperationRuntime, System.Object[], System.Object[], System.TimeSpan) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(System.Runtime.Remoting.Messaging.IMethodCallMessage, System.ServiceModel.Dispatcher.ProxyOperationRuntime) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(System.Runtime.Remoting.Messaging.IMessage) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(System.Runtime.Remoting.Proxies.MessageData ByRef, Int32) at MM.Monitor.Service.ServerService.IServer.GetServerInfo() at . () at .(System.Object, System.Timers.ElapsedEventArgs) at System.Timers.Timer.MyTimerCallback(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.TimerQueueTimer.CallCallback() at System.Threading.TimerQueueTimer.Fire() at System.Threading.TimerQueue.FireNextTimers() Fault bucket -320202476, type 5 Event Name: FaultTolerantHeap Response: Not available Cab Id: 0 Problem signature: P1: PCMonitorSrv.exe P2: 4.1.1.0 P3: 527D2D13 P4: ffffbaad P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\ServiceProfiles\LocalService\AppData\Local\Temp\FTH61A8.tmp\fthempty.txt These files may be available here: Analysis symbol: Rechecking for solution: 0 Report Id: bd612572-4bda-11e3-bf9c-94de806b51c4 Report Status: 0 Hashed bucket: 3d965f26b0222103c257bd09a1178d35
  2. I installed the new client and will keep you posted on the results.
  3. My issue has appeared again. I am convinced there is an issue with the client itself and being incompatible with 8.1. Faulting application name: PCMonitorSrv.exe, version: 4.1.0.0, time stamp: 0x526beb33 Faulting module name: ntdll.dll, version: 6.3.9600.16408, time stamp: 0x523d5305 Exception code: 0xc0000005 Fault offset: 0x000000000005b459 Faulting process id: 0x4a4 Faulting application start time: 0x01ced681f7c126e6 Faulting application path: C:\Program Files\PC Monitor\PCMonitorSrv.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 388d9223-4275-11e3-bf65-94de806b51c4 Faulting package full name: Faulting package-relative application ID:
  4. sfc /scannow did not detect any corruption. However I was able to fix the issue using the same command. I renamed the ntdll.dll file and then ran sfc /scannow to force the system to create a new ntdll.dl file. I then repair installed pcmonitor. Thanks
  5. Here is what I've done so far: Uninstalled PCMonitor Follow these steps if you are running Windows 8: Swipe in from the right edge of the screen, and then tap Search. Note If you're using a mouse, point to the upper-right corner of the screen, move the mouse pointer down, and then click Search. Tap or click Settings, and then enter the name of the app you want to find. Tap or click Uninstall a program Tap or click Turn Windows features on or off Tap or click to unselect the box for .Net framework 3.5 (includes .Net2.0 and 3.0) Tap or click OK and click Close when the uninstall is complete. Tap or click to close the Uninstall a program window. I also selected the option to uninstall .NET Framework 4.5 Advanced Services. And then DISM /Online /Cleanup-Image /RestoreHealth I then rebooted and re-installed PCMonitor. I still have the same issue.
  6. It did not fix the issue. However I do see that the service attempted to start with the below errors. Faulting application name: PCMonitorSrv.exe, version: 4.0.4.0, time stamp: 0x5264088a Faulting module name: ntdll.dll, version: 6.3.9600.16408, time stamp: 0x523d5305 Exception code: 0xc0000005 Fault offset: 0x000000000005b459 Faulting process id: 0xbfc Faulting application start time: 0x01ced0c55534a6a2 Faulting application path: C:\Program Files\PC Monitor\PCMonitorSrv.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 96019639-3cb8-11e3-bf4f-94de806b51c4 Faulting package full name: Faulting package-relative application ID: Second Error ----------------- Application: PCMonitorSrv.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException Stack: at System.Net.UnsafeNclNativeMethods+SafeNetHandles_SECURITY.EnumerateSecurityPackagesW(Int32 ByRef, System.Net.SafeFreeContextBuffer_SECURITY ByRef) at System.Net.SafeFreeContextBuffer.EnumeratePackages(System.Net.SecurDll, Int32 ByRef, System.Net.SafeFreeContextBuffer ByRef) at System.Net.SSPIWrapper.EnumerateSecurityPackages(System.Net.SSPIInterface) at System.Net.SSPIWrapper.GetVerifyPackageInfo(System.Net.SSPIInterface, System.String, Boolean) at System.Net.Security.SecureChannel..ctor(System.String, Boolean, System.Net.SchProtocols, System.Security.Cryptography.X509Certificates.X509Certificate, System.Security.Cryptography.X509Certificates.X509CertificateCollection, Boolean, Boolean, Boolean, System.Net.Security.EncryptionPolicy, System.Net.Security.LocalCertSelectionCallback) at System.Net.Security.SslState.ValidateCreateContext(Boolean, System.String, System.Security.Authentication.SslProtocols, System.Security.Cryptography.X509Certificates.X509Certificate, System.Security.Cryptography.X509Certificates.X509CertificateCollection, Boolean, Boolean, Boolean) at System.Net.TlsStream.ProcessAuthentication(System.Net.LazyAsyncResult) at System.Net.TlsStream.Write(Byte[], Int32, Int32) at System.Net.ConnectStream.WriteHeaders(Boolean) at System.Net.HttpWebRequest.EndSubmitRequest() at System.Net.HttpWebRequest.GetResponse() at System.ServiceModel.Channels.HttpChannelFactory`1+HttpRequestChannel+HttpChannelRequest[[system.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].WaitForReply(System.TimeSpan) at System.ServiceModel.Channels.RequestChannel.Request(System.ServiceModel.Channels.Message, System.TimeSpan) at System.ServiceModel.Channels.ServiceChannel.Call(System.String, Boolean, System.ServiceModel.Dispatcher.ProxyOperationRuntime, System.Object[], System.Object[], System.TimeSpan) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(System.Runtime.Remoting.Messaging.IMethodCallMessage, System.ServiceModel.Dispatcher.ProxyOperationRuntime) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(System.Runtime.Remoting.Messaging.IMessage) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(System.Runtime.Remoting.Proxies.MessageData ByRef, Int32) at MM.Monitor.Service.ServerService.IServer.GetServerInfo() at . () at .[1](System.Object, System.Timers.ElapsedEventArgs) at System.Timers.Timer.MyTimerCallback(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.TimerQueueTimer.CallCallback() at System.Threading.TimerQueueTimer.Fire() at System.Threading.TimerQueue.FireNextTimers()
  7. I have seen this issue in Windows 8.1 also. I have found that since the upgrade pcmonitor service no longer starts automatically even though it is set to. I have submitted my logs in the Windows forum so hopefully there will be a fix.
  8. Hello ever since upgrading my machine to Windows 8.1 the PcMonitor service no longer automatically starts. I did confirm that the service is set to start automatically. I have also uninstalled and reinstalled a few times. If I start the service manually it works. My event logs show: Log Name: Application Source: Windows Error Reporting Date: 10/22/2013 11:31:47 AM Event ID: 1001 Task Category: None Level: Information Keywords: Classic User: N/A Computer: xxxxxxxx Description: Fault bucket 136968820, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: PCMonitorSrv.exe P2: 4.0.4.0 P3: 5264088a P4: ntdll.dll P5: 6.3.9600.16408 P6: 523d5305 P7: c0000005 P8: 000000000005b459 P9: P10: Fault bucket 136968820, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: PCMonitorSrv.exe P2: 4.0.4.0 P3: 5264088a P4: ntdll.dll P5: 6.3.9600.16408 P6: 523d5305 P7: c0000005 P8: 000000000005b459 P9: P10: Attached files: C:\Windows\Temp\WER3588.tmp.appcompat.txt C:\Windows\Temp\WER35D7.tmp.WERInternalMetadata.xml C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_PCMonitorSrv.exe_78348e527734756114765f530337863bd143a43_84b5484f_cab_087c35d5\memory.hdmp C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_PCMonitorSrv.exe_78348e527734756114765f530337863bd143a43_84b5484f_cab_087c35d5\triagedump.dmp These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_PCMonitorSrv.exe_78348e527734756114765f530337863bd143a43_84b5484f_044cfb4d Analysis symbol: Rechecking for solution: 0 Report Id: 4c7026cc-3a5b-11e3-bf47-94de806b51c4 Report Status: 0 Hashed bucket: f133cc2496a12213ab73d88630af4164
×
×
  • Create New...