new anomoly with 7.1.7 and Colossus

[tvmaster2]

Originally Posted by coryking

Yes, the delay_to_wait_after_tuning.

I do not have my cable box locked to a specific resolution. I plan to do what the Hauppage people say and take out the HVR1600 first. If that doesn't fix it, I'll keep the resolution fixed (or just do whatever they tell me to do next).

have you complained to Hauppauge yet? that would be preferable to limiting your viewing options by locking the resolution. just my .02

[coryking]

Yup. They want me to pull the second capture card out and see if that makes a difference. Gonna try that today if I have time.

Honestly though, I am seeing fewer BSOD's than I was before bumping that "delay_<blah>" property up to 8 seconds.

I hate troubleshooting random hardware issues. Reminds me of troubleshooting electrical troubles on cars, only with cars it is usually a ground issue :-)

[FlyingDoc]

Just thought i would update you all on my e-mails with Hauppauge....
I logged this blue screen as a bug with them ....
First response was to imply they had never seen this issue....
I suggested they check out this thread.... They stated that they would not output a blue screen in the event of a video loss.. and then they implied the source device was producing the blue screen

In an attempt to point their engineering in the correct direction i suggested re-reading the datasheet of the A-D used on the board as it will generate a blue screen its-self under some conditions ... so far no response from them.

We'll see what Monday brings..

[KeithAbbott]

Originally Posted by FlyingDoc

In an attempt to point their engineering in the correct direction i suggested re-reading the datasheet of the A-D used on the board as it will generate a blue screen its-self under some conditions ... so far no response from them.

Wow, nice research. Hopefully it pays off, there are some of us who are very interested in getting the blue screen issue resolved. Do you have a link to the datasheet that you could post here?

[FlyingDoc]

The part is from Analog Devices ADV 7441a .. try googling 'ADV7441a datasheet' or 'ADV7441a blue screen'

[KeithAbbott]

Originally Posted by FlyingDoc

In an attempt to point their engineering in the correct direction i suggested re-reading the datasheet of the A-D used on the board as it will generate a blue screen its-self under some conditions ... so far no response from them.

So, if the problem lies in the A-D chip used in the Colossus, I wonder if using a component input to HDMI output converter like the HDC-CAH (http://www.monoprice.com/products/pr...seq=1&format=2) would resolve (well, bypass) the issue? The converter would need to be inserted between the cable box and the Colossus. It's still a workaround, and I would prefer the Colossus component inputs to work properly without blue-screening, but it might be worth a try.

[coryking]

Just as a follow up to my research.

So far, I still get blue screen recordings and BSOD's. I've also noticed a heck of a lot of interlacing when it records fast motion. By "interlacing" I mean you can kind of see half the picture change to the next frame then the second half--only interlaced.

About five minutes ago I pulled my older HVR1600 at the suggestion of Hauppauge's support. I'm crossing my fingers that will (temporarily) fix the problem with at least the BSOD's.

I have not yet got my set top box to record on a fixed resolution--trying to keep things to one change at a time.

[coryking]

Originally Posted by KeithAbbott

So, if the problem lies in the A-D chip used in the Colossus, I wonder if using a component input to HDMI output converter like the HDC-CAH (http://www.monoprice.com/products/pr...seq=1&format=2) would resolve (well, bypass) the issue? The converter would need to be inserted between the cable box and the Colossus. It's still a workaround, and I would prefer the Colossus component inputs to work properly without blue-screening, but it might be worth a try.

If somebody buys that and it works, make sure to let us know :-)

[Vysrany]

I haven't noticed any of those interlacing issues. How common is that for you?

My BSOD's went away when I changed the merits on my tuners. Priority order from most desired tuner to least is HVR2250, Colossus, HDPVR. When I had them all sharing the same priority, my system would last 4 hours max before a BSOD.

[tvmaster2]

Originally Posted by Vysrany

I haven't noticed any of those interlacing issues. How common is that for you?

My BSOD's went away when I changed the merits on my tuners. Priority order from most desired tuner to least is HVR2250, Colossus, HDPVR. When I had them all sharing the same priority, my system would last 4 hours max before a BSOD.

how do you change the priority order merits of your tuners?

[sleonard]

Originally Posted by tvmaster2

how do you change the priority order merits of your tuners?

Each of your tuners will have a line in the sage.properties file that looks like this:

mmc/encoders/-112107779/encoder_merit=0

The number there is unique to your tuner and will be different for each one. The merit setting is higher for higher priority, i.e. - a tuner with a merit of 3 will get higher priority than one with a merit of 1.

S

[damonbrodie]

Sorry for the dumb question.. Are you folks talking about Blue Screen Of Death (BSOD) or recording a blue screen with the colossus card?

My Sage 7.1.7 server is BSODing about once every 5-7 days - it is the only tuner in the server. I'm running the latest available drivers for the card.

Today I set the machine to reboot once per day to help avoid the BSODs. I think I have my STBs set to a fixed 1080i resolution, but I need to verify that.

I'm a recent convert over from BTV. Sage is very nice compared to BTV and overall feels more solid. Hopefully the Colossus turns out better than the hd-pvr in the long term (I had 2 of those on BTV, RMAed them twice each and gave up when they both died a third time....)

[coryking]

I get both "blue screen" recordings and the dreaded Blue Screen Of Death.

I finally took some time and pulled up several of the memory dumps generated after a BSOD and it clearly pins the fault on the hauppauge driver. Both before and after pulling the second tuner out of the system.

If anybody is curious how to get these crash dumps, you can check out this helpful article: http://forums.majorgeeks.com/showthread.php?p=1418737

Needless to say, I've emailed my findings to the folks at Hauppauge. Hopefully this will help them figure out what is going on.

Honestly, it makes me a bit releaved as I was worried it was some other component of my system causing the trouble.

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000040, memory referenced
Arg2: 000000000000000c, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8000286b20a, address which referenced memory

Debugging Details:
------------------


AUTOBUG_USER_LCID_STR:  ENU

AUTOBUG_OS_SKU:  1

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002a41080
 0000000000000040 

CURRENT_IRQL:  c

FAULTING_IP: 
nt!KeWaitForSingleObject+14a
fffff800`0286b20a 807d0002        cmp     byte ptr [rbp],2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffffa60019d47f0 -- (.trap 0xfffffa60019d47f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80002a43440 rbx=0000000000000000 rcx=fffffa60017d27f0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000286b20a rsp=fffffa60019d4980 rbp=0000000000000040
 r8=fffffa80036b67d8  r9=fffffa80036b68a8 r10=0000000000000000
r11=000000000000000c r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KeWaitForSingleObject+0x14a:
fffff800`0286b20a 807d0002        cmp     byte ptr [rbp],2 ss:0018:00000000`00000040=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000287422e to fffff80002874490

STACK_TEXT:  
fffffa60`019d46a8 fffff800`0287422e : 00000000`0000000a 00000000`00000040 00000000`0000000c 00000000`00000000 : nt!KeBugCheckEx
fffffa60`019d46b0 fffff800`0287310b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x6e
fffffa60`019d47f0 fffff800`0286b20a : 00000000`00000000 00000001`00000110 fffffa80`036b6700 fffffa60`019d49b0 : nt!KiPageFault+0x20b
fffffa60`019d4980 fffffa60`080f6b7d : 00000000`00000000 fffffa80`00000000 fffffa80`05989600 00000000`00000000 : nt!KeWaitForSingleObject+0x14a
fffffa60`019d4a10 00000000`00000000 : fffffa80`00000000 fffffa80`05989600 00000000`00000000 00000000`00000000 : hcwD1cap+0x8b7d


STACK_COMMAND:  kb

FOLLOWUP_IP: 
hcwD1cap+8b7d
fffffa60`080f6b7d ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  hcwD1cap+8b7d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hcwD1cap

IMAGE_NAME:  hcwD1cap.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4dafde38

FAILURE_BUCKET_ID:  X64_0xA_hcwD1cap+8b7d

BUCKET_ID:  X64_0xA_hcwD1cap+8b7d

Followup: MachineOwner
---------

[tvmaster2]

Originally Posted by coryking

I get both "blue screen" recordings and the dreaded Blue Screen Of Death.

I finally took some time and pulled up several of the memory dumps generated after a BSOD and it clearly pins the fault on the hauppauge driver. Both before and after pulling the second tuner out of the system.

If anybody is curious how to get these crash dumps, you can check out this helpful article: http://forums.majorgeeks.com/showthread.php?p=1418737

Needless to say, I've emailed my findings to the folks at Hauppauge. Hopefully this will help them figure out what is going on.

Honestly, it makes me a bit releaved as I was worried it was some other component of my system causing the trouble.

[---------[/CODE][/SIZE]
[/FONT]

yeah, I concur - my problems started after installing the latest Hauppauge drivers for the Colossus. It seems to take Hauppauge quite some time to make working drivers. Thanks for emailing them - did you send them this forum link?

[sleonard]

I take back my previous claims to not experiencing BSOD's. I definitely am. I just didn't notice at first because the server is headless and not used for anything but Sage stuff. I have found three "Recovered from Blue screen" messages upon logging into RD lately.

S

[jptheripper]

Originally Posted by sleonard

I take back my previous claims to not experiencing BSOD's. I definitely am. I just didn't notice at first because the server is headless and not used for anything but Sage stuff. I have found three "Recovered from Blue screen" messages upon logging into RD lately.

S

What does you event log say for the system error?

[damonbrodie]

I have three DMP files that have similar signatures. I've decided to set my SageTV to reboot every day in hopes of staying stable. I have two Colossus cards.

I really hope Hauppauge does a better job with Colossus than they did with HDPVR. I had no end of crashes, and dead units with that piece of junk.

UPDATE:

Here are the contents of my BSOD:

==================================================
Dump File : 053011-19874-01.dmp
Crash Time : 5/30/2011 7:09:26 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 0x00000024
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x828c2fb9
Caused By Driver : halmacpi.dll
Caused By Address : halmacpi.dll+5ba9
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Crash Address : ntkrnlpa.exe+415cb
Stack Address 1 : ntkrnlpa.exe+76fb9
Stack Address 2 : hcwD1cap.sys+6ad9
Stack Address 3 : hcwD1cap.sys+13b3b
Computer Name :
Full Path : C:\Users\Damon\Desktop\053011-19874-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 145,280
==================================================



I submitted my dumps to Hauppauge via their support web site. I'd encourage everyone to do that so that pressure is applied to get the driver fixed.

[KeithAbbott]

Originally Posted by KeithAbbott

So, if the problem lies in the A-D chip used in the Colossus, I wonder if using a component input to HDMI output converter like the HDC-CAH (http://www.monoprice.com/products/pr...seq=1&format=2) would resolve (well, bypass) the issue? The converter would need to be inserted between the cable box and the Colossus. It's still a workaround, and I would prefer the Colossus component inputs to work properly without blue-screening, but it might be worth a try.

I received and installed my converter yesterday, and while it is still too early to celebrate, there have been no blue screens yet. I am able to switch back and forth between 480i, 720p, and 1080i channels without a problem. Although after enough channel surfing, eventually the server did crash and reboot, which is a different issue. As much as I hate to do it, a daily therapeutic restart would get the system stable enough for WAF/KAF, I believe. PQ seems roughly comparable to using component directly into the Colossus.

I am a little sad, after reviewing the release notes for the 7.1.8 beta, there looks to be nothing in there to improve on the stability/reliability of the Colossus. Still waiting for the updated driver that SHS mentioned a month or so back, maybe that will get us where we need to be...

[tvmaster2]

Originally Posted by KeithAbbott

I received and installed my converter yesterday, and while it is still too early to celebrate, there have been no blue screens yet. I am able to switch back and forth between 480i, 720p, and 1080i channels without a problem. Although after enough channel surfing, eventually the server did crash and reboot, which is a different issue. As much as I hate to do it, a daily therapeutic restart would get the system stable enough for WAF/KAF, I believe. PQ seems roughly comparable to using component directly into the Colossus.

I am a little sad, after reviewing the release notes for the 7.1.8 beta, there looks to be nothing in there to improve on the stability/reliability of the Colossus. Still waiting for the updated driver that SHS mentioned a month or so back, maybe that will get us where we need to be...

yeah - it is taking a long time for these things - switching between resolutions, since advertised in Colossus initial literature, shouldn't be something we're having trouble with four months after release

[gplasky]

Originally Posted by tvmaster2

yeah - it is taking a long time for these things - switching between resolutions, since advertised in Colossus initial literature, shouldn't be something we're having trouble with four months after release

Why not? Some people stilll have this same issue with the HD-PVR. Everyone thought the Colussus was going to be the fix for all the ills people have seen with the HD-PVR. It just may be that this issue seen with resolution/audio changes with different chipsets (Colussus and HD-PVR use different chipsets) is just the nature of the beast and is tougher to solve than anyone ever thought. I also think the fix will be found within the drivers and mostly is not a fix that Sage can implement. Just my 2 cents.

Gerry