Hi, I'm an XP 64 bit user, and have just today upgraded the to the latest version (of 32 bit ProgDVB) and it kills my whole machine (Blue Screen) immediately after attemptng to output to the screen. In years of use I have never had such a critical error. I have uninstalled prog, and re-installed it with exactly the same problem at exactly the same point. I have never managed to get the 64bit version of prog to stay in sync (after hours and hours of single changes to config etc) , hence still using the 32 bit version. I've had problems with the subs before, could it be this (don't get chance to switch them off) ? Thanks

1. ProgDVB (or any application) not can request Blue screen. Only driver can do that.

Non of the previeous versions did this, and the drivers haven't changed. Are you honestly sayng that this is not related to prog code?? Also, where is point 2 ? or does point 1. and at point 1.

What problem with subs?

Maybe you should look into ProgDVB.ini with your editor / notepad.

For example, there is a line

ParseTeletextAlltime=1

Change to

ParseTeletextAlltime=0

A bit below you'll find a section named

[DisabledModules]

Here you can disable some modules, that are suspected to cause trouble at startup time, like TXT or EPG.
Subs normally come from TXT module, but in case of ETSI based subs, it's an extra module.
Further down there is

[AVManager_Record]

Set

Subtitles=0

there.

Also delete EPG.dat from ProgDVB base folder

I have never played around with skins, but those may also cause trouble sometimes. Same goes for language files.
Default what's possible.
Remove all plugins.


Regarding BSOD, an application normally can't produce this (on modern Windows), but theoretically it could cause a driver to do this.
In such cases, the original reason would surely be a weakness in the driver and / or bad documentation on driver <-> application communication.

Thanks Juergen,

I will re-install the 32 bit version and make the changes you have described. I'll let you know the outcome.

For further information, I have installed the 64 bit version of the 6.45.03 code, and it does NOT act in the same way, although I still have the problems with synchronisation that I have always had.

One thing that I did notice with the 32bit version, is that it would 'scrape' the desktop background into the output screen area, so it's clearly not refershing itself. I've not seen this before either, so I'm assuming they are related. Andy

Hi again Juergen,

I have re-installed 32bit Prog and replicated the error exactly. unfortunately after making all the changes you have mentioned, it is still the same. I have even disabled ALL the modules.

I also removed 6.45.03 and installed 6.45.02, which hasn't made any difference, so it's nothing that was changed for 6.45.03.

Regarding the drivers. It's just a standard DVB-S1 BDA Device (Skystar 2). I'm using the same drivers I have used for quite a while now (years) and have never had this problem before. Whatever call is being made from prog at this point, it is really upsetting it.

I will also look into finding a newer version of the X64 Skystar2 drivers.

How can I get an earlier version of the ProgDVB code ?

Thanks, Andy

Some older 32bit versions of ProgDVB are still available from the download page here.
Don't remember, from which on the SS2 was supported, but some early 4.x I suppose...

Hi Juergen,

I installled the latester (2010) BDA Drivers for the SS2, and it made no difference.

I do however know where the problem lies now, and it's when you render the screen. I had noticed that it was the moment that the channel information was shown that the machine went to blue screen, so I switched to 'VMR-9 Renderless' from the default 'Enhanced Video Renderer' and it worked fine. I've sinced put the rendering back on using VMR-9, and so far it seems to be ok, so it looks like the problem is with how the 32bit code uses the Enhanced Video Renderer on a 64 bit system.

I hope this is of use to you. Andy