HS3 Has Stopped Working

[kwatt]

As ever when something breaks, a really helpful Windows message as attached!

It *seems* to be happening about the same time-ish each day so I think it's something in the schedule that might be causing it but what I can't work out is, how to determine what it is.

I was trying to find any crash logs etc but I can't find anything.

Can anyone help me hunt down the problem please as it's driving me bonkers?

It runs on a basic Win10 box that pretty much is completely dedicated to HS so, there's nothing else running on it really other than a Plex server that's not really in use and, there's not other errors with anything I can find.

Thanks.

K.

[Rupp]

Check the systems event viewer for more information.

[kwatt]

This is a bit odd, the last even ran was at 9:00am yet every afternoon into evening time HS3 just stops.

I looked at the log, in so much as I can see as I can't get to historical stuff, and nothing seems off there.

By event viewer I'm not quite sure what you mean, I can get to the log which shows me:

Jul-07 7:19:54 PM Startup
Jul-07 7:19:54 PM Startup ************************************************************ ********************
Jul-07 7:19:54 PM Startup HomeSeer version 3.0.0.318 Edition: HS3 Pro Starting Now
Jul-07 7:19:54 PM Startup ************************************************************ ********************
Jul-07 7:19:54 PM Startup
Jul-07 7:19:54 PM Startup Settings Loaded.
Jul-07 1:40:06 PM Z-Wave Device: Ground AV Room Temperature Set to 23.6 (C)
Jul-07 1:39:33 PM Z-Wave Device: Ground Conservatory Luminance Set to 519 (Lux)
Jul-07 1:39:17 PM Z-Wave Device: Ground Conservatory Luminance Set to 521 (Lux)
Jul-07 1:39:14 PM Z-Wave Device: Ground Conservatory Temperature Set to 23.4 (C)
Jul-07 1:39:13 PM Arduino Plugin Board1, Input:3, Value:0
Jul-07 1:39:04 PM Arduino Plugin Board1, Input:3, Value:1
Jul-07 1:39:00 PM Arduino Plugin Board1, Input:4, Value:0
Jul-07 1:38:55 PM Arduino Plugin Board1, Input:4, Value:1
Jul-07 1:38:53 PM Arduino Plugin Board1, Input:4, Value:0

Which doesn't really tell much other than, last thing it did was to check some Arduino ports and a few ZW sensors then fell over. But that makes no sense to me as they're running all the time and have been for goodness knows how long so I can't understand why they'd cause any issues.

K.

[ewkearns]

By event viewer I'm not quite sure what you mean, ...

Go here and do a little reading. Steps to access the viewer are included:

http://www.dummies.com/computers/ope...in-windows-10/

[kwatt]

D'oh!

Here was I looking for something inside HS, not Windoze!

Errors reported being...

EventData 

   HS3.exe 
   3.0.0.318 
   58e6a9d9 
   ntdll.dll 
   10.0.14393.479 
   58256ca0 
   c0000005 
   00058833 
   10c0 
   01d2f675c47eb0f6 
   C:\Program Files (x86)\HomeSeer HS3\HS3.exe 
   C:\WINDOWS\SYSTEM32\ntdll.dll 
   24d9f18c-7233-477e-ba7c-b18611365661 

+ System 

  - Provider 

   [ Name]  .NET Runtime 
 
  - EventID 1026 

   [ Qualifiers]  0 
 
   Level 2 
 
   Task 0 
 
   Keywords 0x80000000000000 
 
  - TimeCreated 

   [ SystemTime]  2017-07-07T12:42:29.891823600Z 
 
   EventRecordID 41774 
 
   Channel Application 
 
   Computer HAPC-PC 
 
   Security 
 

- EventData 

   Application: HSPI_JowiHue.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.NullReferenceException at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(System.Runtime.Remoting.Messaging.IMessage) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(System.Runtime.Remoting.Proxies.MessageData ByRef, Int32) at HomeSeerAPI.IHSApplication.WriteLog(System.String, System.String) at HSPI_JowiHue.utils.Log(System.String, LogLevel) at HSPI_JowiHue.UPNP.Bridgescan() at HSPI_JowiHue.UPNP+_Closure$__._Lambda$__R0-1(System.Object) at System.Threading.TimerQueueTimer.CallCallbackInContext(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() at System.Threading.TimerQueue.AppDomainTimerCallback()  


+ System 

  - Provider 

   [ Name]  Application Error 
 
  - EventID 1000 

   [ Qualifiers]  0 
 
   Level 2 
 
   Task 100 
 
   Keywords 0x80000000000000 
 
  - TimeCreated 

   [ SystemTime]  2017-07-07T12:42:29.969949000Z 
 
   EventRecordID 41775 
 
   Channel Application 
 
   Computer HAPC-PC 
 
   Security 
 

- EventData 

   HSPI_JowiHue.exe 
   1.1.2.9 
   593e6de1 
   mscorlib.ni.dll 
   4.6.1648.0 
   58e3fad3 
   c0000005 
   003d0ea2 
   154c 
   01d2f703a7da75d7 
   C:\Program Files (x86)\HomeSeer HS3\HSPI_JowiHue.exe 
   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\mscorlib\a8ad9c1eb84ee05773b04b298573fa35\mscorlib.ni.dll 
   dbd2dbdc-5664-477e-b5b8-7ff62430b491

Wild guess it's Jowihue then. :?

K.

[Rupp]

You can try to repair your .net frame works on this PC which may help or you could try running it on another PC you may have one as something is corrupt on this server if the .net repairs do not work.

[kwatt]

Hi Rupp,

What I keep getting is the following on this when it crashes:

Faulting application name: HS3.exe, version: 3.0.0.318, time stamp: 0x58e6a9d9
Faulting module name: ntdll.dll, version: 10.0.14393.1378, time stamp: 0x594a1295
Exception code: 0xc0000005
Fault offset: 0x00058833
Faulting process id: 0x2c14
Faulting application start time: 0x01d2ffec55eaf565
Faulting application path: C:\Program Files (x86)\HomeSeer HS3\HS3.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 05720a39-ce6e-4028-baea-cc7917ed8172
Faulting package full name:
Faulting package-relative application ID:

My big problem is, as a Mac fanboy, this is the only Windows box I run, it's used almost exclusively for HS3 and little else.

There's no email, no web browsing, no much of anything on it at all. And, it's not shared or used by anyone other than me.

All that's been done is the Windows updates and pretty much, that's it.

I tried reinstalling .net, redid the Arduino stuff, probably done Wim's head in about Jowi Hue and I just cannot fathom why this just all of a sudden started happening out the blue when, I really can't see that I've altered anything at all.

I must admit to getting a bit stressed about it as it really is super annoying that the only thing I can rely on is that HS will crash in the late afternoon every day.

That's the weird bit, it happens at the same time +/- an hour or so every day without fail and yet, no routines or anything are running at that time.

K.

[kwatt]

I might have fixed it.

Back to basics... reinstall the thing... try again!

For now it appears to have cured it.

K.

[RTJ]

I have the identical problem. It only started happening a few weeks ago probably after an update. Two questions:

What did you re-install? HS3Pro or the .net framework?

Is it still working?

[Rupp]

This error is a .net error so that's where I would recommend starting. In the past when I've encountered these errors I've wiped my hard drive and rebuilt my PC which typically solves these issues.

[Michel]

Same proplem.

I'm getting the same "ntdll.dll" error. Running either HS2 or HS3. So I will investigate the NET framework side of it.

kwatt, RTJ,

What ended-up being your solution?

Thanks for sharing.

[Pete]

Back in the Homeseer 2 days (running Windows server) it was just a reinstall of dot net. I never reinstalled the entire OS or Homeseer. That would have been too time consuming.

(3.5 back then and today maybe 4.X). Make sure that Homeseer 3 is OFF.

ntdll.dll is

The ntdll.dll file is a file created by Microsoft that has a description of "NT Layer DLL" and is the file that contains NT kernel functions. The ntdll.dll file is located in the c:\windows\system32 or c:\winnt\system32 directory and can also be found in the c:\i386 directory.

At the time did create a small base C partition that was 20Gb in size. I would image this partition such that I had a working Windows OS base partition archived in case of disaster.

BTW there have been some changes in the core of Homeseer 3 and this has affected some 3rd party plugins.

This is concurrent to Windows 10 updates (changes) over the last few months.


Read this first:

Discussions related to HomeSeer Beta 3.0.0.332->356

Then read this:

Discussions related to HS3 build 3.0.0.368

[kwatt]

It seemed to be solved but, again and more frequently now getting this:

Faulting application name: HS3.exe, version: 3.0.0.368, time stamp: 0x59c917e9
Faulting module name: ntdll.dll, version: 10.0.15063.447, time stamp: 0xd51d5c5e
Exception code: 0xc0000005
Fault offset: 0x0005da74
Faulting process id: 0x624
Faulting application start time: 0x01d339d53f99a7f3
Faulting application path: C:\Program Files (x86)\HomeSeer HS3\HS3.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: da9ea3bd-b130-4bab-a771-df71caa90c2c
Faulting package full name:
Faulting package-relative application ID:

Repaired HS3, reinstalled, it, rebooted etc but no joy.

I will try .net now as well.

K.

[Pete]

Recalling now that dot net issues presented themselves differently than an ntdll.dll error.

Occassionally in the Homeseer 2 days would see BSOD's mostly relating to hardware drivers.

Have a read here:

How to Fix Ntdll.dll Errors

[kwatt]

Yeah I'd seen that as well but given I've not changed any hardware on it for a long, long time and there's been no driver updates of any real note I'd sorta discounted that.

Could be some background auto update but not that I am aware of. And, all that appears to be okay.

I really am struggling to find any real reason.

There was a minor HS3 update but I can't see that being any issue either.

K.