This could be a blbackup issue as that is where the crash happened, but it happened when it tried to access the HS log so its possible HS went away first. Can you look at the Windows event log and see if any other exceptions were logged.

Quote:

Originally Posted by Tomgru

I woke up to a crash this morning..... happened when BLBackup started. I'm running on Win10 Pro version 1703.
Running HS3 v379
Znet on Zwave plugin v130

worked great for a week.... checked task manager every morning and saw no signs of memory leakage.

This could be a blbackup issue as that is where the crash happened, but it happened when it tried to access the HS log so its possible HS went away first. Can you look at the Windows event log and see if any other exceptions were logged.

This could be a blbackup issue as that is where the crash happened, but it happened when it tried to access the HS log so its possible HS went away first. Can you look at the Windows event log and see if any other exceptions were logged.

I have seen this type of crash during a BLBackup as well (it is trying to backup the HomeSeer directory at the time). . .on my Pi2 (running HS3 Std).

I can add HSBuddy and EasyTrigger as plugins that cause the callback queue to grow. With HSBuddy, the queue count started to rise immediately. Yesterday I let it go all day, and the queue count went up over 8 million. The HSConsole process got up to 1.6GB of virtual memory and then things started failing, so I restarted HS3. But all day HS3 was working well, some slowness at times, but no failures and no major slowdowns. I've got those two plugins disabled again and so far so good today.

I dont get crashes but I get hangs / unresponsive app.... it usually happens when I'm in the UI and doing something. Unfortunately, there is nothing I can do except kill the process and restart. The web UI never responds, even on the local machine.

CPU & Memory usage seems fine when it hangs: nearly 0% & ~45mb

This happens to me every 3-4 days.

Looks like I now need to install an app/script just to remotely kill HS3 and restart it.

Iíve been running 3.72 beta for about a month without issues and suddenly the s6 box has crashed twice (at random times) with the blue screen of death. The last crash was sometime during the night last night. Any suggestions?

I have seen similar on my Homeseer Touch tabletops running embedded Windows, Homeseer Touch and Homeseer speaker. Mostly on just one tabletop and twice in 2017. Even though the media is SSD I still occasionally do a disk check on it. I let the tabletop go to a screensaver and here it looks to be a video issue when the screen saver kicks in.

Check the Microsoft Event viewer for issues. Here the tabletops have nothing connected except for one Gb NIC.

Googling the error

In this Stop error message, each parameter is a hexadecimal number that refers to a specific issue:

Parameter 1 - An address that was referenced incorrectly.
Parameter 2 - An IRQL that was required to access the memory.
Parameter 3 - The type of access, where 0 is a read operation and 1 is a write operation.
Parameter 4 - The address of the instruction that referenced memory in parameter 1.

I have seen similar on my Homeseer Touch tabletops running embedded Windows, Homeseer Touch and Homeseer speaker. Mostly on just one tabletop and twice in 2017. Even though the media is SSD I still occasionally do a disk check on it. I let the tabletop go to a screensaver and here it looks to be a video issue when the screen saver kicks in.

Check the Microsoft Event viewer for issues. Here the tabletops have nothing connected except for one Gb NIC.

Googling the error

In this Stop error message, each parameter is a hexadecimal number that refers to a specific issue:

Parameter 1 - An address that was referenced incorrectly.
Parameter 2 - An IRQL that was required to access the memory.
Parameter 3 - The type of access, where 0 is a read operation and 1 is a write operation.
Parameter 4 - The address of the instruction that referenced memory in parameter 1.

Pete, thanks but that still doesnít tell me whatís causing it or how to resolve it! Lol

From past experience probably disk issues. Failing that suspect memory modules will trigger it. Do a disc scan as a first option and check for errors. Possible FAT corruption. If you have a POST memory check utility give that a spin too.

What ever you do make sure you have a full system back up done before you try anything. BSOD are so random it could be a one-off event but it could be a sign of hardware failing too.

From past experience probably disk issues. Failing that suspect memory modules will trigger it. Do a disc scan as a first option and check for errors. Possible FAT corruption. If you have a POST memory check utility give that a spin too.

What ever you do make sure you have a full system back up done before you try anything. BSOD are so random it could be a one-off event but it could be a sign of hardware failing too.

Well itís a homeseer s6 box and I believe it has an ssd. I guess thatís gonna be their warranty issue if thatís the case

Well itís a homeseer s6 box and I believe it has an ssd. I guess thatís gonna be their warranty issue if thatís the case

Sent from my iPhone using Tapatalk

Maybe a little more info on your setup might help people troubleshoot the problem for you. SD issues can be quite popular. There's so many variations of HS3 setups the more information you can supply the better.

Maybe a little more info on your setup might help people troubleshoot the problem for you. SD issues can be quite popular. There's so many variations of HS3 setups the more information you can supply the better.

What info are you looking for? Itís the S6 pro windows appliance sold by homeseer that comes pre installed with windows 7 and hs3 pro

Best advice I could give is to take an image copy of your 32gb SD device and in the event of a serious failure you can reinstall your setup without much effort.

I assume your unit is still under warranty so I wouldn't dismantle anything. It would probably void your warranty if you do.

The fact that your system restarted without any ill effects it may be one of those random crashes that tend to happen to Windows systems. May be no harm reporting the matter directly to HS Technical support just to be on the safe side

Really odd, let me add some code to check for this and at least allow other plugins to run. The way it is now, if one plugin does not respond, it will stop all other plugins from getting events. I will put in a fix for that.

Quote:

Originally Posted by bdickhaus

I can add HSBuddy and EasyTrigger as plugins that cause the callback queue to grow. With HSBuddy, the queue count started to rise immediately. Yesterday I let it go all day, and the queue count went up over 8 million. The HSConsole process got up to 1.6GB of virtual memory and then things started failing, so I restarted HS3. But all day HS3 was working well, some slowness at times, but no failures and no major slowdowns. I've got those two plugins disabled again and so far so good today.