galmok Posted January 3, 2008 Posted January 3, 2008 I had set DVBViewer to record something during the night and when I checked the pc this morning, DVBViewer was crashed. AppVer: 3.9.1.1 ModName: ntdll.dll ModVer: 5.1.2600.2180 Offset: 00018fea I use an nforce4 motherboard, amd x2 cpu, ati 1900xtx graphic card and a Sandberg USB Digi-TV (AF9015 BDA Device). DVBViewer was started by windows task scheduler as setup by scheduler.exe. DVBViewer, although with a crash box, still continued to show video and audio. Actually, DVBViewer seems to work fine (including channel switching) except it produced the crash box. :-/ support.zip Quote
galmok Posted January 10, 2008 Author Posted January 10, 2008 Well, now DVBViewer locked up. It is minimized and I can't restore it. This is the task's info from TaskInfo: [Current Process Pane] Thread Start Address: Symbol Name: Line Number: PC: DVBViewer + 4287A0 ------ 8287A0 Thread Stack:: Symbol: Line Number: PC:Stack Frame: ntdll ! KiFastSystemCallRet() + 0x0 ------ 7C90EB9412BB4C ntdll ! RtlEnterCriticalSection() + 0x46 ------ 7C90104B12BB84 DVBViewer + F1528 ------ 4F152812FBA4 DVBViewer + 2864E3 ------ 6864E312FCC0 DVBViewer + 283945 ------ 68394512FCF4 DVBViewer + 1D6C88 ------ 5D6C8812FDC4 DVBViewer + 46FAE ------ 446FAE12FDF0 DVBViewer + 3155E ------ 43155E12FE08 USER32 ! GetDC() + 0x6d ------ 7E41873412FE34 USER32 ! GetDC() + 0x14f ------ 7E41881612FE9C USER32 ! GetWindowLongW() + 0x127 ------ 7E4189CD12FEFC USER32 ! DispatchMessageA() + 0xf ------ 7E4196C712FF0C DVBViewer + 8DC5C ------ 48DC5C12FF78 DVBViewer + 2F54B1 ------ 6F54B112FFC0 kernel32 ! RegisterWaitForInputIdle() + 0x49 ------ 7C816FD712FFF0 The task is using 1 full cpu. My only option is to kill it. Again, DVBViewer was started with scheduler and again it failed to fully record what I wanted. I have still not managed to crash DVBViewer while I started it myself. It has only crashed when started by scheduler (not always, though). support.zip Quote
galmok Posted January 10, 2008 Author Posted January 10, 2008 Could it be that DVBViewer doesn't like that it has to spin up my hard disks before it can write to them? I noticed one file was 0 bytes, indicating DVBViewer was ready to write, but didn't get to write 1 single byte... On the other hand, another show it recorded was cut short, probably due to the lockup or maybe the disk spun down. I hope DVBViewer can handle this delay with internal buffers (got 2GB memory, should be plenty). Quote
Moses Posted January 11, 2008 Posted January 11, 2008 is this on encrypted channels? Maybe decryption had problems, this is the most likely reason for such things. You could try and enable the "smart buffer" and the size very high (DVBViewer will only use it, if it has to). DVBViewer uses normal winapi calls to write to disc, so if windows can, DVBViewer will be able, too. Quote
galmok Posted January 11, 2008 Author Posted January 11, 2008 Non-encrypted channel (don't have any encrypted ones). Smart buffer was already enabled (20MB), but I raised it to 100MB now. Maybe that helps. Still, if that is the reason, I think DVBViewer should produce a warning/error instead of crashing. :-P Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.