ProgDVB x86(or x64) 6.90.01
TBS DVBC USB Stick - version driver 2.0.0.2 (last)
Windows 7 Home Premium x86 (all updates)


I use PMS(home) unicast for LAN streaming.
After hours or days ProgDVB(server side) freezing and after restart computer has BSOD 0x000009F ("Driver Power State Failure").
If I kill task from task manager the process(ProgDvbNet.exe) is Suspended from Running, but not dead.

Please, help me!

You can look on blue screen, what driver crash your system.

I think the problem isn't the driver.

Program: ProgDVB Professional x86(or x64) 6.90.1 with active PMS(home/pro/large).
OS: Windows 7 Home Premium x64 (all updates)

try this method(A):
1. Open with /NoGraph (this is change to "Video renderer(OSD not supported)")
2. Minimized in tray
3. right click and close program.
4. Open program again(program started minimized)
5. Try open program from tray icon, this is impossible

but with this method(B):
1.Open without /NoGraph (set "Enhanced video renderer" manually)
2. Minimized in tray
3. right click and close program.
4. Open program again(program started minimized)
5. Try open program from tray icon. NO PROBLEM! All works fine.

If I try kill process from task manager when ProgDVB is freeze the process ProgDvbNet.exe change status from "Running" to "Suspended".
I try this methods with x64 and x86 versions and Standart and Professional versions.

With "stability mode" or without - method A freeze and BSOD.

Sorry for my very bad english!

Again. BSOD is driver problem. You can look on blue screen what driver is crash.

If the problem is in the driver why with "/NoGraph" I have problem, but without "/NoGraph" all work fine?

This is not important. Application (any application) not have rights for BSOD. Only driver can do that.

Driver worked perfectly but without option "/NoGraph".
The problem is after use "/NoGraph", this is option for ProgDVB, this is NOT option for the driver.

TBS sent me a new driver but I have againt BSOD with same parametres.

You are sure for driver problem?
I think the program is not working properly with the driver.

Please read driver file name (xxxxxx.sys for example) on blue screen at first. It can be any driver in system, not only BDA.