Blender benchmark error #83421
Labels
No Label
legacy module
Rendering & Cycles
legacy project
1.0.0-beta.2
legacy project
Blender Benchmark
legacy project
Cycles
Priority::Normal
Status::Archived
Status::Confirmed
Status::Duplicate
Status::Needs Triage
Status::Resolved
Type::Bug
Type::Design
Type::Report
Type::To Do
No Milestone
No project
No Assignees
4 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: archive/blender-benchmark-bundle#83421
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: win10 pro
Graphics card: rtx 3070
CPU: AMD 3900x
Blender Version
Broken: Blender open data benchmark
2.90 GPU CUDA OPTIX
**Before I overclocked my GPU, both GPU and CPU test run well.
After I overclocked gpu with msi afterburner, when running benchmark app, it shows WHOOPS! didn't receive benchmark jason data.
But it still can benchmark my CPU.
**error id 8e688f3106ad47c5a152788279afaa72
Added subscriber: @Electricalfork
OPTIX is fine. Only CUDA will show this error
Added subscriber: @rjg
Changed status from 'Needs Triage' to: 'Needs User Info'
@Electricalfork If the issue is caused by overclocking then this is not a bug in Blender. If you're operating the hardware outside of its specification it may happen to not work properly. Undo the overclocking and check if the problem still occurs.
Added subscriber: @espectalll
Oh hey, this seems very similar to the issue I just reported while using an AMD card with OpenCL, #83431. No overclocking applied.
I cannot reproduce the issue. Does this still occur with the current Benchmark software?
Added subscriber: @lichtwerk
Changed status from 'Needs User Info' to: 'Archived'
No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.
Thanks again for the report. If the problem persists please open a new report with the required information.