Tuner causes Nrecord crash??

[sub]

Great - glad you got it fixed. Microsoft was trying to make me look bad.

[macgyver]

I've been having the psisdecd.dll issue but it has much improved since upgrading to latest directX and XP SP3 but still occurs daily. I have found that dvbfix.zip file you mentioned but using that copy either failed completely (NRecord would crash instantly) or created 0 byte recordings or ran but still caused crashes, depending on which files in the zip I included.

Can you confirm that yours is still running OK now, which files you used and if you also have latest directX and SP3? Was it just psisdecd.dll you used?

Any other advice appreciated, but I'm guessing it may be time for Windows 7...

[petercooperjr]

This seems like the same issue I've had with [thread=48855]NRecord breaking when recording on multiple tuners[/thread]. I haven't had NRecord crash much or had a bluescreen, but I may not have just let it run for long enough. But looking back a little, I did get an NRecord crash once with this in my event log:

Code:

Event Type:    Error
Event Source:    Application Error
Event Category:    (100)
Event ID:    1000
Date:        1/5/2011
Time:        6:42:30 PM
User:        N/A
Computer:    ICE
Description:
Faulting application NRecord.exe, version 1.0.0.0, faulting module PsisDecd.dll, version 6.5.2600.5512, fault address 0x0000f34b.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 4e 52 65   ure  NRe
0018: 63 6f 72 64 2e 65 78 65   cord.exe
0020: 20 31 2e 30 2e 30 2e 30    1.0.0.0
0028: 20 69 6e 20 50 73 69 73    in Psis
0030: 44 65 63 64 2e 64 6c 6c   Decd.dll
0038: 20 36 2e 35 2e 32 36 30    6.5.260
0040: 30 2e 35 35 31 32 20 61   0.5512 a
0048: 74 20 6f 66 66 73 65 74   t offset
0050: 20 30 30 30 30 66 33 34    0000f34
0058: 62                        b

It being an issue with reading the PSIP data would definitely explain why it works for a little bit and then breaking: there's something in the stream that it doesn't like, but somehow only when recording two things at once.

So I too would be interested in the exact fix for this.

[sub]

Crashes in PsisDecd.dll have been pretty common over the years, especially in XP. You'll also find threads about it on the Hauppauge forums, or Mediaportal forums. Personally I've never encountered it, but I think its limited certain data some broadcasters use in their streams, so may not be problem here in NZ. The fix has always been finding a different version of this dll. I havnt followed the issue closely myself though, so I cant tell you exactly what version of the dll you should be looking for.

[StevHodge]

The fix I wrote about above does work, mostly. I sometimes still get crashes, but only once or twice since I put the "fix" in. I only used the dll I mentioned in the post, not the rest of dbfix. Indeed that did seem to crash everything. This occasional crash syndrome does cause a certain amount of angst, but the work around is not to multiple record when you are scheduling something vital - not truly satisfactory! In the UK the combination of BBC2 and Channel 4 seems the most crash prone

Steve

[macgyver]

OK, for information, here's a summary of my recent experience in case anyone else is hair-tearing too.

- I have never had this error in all my years with GB-PVR
- I moved to NPVR and the errors started and were frequent, recordings would not usually reach an hour.
- I upgraded to XP SP3 (which updates the psisdecd files) and the problem was much reduced, but still got crashes daily.
- I found the dvbfix.zip file on the media portal forum and tried to install just psisdecd.dll but nothing would work then, if it didn't crash I had 0 byte files.
- Tried to install all three files but the psisrndr.ax would not register. A quick Google told me that it needs Windows Media Player 11 and I only had 10 so I upgraded that and then all three files registered.

Since then, a few days ago now, I have not had a single crash. However, I needed to do a rescan and this crashed. DOH! So I had to restore the latest psisdecd trio, re-register them, do the scan and then put the older versions back and re-register them. Bit of a pain but obviously I rarely scan so not a problem.

Fingers crossed I'm all OK now.

[morser]

I wanted to mention a good program for determining what crashes a system. After a blue screen, install "WhoCrashed Home Edition 2.10" which can be downloaded for free from http://www.respendence.com. It will identify the culprit (driver, etc) of the last crash. Makes it easier than catching the BSOD.

A quick note i'm experiencing the same symptoms described in this thread. If there is room I'll move in here and stop my other thread

[petercooperjr]

- I have never had this error in all my years with GB-PVR

That's what I keep coming back to in my mind. This works in GB-PVR just fine. There's got to be something different in how they work somehow, in a way that's not obvious.

[morser]

Starting to manually record one show, it records just fine.
Adding a 2nd manually recorded show, it crashes. Both recordings stop, lucky if I can cancel them. End Service and End Task on NPVR.

So are only Windows Xp 32 users having the issue? Is Windows 7 64Bit better for NPVR? It's obviously a better O/S. but if that fixes this then that is enough for me.

[johnsonx42]

it does seem to me most people who are suddenly reporting all these problems are running XP. I've always run NPVR on Windows 7 32-bit, and I've never had the sorts of problems being reported in this and other similar threads.