TBSDTV Community Forum

by **trickymundo** » Sun Oct 12, 2014 5:21 pm

Hi,

I'm getting regular BSODs from my Windows 7 32-bit Media PC. It is an Intel Core2 Duo E4700 CPU, with 2GB ram and an ATI Radeon HD4600 graphics card. It has a Gigabyte 965P-DQ6 motherboard. It runs MediaPortal 1.9pre and the BSOD occurs whilst playing back recorded programmes. I find this a bit odd as I wouldn't have thought the TV card would be in use at this point? I have had it crash playing back SD and HD material.

As well as the 6281, I have a 6280 dual-tuner card too. The 6281 is using drivers version 1.0.0.6 and the 6280 is using drivers version 1.0.1.2

I'm having difficulty finding the full details of the BSOD, I think the details are written to the PC, but I don't know where to exactly. Plus I'm posting this on a different PC.

The BSOD definitely refers to the 6281 drivers.

If anyone can point me to any way of getting at the BSOD details from the PC, I will post them on here.

Thanks

by **trickymundo** » Mon Oct 13, 2014 1:03 am

Ok,

I've found the Memory.dmp file and ran it through WinDBG as described here:

http://www.microsoft.com/en-us/download/details.aspx?id=8279

The resulting output from the debug session is below, if I can provide any further info, please ask.

Code: Select All Code: Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\MEMORY - Copy.DMP] Kernel Complete Dump File: Full address space is available Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.18409.x86fre.win7sp1_gdr.140303-2144 Machine Name: Kernel base = 0x82c38000 PsLoadedModuleList = 0x82d815b0 Debug session time: Fri Oct 10 21:43:38.567 2014 (UTC + 1:00) System Uptime: 1 days 13:39:25.128 Loading Kernel Symbols ............................................................... ................................................................ .......................... Loading User Symbols ......................Unable to read NT module Base Name string at 0054f4ee - NTSTATUS 0xC0000147 Missing image name, possible paged-out or corrupt data. ....Unable to read NT module Base Name string at 0055c53a - NTSTATUS 0xC0000147 Missing image name, possible paged-out or corrupt data. ...................................... ...........Unable to read NT module Base Name string at 005e9b12 - NTSTATUS 0xC0000147 Missing image name, possible paged-out or corrupt data. .Unable to read NT module Base Name string at 005e9fac - NTSTATUS 0xC0000147 Missing image name, possible paged-out or corrupt data. ...Unable to read NT module Base Name string at 0056808c - NTSTATUS 0xC0000147 Missing image name, possible paged-out or corrupt data. ....................Unable to read NT module Base Name string at 04fc6be0 - NTSTATUS 0xC0000147 Missing image name, possible paged-out or corrupt data. .............Unable to read NT module Base Name string at 050316d0 - NTSTATUS 0xC0000147 Missing image name, possible paged-out or corrupt data. .Unable to read NT module Base Name string at 05031718 - NTSTATUS 0xC0000147 .Unable to read NT module Base Name string at 05031760 - NTSTATUS 0xC0000147 .Unable to read NT module Base Name string at 050317a8 - NTSTATUS 0xC0000147 .Unable to read NT module Base Name string at 050319a0 - NTSTATUS 0xC0000147 ...Unable to read NT module Base Name string at 04f96578 - NTSTATUS 0xC0000147 Missing image name, possible paged-out or corrupt data. ....Unable to read NT module Base Name string at 04fceee0 - NTSTATUS 0xC0000147 Missing image name, possible paged-out or corrupt data. ..... ................Unable to read NT module Base Name string at 05031640 - NTSTATUS 0xC0000147 Missing image name, possible paged-out or corrupt data. ......Unable to read NT module Base Name string at 05031d48 - NTSTATUS 0xC0000147 ................ Loading unloaded module list ......................... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {ac, 2, 0, 8ea505c5} *** ERROR: Module load completed but symbols could not be loaded for TBS6281.sys *** WARNING: Unable to verify timestamp for Unknown_Module_10000000 *** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_10000000 Probably caused by : TBS6281.sys ( TBS6281+305c5 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 000000ac, memory referenced Arg2: 00000002, IRQL Arg3: 00000000, value 0 = read operation, 1 = write operation Arg4: 8ea505c5, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: 000000ac CURRENT_IRQL: 2 FAULTING_IP: TBS6281+305c5 8ea505c5 39bbac000000 cmp dword ptr [ebx+0ACh],edi DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: TvService.exe MANAGED_STACK: !dumpstack -EE OS Thread Id: 0x0 (1) TEB information is not available so a stack size of 0xFFFF is assumed Current frame: ChildEBP RetAddr Caller, Callee TRAP_FRAME: a9b559b0 -- (.trap 0xffffffffa9b559b0) ErrCode = 00000000 eax=a9b55ab8 ebx=00000000 ecx=00000000 edx=00000000 esi=866d4e48 edi=00000000 eip=8ea505c5 esp=a9b55a24 ebp=a9b55aa0 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 TBS6281+0x305c5: 8ea505c5 39bbac000000 cmp dword ptr [ebx+0ACh],edi ds:0023:000000ac=???????? Resetting default scope LAST_CONTROL_TRANSFER: from 8ea505c5 to 82c78b7f STACK_TEXT: a9b559b0 8ea505c5 badb0d00 00000000 00000000 nt!KiTrap0E+0x1b3 WARNING: Stack unwind information not available. Following frames may be wrong. a9b55aa0 8ea46fa1 a9b55ab8 00000000 8774a9cc TBS6281+0x305c5 a9b55b00 8ea2f5f6 a9b55b28 8ebb72b2 8774a7b0 TBS6281+0x26fa1 a9b55b08 8ebb72b2 8774a7b0 862c43c4 8774a724 TBS6281+0xf5f6 a9b55b28 8ebb7374 0074a724 862c4300 a9b55b60 ks!CKsPin::ProcessingObjectWork+0xc1 a9b55b38 8ebb6e60 8774a724 00000000 9e518f90 ks!CKsPin::Process+0x5f a9b55b60 8ebb7936 018987c8 8774a720 00000000 ks!CKsQueue::AddFrame+0x15c a9b55b90 8ebc66dc 862c4300 9e518ef8 a9b55bb4 ks!CKsQueue::TransferKsIrp+0x30e a9b55bbc 8ebc648f 85e30ee8 9e518ef8 a9b55be4 ks!CKsPin::DispatchDeviceIoControl+0x1c3 a9b55bcc 8ebb60ba 85e30ee8 9e518ef8 85e30ee8 ks!KsDispatchIrp+0xb0 a9b55be4 8ea20d2f 85e30ee8 9e518ef8 858278b0 ks!CKsDevice::PassThroughIrp+0x46 a9b55bfc 82c6ec1e 85e30ee8 9e518ef8 9e518ef8 TBS6281+0xd2f a9b55c14 82e62c09 858278b0 9e518ef8 9e518f8c nt!IofCallDriver+0x63 a9b55c34 82e65df2 85e30ee8 858278b0 00000000 nt!IopSynchronousServiceTail+0x1f8 a9b55cd0 82eac789 85e30ee8 9e518ef8 00000000 nt!IopXxxControlFile+0x6aa a9b55d04 82c758c6 00001dfc 00000e58 00000000 nt!NtDeviceIoControlFile+0x2a a9b55d04 77bb70f4 00001dfc 00000e58 00000000 nt!KiSystemServicePostCall 1595f8e8 77bb58a4 75be97f6 00001dfc 00000e58 ntdll!KiFastSystemCallRet 1595f8ec 75be97f6 00001dfc 00000e58 00000000 ntdll!NtDeviceIoControlFile+0xc 1595f94c 75f2ba7d 00001dfc 002f4017 00000000 KERNELBASE!DeviceIoControl+0x7e 1595f978 5cfd8992 00001dfc 002f4017 00000000 KERNEL32!DeviceIoControlImplementation+0x80 1595f9f4 5cfc0e84 0d0653c4 00000001 1595fa2c ksproxy!CStandardInterfaceHandler::KsProcessMediaSamples+0x2b0 1595fa34 5cfc0fac 00000000 1595fa64 5cfca9e0 ksproxy!CKsOutputPin::QueueBuffersToDevice+0x128 1595fa40 5cfca9e0 00000000 0d05f740 00000000 ksproxy!CKsOutputPin::MarshalRoutine+0x16 1595fa64 75f2ee1c 000c1060 1595fab0 77bd37eb ksproxy!CAsyncItemHandler::AsyncItemProc+0x1c2 1595fa70 77bd37eb 0d0c1060 6251e018 00000000 KERNEL32!BaseThreadInitThunk+0xe 1595fab0 77bd37be 5cfca81e 0d0c1060 00000000 ntdll!__RtlUserThreadStart+0x70 1595fac8 00000000 5cfca81e 0d0c1060 00000000 ntdll!_RtlUserThreadStart+0x1b STACK_COMMAND: kb FOLLOWUP_IP: TBS6281+305c5 8ea505c5 39bbac000000 cmp dword ptr [ebx+0ACh],edi SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: TBS6281+305c5 FOLLOWUP_NAME: MachineOwner MODULE_NAME: TBS6281 IMAGE_NAME: TBS6281.sys DEBUG_FLR_IMAGE_TIMESTAMP: 533bd584 FAILURE_BUCKET_ID: 0xD1_TBS6281+305c5 BUCKET_ID: 0xD1_TBS6281+305c5 Followup: MachineOwner ---------

by **smile** » Tue Oct 14, 2014 6:05 pm

Hi
i will check this mistake.and if it is true,i will release a new driver as soon as possible.

Thanks.
best wishes.

by **trickymundo** » Wed Oct 15, 2014 3:13 am

Thank you. :-)

Is this a similar unresolved problem with the TBS6280?

http://www.tbsdtv.com/forum/viewtopic.php?f=51&t=8869

by **thebluevoice** » Tue Oct 28, 2014 7:18 pm

Yep I'd say this is related to the problem I've been having for months.

Seems better since I had the 6280 replaced with a 6281 but still have had a few bsods

In the other thread I started, someone else mentioned that Microsoft are aware of it too..

by **trickymundo** » Sat Dec 13, 2014 5:31 pm

Any progress on this? It's been two months since this was reported. Nine months if you include the similar issue on the 6280 thread. Bit disappointed with lack of response.

by **infi** » Sat Jun 27, 2015 3:27 am

Having contributed to the 6280 thread, I thought I'd jump in to this one too as I bought a 6281 a month or so ago. I ran across the BSoD problem the other week and have been speaking to Lucy in TBS support again. There's now a 1.0.0.7 driver in the downloads section if anyone else having problems wants to try it. I only installed it on my server yesterday, so can't comment as to whether the issue is totally resolved, although I'm hopeful after the 6280 update from earlier this year.

by **infi** » Sat Sep 26, 2015 9:31 pm

Well it looks like the 1.0.0.7 driver hasn't fixed the issue. I've had three BSoDs in the last two weeks (two in one day) all attributed to the TBS driver according to the Microsoft Debugger. Back to the drawing board

by **Minari** » Fri Nov 13, 2015 2:28 am

I came across this thread when searching for BSOD problems connected with TBS6281 tuner. I've been having this issue too, sometimes several times a day - minidump extract attached. Has anyone had a response from TBS in regard to this issue?

My configuration:Windows 7 on an AMD A10-6700T APU with AMD Radeon HD 8650D graphics, 2.5GHz with 16GB ram on a Gigabyte motherboard. Media server is MediaPortal 1.12.0

by **infi** » Wed Apr 20, 2016 5:42 pm

It's been a long time since I looked at this board, mostly because I stopped using the 6281 due to it's unreliable drivers.

I did get responses from TBS. They were very polite, but said they couldn't reproduce the BSoDs or find much to diagnose even after I sent them a full debug dump. To be honest they didn't seem interested in spending much time investigating and fixing the problem from what I could see.

As such, I went shopping and bought a competitor product instead and haven't had a single BSoD in the last 3 months.

TBSDTV Community Forum

TBS6281 Blue screen of death

TBS6281 Blue screen of death

Re: TBS6281 Blue screen of death

Re: TBS6281 Blue screen of death

Re: TBS6281 Blue screen of death

Re: TBS6281 Blue screen of death

Re: TBS6281 Blue screen of death

Re: TBS6281 Blue screen of death

Re: TBS6281 Blue screen of death

Re: TBS6281 Blue screen of death

Re: TBS6281 Blue screen of death

Who is online