DCX3200 FireWire Tuning Device Issue

[smdl]

Hi, folks.

I've had an unusual issue come up over the past couple of weeks that I have not seen previously, and I haven't been able to find another example of this by searching. First, some background:

I'm running a Win7 machine as my server, and currently have two HD-PVRs connected to two Motorola DCX3200 STBs. I've been using SageChanger for FireWire tuning for the past few months, and it has been trouble-free. Although I have found issues (as many have) with the HD-PVR power supplies, I have never seen an issue with FireWire tuning on the DCX3200 boxes. However, I am now seeing fairly consistent issues when the server reboots. Unfortunately, due to performance issues that accumulate over time, I have had the server set up to reboot automatically for many years. With the new problems, this means that I am experiencing issues with tuning on a daily basis.

Now to the problem: What I am noticing is that I'm getting incorrect recordings on one or both STBs almost daily. When I check within the application, both video sources are set up fine, and the HD-PVRs are recording perfectly. So, looking into the Device Manager, I find that the FireWire devices are not present on the corresponding STB(s). As soon as I unplug and plug in the FireWire cable from the problem STB(s), the device immediately registers, and everything returns to normal. See attached image of the Device Manager before and after the second STB connection was reset by unplugging and plugging in the FireWire cable.

So, what I am trying to determine is why is this suddenly happening when things have been working so well in this exact configuration for months? The only thing I can think of that has changed recently is that I conducted a Java update a few weeks back, but I'm not sure that could have impacted this. Hoping someone has seen this, and can offer some advice. All feedback welcome.

Cheers,
Shaun

[smdl]

Just realized that I never did post a follow-up to this issue, which is now resolved. What did I do to fix it? Nothing -- it just stopped. Without knowing specifically what changed, I can only assume that a Windows update might have caused the issue, and that it was resolved in a subsequent update.

Cheers,
Shaun