609 causing consistent BSODs

#1
Guys

First, I know what you're going to say... But I'm not a dill and I know my way around these things.

VRD is 100% reliable for me in almost all instances and I can run my machine at 100% load with no problems for weeks on end.

However I have now at least 2 video files which will cause VRD to BSOD at exactly the same point in editing. They are each 6-8Gb or so, HD MPEG-2 and both recorded from the same channel.

I haven't QSF'd them yet to see if that clears the problem. What I wanted to do was work out how to get them to you to see what you can find out....
 
#3
Not all files are perfect. Try to QSF them first.
I'm not going to QSF all my files just because a program can't handle common faults elegantly - I'm OK if VRD spits the file out and tells me to QSF it but if it makes the machine BSOD its clearly doing something it shouldn't and its something I'd hope the vendor would want to resolve.

I'm happy to QSF them and hopefully then edit them OK but its not OK to QSF everything for a few bad files.
 
#4
A BSOD usually points to a driver problem. Are you running the latest/best drivers for your graphics and sound devices? Something VRD is doing during editing/processing may be triggering a bug in one of the drivers which is causing the BSOD.

You might want to try changing the video driver that VRD is using (Tools menu>Options>Playback devices>Video Driver) and see if that makes a difference with the problem file.
 
#5
I defintitely am. This machine works hard, I use EDIUS to do high definition editing all day long and it does not miss a beat, I run ad-scans with VAP & VRD and its perfectly stable, its only while scrubbing on the timeline of these clips I get the BSOD so maybe you're on to something with the video driver.

I do run a dual-head configuration so I think offhand I only have one choice there.
 

Dan203

Senior Developer
Staff member
#6
Try changing the video driver under Tools->Options->Playback Devices. One change we made in the later versions is that the default is now VMR9. In older versions it was VMR7 or even DirectX depending on how old your previous version was. Try one of those other drivers and I bet the problem goes away.

Dan
 
#7
Well my system was set to VMR7. I tried DirectX 7 Multi-Mon and I've had a BSOD already, I grabbed the recovered project file and switched to VMR9 and was able to complete that job without a BSOD, we will see how we go...
 

Dan203

Senior Developer
Staff member
#8
I would recommend you run a video card stress test. One of the ones overclockers use to make sure their system is stable. You may have a failing video card.

Dan
 

Dan203

Senior Developer
Staff member
#9
I would recommend you run a video card stress test. One of the ones overclockers use to make sure their system is stable. You may have a failing video card.

Dan
 
#10
Dan,

There's nothing wrong with my video card - I can watch movies on it for hours every day and it never BSODs. I can use other editing and encoding software and it never BSODs. I regularly use Grass Valley EDIUS which is far more intensive than VRD and also Corel Video Studio X3 and its flawless with those.

I'm happy to presume its a driver interaction with VRD that I can hopefully solve, but this only happens with VRD and ALWAYS under the same circumstances, jumping around on the timeline between markers. So I feel it something to do with the overlay functions or thumbnail generation.
 

Dan203

Senior Developer
Staff member
#11
I think I have you mixed up with another user. There was someone else complaining about BSOD but he said it was happening in other programs as well. When I came back to this thread I just assumed it was that one. :eek:

OK so there are actually a few things I'd like to ask you...

1) Does it BSOD when you simply scrub to a specific portion of the program? Or only when actually outputting?

2) Have you looked at the BSOD error, is it definitely the video driver crashing? If so have you tried disabling YUV acceleration?

3) Can you use the Trim & Copy tool in VRD to grab just a small section of the offending video and still reproduce the problem?

If yes to #3 go ahead an upload it to our FTP and I'll check it out and see if I can reproduce the problem.

Dan
 
#12
I think I have you mixed up with another user. There was someone else complaining about BSOD but he said it was happening in other programs as well. When I came back to this thread I just assumed it was that one. :eek:
No problems. I am used to people assuming I don't know about stuff, when infact I worked for Canopus for 12 years and I work for a current Corel/Cyberlink/Pinnacle distributor and I do know my way around these things ;)

1) Does it BSOD when you simply scrub to a specific portion of the program? Or only when actually outputting?
Only when scrubbing or jumping between edit points, and I can reproduce it, it will crash always at the same point in the program.

2) Have you looked at the BSOD error, is it definitely the video driver crashing?
Event log shows this:
The computer has rebooted from a bugcheck. The bugcheck was: 0x10000050 (0xfffffffb, 0x00000000, 0x8054b51a, 0x00000000).

3) Can you use the Trim & Copy tool in VRD to grab just a small section of the offending video and still reproduce the problem
I will try. I had 2 videos on a hard drive which had BSOD on me. I tried one after changing from VMR7 to DX7/Multi Mon and still had the BSOD in the same spot, but after changing to VMR9 I was able to edit that same video just fine. I'm going to work through all my videos and see if I can make it fall over now with VMR9. What would "ideal" be for the overlay function?

I'm just wondering if the VMR7/DX7 functions, being deprecated are not being properly maintained.
 

Dan203

Senior Developer
Staff member
#13
VMR7 is still being maintained. In fact I recently added the same overlay functionality we previously only supported in VRM9 (used for display of CC/Subtitles) to VMR7 as well. In fact they share a lot of code, as there are only minor differences between the COM objects used to access them. The DirectX options haven't been updated in quite some time, but they use a very small subset of DX functionality which should be compatible regardless of which version of DX you're running.

If VMR9 doesn't fix the problem try disabling YUV acceleration and setting the audio output driver to "Wave Out". Those are the only other functions in VRD which have direct hardware access and could possibly cause a BSOD.

Dan
 
#14
If VMR9 doesn't fix the problem try disabling YUV acceleration and setting the audio output driver to "Wave Out". Those are the only other functions in VRD which have direct hardware access and could possibly cause a BSOD.
Will do - in fact I disabled audio when I switched to VMR9, bad idea to change 2 things in one go but if the crashing stops, I'll go back to it.

VRD doesn't have audio on scrub so I figure its not a problem but you just never know.
 
#16
Hey again Dan,

I suspect the condition that causes my laptop with XP to BSOD is trapped in Vista:

Code:
Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	VRDPlus3.exe
  Application Version:	3.10.3.609
  Application Timestamp:	4ce2af6d
  Fault Module Name:	VRDPlus3.exe
  Fault Module Version:	3.10.3.609
  Fault Module Timestamp:	4ce2af6d
  Exception Code:	c0000005
  Exception Offset:	00157110
  OS Version:	6.0.6002.2.2.0.256.1
  Locale ID:	3081
  Additional Information 1:	fd00
  Additional Information 2:	ea6f5fe8924aaa756324d57f87834160
  Additional Information 3:	fd00
  Additional Information 4:	ea6f5fe8924aaa756324d57f87834160
 

Dan203

Senior Developer
Staff member
#17
Vista and Win7 will not let a video driver crash take down the whole OS. So BSOD are a lot less common.

Is this the same PC just running Vista? Or is this another PC?

Dan
 
Top