Am 10.09.2016 um 01:05 schrieb jmichae3:
> another problem. after 1 successful run of pvengine.exe, can no longer run
> pvengine.exe, even with a reboot.
> "[Microsoft Windows]
> POV-Ray for Windows v3.7 has stopped working
> A problem caused the program to stop woring correctly.
> Please close the program.
> [->Close the program]"
> and this is the same bug I see when I run good programs compiled with gcc lately
> (iostream/fstream bugs?)

It's an obvious plot between the people behind the GNU Compiler
Collection (gcc), the folks behind Microsoft Visual Studio 2010 (used to
build POV-Ray 3.7.0), and of course the people behind POV-Ray, who all
back in 2010 conspired to make your life miserable in 2016.


As Thorsten already mentioned, you may want to consider the possibility
that your computer suffers from a CPU defect. Such defects may present
with quite obscure symptoms, for instance they may be triggered by a
certain sequence of instructions that normally happens to be generated
only by particular compilers or maybe even particular compiler versions.

Such defects may be intrinsic to the CPU type, which is actually pretty
common with modern CPUs. In that case, a BIOS update may solve the
problem by providing patched microcode for the CPU.

Other defects may be the result of wear. CPUs do age over time, and
frequently operating a CPU at its limits will drastically speed up this
aging process, to the point that it may show sporadic malfunctions under
certain conditions -- sometimes rather vague, sometimes very specific.

As an example, we once(*) had a report on these newsgroups of POV-Ray
producing strange stray white pixels in the output image; after some
research, it turned out that this guy had apparently been operating his
CPU (also some AMD, btw) without adequate cooling, and while the CPU
appeared to still be fine to do other things, it did fail sporadically
but frequently while executing POV-Ray, littering the output with ramdom
white pixels. Replacing the CPU solved the issue. (*Until the same
person burned out the replacement CPU as well.)

Post a reply to this message