-
Blue Screen of Death when rendering
-
So that explains it, i always thought it was, whenever i got one of those BSOD’s, the computer was pretty hot, but the error proved me wrong, thanks for the help
-
One more thing you have to look at: your video card.
During render it could be used by encoder and sometimes could causes problems. At the beginning you have to try disable GPU usage in Vegas Preferences as well as encoder preferences. -
I am having the same problem now.
I have Sony Vegas Pro 13, and I get a BSOD at random times, and this happens both during pre-render as well as a true render operation.
My system:
OS: MS Windows 7 Ultimate 64 bit
RAM: 2 x 4GB DDR3 Corsair Vengeance
HDD: 2 x 2TB HDD (Not sure of manufacturer)
Graphics: 2 x Nvidia GeForce 550TI 1GB GDDR5 in SLI
CPU: AMD Phenom II 965 Quad Core 3.4GHz
MB: ASUS M5A97 R2
PSU: Fractal Design Newton R2 1,000W Modular PSU
CPU cooler: Corsair Hydro Series H60 closed loopAs for my PC case, it’s custom built by myself. Made of wood, inside I have sectioned off areas for the HDDs, graphics cards and CPU. This gives most efficient cooling so hot air from the H60 radiator doesn’t mix with the air to cool the graphics cards or HDD. Each section has it’s own fan based cooling channel, so to speak. All fans are operating properly.
I’ve already run CHKDSK /F and no errors have been found. MS Driver Verifier also reports no problems. A standard RAM test comes up with no problems, but as I type this (on my laptop) I’m running an extended RAM test.
For my HDD configuration, 1 drive has just the one partition for Windows, the main C: drive. This has approx 320GB remaining space. The 2nd HDD is partitioned to drive E: (1TB capacity, 800GB free space), F: (400GB capacity, 160GB free space), H: (400GB capacity, approx 80GB free space), and X: (20GB capacity). A S.M.A.R.T health test shows both drives as healthy, some wear and tear (after 2.5 years of use) but no bad sectors.
Drive G: is reserved for my multifunction memory card reader and Drive X is where I keep my Windows page file.
I have previously rendered videos using Adobe Premier Pro, CyberLink PowerDirector and Serif MoviePlus X6 and none have thrown up BSODs while video rendering, only Sony Vegas (I have settled for Vegas as it’s easier to use and has better video codec rendering options).
I haven’t installed questionable third party codecs because I’m a system builder and very aware of the problems they can cause. The only non-standard codecs that I’ve installed comes from iTunes, DivX, RealPlayer and VLC Player.
When viewing the minidump files, the BSOD seems to be called from NTOSKRNL.SYS, though as I’ve mentioned above, Driver Verifier hasn’t found anything, neither has CHKDSK, and right now an extended RAM test shows 61% complete of pass 1 of 2, 30% complete in total but no errors present (standard test reported no errors).
When dealing with the video files, I compress them to MP4 or WMV for working with. They are about 1 hour long and about 4GB in size.
I would greatly appreciate any suggestions and I’ll report back probably tomorrow when my extended RAM test completes.
Kind regards
Kevin Pearson -
-
Hi Stephen,
Thank you for your quick reply.
I misrepresented the size of Drive X. It was actually 32GB not 20GB and I set the page file manually to be between 8,192MB to 32GB. This was when I first built the computer 2.5 years ago. I wouldn’t think the page file or it’s drive it’s stored on would be the issue.
I have now moved the page file back to Drive C and is now system managed. I’ll report back if I come across any problems.
As an update though, the extended RAM test came back with no errors and a SFC check also reported no corruptions.
Kind regards
Kevin PearsonEDIT:
Nope. I still get BSODs. I’ve even tried switching from CUDA rendering to OpenCL as well as CPU only.I have now attached the last minidump file created. I would imagine it seems to be a driver issue, but I don’t have any experience in debugging a dump file. My graphics drivers are up-to-date using GeFore Experience and the driver version is 344.75, release date Nov 18, 2014.
Kind regards
Kevin Pearson -
I would suspect that it’s time to re install everything. BSOD is pretty rare in Win7 but PageFile errors are one place that you can still get them. The NTOSKRNL is pretty much the heart of the OS. Windows 7 is built on the Windows NT Kernel, which was built on top of DOS, so all this means is that the kernel was trying to do an operation when it crashed. Your Pagefile is managed by the kernel which is why that is the first thing to check. But switching it back to your boot drive and letting Windows manage it was a good test. You probably know this, but Pagefile settings don’t change until you reboot.
You can also get BSOD if you use up your allotment of GDI resources. Every graphics object, the ones you see like icons and windows, plus those held in RAM is a GDI object. I haven’t ever seen it happen, but if you have thousands of still images on a video project, every one of those images consume a GDI.
Here’s an article from Microsoft that may help, at least to use Task Manager to see if you are anywhere near using all the allocated GDI objects.Steve Mann
MannMade Digital Video
http://www.mmdv.com -
Yes I did reboot when changing page file settings as the settings will not physically change until the computer is rebooted.
One would have thought Microsoft would have updated the coding and capabilities properly for NTOSKRNL, of which I know also of it’s history since Microsoft didn’t give Windows 7 any official release name except the NT version it’s built on.
As for the GDI resources, I really cannot see these being maxed out. My project currently is just overlaying a webcam video over a gameplay video for my YouTube channel. At most I’ve used 20 pictures in a project and only the 2 videos. My initial assumption from the very start was the program trying to interpolate a 30fps webcam video onto a 60fps gameplay video. So to ease up on this I re-rendered the webcam video only (the webcam itself is locked to 30fps so I cannot do a raw video capture any higher) using field interpolation and upscale it to 60fps on the single video track. Then I later overlay this video onto the gameplay video after a program restart to flush the memory.
I’ve now even come to the point where to minimize resources, once the two video tracks have been rendered into a single video file, that’s when I get to work splitting it and adding text overlays.
I think what I’ll do is, I don’t want to go down re-install just yet as every other software still works without any crashing, I’ll wait until Windows 10 is released as it’s supposedly going to be free, buy a bigger harddrive to use in my 2nd PC, beef up the RAM a bit in it and use that as my media editor. I will only re-install Windows on my main PC if and when it either slows to crawl or I get more BSODs while running other resource intensive software (such as games or CAD software).
Thank you for looking into it though Stephen. Very much appreciated.
Kind regards
Kevin Pearson -
look at the GDI’s while rendering anyway. I haven’t seen it happen but another user had an errant driver or codec, I don’t recall which, that was not releasing GDI’s properly. He reported that he could watch the GDI useage climb during the render, and as soon as it got really high, he got the BSOD. If I recall, it was a New Blue F/X plug-in. If you are using any NB FX, try a render without it.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
Well, I’ve opened Sony Vegas and without rendering it uses 699 GDI objects. So at least I can get some work done I’ve reverted back to Serif MoviePlus for now. Doesn’t have the same great effects and plugins Vegas has to offer, nor does it support GPU rendering, but as I type this I’m rendering the same project of 2 video tracks into one video, and that has a GDI of 944.
Once this render has completed I’ll attempt another Vegas render and report back (this will take a while though) but I honestly do not feel GDI resources are the issue.
As for the plug-ins, I’m not using any. I place the webcam video in one corner of the screen and using Track Motion I put a green-glow 2D shadow around the webcam. That’s it.
You could be right on your first suggestion, re-installing Windows maybe the solution.
Kind regards
Kevin Pearson
Reply to this Discussion! Login or Sign Up