Blue screen when recording changes from 2 channels to 1 (2 Viewers)

[Brocklander]

Odd that is the CVS I am useing to. I recently added a pvr 150 to my line up and I didn't have any problems. I did uninstall, reinstall RC2 then add only that CVS to it. I didn't lay CVS over CVS. If that makes a difference.

Which Hauppauge driver version are you using? My setup is very close to yours (Nvidia codec and card, FFDShow, Hauppauge card and AMD based), so with some luck...

[Edit] I assume you're using the latest drivers from your post above 8)

 

[wishywashy]

I am useing the non-beta version of the driver from the Hauppauge site. I don't have the version numbers off hand but it came in two parts. There is a "base driver" and an update.

 

[scoop]

Hi,

There's quite some difference between the MCE and non-MCE drivers, so I wouldn't want to be mixing between MCE products and non-MCE drivers. I'd stay with the MCE drivers.
Anyway, it looks like I've solved my problem. I've been recording and switching back an forth between channels, switching tuners etc. and till so far no BSOD anymore.

I debugged the dumpfile windows had generated in C:\Windows\minidump with WinDbg. That gave me the following details:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

...

Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: f730f8d5, The address that the exception occurred at
Arg3: f7604a0c, Exception Record Address
Arg4: f7604708, Context Record Address

...

MODULE_NAME:  hcwPP2

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  43a05a91

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. De lees- of schrijfbewerking ("%s") op het geheugen is mislukt.

FAULTING_IP: 
hcwPP2+d8d5
f730f8d5 8b80505e0000     mov     eax,[eax+0x5e50]

EXCEPTION_RECORD:  f7604a0c -- (.exr fffffffff7604a0c)
ExceptionAddress: f730f8d5 (hcwPP2+0x0000d8d5)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00005e50
Attempt to read from address 00005e50

CONTEXT:  f7604708 -- (.cxr fffffffff7604708)
eax=00000000 ebx=00000014 ecx=8548524c edx=ba800100 esi=8548524c edi=00000000
eip=f730f8d5 esp=f7604ad4 ebp=f7604b3c iopl=0         nv up ei pl zr na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
hcwPP2+0xd8d5:
f730f8d5 8b80505e0000     mov     eax,[eax+0x5e50]  ds:0023:00005e50=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from f730b498 to f730f8d5

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
f7604b3c f730b498 00000000 00000100 85c47000 hcwPP2+0xd8d5
f7604bc0 f730b85a 00000000 00000001 00000100 hcwPP2+0x9498
f7604c28 f730d87c 00000016 85eba770 00000000 hcwPP2+0x985a
f7604d70 f730948e 00000000 85471488 00000000 hcwPP2+0xb87c
f7604da8 f73094f3 8057be15 85eba770 00000000 hcwPP2+0x748e
f7604ddc 804fa4da f73094ea 85eba770 00000000 hcwPP2+0x74f3
00000000 00000000 00000000 00000000 00000000 nt+0x234da


FOLLOWUP_IP: 
hcwPP2+d8d5
f730f8d5 8b80505e0000     mov     eax,[eax+0x5e50]

SYMBOL_STACK_INDEX:  0

FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  hcwPP2+d8d5

IMAGE_NAME:  hcwPP2.sys

STACK_COMMAND:  .cxr fffffffff7604708 ; kb

BUCKET_ID:  WRONG_SYMBOLS

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

In short the hcwPP2.sys driver caused a memory access violation... Not pretty useful. Basically this could mean:

• 
  - insufficient diskspace (not in my case)
  - incompatible BIOS (tried upgrading, to no avail)
  - defective RAM (tested my RAM, with memtest86)
  - defective device driver

After getting the BSOD's I tried upgrading my BIOS to the latest version and up/downgrading my audio drivers (onboard audio shares an interrupt with with one of the hauppauge tuners) all to no avail.

Last thing I've tried so far is loading BIOS setup defaults and resetting configuration (ECSD) in the BIOS, and so far no bluescreens anymore... So it must have been one of the non-default settings I was using...or maybe this is just my lucky day and the PC decided not to BSOD on me...

EDIT: OK, I spoke too soon...Just got the same BSOD. :roll: Now I'm trying to switch back to older drivers (2.0.30.23074) to see if that helps then...

Kind regards,
Michel

 

[Brocklander]

MediaPortal MyTv:
On 13/01/2006 [22:14:32] _Frodo added the following change: fixed issues with mce cards

Frodo really is amazing... I'm off to try and crash my system! Thank you so very, very much, I can safetly use my HTPC for recording again - watching normal tv is weird!

 

[scoop]

Hi Brocklander,

Can you confirm that fix for MCE-type cards solves your BSOD's? Yesterday I reverted back to (way) older drivers from here and for me my BSOD's are gone so far.

I was actually wondering what issues exactly were fixed with that CVS log message? If current CVS fixes it for you then I'm very happy to know that, so I can try going back to the new version and upgrade my HTPC to (later|latest) CVS.

Kind regards,
Michel

 

[Brocklander]

After an hour or so of testing, I had one bluescreen which I haven't been able to reproduce. It was while watching a recording timeshifted channel, then switching to another recording channel.

Every other recording scenario seems to work fine! I'll do some more testing in another couple of hours, but it all seems alright so far!