POV-Ray : Newsgroups : povray.unofficial.patches : Bigtime MegaPov 0.7 CRASH! Server Time
10 Oct 2026 07:47:11 EDT (-0400)
  Bigtime MegaPov 0.7 CRASH! (Message 1 to 26 of 26)  
From: GrimDude
Subject: Bigtime MegaPov 0.7 CRASH!
Date: 16 May 2001 07:50:07
Message: <3b02696f$1@news.povray.org>
I moved to a new system AMD 800 Duron on an Epox 8kta3 MB with the latest
BIOS, 128 Megs PC 100 RAM. Partial renderings with scenes that used to
render fine now crash to a black screen. No error message is reported, no
warning, just "black screen." The scene I have been working with involves
rather large models, so I couldn't post a scene very easily. I will attempt
to find a similar situation, but you can probably see why I might shy away
from too much of it.

The scene that is crashing has an H_F, sky_sphere, cloud layer, water, and
aircraft (of course), with several very 'deep' textures and materials,
motion_blur, etc. I'm not sure as to what exactly I should be concentrating
on to replicate the problem.

If anyone has a suggestion as to what to try I am all ears.

Grim


Post a reply to this message

From: Thorsten Froehlich
Subject: Re: Bigtime MegaPov 0.7 CRASH!
Date: 16 May 2001 08:09:35
Message: <3b026dff$1@news.povray.org>
In article <3b02696f$1@news.povray.org> , "GrimDude" <gri### [at] netzerocom>
wrote:

> If anyone has a suggestion as to what to try I am all ears.

Re-install your system and the re-install POV-Ray.


    Thorsten


Post a reply to this message

From: Bob H 
Subject: Re: Bigtime MegaPov 0.7 CRASH!
Date: 16 May 2001 09:12:16
Message: <3b027cb0$1@news.povray.org>
"Thorsten Froehlich" <tho### [at] trfde> wrote in message
news:3b026dff$1@news.povray.org...
>
> Re-install your system and the re-install POV-Ray.

Drastic  :-)
Is that still the Windows platform?  If so, black screen no errors sounds
very fundamentally wrong, like a CPU error perhaps.  Could it be that the
Duron has trouble with the MSVC Win32 (Pentium II optimized) build of
POV-Ray?  Seems plausible anyway.
What's the video in that?  Onboard or card? I ask out of curiosity but maybe
it's related to handling the output to screen somehow instead, which again
would be very low-level since a error message should have been shown
otherwise.

Bob H.


Post a reply to this message

From: GrimDude
Subject: Re: Bigtime MegaPov 0.7 CRASH!
Date: 16 May 2001 10:17:38
Message: <3b028c02@news.povray.org>
I just realized, and came here, because I failed to post video information.

GeForce 2 MX AGP (card).

I am beginning to wonder if I will have to buy an Intel machine just to
render with. This machine rocks for gaming, and rendering too, but if it's
going to cause problems with Pov I'll need another machine. :(

Grim


Post a reply to this message

From: Gail Shaw
Subject: Re: Bigtime MegaPov 0.7 CRASH!
Date: 16 May 2001 10:28:00
Message: <3b028e70@news.povray.org>
GrimDude <gri### [at] netzerocom> wrote in message
news:3b028c02@news.povray.org...
> I am beginning to wonder if I will have to buy an Intel machine just to
> render with. This machine rocks for gaming, and rendering too, but if it's
> going to cause problems with Pov I'll need another machine. :(
>

How big is the scene? If it zips small enough to email (<5MB), send it to me
and
I'll try it on a pentium2 and an athlon, see if it crashes on either.

Gail
*************************************************************************
* gsh### [at] monotixcoza                *   Step into the abyss,           *
* http://www.rucus.ru.ac.za/~gail/   *   and let go.        Babylon 5   *
*************************************************************************
* The difficult we do immediately, the impossible takes a little longer *
*************************************************************************


Post a reply to this message

From: Warp
Subject: Re: Bigtime MegaPov 0.7 CRASH!
Date: 16 May 2001 10:36:48
Message: <3b02907f@news.povray.org>
GrimDude <gri### [at] netzerocom> wrote:
: I am beginning to wonder if I will have to buy an Intel machine just to
: render with. This machine rocks for gaming, and rendering too, but if it's
: going to cause problems with Pov I'll need another machine. :(

  I upgraded my old P-II 350MHz to an Athlon 1.2GHz and I haven't found
any problems whatsoever. I didn't even have to re-install anything.
  POV-Ray works like a charm.

-- 
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}//                     - Warp -


Post a reply to this message

From: Warp
Subject: Re: Bigtime MegaPov 0.7 CRASH!
Date: 16 May 2001 10:42:13
Message: <3b0291c4@news.povray.org>
Are you sure that you are not suffering from CPU temperature problems?
This can be sometimes the cause for crashes with CPU-intensive programs
(such as POV-Ray). The CPU gets warmer when it's very busy.
  Watch the CPU temperature with a monitoring program such as
http://web.bham.ac.uk/jst829/mbprobe/

-- 
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}//                     - Warp -


Post a reply to this message

From: Gail Shaw
Subject: Re: Bigtime MegaPov 0.7 CRASH!
Date: 16 May 2001 10:51:29
Message: <3b0293f1@news.povray.org>
Warp <war### [at] tagpovrayorg> wrote in message news:3b0291c4@news.povray.org...
>   Are you sure that you are not suffering from CPU temperature problems?
> This can be sometimes the cause for crashes with CPU-intensive programs
> (such as POV-Ray). The CPU gets warmer when it's very busy.
>   Watch the CPU temperature with a monitoring program such as
> http://web.bham.ac.uk/jst829/mbprobe/
>

Thanks, I was looking for something like that earlier today.

Gail
*************************************************************************
* gsh### [at] monotixcoza                *   Step into the abyss,           *
* http://www.rucus.ru.ac.za/~gail/   *   and let go.        Babylon 5   *
*************************************************************************
* The difficult we do immediately, the impossible takes a little longer *
*************************************************************************


Post a reply to this message

From: Thorsten Froehlich
Subject: Re: Bigtime MegaPov 0.7 CRASH!
Date: 16 May 2001 11:54:26
Message: <3b02a2b2@news.povray.org>
In article <3b027cb0$1@news.povray.org> , "Bob H." <omn### [at] msncom> 
wrote:

> Is that still the Windows platform?  If so, black screen no errors sounds
> very fundamentally wrong, like a CPU error perhaps.  Could it be that the
> Duron has trouble with the MSVC Win32 (Pentium II optimized) build of
> POV-Ray?  Seems plausible anyway.
> What's the video in that?  Onboard or card? I ask out of curiosity but maybe
> it's related to handling the output to screen somehow instead, which again
> would be very low-level since a error message should have been shown
> otherwise.

Sorry, neither of these is a possible reason if there is _no_ defect
elsewhere.  Screens don't just randomly black out if you call the operating
system, neither has any optimization for any processor something do with it.

Assuming it is not a hardware problem (if the system runs well under load
for a long time if POV-Ray is not running), the problem is most likely some
damaged software install.  The solution to these if running Windows is to
re-install, as well as update all drivers, bios, and add all operating
system bug fixes that are not buggy themselves per se.  however, I do not
think the problem can be found without physical access, i.e. it cannot be
found in this newsgroup except someone had the same problem before and found
a solution.

Computer hardware and software are no _magic_ boxes - if there is a problem
there is a specific cause and a (not necessarily obvious) solution.


      Thorsten


Post a reply to this message

From: Thorsten Froehlich
Subject: Re: Bigtime MegaPov 0.7 CRASH!
Date: 16 May 2001 11:55:47
Message: <3b02a303$1@news.povray.org>
In article <3b027cb0$1@news.povray.org> , "Bob H." <omn### [at] msncom> 
wrote:

>> Re-install your system and the re-install POV-Ray.
>
> Drastic  :-)

Windows ;-)


Post a reply to this message

From: Bob H 
Subject: Re: Bigtime MegaPov 0.7 CRASH!
Date: 16 May 2001 14:49:37
Message: <3b02cbc1@news.povray.org>
I'd be real interested in hearing of the result of that myself, in fact many
other people would probably be listening in too.

Bob H.

"Gail Shaw" <gsh### [at] monotixcoza> wrote in message
news:3b028e70@news.povray.org...
>
> I'll try it on a pentium2 and an athlon, see if it crashes on either.


Post a reply to this message

From: GrimDude
Subject: Re: Bigtime MegaPov 0.7 CRASH!
Date: 16 May 2001 14:56:38
Message: <3b02cd66@news.povray.org>
Well, the system hits a peak at about 107 F., so I don't think that's it. I
was prepared to put a new 1.4Ghz proc. in when they are here, so I have
adequate cooling (I think).

I think Thorsten probably has the best answer, though I do not look forward
to a re-format reinstall. Gail, the entire scene comes in over 10Megs, so
I'll see if I can narrow it down. I will try to reinstall Windows on top of
what I have and see how that goes.

Additionally, I have a small file that is causing the official Pov 3.1g to
crash. It renders inside of MegaPov, which has me perplexed. I have been
away from rendering for a few months, so this has me scratching my head and
wondering if I have done something stupid. I will post the code (for the
latest scene) in binaries.scene-files and see if anyone else has this
problem.

If, it renders fine, we will know that it is my system, right? :)

TIA,
Grim


Post a reply to this message

From: GrimDude
Subject: Re: Bigtime MegaPov 0.7 CRASH!
Date: 16 May 2001 15:00:02
Message: <3b02ce32$1@news.povray.org>
I'll get right on sorting out which files are needed, and see if I can limit
the models, etc. It may take a little while, but I'll get it off to you.

(SIGH) O.T., but I am going through a nasty divorce right now, and my
spirits are down. The ex is pestering me with harassing phone calls and
setting my nerves on edge. I'm not happy.

At least I have you all! :)

Grim


Post a reply to this message

From: GrimDude
Subject: Re: Bigtime MegaPov 0.7 CRASH!
Date: 16 May 2001 15:09:06
Message: <3b02d052$1@news.povray.org>
Oops! :)

MBProbe gives a different picture then the BIOS reported.

The MB usually sits at about 101F, the CPU at about 89F, and the system (VIA
chipset) at about 75F. It doesn't seem critical to me, but what do I know?
:)

Grim


Post a reply to this message

From: Bob H 
Subject: Re: Bigtime MegaPov 0.7 CRASH!
Date: 16 May 2001 15:10:50
Message: <3b02d0ba$1@news.povray.org>
"Warp" <war### [at] tagpovrayorg> wrote in message
news:3b0291c4@news.povray.org...
>   Are you sure that you are not suffering from CPU temperature problems?
> This can be sometimes the cause for crashes with CPU-intensive programs
> (such as POV-Ray). The CPU gets warmer when it's very busy.
>   Watch the CPU temperature with a monitoring program such as
> http://web.bham.ac.uk/jst829/mbprobe/

Sure wish one of those utilities would monitor the motherboard and sensors I
have.  Ah ha! That one lists the i815EM!  Finally...  Thanks so much for
posting that URL!

Seems I read someplace that AMD's are run hotter than equivalent clockrate
Intel's, the Athlon anyway.  Same for Duron?  I couldn't say, not sure
anyhow.  My DELL notebook is a PIII at 800Mhz and I suspect it isn't wholly
stable, but a well-fanned tower case must be very different.

Bob H.


Post a reply to this message

From: Bob H 
Subject: Re: Bigtime MegaPov 0.7 CRASH!
Date: 16 May 2001 15:22:41
Message: <3b02d381@news.povray.org>
"GrimDude" <gri### [at] netzerocom> wrote in message
news:3b02ce32$1@news.povray.org...
>
> (SIGH) O.T., but I am going through a nasty divorce right now, and my
> spirits are down. The ex is pestering me with harassing phone calls and
> setting my nerves on edge. I'm not happy.

At least you have someone...  :'{
Heh,  sorry, I thought I might try cheering you up.

> At least I have you all! :)

And that's a good thing, right?  Guess you can't get a better 50-50
relationship than that with fellow and fellowette POVers.  Where's a chapel
scene at?  Maybe Gail isn't married.

Bob H.


Post a reply to this message

From: Bob H 
Subject: Re: Bigtime MegaPov 0.7 CRASH!
Date: 16 May 2001 15:27:42
Message: <3b02d4ae$1@news.povray.org>
"GrimDude" <gri### [at] netzerocom> wrote in message
news:3b02d052$1@news.povray.org...
>
> MBProbe gives a different picture then the BIOS reported.
>
> The MB usually sits at about 101F, the CPU at about 89F, and the system
(VIA
> chipset) at about 75F. It doesn't seem critical to me, but what do I know?

More than I do, it tells me water should freeze on it, 32 degrees F or 0 C.
I knew I was speaking to soon thinking it would finally be the monitoring
utility that could work on this thing.  I'm beginning to think DELL took all
the sensors out.

Bob H.


Post a reply to this message

From: Ken
Subject: Re: Bigtime MegaPov 0.7 CRASH!
Date: 16 May 2001 22:43:27
Message: <3B033B6F.5BC2DE2D@pacbell.net>
GrimDude wrote:

> Additionally, I have a small file that is causing the official Pov 3.1g to
> crash.

<snip>

> If, it renders fine, we will know that it is my system, right? :)

It crashes on my system too. If you comment out "ambient_light 0" below
the scene will render ok. Sounds like a bug but I don't know where or
why.

global_settings { max_trace_level 11 assumed_gamma 1 ambient_light 0 }

-- 
Ken Tyler - 1400+ POV-Ray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/


Post a reply to this message

From: Bob H 
Subject: Re: Bigtime MegaPov 0.7 CRASH!
Date: 16 May 2001 23:35:15
Message: <3b0346f3@news.povray.org>
"Ken" <tyl### [at] pacbellnet> wrote in message
news:3B033B6F.5BC2DE2D@pacbell.net...
>
> > Additionally, I have a small file that is causing the official Pov 3.1g
to
> > crash.
>
> > If, it renders fine, we will know that it is my system, right? :)
>
> It crashes on my system too. If you comment out "ambient_light 0" below
> the scene will render ok. Sounds like a bug but I don't know where or
> why.
>
> global_settings { max_trace_level 11 assumed_gamma 1 ambient_light 0 }

Strange, renders without a crash here.  You both have the Athlon chips eh?
:-|

Bob H.


Post a reply to this message

From: Ken
Subject: Re: Bigtime MegaPov 0.7 CRASH!
Date: 17 May 2001 00:09:55
Message: <3B034FB2.E8BABAA8@pacbell.net>
"Bob H." wrote:

> Strange, renders without a crash here.  You both have the Athlon chips eh?

If running 3.1g try rendering it a few times in succession and see if
that causes it to crash. I got it to render a couple of times but not
reliably.

Yes I have an Athlon.

-- 
Ken Tyler


Post a reply to this message

From: Francois Labreque
Subject: Re: Bigtime MegaPov 0.7 CRASH!
Date: 17 May 2001 00:26:35
Message: <3B03518C.172B7F29@videotron.ca>
Ken wrote:
> 
> "Bob H." wrote:
> 
> > Strange, renders without a crash here.  You both have the Athlon chips eh?
> 
> If running 3.1g try rendering it a few times in succession and see if
> that causes it to crash. I got it to render a couple of times but not
> reliably.
> 
> Yes I have an Athlon.

Runs perfectly fine on this Athlon 650.  (Ran it 20 times in a row
without problems).

-- 
Francois Labreque | In the future, performance will be measured
    flabreque     | by the size of your pipe.
        @         |             - Dogbert, on networking
   videotron.ca   |


Post a reply to this message

From: GrimDude
Subject: Re: Bigtime MegaPov 0.7 CRASH!
Date: 17 May 2001 00:48:44
Message: <3b03582c$1@news.povray.org>
Strange, it crashes on my system regardless of whether ambient_light is
defined, or not.

I finally got the original scene (and the reason for this thread) to work.
The VIA 4in1 driver pack fixed that up, and this 3.1g problem isn't really a
big deal, just a curious irritation.

Thanks for all the help, all. Thanks for the offer, Gail. :)

Grim


Post a reply to this message

From: Ken
Subject: Re: Bigtime MegaPov 0.7 CRASH!
Date: 17 May 2001 01:23:01
Message: <3B0360D5.A1777A89@pacbell.net>
GrimDude wrote:
> 
> Strange, it crashes on my system regardless of whether ambient_light is
> defined, or not.
> 
> I finally got the original scene (and the reason for this thread) to work.
> The VIA 4in1 driver pack fixed that up, and this 3.1g problem isn't really a
> big deal, just a curious irritation.
> 
> Thanks for all the help, all. Thanks for the offer, Gail. :)

I'm sorry but this last reply is unacceptable. You can't come in here
crying about a major problem and then go off and fix it yourself.
What are we supposed to do now, Grim ?

Sheeeeeesh !

-- 
Ken Tyler - 1400+ POV-Ray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/


Post a reply to this message

From: Nekar Xenos
Subject: Re: Bigtime MegaPov 0.7 CRASH!
Date: 17 May 2001 02:34:32
Message: <3b0370f8@news.povray.org>
My Duron650 had lots of blacks screens this summer. I see the cpu is basically
closed in by the power suppy unit and the card slots. Also Via motherboard. I
haven't heard anything good about Via...
I now got AMN Refridgerator from a PCFormat cover disk, but it's almost winter
now here...
I'm also gonna check out this MBprobe...

Nekar
--
#local N=<-20,40,100>;#local K=<20,-40,100>;#local R=seed(0);blob{#while((K-N).
x>0)#local X=N;#local N=N+<rand(R),rand(R),1>/3;#local N=(vlength(N-K)<vlength(
X-K)?N:2*X-N);sphere{<N.y,-N.x,N.z>,1,1 scale .02}sphere{N,1,1 scale.02}sphere{
<-N.x-40,N.y,N.z>1,1 scale.01}sphere{<N.x+40,-N.y,N.z>1,1 scale.01 }#end
pigment{rgbt 1}interior{media{emission <2,4,5>*5}}hollow}// Nekar Xenos
"Bob H." <omn### [at] msncom> wrote in message
news:3b02d0ba$1@news.povray.org...
> "Warp" <war### [at] tagpovrayorg> wrote in message
> news:3b0291c4@news.povray.org...
> >   Are you sure that you are not suffering from CPU temperature problems?
> > This can be sometimes the cause for crashes with CPU-intensive programs
> > (such as POV-Ray). The CPU gets warmer when it's very busy.
> >   Watch the CPU temperature with a monitoring program such as
> > http://web.bham.ac.uk/jst829/mbprobe/
>
> Sure wish one of those utilities would monitor the motherboard and sensors I
> have.  Ah ha! That one lists the i815EM!  Finally...  Thanks so much for
> posting that URL!
>
> Seems I read someplace that AMD's are run hotter than equivalent clockrate
> Intel's, the Athlon anyway.  Same for Duron?  I couldn't say, not sure
> anyhow.  My DELL notebook is a PIII at 800Mhz and I suspect it isn't wholly
> stable, but a well-fanned tower case must be very different.
>
> Bob H.
>
>
>


Post a reply to this message

From: Gail Shaw
Subject: Re: Bigtime MegaPov 0.7 CRASH!
Date: 17 May 2001 03:41:28
Message: <3b0380a8@news.povray.org>
Bob H. <omn### [at] msncom> wrote in message
news:3b02d381@news.povray.org...
> And that's a good thing, right?  Guess you can't get a better 50-50
> relationship than that with fellow and fellowette POVers.  Where's a
chapel
> scene at?

http://www.rucus.ru.ac.za/~gail/Raytracing/Church.htm

> Maybe Gail isn't married.

I'm not, and no plans in that direction either.

Heading off-topic...

Gail
*************************************************************************
* gsh### [at] monotixcoza                *   Step into the abyss,           *
* http://www.rucus.ru.ac.za/~gail/   *   and let go.        Babylon 5   *
*************************************************************************
* The difficult we do immediately, the impossible takes a little longer *
*************************************************************************


Post a reply to this message

From: GrimDude
Subject: Re: Bigtime MegaPov 0.7 CRASH!
Date: 25 May 2001 20:45:23
Message: <3b0efca3@news.povray.org>
BTW, Ken. Your reply helped to ease the pain I was going through. Thanks,
man.

Grim
"Ken" <tyl### [at] pacbellnet> wrote in message
news:3B0360D5.A1777A89@pacbell.net...
>
>
> GrimDude wrote:
> >
> > Strange, it crashes on my system regardless of whether ambient_light is
> > defined, or not.
> >
> > I finally got the original scene (and the reason for this thread) to
work.
> > The VIA 4in1 driver pack fixed that up, and this 3.1g problem isn't
really a
> > big deal, just a curious irritation.
> >
> > Thanks for all the help, all. Thanks for the offer, Gail. :)
>
> I'm sorry but this last reply is unacceptable. You can't come in here
> crying about a major problem and then go off and fix it yourself.
> What are we supposed to do now, Grim ?
>
> Sheeeeeesh !
>
> --
> Ken Tyler - 1400+ POV-Ray, Graphics, 3D Rendering, and Raytracing Links:
> http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.