My friend is running the latest JRiver 20 on his back lanai in an HP dc5700, small desktop Core2 Duo E8400/3 Gig Ram/Radeon 5450 video card machine, set up with Local library, accessing flac and mp3 music files via network share, wireless N. The file shares are located on a 2 year old laptop hard wired to network in the house, Windows 8.1 on all machines.
The HP can play music or video (plays uncompressed blu-ray on local USB drive at >5% CPU utilization) flawlessly all day long, until Theater View is selected. Then the PC hard freezes, usually almost immediately. The only cure is a hard power button re-boot.
This almost certainly does not have anything to do with the network, and certainly isn't a data bottleneck issue.
Hard freezing or blue screens can
only be caused by one of four things on modern versions of Windows (anything with an NT kernel):
* Hardware failure (including overheating)
* Driver problem
* OS problem
* Malware running in the kernel space
That's it. Theater View cannot "cause" this condition. Theater View can, however, tell the drivers to do things (which they should be able to do, or fail gracefully) that create the condition. That's what you're seeing here.
The most likely culprit, since the condition occurs when entering Theater View (which is a full-screen Direct3D application, like a game), is the GPU driver. It is possible, I suppose, that it is a network interface driver, but that would be pretty far down on my list of possible culprits (especially since this would apply any time data is accessed over the network, not just in Theater View).
Laptops have particularly troublesome video card drivers. In most cases, you cannot run the driver directly from AMD or Nvidia on them, and must use the driver from the OEM. There are a few exceptions to this, but that's the typical case for laptops. I'd recommend:
1. Obtaining the most up-to-date video card driver for his computer from HP's support web site.
2. Fully uninstalling the GPU driver, and any additional video card related utilities that might be installed.
3. Reboot. Do not skip this step because you are lazy.
4. Install the driver you obtained from HP.
If that doesn't help, it could be an indicator that there is something physically wrong with the machine, and there are additional troubleshooting steps you can take.