Tech. Guru's...odd problem.

Bruthish wrote on 8/31/2003, 7:55 AM
Not sure if this is related directly to VV3 or not. I have a homebuilt PC..PIII 1000mhz. 512 Ram. Runs great doesn't really crash at all.
When I try to render down(in .AVI or MPEG2) a file with "glow" plug-in, the computer shuts OFF and restarts. If I turn the glow off, it will render. It seems this puts a extreme load on the computer for some reason. Is there a bug in the glow plug-in? Now, it has shut off twice before outside of VV3. I have removed and air-cleaned the memory. I have defraged and checked my resources...any ideas....

Comments

kameronj wrote on 8/31/2003, 9:49 AM
1000 mhz.

Translated - isn't that 1 ghz?

I didn't think a PIII board could handle 1 GHZ. Do you have it overclocked or somethin?

Anyway.....the times I have seen a PC shut itself off (outside of a virus) has been because it was overheating. Next time it does that - check your BIOS and see what the temperature is reading.

Right before my older PC blew up (and I literally mean blew up!!) I knew I had a problem with the fan - as in the fan wasn't working. It got waaaaayyyy hot and would shut itself off. So Iopened up the case and had a desk fan cooling the unit.

That is until the power supply blew - causing sparks to fly out from the motherboard and fried all the damn capacitors. Luckily....it only wiped one of my HDs....and it was the one that only had some minor backup data on it. My most imortant drive survived...but tht is a different story.

Hope this helps.
craftech wrote on 8/31/2003, 10:11 AM
Are you using NAV 2002? If so Symmantec has a LiveUpdate to fix a stack overflow issue. It will be especially noticeable if you are running W98 or ME. You may have to update several times in order to bring it up to date. Also run a drive error check since you have had unexpected reboots.

John
TorS wrote on 8/31/2003, 11:03 AM
Overclocking has been known to create problems with Vegas. But PIIIs come in flavours up to 1100 these days I think.
Tor
kameronj wrote on 8/31/2003, 11:25 AM
"Overclocking has been known to create problems with Vegas. But PIIIs come in flavours up to 1100 these days I think."

Interesting. Ya learn something new everyday.

I guess it all depends on the motherboard. My old PC (prior to it's fiery demise) could only go up to about a PIII 800 MhZ.
craftech wrote on 8/31/2003, 1:16 PM
Mine is a PIII 1GHZ. It's on a slot 1 BX board and is not overclocked.

John
filmy wrote on 8/31/2003, 3:26 PM
Check the CPU fan and make sure it still works. I can't think of anything else of the top of my head that would make the system do a full shut down durning a render and the only reason I think of the CPU fan is an overload on the CPU causing overheating.

Now if you are trying to preview on the monitor it might overload the graphics card and cause that to overheat but that would more than likely cause a lock up rather than a shut down. Normally though I haven't seen a graphics card cause a lock up during render.
Flack wrote on 8/31/2003, 5:07 PM
filmy

Is this the new tecky term for a shutdown...


"quote"that would make the system do a full shit down durning a render.. LOL


Flack

rebel44 wrote on 8/31/2003, 5:09 PM
I had PIII for allmost a year 1GIG(1.6GIG) CPU,but run only 1GIG speed.Nothing new.Check your BIOS setting and increase the AGP video to 128.IF you updated your bios then is supporting 8X AGP.Make shure that is disable. IN worst case you have bad memory chip-that will couse computer to shut down.Windows will never tell you that. The only program what really test memory is MemTest86 and it is free.It is non-os oriented.That means that does matter what os are you running. If you are using win98 then that could be a problem too.The most stable OS I found is win2000.I did updated my computer to 2.5GIG, but with that 1GIG what I had-I had no problems at all.
Bruthish wrote on 8/31/2003, 5:33 PM
Hey guys thanks for the replys. I have 1GHZ ABIT BX133-Raid board. In did it in the past and thought I had found the problem being low disk space...but its back and I have plenty. I have the BIOS set AGP Aperture set to 256. When I had it set lower it seemed to be worse. I have also tried to put a desk fan towards the CPU to cool it more and did not help.
I am running WIN98SE but sorry I don't know what NAV2002 is. My initial thought was bad memory....I will pull one(I have 2 sticks) and see if it helps.
Thanks!!
kameronj wrote on 8/31/2003, 5:46 PM
I didn't ask this before - but I guess I should have....

How big is the file you are rendering with the glow?

Or, stated a different way - does this only happen on the one file, or does it happen when ever you try and use the glow? Is the glow very long or is it a short glow?

Have you tried to render, say, a 10 second clip with and without the glow to see if you still get this problem?

If it is a very short clip and you still get this problem - then I highly doubt it's the RAM or overheating....it may be a software issue where a file may be corrupt (or something).

craftech wrote on 8/31/2003, 5:50 PM
NAV2002 is Norton Antivirus 2002.

Also, check your chipset settings in the Bios and set them to conservative settings if you suspect the ram. In other words CAS latency timings should be 3-3-3 not 2-2-2.
Try booting into safe mode and look in the Device Manager for any ghost devices which should be deleted or any duplicate device entries.

John
Bruthish wrote on 8/31/2003, 11:20 PM
UPDATE: Thanks again guys. I pulled one of the 256meg sticks and the computer wouldn't even make it into windows. I thought problem was solved. Put the other one in there and it booted up fine. Went back into VV3 and started to render the same video. I had to goto work but my wife says that the computer has rebooted.
I do not run any anti-virus software. I have tried pre-rendering this parts thinking it will take load off with no success. The whole video is less than 3 minutes. And the parts with the glow is only maybe 20 seconds if that.
I do wedding videos in parts....all the other 20+ parts have rendered fine....justthe one with the glow is giving me the problem. I will try the memory settings as you have discribed and see if that helps. Do youthink it could be not enough memory?
rmack350 wrote on 9/1/2003, 2:15 AM
As far as I know that chipset won't support more than 512 MB total-even though you might lay your hands on 2 512MB DIMMS.

I'm sure that no matter what you do, a render will use 100% CPU. I don't see how glow could make things any hotter except that it makes the render longer.

Does the system reboot immediately or after working on the glow segment for a few minutes. I see on my system (PIII/1 Ghz, 512MB WinXP) that the swap file usage is slowly rising as I render glow on a 5 second still. Have you set your swap file to a static size? Could it be filling up?

A total reboot seems like it could be hardware failure. Do you render to/from 1394 drive? Or maybe the graphics card is a culprit (although I doubt it). You could try unchecking "Show Progress in Video Preview While Rendering".

Reinstalling Vegas won't hurt you.

Rob Mack
craftech wrote on 9/1/2003, 6:47 AM
1. In your first statement you said: "Now, it has shut off twice before outside of VV3". Is that accurate or is it only when you try to render the Vegas file with the "glow" plugin?

2. As far as cooling problems go, try running the computer with the cover off for now. That will reduce the temperature considerably although my guess is that you have done that because you said that you had a desk fan blowing on the CPU so I assume that you had to have the cover off anyway.

3. What about those "ghost entries" or duplicate entries in Safe Mode that I suggested you check for?

4. Exactly which "glow" plugin are you using and have you ever used it successfully before? Did you just install it?

5. Which versions of WMP and Direct X are you using and did you JUST install one of them just before the problem began?


6. A distant last:

Are both sticks of ram the same? Make sure your ram supports 133 MHZ-----AND Make sure you try 3-3-3) settings FIRST (Cas 3, Ras 3, and Cas to Ras 3). Then try 2-3- 3, then 2-3-2, then 2-2-2. (these are successively faster timings). Make sure the PCI raio is 1/4. (The PCI bus runs at 1/4 the clock speed of the processor) If it is at 1/3, the board has almost no chance of running at a PCI bus speed of (133 MHz/3=) 44.33 MHz. If using an AGP video card, make sure its timing in the BIOS is (2/3) NOT (1/1). At 1 to 1 (1/1) the video card is running at the same bus speed as the processor, (133 MHz). At (2/3), it is still running (133 MHz X (2/3) =) 89 MHz. Note that some AGP video cards can't run at 89 MHz, either. Try another AGP video card or a PCI card (make sure (PCI/CPU) ratio is 1/4). Try disabling System Bios Cacheable, Video Bios Cacheable, and Video Ram Cacheable in the BIOS. Some processors need 0.05 Volts more to run stable in the ABIT BX boards. Try 1.70 Volts in the BIOS if yours is a 1.65 Volt CPU, or if a 1.70 volt CPU, try 1.75 Volt. Check the big capacitors near the CPU socket. If they show signs of leakage let me know.

John
Bruthish wrote on 9/1/2003, 3:34 PM
Ha! You may be on to something...the capacitors above the CPU....looks like nine of them. On 5 of them...them tops have stuff coming out of them...on one other its starting to. It for sure does not look good. Looks like I may be needing a new board soon(faster!) Until I hear back from you, I will try the other stuff too.
Thanks!

P.S. I did check for ghost entries and found a bunch of old stuff I don't use anymore and I got rid of those. I have a few dups under my drives and under system stuff(like DM Controller or the like). Just afraid to delete them afraid of not being able to reboot.
BillyBoy wrote on 9/1/2003, 4:17 PM
Good golly Miss Molly! If you have 5 capacitors oozing "something" how much more of a clue you need your MB has about had it?

Reminds me of a scene in the classic "earthquake" movie where they have several minutes of buildings falling apart and just before the sequence ends this guy is told hey go shut the gas off in this house. Well, he nods, and we last see him running into the building with a cigarette in his mouth.

BOOM!
Bruthish wrote on 9/1/2003, 5:08 PM
HAHA!! Tell me about it...I never noticed it until Craftech told me to look. The board has lasted over two years anyhow....I guess I am ready for some more speed! Whooohoo!! (now I just have to convince the wife)
craftech wrote on 9/1/2003, 6:35 PM
The problem is not just with your MB:

http://www.niccomp.com/taiwanlowesr.htm


You can replace the capacitors if you are careful. They are low ESR aluminum 6.3 volt 1500uF electrolytic capacitors but I would replace them with 10volt caps which can be obtained inexpensively from several sources. I looked in a year old Digikey catalog (www.digikey.com) and I see them listed as part # P10228-ND and here's the Panasonic part # EEU-FC1A152: Description: CAP 1500UF 10V ELECT FC RADIAL. 105*C max temp.
Mouser (www.mouser.com) has them listed as part number: 647-UPW1A152MPH6. Forget Radio Shack.

You need a desoldering tool or some wick (the former is much better). You will also need a soldering iron with a fine tip and a variable voltage to control the heat. Remove them but work fast and slip a heat sink (microclip will do) onto the wires from the cap. Pull out one side at a time with fine needle nose or tweezers or a divider point. The tiny hole must be cleaned out. The desoldering tool should work or heat it and blow it out the other side. That's the hardest part. Careful with the tiny holes as printed circuit boards often have circuit traces INSIDE the layers as well as on the top and bottom.

Insert your new caps in the holes, solder in place quickly, then snip the excess wire off. Use an Optivisor or other magnifier to check for goofs. It doesn't have to look pretty, but you don't want any short circuits. That should put an otherwise fine board back in action for an indefinite period of time.

John


BillyBoy wrote on 9/1/2003, 8:45 PM
Hi John... I put my soldering iron back in its holster, pretty much for good, a long tmie ago. ;-)

The traces are simply too close together for me to see well enough anymore. Not to discourage anyone wanting to try, just be aware of what you're getting into. Tiny is an understatement. Besiides, before I would take a stab at it, I'd want to first know WHY did all those capacitors burn up?

Just caused a flash back... Way back when I got some of chemicals they sell at Radio Shack and you made your own custom printed circuity boards. Similar to developing your own film, run down to the basement hope your design took as you washed of the chemical. I think that's how it worked... its been awhile like ah... 25 years or so. Geez...


craftech wrote on 9/1/2003, 10:30 PM
Bill,

If you click on that URL I placed in my previous post the Filter Cap problem has affected about 10 Motherboard manufacturers in Taiwan over the past few years on many boards manufactured for PIII, particularly i440BX boards up to 2001. Many of the motherboard manufacturers purchased from two companies in Taiwan which used bad electrolytes. Unfortunately, many people still don't know about it and have thrown away perfectly good mainboards as a result.

I did the filter cap swap on a Soyo 6BA+IV two years ago and it is still working like new. It's really not that hard to do. I used an Optivisor which I kept from when I was doing jewelry and gemsetting for a sideline instead of videography. You can see a dust mite with one of those.

The BX chipset is arguably the best one Intel ever produced. Even considering its AGP/PCI timing limitations it can hold it's own with a faster PIII such as the one Bruthish has.

Go for it Bruthish.

John
Bruthish wrote on 9/2/2003, 2:12 PM
Craftech..do you think that is the problem? I mean, I rendered down 20 other projects that were longer with no problem...then this one has Gow and film effects and it shuts off. Also, it did shut off outside of VV. I turned on the computer and immediatly went to AOL....once i said "welcome" it shut off.
As far as the capaciters, Ithink I will pass just because its an excuse to get a new board. Thanks for all you help!
craftech wrote on 9/2/2003, 3:29 PM
Spontaneous reboots are a common symptom since the resulting voltage fluctuations to the CPU can do that among other things. I am not familiar with the "glow" plugin as I said, but the failing caps are probably a contributing factor to any issues you may have had with the computer. The other possibility is a poor quality power supply. That's easy to replace.

Where are you going to find a new PIII board? You will also need a new processor and new ram. Even if you choose a new board and processor which uses PC133 the older ram may not read full capacity.

If your board is less than three years old it may be covered under warranty:
http://www.abit-usa.com/services/rma/

Ther is a guy who replaces the caps on a motherboard who has been around for awhile and is very reputable across the internet. He charges $50 and has a 1-2 day turnaround. :
http://www.motherboardrepair.com/

John
Bruthish wrote on 9/2/2003, 3:32 PM
Thanks for the links....I was going to go ahead and get a P4 2.4 or higher with new RAM. The way it is now I upgrade every two years or so anyway...so its about time.
craftech wrote on 9/3/2003, 8:02 AM
If you plan on upgrading anyway, you may want to try a new bios for the heck of it. The BX133 was an out of spec BX board which was finnicky about processors and ram especially in light of the voltage fluctuations. Tualitin core Intel processors never worked correctly and 133FSB processors weren't great either. Here is a quote from someone who has developed hybrid bios for the board:

"...first, you are using a very old and out of date bios and driver set for the
Highpoint. Personal opinion, the 2.0.1203 bios and drivers are the best but
others also like the 2.32 to 2.34 match sets. I carry all of the above
using Abit mainboard bios with newer Highpoint inserts which were provided
either by Richard Hopkins (in an optimized version of the Abit mainboard
bios) or myself. see my server at the address below and the modified bios
sets are kept under the /beta path to keep them separate from the regular
released Abit mainboard bios sets.

I don't know of any command line interface to Highpoint drivers or bios.
there is a GUI that runs at the OS level to administer the Highpoint raid
but other than checking on your drive status, there is little need to have
that GUI installed. personal opinion, you will see much better performance,
even in a non-raid configuration, if you update the Highpoint bios and
drivers. updating the Highpoint bios requires that you flash the mainboard
bios with a version of the mainboard bios that has the newer Highpoint
insert contained within."
--

Thomas Geery
Network+ certified

ftp://geerynet.d2g.com <<< STATIC Address!
ftp://68.98.180.8 Abit Mirror <--- NEW 12/27/02!!
This IP is dynamic so it *could* change!
...over 110,000 FTP users served!

Why not try it?

John