Vegas 12 causing system to restart.

deadbandman wrote on 10/3/2013, 11:31 PM
I can't do anything. I'm lucky to get more than four minutes worth of editing and one minute worth of playback becore the entire system just restarts on me.

I re-installed windows and afetr I was done restoring everything I tried to render a video and it immediatly restarted.

Vegas 12.0 64bit Build 486
Windows 7 X64
AMD 8-core bulldozer CPU
32Gigs corsair dominator ram
Radeon 6770HD PCIe

I'm downloading build 726 now and will give that a try.

Comments

Gyan wrote on 10/3/2013, 11:41 PM
I'd suspect bad RAM.

Download and run Memtest86+ for at least 2 passes.
deadbandman wrote on 10/4/2013, 10:13 AM
I too am wondering if it was RAM as this has been a progressivly worsening issue but my tester can't handle 8G cards so thanks for the link. Luckily Corsair honors their product and in the past have given me complete replacement of a bad card. Unfortunatly this is a really bad time for me and I may be forced to remove the offending card and hold out replacement until after I'm done the project I'm working on.

....If it's the RAM.
set wrote on 10/4/2013, 10:34 AM
If you can do it: my PC builder suggested to open the case, and clean it, especially the RAM memory connections, discard, clean it, and attach it again.

Setiawan Kartawidjaja
Bandung, West Java, Indonesia (UTC+7 Time Area)

Personal FB | Personal IG | Personal YT Channel
Chungs Video FB | Chungs Video IG | Chungs Video YT Channel
Personal Portfolios YouTube Playlist
Pond5 page: My Stock Footage of Bandung city

 

System 5-2021:
Processor: Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz   2.90 GHz
Video Card1: Intel UHD Graphics 630 (Driver 31.0.101.2127 (Feb 1 2024 Release date))
Video Card2: NVIDIA GeForce RTX 3060 Ti 8GB GDDR6 (Driver Version 551.23 Studio Driver (Jan 24 2024 Release Date))
RAM: 32.0 GB
OS: Windows 10 Pro Version 22H2 OS Build 19045.3693
Drive OS: SSD 240GB
Drive Working: NVMe 1TB
Drive Storage: 4TB+2TB

 

System 2-2018:
ASUS ROG Strix Hero II GL504GM Gaming Laptop
Processor: Intel(R) Core(TM) i7 8750H CPU @2.20GHz 2.21 GHz
Video Card 1: Intel(R) UHD Graphics 630 (Driver 31.0.101.2111)
Video Card 2: NVIDIA GeForce GTX 1060 6GB GDDR5 VRAM (Driver Version 537.58)
RAM: 16GB
OS: Win11 Home 64-bit Version 22H2 OS Build 22621.2428
Storage: M.2 NVMe PCIe 256GB SSD & 2.5" 5400rpm 1TB SSHD

 

* I don't work for VEGAS Creative Software Team. I'm just Voluntary Moderator in this forum.

dxdy wrote on 10/4/2013, 10:57 AM
Vegas won't come close to using 32G of RAM. Take half of it out and try it. If it works fine, you know it's the other half of the RAM.

If Vegas still crashes with half the RAM out, take out another half of the RAM and try again - it will run fine with 8G or even 4G.

The good old "half interval method".
deadbandman wrote on 10/4/2013, 11:00 AM
My cooling system is in another room(Liquid cooled), there's no dust inside my case.
deadbandman wrote on 10/4/2013, 11:02 AM
Why won't it use that much ram? My project has 60+Gs of .TOD video in it?

The test is taking 1 hour per pass, per card so after the test on this card is done I'm putting them all back in, pull one and try it. Repeat each card and if it stops, test that pulled card.
John222 wrote on 10/4/2013, 11:48 AM
If it turns out not to be a ram problem and the shut down was preceeded by a blue screen, you can use this viewer to determine exactly which driver failed.

http://www.nirsoft.net/utils/blue_screen_view.html
Pete Siamidis wrote on 10/4/2013, 12:06 PM
The only time I ever had an issue with Vegas was years ago and it turned out to be due to a no-name power supply I was using. Took forever to track the issue down, but basically that power supply being a generic brand couldn't supply the consistent power that Vegas needed and all sorts of weirdness would result, sometimes just basic crashes but also including system restarts. I switched to a more expensive but quality name brand power supply years ago and haven't had any issue with Vegas since.
OldSmoke wrote on 10/4/2013, 1:14 PM
+1 Pete!

Many PC owners dont understand how important a good and constant power supply is. Aside from a very good PSU I also have a UPS that not only safes me from power outage but also smooth over the "dirty" power that comes from a standard wall socket. I never had any of the issues people are complaining here, not with VP11 and not with VP12.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

Steve Mann wrote on 10/4/2013, 1:42 PM
Run the Windows Reliability Monitor (Start/run/ "Reliability") and see if there's any helpful information.
Gary James wrote on 10/4/2013, 2:28 PM
"Run the Windows Reliability Monitor (Start/run/ "Reliability") and see if there's any helpful information."

Win7 64 bit can't find this program. Is this unique to Win8 or something else?
deadbandman wrote on 10/4/2013, 2:32 PM
OK, I pulled ram cards one at a time and tried rendering my project and sure enough th esystem restarted. (FYI there was no blue screen after restart, just restarting.) I would put the card back in and pull the one next to it and try again. Finally on the last card I pulled before getting to the one that had passed one pass of the test, the render completed with no restart. In a bit I'm going to pull all cards and put that one card back in and run the ram test.
VMP wrote on 10/4/2013, 2:57 PM
I had the restarting issue because my CPU got overheated!
Re-pasting a new cool sink on the CPU plus some new fans for airflow solved the problem.
That was on my previous system.

There are many tools available to check the CPU temp. I used the software that came with the Asus motherboard. Best is to do this during render. The restart always occurred during the renders of H264 files.

But reading your post it could be the RAM.

VMP
deadbandman wrote on 10/4/2013, 3:17 PM
My CPU is designed to handle 160F. A CPUtemp program I run says all 8 cores are around 90-120F and my water coming out of the block is 75F. I used to have an overheating problem because of stagnant air in my studio so I mounted the radiator in my basement where it's 70F during a summer heatwave and ran the lines through the floor. This also almost completely silenced my system as now the only fan is the video card.
Steve Mann wrote on 10/4/2013, 9:28 PM
Win7
Control Panel\All Control Panel Items\Action Center\Reliability Monitor

From what I've read, I strongly suspect the PSU. Especially since you shed some load by pulling memory cards.
deadbandman wrote on 10/5/2013, 2:03 AM
I believe I have the offending card found out and so far the system is no longer crashing. Not only did it fully render my project, I even was able to watch the playback for the full 8 minutes and not one restart. I even tested different slots but none of that made any difference. However the RAM test finds nothing wrong with the card but if I put it back in and test all the ram is restarts at about 70% pass.
Gary James wrote on 10/5/2013, 7:29 AM
"Win7 - Control Panel\All Control Panel Items\Action Center\Reliability Monitor"

Steve I looked where you suggested, and there isn't a Reliability Monitor anywhere in my Control Panel. I checked under both drop downs, and it isn't there either. What version of Win7 do you have?

JohnnyRoy wrote on 10/5/2013, 9:03 AM
> "FYI there was no blue screen after restart, just restarting."

I know you've found the problem but I thought I would post this just in case you weren't aware of Microsoft's tactics.

We all know that Microsoft has always been plagued with what is now know as the Blue Screen Of Death (BSOD) problem. They claim that starting with Windows Vista customers would not "see" the BSOD anymore. Their "fix" was to hide it! So starting with Vista, you actually have to enable the BSOD otherwise the system will just reboot without notice. It's that nice? (NOT!)

Here's how to re-enable it:

(1) Right-click on Computer in the Windows Explorer and select Properties
(2) Click the Advanced System Settings link on the left
(3) On the Advanced tab, press the Settings... button under Startup and Recovery
(4) Under System Failure uncheck Automatically Restart

This will cause your computer to stop and show the BSOD on system failure so that you can actually diagnose the problem instead of mindlessly restarting. You may be able to put the offending card back and and get a better error message this way.

~jr
Steve Mann wrote on 10/5/2013, 11:41 AM
It must be a consumer feature - I am running Home Premium because I can only put 16Gb into this MB. (More RAM and dual processors is all Pro would give me).

The Reliability Monitor is a dumbed down version of the Event Viewer that shows the most significant events that affect performance.

Enabling Blue Screen like JohnyRoy suggested is also a good idea. I still suspect the PSU. Can you swap the suspect RAM with a known good one?
WillemT wrote on 10/5/2013, 12:01 PM
@Gary

On the Action screen in your capture above, click the Maintenance arrow to display the options. The first item has a list of options and the last one is "View reliability history". Selecting that one shows the Reliability Monitor.

That is a very handy one to review past hardware and software actions.

Hope that helps
Willem.
Gary James wrote on 10/5/2013, 3:33 PM
I had looked under the Maintenance Drop-down, but I was expecting Reliability Monitor to be a Major item in the list, not a small option link under a different major list selection.

When I ran it, it opened a Window and put up and hourglass for about 2 minutes. Then it drew a graph with no data in it. I don't know what to make of these results. Anyway Thanks Willem.
Steve Mann wrote on 10/5/2013, 10:22 PM
You click on any of the events on the graph to see what caused it.
Gary James wrote on 10/6/2013, 8:42 AM
Steve, the graph was blank. No line in the plot, and no events in the list.
Steve Mann wrote on 10/6/2013, 12:06 PM
That's strange - this is what it should look like. You click on the red "X" and you get a snapshot of the event log telling why Windows didn't like something at that time. You can do it the hard way and look at the event viewer itself.