archive/blender-benchmark-bundle
Archived
1
0
Fork 0
Code Issues 12 Pull Requests Projects Releases Wiki Activity

Blender Benchmark on GPU terminates without error message #56361

New Issue
Closed
opened 2018-08-13 23:03:06 +02:00 by CodeManX · 9 comments
CodeManX commented 2018-08-13 23:03:06 +02:00
Copy Link

Version: blender-benchmark-1.0beta-windows64
OS: Windows 10 Pro 1803
GPU: Nvidia Geforce GTX 970 with Geforce Game Ready Driver 398.82

Shortly after the first warmup pass of the first scene, using the GPU and the complete benchmark, the process terminates without telling anything about the problem that apparently occurred.

From Windows event log:

NVIDIA OpenGL Driver

A TDR has been detected.
The application must close.

Error code: 7
(pid=12800 tid=1000 blender-benchmark.exe 64bit)

Visit http://nvidia.custhelp.com/app/answers/detail/a_id/3633 for more information.

And also:

Name der fehlerhaften Anwendung: blender-benchmark.exe, Version: 2.8.0.0, Zeitstempel: 0x5b69e20f
Name des fehlerhaften Moduls: nvoglv64.dll, Version: 24.21.13.9882, Zeitstempel: 0x5b5f4c60
Ausnahmecode: 0xc0000409
Fehleroffset: 0x0000000000db9ef9
ID des fehlerhaften Prozesses: 0x3200
Startzeit der fehlerhaften Anwendung: 0x01d43335f1d8a71e
Pfad der fehlerhaften Anwendung: C:\Users\Cody\Downloads\blender-benchmark-1.0beta-windows64\blender-benchmark.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_52ac7eb8f32780d5\nvoglv64.dll
Berichtskennung: 8d126e40-77f1-4817-98a7-321248464c49
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

Out of approximately 15 runs it terminated 13 times. Two other times, the UI showed "barbershop_interior: crashed :(" and continued with the other scenes, which rendered just fine.

I then followed this suggestion to increase the TDR value. With the increased timeout of 8 seconds, it only terminated the process once, all other attempts (roughly 8) made the UI show "barbershop_interior: crashed :(" and it continued with the other scenes. I did not reboot the system after changing the registry, I only restarted blender benchmark. It looks like it takes (somewhat of an) effect immediately however based on the statistics for termination vs. graceful crashes. The barbershop scene never rendered successfully though.

Anyway, the program should catch the OpenGL driver crashes and provide some useful hints how to fix the problem and never terminate silently.

**Version:** blender-benchmark-1.0beta-windows64 **OS:** Windows 10 Pro 1803 **GPU:** Nvidia Geforce GTX 970 with Geforce Game Ready Driver 398.82 Shortly after the first warmup pass of the first scene, using the GPU and the complete benchmark, the process terminates without telling anything about the problem that apparently occurred. From Windows event log: > NVIDIA OpenGL Driver > > A TDR has been detected. > The application must close. > > > Error code: 7 > (pid=12800 tid=1000 blender-benchmark.exe 64bit) > > Visit http://nvidia.custhelp.com/app/answers/detail/a_id/3633 for more information. And also: > Name der fehlerhaften Anwendung: blender-benchmark.exe, Version: 2.8.0.0, Zeitstempel: 0x5b69e20f > Name des fehlerhaften Moduls: nvoglv64.dll, Version: 24.21.13.9882, Zeitstempel: 0x5b5f4c60 > Ausnahmecode: 0xc0000409 > Fehleroffset: 0x0000000000db9ef9 > ID des fehlerhaften Prozesses: 0x3200 > Startzeit der fehlerhaften Anwendung: 0x01d43335f1d8a71e > Pfad der fehlerhaften Anwendung: C:\Users\Cody\Downloads\blender-benchmark-1.0beta-windows64\blender-benchmark.exe > Pfad des fehlerhaften Moduls: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_52ac7eb8f32780d5\nvoglv64.dll > Berichtskennung: 8d126e40-77f1-4817-98a7-321248464c49 > Vollständiger Name des fehlerhaften Pakets: > Anwendungs-ID, die relativ zum fehlerhaften Paket ist: Out of approximately 15 runs it terminated 13 times. Two other times, the UI showed "barbershop_interior: crashed :(" and continued with the other scenes, which rendered just fine. I then followed [this suggestion ](https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/windows-10-display-driver-has-stopped-responding/5caff7ea-bed5-4111-baac-e72d32d4dbe2) to increase the TDR value. With the increased timeout of 8 seconds, it only terminated the process once, all other attempts (roughly 8) made the UI show "barbershop_interior: crashed :(" and it continued with the other scenes. I did not reboot the system after changing the registry, I only restarted blender benchmark. It looks like it takes (somewhat of an) effect immediately however based on the statistics for termination vs. graceful crashes. The barbershop scene never rendered successfully though. Anyway, the program should catch the OpenGL driver crashes and provide some useful hints how to fix the problem and never terminate silently.
CodeManX commented 2018-08-13 23:03:06 +02:00
Author
Copy Link

Added subscriber: @CodeManX

Added subscriber: @CodeManX
CodeManX commented 2018-08-14 00:12:04 +02:00
Author
Copy Link

It still crashes with TdrDelay of 8 after reboot.
I just noticed that notifications pop up a bit before the process terminates, saying that access had been blocked to the graphics hardware for blender.exe:

Notification.png

It still crashes with TdrDelay of 8 after reboot. I just noticed that notifications pop up a bit before the process terminates, saying that access had been blocked to the graphics hardware for blender.exe: ![Notification.png](https://archive.blender.org/developer/F4217821/Notification.png)
Maciej Jutrzenka commented 2019-11-26 17:36:51 +01:00
Copy Link

Added subscriber: @MaciejJutrzenka

Added subscriber: @MaciejJutrzenka
Maciej Jutrzenka commented 2019-11-26 17:36:51 +01:00
Copy Link

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Maciej Jutrzenka self-assigned this 2019-11-26 17:36:51 +01:00
Maciej Jutrzenka commented 2019-11-26 17:36:51 +01:00
Copy Link

probably fixed plz check if it happens in official 2.81 version if yes make new bug report

probably fixed plz check if it happens in official 2.81 version if yes make new bug report
Maciej Jutrzenka commented 2019-11-26 18:42:42 +01:00
Copy Link

Changed status from 'Archived' to: 'Open'

Changed status from 'Archived' to: 'Open'
Evan Wilson commented 2020-01-17 03:36:49 +01:00
Copy Link

Added subscriber: @EAW

Added subscriber: @EAW
Evan Wilson commented 2020-01-17 03:36:49 +01:00
Copy Link

Changed status from 'Needs User Info' to: 'Archived'

Changed status from 'Needs User Info' to: 'Archived'
Evan Wilson commented 2020-01-17 03:36:49 +01:00
Copy Link

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.

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.
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Priority::Normal
Status::Archived
Status::Confirmed
Status::Duplicate
Status::Needs Triage
Status::Resolved
Type::Bug
Type::Design
Type::Report
Type::To Do
legacy module
Rendering & Cycles
legacy project
1.0.0-beta.2
legacy project
Blender Benchmark
legacy project
Cycles
No Label
Priority::Normal
Status::Archived
Type::Report
legacy project
Blender Benchmark
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
blender-admin
No Assignees Maciej Jutrzenka
3 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: archive/blender-benchmark-bundle#56361
No description provided.
Delete Branch "%!s()"

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?