Record Error: Root element is missing.

[seattlefog]

Thank you for clarifying. I would like to repeat one prior piece of information. I have been using this tuner, and it's associated drivers on Nextpvr V4 without issues for some years. Only when i went to V5 (the next day or so) did I start having recording issues. Since the drivers didn't change, but nextpvr did, I'm thinking that while it might be the drivers faulting, it's the different invocation by V5 that is triggering it. not the unchanged drivers. I take it I'm the only Hauppauge tuner user that is having issues after the upgrade to v5? I certainly didn't spot many similar posts to mine, but I defer to you on that count. Thanks for your thoughts.

[Graham]

Since the drivers didn't change, but nextpvr did, I'm thinking that while it might be the drivers faulting, it's the different invocation by V5 that is triggering it. not the unchanged drivers.

It is my understanding that V5 tidies up the software that evolved during the previous ten or more years.  It might be that the now tidy and efficient V5 software exposes something in the drivers.

But ... There are quite a few that use the Hauappauge Quad without incident ... I dunno what makes you the lucky recipient of this problem.

[klemo]

Sorry, I didn't see this before now.

I've been having what appears to be the same problem using Hauppauge Quad PCIe tuners and "Root element is missing". It ran it's course for a few weeks in Dec 2020, then stopped on Jan 1, 2021 (don't know why) but then resumed on Dec 1 2021 with multiple "Root element is missing" errors every day. At first I was reinstalling the Hauppauge win 10 driver and rebooting which works for a day.

A week ago I just started rebooting this win 10 PC every day which also works for a day.

See my post for more info. https://forums.nextpvr.com/showthread.php?tid=63383

I'm about the stop rebooting every morning and now decided to my antivirus software (Bitdefender) which is last thing I can think of before throwing in the towel.

I have another win 10 on v4 using the same QuadHD tuner card since 2019 with a few minor issues at time but nothing like this.

Oh, I never installed Hauppauge Win software, except for the QuadHD win 10 driver on either of my win 10 v4 and v5 setups.

Did you ever solve your problem with v5?

[seattlefog]

In late February 2021 I ran the v5 install one last time, and that cleared it up. However just a few weeks ago, the problem began again. I ran the v5 install and reinstalled the same Hauppague drivers but that hasn't seemed to clear the issue. I note that there appears to be a memory leak. that is, the nextpvr service task goes to a couple hundred MB. It could be associated with the .NET framework upgrade that occcured about that time. I'm monitoring the memory. I also wrote a simple find script to locate errors in the log. If i detect either errors or memory > 200MB i run a command line to stop then start the nextpvr record service. So I'm limping along. I'm also running Bitdefender and the quad tuner. So I wouldn't rule out Bitdefender, which has periodic updates. I'm hoping it will just "go away" as it did before when whatever software gets updated again.

[sub]

I ran the v5 install and reinstalled the same Hauppague drivers but that hasn't seemed to clear the issue. I note that there appears to be a memory leak. that is, the nextpvr service task goes to a couple hundred MB. It could be associated with the .NET framework upgrade that occcured about that time. I'm monitoring the memory. I also wrote a simple find script to locate errors in the log. If i detect either errors or memory > 200MB i run a  command line to stop then start the nextpvr record service.

FYI, using 200+ MB is totally normal. It often requires more than this to process the EPG update. The application does free up the memory after it's used it, but because of the .NET works, it wont return the memory to the system unless it absolutely needs. The following night when the next EPG update happens, it ends up reusing that previously freed memory (ie, wont grow an additional 200MB each night)

[seattlefog]

Yesterday it threw an out of memory exception. The task manager screenshots are from 2 different times this morning. I'm anticipating either a root element missing symptom or other tuner related error.