Windows 8 Pro 64bit + Vbox DTA-150 not working

[laberet]

I'm trying to get my server moved from win7 32bit to win8 64bit. I've run in to a problem that is generating -WAF. My vbox DTA-150 will not work. The device drivers were loaded by windows 8 installer. I see the devices fine in device manager. Sagetv and 8 MCE see the tuner but neither work. Both see the device. I can see the signal strength in sagetv for those channels that do or do not exist in my area. When I try to watch or preview anything on the DTA-150 tuner I just get a black screen that eventually says "no signal". Win8 will also do a win 8 version of a blue screen and reboot after a few attempts to use the device.

I'm guessing its a driver issue as MCE doesn't work either and has the same behavior as sagetv. I also have 2 HD-PVRs connected to dish 211k receivers and they are working fine.

Does anyone have vbox DTA-150s working on win 8 64bit?

I'd like to try different drivers but the vbox site hardly has anything on it. I thought they had shutdown at first when I looked through their support site...

Anyone have access to 64 drivers I can try. The ones that windows installed for me look to be 2.1.705.14 but when I dig in to them they say AMD64. My system is Intel64. not sure if thats a clue or not...

[laberet]

update on the AMD64 driver thing. It has no bearing. All 64 bit drivers use "NTamd64" in their drivers. Supposedly because AMD had 64 bit first.

Still curious if anyone has 64 bit drivers for the vbox DTA-150 that I can try.

[drewg]

Originally Posted by laberet

Win8 will also do a win 8 version of a blue screen and reboot after a few attempts to use the device.

<....>

The ones that windows installed for me look to be 2.1.705.14 but when I dig in to them they say AMD64. My system is Intel64. not sure if thats a clue or not...

AMD64 is a red herring. That is the name of the 64-bit x86 platform. If you recall, AMD came up with the 64-bit extensions to the x86 architecture & were first to market with them, while Intel was busy pushing Itanium. The early supporters of this architecture called it "amd64". Intel came on board eventually & licensed the extensions, and most projects were renamed to less AMD-centric names, but there are lots of internal tools on almost every platform that call 64-bit x86 "amd64".

If I had to guess, I'd say that to me, it sounds like you're hitting a driver or hardware bug where something is unprepared to deal with 64-bit DMA addresses. I do not know much about the Windows DMA model, but there is some small chance that enabling VT-d in the BIOS may cause the DMA address space to be restricted to 32-bit & could work around the issue.

Drew

[laberet]

Thanks Drew. I'll look through the BIOS. The board is an ASUS P5E WS Pro. I needed something with PCI-X because I have a 3ware 9550SX-8LP SATA RAID controller I wanted to use.

I have an HDHR3-US DUAL on order to replace the vbox DTA-150 for OTA ATSC. I don't have much hope that I will get the DTA-150 functioning based on the vbox web site. I did submit a support form. They don't have any drivers for the DTA-150 posted at all. They only have a spotty handful up for all their products. It looks like they are out of business based on how poor their web site is.

I created a signature with details on my setup in case anyone else has ideas.

[drewg]

Originally Posted by laberet

Thanks Drew. I'll look through the BIOS. The board is an ASUS P5E WS Pro.

That's x38 right? I don't think vt-d is supported on an x38 chipset... Good luck with the HDHR3.

Drew