10-02-2015
08:38 AM
- last edited on
03-06-2024
01:26 AM
by
ROGBot
10-15-2015 07:08 AM
10-29-2015 04:09 PM
11-02-2015 03:43 PM
11-09-2015 07:06 AM
Handbrake: x264 [warning]: --psnr used with psy on: results will be invalid!
x264 [warning]: --tune psnr should be used if attempting to benchmark psnr!
error opening C:/.../RealBench_v2.41/RealBench/Video/DVD/BDMV/BACKUP/index.bdmv
nav_get_title_list(C:/.../RealBench_v2.41/RealBench/Video/DVD) failed
libdvdread: Encrypted DVD support unavailable.
libdvdread: Device (null) inaccessible, CSS authentication not available.
NAME OPEN FAILED
libdvdnav: Unable to find home directorylibdvdnav: DVD disk reports itself with Region mask 0x00000000.
Regions: 1 2 3 4 5 6 7 8
libdvdread: Encrypted DVD support unavailable.
libdvdread: Device (null) inaccessible, CSS authentication not available.
libdvdnav: Language 'en' not found, using '��' instead
libdvdnav: Menu Languages available: ��
11-10-2015 07:20 AM
My bet would be on your power supply. RB's stress test is very different from the rest. It overloads ALL
subsystems, CPU/Cache/GPU (all of them)/RAM, Drive subsystems(I/O)/Bus. This means that while running the
stress test the power consumption of your system is through the roof and EVERY component is very stressed.
Since this happens on stock it's for sure a hardware failure. As I said my bet is on the PSU not supplying enough
juice or not supplying clean juice.
The error in itself, means that a certain file that is being written on every pass does not contain the
data it should. Meaning there is data corruption on your system FOR SURE, while the ST is running. If it's not
the PSU that's causing this it can be any number of things with the CPU and board being the main suspects.
It is quite possible that the issue manifests only on when the PCIe bus is stressed so much.. or whatever. It's
really hard to diagnose without testing replacement parts that you know they work properly. Make no mistake
though, there is an issue. The file gets corrupted for sure.
PS Also Windows memory diagnostic is largely useless. Use only Memtest86+ for RAM.
11-10-2015 07:50 AM
PetrolHead wrote:
My PSU is a 650W unit, so it's nowehere near it's limits with my hardware. Basically a good quality 400W PSU
should be enough to run all components at full load, so I should have more than enough headroom to run
anything I can think of. Also, Tom's Hardware lists the CM VS Series as a "Tier 2", which means that unless it's
broken there shouldn't be any issues with the cleanliness of juice either. I'm not ruling the PSU out totally, but
it's probably one of the better components in my system. Maybe it's just that the VRM's on the motherboard are
not up to the task when running hot? After all, this board has only a 4+1 power phase design. Running the
stress test again once I get a top-down cooler for the CPU might provide some answers...
I'm not doubting there's a mismatch. I'm only suspecting that it might be a software/firmware issue. There's
no way this software has been tested on all possible hardware and software combinations to ensure there are
no compatibility issues with the code.
In any case, I'll try to see whether I can use a combination of other stress tests to simulate your description
of what RB ST does.
MemTest86+ is not UEFI compatible and is basically obsolete software, as it's not really updated at the moment.
I've run a couple of passes of MemTest86 and it hasn't encountered any errors so far, but I've yet to do four
passes (or more), so there's still a chance it might.
11-10-2015 09:02 AM
Nodens wrote:
No a 400W would not be able to handle your components at full load.
But even if there was not it's not a good idea to run any PSU long term above 60-70% of its output.
In any case, it doesn't matter what TM lists or whatever reviews. If they PSU is faulty then it's faulty.
Have in mind that Blender is a software used by millions allover the world. But in any case there is no
possibility of a software issue whatsoever. It's not technically possible.
You will not be able to simulate the load of RB's ST no matter what combinations of other stress test
you try.
EDIT: You can try the AIDA64 stress test. It's the only one that comes close although still synthetic.
11-10-2015 11:11 AM
PetrolHead wrote:
In theory it should be, at least according to PSU manufacturers. The estimated power consumption for my
hardware is somewhere around 350 W if I remember correctly and the suggestions I got were max 450 W.
Even assuming PSU makers were _very_ optimistic, 650 W should be more than enough - even accounting
for the variations between different units (which should not be drastic in quality PSUs).
Yet it shouldn't be run much below 50% either, since that's where PSUs are generally most efficient. This is why its
usually better to spend on a quality PSU with a 600-750 W output than go for a 1000+ W unit - unless of course the
system has something like an FX-9xxxx and two or more GPUs.
Regarding GPUs, you also mentioned that it's a possible reason for the mismatch. As graphical bugs are just about the only bugs I've encountered, to me it seems the most likely piece of my hardware that could cause the error. It's just hard to know whether the bugs I've seen are due to software (either game or driver related) or actual hardware issues. I got the GPU used, so it's not like I installed it fresh from the box.
Sure, but then again there's still little reason to assume my PSU is faulty.
I find your faith in faultless code amusing. 😉 The larger and more complicated a software is, the more likely it
will contain bugs. A list of Blender's current (known) bugs can be found at:
https://developer.blender.org/maniphest/project/2/type/Bug/
A very brave statement. It's not like RB's ST is a magical combination of operations that pushes the system beyond
what is possible to reach with anything else. Then again, if it was, it wouldn't really matter if as much if a system fails
a RB ST, since it could still be stable and issue-free in _everything_ else. While it is correct that it'll be hard to load
the system similarly to RB's ST, I decided to try another way of pushing the system to its limits. This is what I ran
simultaneosly:
-Prime95, 6 workers & small FFTs (stresses CPU and cache)
-y-cruncher with 6 threads and calculating 3 000 000 000 digits of Pi (stresses RAM)
-Unigine Heaven Extreme (stresses GPU)
-MSI Kombustor 3 OpenCL Julia4D (GL3) (stresses GPU)
-SiSoftware Sandra burn-in test (continuous SSD benchmark, stresses SSD)
(-HWMonitor + Task Manager + Resource Monitor for checking the system's state)
(-Firefox, Steam, anti-virus software etc.)
It took a bit more than half an hour to finish the Pi calculation. In the end the digits checked out and Prime95
didn't encounter any errors. Socket temp reached 69 C, package temp reached 53 C, SSD temp reached 41 C
and GPU temp reached 59 C. As far as temps go, this was just about the hardest use my computer has seen,
RB's ST included. Of course, if the GPU is the source of the error in RB's ST then this error could easily go
unnoticed in such a test, as not all artefacts can be seen by the naked eye.
Thanks for the tip. I have run it without the GPU stress test without issues, but I'll check the GPU box as well and see
what happens.
Btw, is there a stress test that would only test the GPU with Blender (or something similar) so that it compares the
resulting picture with a picture that is known to be correct down to every pixel? All the GPU tests I know of just rely
on instabilities leading to visible errors or worse, which is already quite far into the unstable territory.
Edit: Of course the RB's ST does this, but it also does other things, which makes it harder to isolate the issue.
11-10-2015 01:34 PM
What kind of graphical bugs? You neglected to mention this. If the GPU is faulty then it could be your
culprit.
Thing is that doing that solo will most likely not produce your problem. In any case if you want to try,
do this:
1) Go to the blender subdirectory in RB and open a command prompt
2) Run "blender -b bmps.blend -F JPEG -o out -t 0 -f 1"
3) Once it's done you will have a out0001.jpg in that directory.
4) Open it with the hashing tool of your choice and check if the SHA-1 hash is
"06170F1A3AB84B173B9A4A0CE600945A7F94B7A2"