DeviceHostWindows.exe Crashing PC

[andrewj]

Crashed again last night. No crashdump file. There is a Minidump file (attached) - this appears to point to emBDA64.sys but googling doesn't confirm what it is.

NPVR logs also attached. I'm not sure whether this is an NPVR problem or the reference to DeviceHostWindows.exe was a coincidence.

Help appreciated, thanks.

[andrewj]

I had another look at the Crashdump file from Tuesday. It's definitely showing the error occurring in DeviceHostWindows:

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 53196d9d (MSNP!CMPEG2Demux::UpdateSignalAndServiceStatus+0x000000f7)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000000
Attempt to read from address 00000000

PROCESS_NAME: DeviceHostWindows.exe

READ_ADDRESS: 00000000

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 00000000

EXCEPTION_PARAMETER2: 00000000

STACK_TEXT:
050cf9b0 53187431 050cfa0b 050cfa07 050cf9f8 MSNP!CMPEG2Demux::UpdateSignalAndServiceStatus+0xf7
050cfa18 5317e4de 06e46d98 06e32a00 00000000 MSNP!CScanningTuner::HeartBeat+0x6e
050cfa2c 5317e315 00000008 00000000 5317e200 MSNP!CNetworkProvider::HandleNetworkProviderEvent+0x185
050cfa6c 5317e20d 050cfa84 76d3fcc9 06e32a00 MSNP!CNetworkProvider::ThreadFunction+0x104
050cfa74 76d3fcc9 06e32a00 76d3fcb0 050cfae0 MSNP!CNetworkProvider::ThreadFunctionWrapper+0xd
050cfa84 77df809e 06e32a00 583db1d6 00000000 kernel32!BaseThreadInitThunk+0x19
050cfae0 77df806e ffffffff 77e19101 00000000 ntdll!__RtlUserThreadStart+0x2f
050cfaf0 00000000 00000000 00000000 00000000 ntdll!_RtlUserThreadStart+0x1b

[mvallevand]

No the stack trace shows it in the Microsoft DLL, DLL's aren't processes.

I still don't see it locking on tuner 2 just tuner 1, did you check WinTV to confirm tuner 2 is working properly like I asked. A quick test in NextPVR If you disable tuner 2 does live TV works does Live TV work.

It is also possible that tuner 2 is not in sync with tuner 1 and the frequencies might be wrong after a rescan. A simple solution to that is to go into tuner 2 hit the trash can to delete all the channels exist and go back into it any copy when prompted.

Martin

[andrewj]

Hi Martin. I have confirmed all tuners have the same channel list. One did have a loose antenna connection.
Happy to test both are working - what's the easiest way to temporarily disable each in turn?
Thanks

[mvallevand]

On Settings->Device holding the control key will show you options to disable tuners. Disable tuner 1 to test if tuner 2 is now working.

Martin

[andrewj]

Thanks. Both tuners working now, so I suspect the failure to get a signal was just the loose antenna connector. That shouldn't have crashed the PC!

[mvallevand]

We will see when you do an EPG update.

As sub wrote that was in a Windows component, create a bug report with Microsoft or Hauppauge that work at the kernel level.

Martin

[sub]

There is a Minidump file (attached) - this appears to point to emBDA64.sys but googling doesn't confirm what it is.

emBDA64.sys is part of the driver for the Empia chipset on your tuner.

[sub]

Thanks. Both tuners working now, so I suspect the failure to get a signal was just the loose antenna connector. That shouldn't have crashed the PC!

It absolutely shouldn't have crashed the PC. When you say that though, do you mean DeviceHostWindows crashed, or literally the entire PC, like BSOD message and reboot? If the latter, then it would have almost certainly inside a driver call that has crashed. That would totally tally up with emBDA64.sys being at fault.

NextPVR couldn't make the machine crash like that if I tried. Drivers can absolutely cause machines to crash though, since they run as ring 0 code, with access to the inner workings of the machine.

I'd be looking for a different version of the drivers for that machine.

[nextmel]

I'd be looking for a different version of the drivers for that machine.

Did I see Hauppauge mentioned earlier? Which device, PCI, USB, dual, quad? I binned their DualHD USB device due to reliability issues, and their QuadHD PCI device is better but still not 100% reliable. Now, I acually cannot compare with another tuner manufacturer so cannot rule out that there's something funky about my system... but it's actually been the upgraded from Windows 10 to 11, and from an Asus motherboard to Gigabyte, and the QuadHD has remained flakey throughout. My system performs many functions, and the only things I ever have crash are Corel PaintShop Pro 2021 and the hardware detection of the QuadHD. That said, it's been more reliable (though not 100%) since I settled on one particular driver version, 5.2022.927.40271. Good luck!

 /mel/

I'd be looking for a different version of the drivers for that machine.