GPU Glitches, Freezing, crashes, speckles, ghosts, etc. #69208

New Issue

Master James · 2019-08-27T12:29:06+02:00

Master James commented

2019-08-27 12:29:06 +02:00

System Information
Operating system: Win10 (currently up to date 2019-08-27)
Graphics card: NVidia GeForce RTX 2080 Ti Driver: 436.02 aka 2019-08-16 [26.21.14.3602]

Blender Version
v 2.80

Short description of error
The Graphics is glitching badly in various ways.
The two attached images show some of these issues.
1 has 'Ghosting' where multiple frames are overlaid.
2 has Green Speckles and pixel spot anomalies that flicker. There are also more in the display then what can be Screen grabbed. It's something like fireworks in a way.

The system will potentially Blue Screen Reboot, after Graphics Driver from glitching out also begins freezing & ultimately crashing and the entire OS becomes disabled by this.

I guess you should know this is happening, with latest Win10 OS updates and NVidia Drivers too?
Not sure how you can reproduce it. It does seem to be caused by Blender or maybe GPU usage.

**System Information** Operating system: Win10 (currently up to date 2019-08-27) Graphics card: NVidia GeForce RTX 2080 Ti Driver: 436.02 aka 2019-08-16 [26.21.14.3602] **Blender Version** v 2.80 **Short description of error** The Graphics is glitching badly in various ways. The two attached images show some of these issues. 1 has 'Ghosting' where multiple frames are overlaid. 2 has Green Speckles and pixel spot anomalies that flicker. There are also more in the display then what can be Screen grabbed. It's something like fireworks in a way. ![NvidiaBlenderGlitching-01.jpg](https://archive.blender.org/developer/F7706013/NvidiaBlenderGlitching-01.jpg) ![NvidiaBlenderGlitching-02.jpg](https://archive.blender.org/developer/F7706014/NvidiaBlenderGlitching-02.jpg) The system will potentially Blue Screen Reboot, after Graphics Driver from glitching out also begins freezing & ultimately crashing and the entire OS becomes disabled by this. I guess you should know this is happening, with latest Win10 OS updates and NVidia Drivers too? Not sure how you can reproduce it. It does seem to be caused by Blender or maybe GPU usage.

Master James commented

2019-08-27 12:29:06 +02:00

Added subscriber: @MasterJames

Master James commented

2019-08-27 14:05:37 +02:00

Here is the Event Viewer during a Blender crash in this situation, where the NVidia Driver is failed. I remind you this is a high-end system and it simply can not be out of Memory.

The description for Event ID 2 from source NVIDIA OpenGL Driver cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

The NVIDIA OpenGL driver has encountered
an out of memory error. This application might
behave inconsistently and fail.
(pid=9300 blender.exe 64bit)

The message resource is present but the message was not found in the message table

Here is the Event Viewer during a Blender crash in this situation, where the NVidia Driver is failed. I remind you this is a high-end system and it simply can not be out of Memory. ``` The description for Event ID 2 from source NVIDIA OpenGL Driver cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: The NVIDIA OpenGL driver has encountered an out of memory error. This application might behave inconsistently and fail. (pid=9300 blender.exe 64bit) The message resource is present but the message was not found in the message table ```

Master James commented

2019-08-27 14:12:18 +02:00

Here is the Blender Event Viewer log...


Fault bucket 1504689781765163320, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: blender.exe
P2: 2.8.0.0
P3: 5d3f1481
P4: nvoglv64.dll
P5: 26.21.14.3602
P6: 5d57036d
P7: 0000000000f40559
P8: c0000409
P9: 0000000000000007
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD2B9.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD356.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD367.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD365.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD395.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_blender.exe_9f15ca4ce1eb25a4db7654a9676a44c203a833f_fd8f7391_d7dfdde4-bb5a-4b1d-af88-c7a85e0de2dc

Analysis symbol: 
Rechecking for solution: 0
Report Id: 3fb00037-6050-4a70-be8d-4e54009bc607
Report Status: 268435456
Hashed bucket: c6709a1397eb341824e1bb626345c938
Cab Guid: 0

It leads to a WER file that follows


Version=1
EventType=BEX64
EventTime=132113813176742000
ReportType=2
Consent=1
UploadTime=132113813179089464
ReportStatus=268435456
ReportIdentifier=d7dfdde4-bb5a-4b1d-af88-c7a85e0de2dc
IntegratorReportIdentifier=3fb00037-6050-4a70-be8d-4e54009bc607
Wow64Host=34404
NsAppName=blender.exe
OriginalFilename=blender.exe
AppSessionGuid=00001dd4-0001-0015-3ffd-fffdcf5cd501
TargetAppId=W:0006060460470f86936932e0ed731ccb163900000904!000040de94469bfc113800a3bbc392a4fd76b760509d!blender.exe
TargetAppVer=2019*07*29:15:45:05!0!blender.exe
BootId=4294967295
ServiceSplit=528085297
TargetAsId=2045
UserImpactVector=808465200
IsFatal=1
EtwNonCollectReason=1
Response.BucketId=c6709a1397eb341824e1bb626345c938
Response.BucketTable=5
Response.LegacyBucketId=1504689781765163320
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=blender.exe
Sig[1].Name=Application Version
Sig[1].Value=2.8.0.0
Sig[2].Name=Application Timestamp
Sig[2].Value=5d3f1481
Sig[3].Name=Fault Module Name
Sig[3].Value=nvoglv64.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=26.21.14.3602
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=5d57036d
Sig[6].Name=Exception Offset
Sig[6].Value=0000000000f40559
Sig[7].Name=Exception Code
Sig[7].Value=c0000409
Sig[8].Name=Exception Data
Sig[8].Value=0000000000000007
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.18362.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=4105
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=678f
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=678f4ed4db5abb2ce01883cbc696c793
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=61b6
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=61b60dfddb8415b7c77e66647b825bc9
UI[2]=C:\Program Files\Blender Foundation\Blender\blender.exe
LoadedModule[0]=C:\Program Files\Blender Foundation\Blender\blender.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\System32\KERNEL32.DLL
LoadedModule[3]=C:\WINDOWS\System32\KERNELBASE.dll
LoadedModule[4]=C:\WINDOWS\System32\USER32.dll
LoadedModule[5]=C:\WINDOWS\System32\win32u.dll
LoadedModule[6]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[7]=C:\Program Files\Blender Foundation\Blender\SDL2.dll
LoadedModule[8]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[9]=C:\Program Files\Blender Foundation\Blender\python37.dll
LoadedModule[10]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[11]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[12]=C:\Program Files\Blender Foundation\Blender\avcodec-58.dll
LoadedModule[13]=C:\WINDOWS\System32\ADVAPI32.dll
LoadedModule[14]=C:\WINDOWS\System32\SHLWAPI.dll
LoadedModule[15]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[16]=C:\WINDOWS\System32\sechost.dll
LoadedModule[17]=C:\WINDOWS\System32\IMM32.dll
LoadedModule[18]=C:\WINDOWS\System32\combase.dll
LoadedModule[19]=C:\WINDOWS\System32\ole32.dll
LoadedModule[20]=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule[21]=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule[22]=C:\WINDOWS\System32\OLEAUT32.dll
LoadedModule[23]=C:\WINDOWS\System32\WS2_32.dll
LoadedModule[24]=C:\WINDOWS\System32\SHELL32.dll
LoadedModule[25]=C:\Program Files\Blender Foundation\Blender\avutil-56.dll
LoadedModule[26]=C:\WINDOWS\System32\cfgmgr32.dll
LoadedModule[27]=C:\WINDOWS\System32\shcore.dll
LoadedModule[28]=C:\Program Files\Blender Foundation\Blender\avdevice-58.dll
LoadedModule[29]=C:\WINDOWS\System32\bcrypt.dll
LoadedModule[30]=C:\Program Files\Blender Foundation\Blender\avformat-58.dll
LoadedModule[31]=C:\WINDOWS\System32\windows.storage.dll
LoadedModule[32]=C:\Program Files\Blender Foundation\Blender\swscale-5.dll
LoadedModule[33]=C:\WINDOWS\System32\profapi.dll
LoadedModule[34]=C:\WINDOWS\SYSTEM32\AVIFIL32.dll
LoadedModule[35]=C:\WINDOWS\System32\powrprof.dll
LoadedModule[36]=C:\WINDOWS\SYSTEM32\OPENGL32.dll
LoadedModule[37]=C:\WINDOWS\System32\UMPDC.dll
LoadedModule[38]=C:\WINDOWS\System32\kernel.appcore.dll
LoadedModule[39]=C:\WINDOWS\System32\cryptsp.dll
LoadedModule[40]=C:\WINDOWS\SYSTEM32\WINMM.dll
LoadedModule[41]=C:\WINDOWS\SYSTEM32\VERSION.dll
LoadedModule[42]=C:\WINDOWS\System32\PSAPI.DLL
LoadedModule[43]=C:\WINDOWS\SYSTEM32\SHFOLDER.dll
LoadedModule[44]=C:\Program Files\Blender Foundation\Blender\swresample-3.dll
LoadedModule[45]=C:\Program Files\Blender Foundation\Blender\VCRUNTIME140.dll
LoadedModule[46]=C:\WINDOWS\SYSTEM32\Secur32.dll
LoadedModule[47]=C:\WINDOWS\SYSTEM32\AVICAP32.dll
LoadedModule[48]=C:\WINDOWS\SYSTEM32\MSACM32.dll
LoadedModule[49]=C:\WINDOWS\SYSTEM32\MSVFW32.dll
LoadedModule[50]=C:\WINDOWS\SYSTEM32\GLU32.dll
LoadedModule[51]=C:\Program Files\Blender Foundation\Blender\libsndfile-1.dll
LoadedModule[52]=C:\Program Files\Blender Foundation\Blender\OpenAL32.dll
LoadedModule[53]=C:\WINDOWS\SYSTEM32\WINMMBASE.dll
LoadedModule[54]=C:\WINDOWS\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.18362.239_none_2a25bd6a466b9e19\COMCTL32.dll
LoadedModule[55]=C:\WINDOWS\SYSTEM32\dxcore.dll
LoadedModule[56]=C:\WINDOWS\SYSTEM32\SSPICLI.DLL
LoadedModule[57]=C:\WINDOWS\system32\uxtheme.dll
LoadedModule[58]=C:\WINDOWS\System32\clbcatq.dll
LoadedModule[59]=C:\WINDOWS\System32\MMDevApi.dll
LoadedModule[60]=C:\WINDOWS\System32\DEVOBJ.dll
LoadedModule[61]=C:\WINDOWS\SYSTEM32\AUDIOSES.DLL
LoadedModule[62]=C:\WINDOWS\SYSTEM32\wintypes.dll
LoadedModule[63]=C:\WINDOWS\SYSTEM32\resourcepolicyclient.dll
LoadedModule[64]=C:\WINDOWS\System32\MSCTF.dll
LoadedModule[65]=C:\WINDOWS\system32\dataexchange.dll
LoadedModule[66]=C:\WINDOWS\system32\d3d11.dll
LoadedModule[67]=C:\WINDOWS\system32\dcomp.dll
LoadedModule[68]=C:\WINDOWS\system32\dxgi.dll
LoadedModule[69]=C:\WINDOWS\system32\twinapi.appcore.dll
LoadedModule[70]=C:\WINDOWS\system32\RMCLIENT.dll
LoadedModule[71]=C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_fd332b7c7ad5fe7e\nvoglv64.dll
LoadedModule[72]=C:\WINDOWS\System32\SETUPAPI.dll
LoadedModule[73]=C:\WINDOWS\SYSTEM32\WTSAPI32.dll
LoadedModule[74]=C:\WINDOWS\System32\WINTRUST.dll
LoadedModule[75]=C:\WINDOWS\System32\MSASN1.dll
LoadedModule[76]=C:\WINDOWS\System32\CRYPT32.dll
LoadedModule[77]=C:\WINDOWS\SYSTEM32\ntmarta.dll
LoadedModule[78]=C:\WINDOWS\SYSTEM32\dwmapi.dll
LoadedModule[79]=C:\WINDOWS\SYSTEM32\WINSTA.dll
LoadedModule[80]=C:\WINDOWS\SYSTEM32\TextInputFramework.dll
LoadedModule[81]=C:\WINDOWS\SYSTEM32\CoreUIComponents.dll
LoadedModule[82]=C:\WINDOWS\SYSTEM32\CoreMessaging.dll
LoadedModule[83]=C:\WINDOWS\SYSTEM32\iertutil.dll
LoadedModule[84]=C:\WINDOWS\system32\explorerframe.dll
LoadedModule[85]=C:\WINDOWS\system32\rsaenh.dll
LoadedModule[86]=C:\WINDOWS\SYSTEM32\CRYPTBASE.dll
LoadedModule[87]=C:\Program Files\Blender Foundation\Blender\2.80\python\lib\_ctypes.pyd
LoadedModule[88]=C:\Program Files\Blender Foundation\Blender\2.80\python\lib\_hashlib.pyd
LoadedModule[89]=C:\Program Files\Blender Foundation\Blender\2.80\python\lib\libcrypto-1_1-x64.dll
LoadedModule[90]=C:\Program Files\Blender Foundation\Blender\2.80\python\lib\_decimal.pyd
State[0].Key=Transport.DoneStage1
State[0].Value=1
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=18362
OsInfo[3].Key=ubr
OsInfo[3].Value=239
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1033
OsInfo[7].Key=geoid
OsInfo[7].Value=39
OsInfo[8].Key=sku
OsInfo[8].Value=48
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=256
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=116682
OsInfo[15].Key=osinsty
OsInfo[15].Value=1
OsInfo[16].Key=iever
OsInfo[16].Value=11.239.18362.0-11.0.135
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=65207
OsInfo[19].Key=svolsz
OsInfo[19].Value=953
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=190318
OsInfo[22].Key=bldtm
OsInfo[22].Value=1202
OsInfo[23].Key=bldbrch
OsInfo[23].Value=19h1_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.18362.239.amd64fre.19h1_release.190318-1202
OsInfo[30].Key=buildflightid
OsInfo[30].Value=2ABBFE8A-57A7-4ECE-870E-2008A39B7D9D.1
OsInfo[31].Key=edition
OsInfo[31].Value=Professional
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=expid
OsInfo[33].Value=RS:3630
OsInfo[34].Key=containerid
OsInfo[35].Key=containertype
OsInfo[36].Key=edu
OsInfo[36].Value=0
FriendlyEventName=Stopped working
ConsentKey=BEX64
AppName=Blender
AppPath=C:\Program Files\Blender Foundation\Blender\blender.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=6820C2187B5E56A34CF5A250CEF8B916
MetadataHash=-246228888

Here is the Blender Event Viewer log... ``` Fault bucket 1504689781765163320, type 5 Event Name: BEX64 Response: Not available Cab Id: 0 Problem signature: P1: blender.exe P2: 2.8.0.0 P3: 5d3f1481 P4: nvoglv64.dll P5: 26.21.14.3602 P6: 5d57036d P7: 0000000000f40559 P8: c0000409 P9: 0000000000000007 P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD2B9.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD356.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD367.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD365.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD395.tmp.txt These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_blender.exe_9f15ca4ce1eb25a4db7654a9676a44c203a833f_fd8f7391_d7dfdde4-bb5a-4b1d-af88-c7a85e0de2dc Analysis symbol: Rechecking for solution: 0 Report Id: 3fb00037-6050-4a70-be8d-4e54009bc607 Report Status: 268435456 Hashed bucket: c6709a1397eb341824e1bb626345c938 Cab Guid: 0 ``` It leads to a WER file that follows ``` Version=1 EventType=BEX64 EventTime=132113813176742000 ReportType=2 Consent=1 UploadTime=132113813179089464 ReportStatus=268435456 ReportIdentifier=d7dfdde4-bb5a-4b1d-af88-c7a85e0de2dc IntegratorReportIdentifier=3fb00037-6050-4a70-be8d-4e54009bc607 Wow64Host=34404 NsAppName=blender.exe OriginalFilename=blender.exe AppSessionGuid=00001dd4-0001-0015-3ffd-fffdcf5cd501 TargetAppId=W:0006060460470f86936932e0ed731ccb163900000904!000040de94469bfc113800a3bbc392a4fd76b760509d!blender.exe TargetAppVer=2019*07*29:15:45:05!0!blender.exe BootId=4294967295 ServiceSplit=528085297 TargetAsId=2045 UserImpactVector=808465200 IsFatal=1 EtwNonCollectReason=1 Response.BucketId=c6709a1397eb341824e1bb626345c938 Response.BucketTable=5 Response.LegacyBucketId=1504689781765163320 Response.type=4 Sig[0].Name=Application Name Sig[0].Value=blender.exe Sig[1].Name=Application Version Sig[1].Value=2.8.0.0 Sig[2].Name=Application Timestamp Sig[2].Value=5d3f1481 Sig[3].Name=Fault Module Name Sig[3].Value=nvoglv64.dll Sig[4].Name=Fault Module Version Sig[4].Value=26.21.14.3602 Sig[5].Name=Fault Module Timestamp Sig[5].Value=5d57036d Sig[6].Name=Exception Offset Sig[6].Value=0000000000f40559 Sig[7].Name=Exception Code Sig[7].Value=c0000409 Sig[8].Name=Exception Data Sig[8].Value=0000000000000007 DynamicSig[1].Name=OS Version DynamicSig[1].Value=10.0.18362.2.0.0.256.48 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=4105 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=678f DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=678f4ed4db5abb2ce01883cbc696c793 DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=61b6 DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=61b60dfddb8415b7c77e66647b825bc9 UI[2]=C:\Program Files\Blender Foundation\Blender\blender.exe LoadedModule[0]=C:\Program Files\Blender Foundation\Blender\blender.exe LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll LoadedModule[2]=C:\WINDOWS\System32\KERNEL32.DLL LoadedModule[3]=C:\WINDOWS\System32\KERNELBASE.dll LoadedModule[4]=C:\WINDOWS\System32\USER32.dll LoadedModule[5]=C:\WINDOWS\System32\win32u.dll LoadedModule[6]=C:\WINDOWS\System32\GDI32.dll LoadedModule[7]=C:\Program Files\Blender Foundation\Blender\SDL2.dll LoadedModule[8]=C:\WINDOWS\System32\gdi32full.dll LoadedModule[9]=C:\Program Files\Blender Foundation\Blender\python37.dll LoadedModule[10]=C:\WINDOWS\System32\msvcp_win.dll LoadedModule[11]=C:\WINDOWS\System32\ucrtbase.dll LoadedModule[12]=C:\Program Files\Blender Foundation\Blender\avcodec-58.dll LoadedModule[13]=C:\WINDOWS\System32\ADVAPI32.dll LoadedModule[14]=C:\WINDOWS\System32\SHLWAPI.dll LoadedModule[15]=C:\WINDOWS\System32\msvcrt.dll LoadedModule[16]=C:\WINDOWS\System32\sechost.dll LoadedModule[17]=C:\WINDOWS\System32\IMM32.dll LoadedModule[18]=C:\WINDOWS\System32\combase.dll LoadedModule[19]=C:\WINDOWS\System32\ole32.dll LoadedModule[20]=C:\WINDOWS\System32\RPCRT4.dll LoadedModule[21]=C:\WINDOWS\System32\bcryptPrimitives.dll LoadedModule[22]=C:\WINDOWS\System32\OLEAUT32.dll LoadedModule[23]=C:\WINDOWS\System32\WS2_32.dll LoadedModule[24]=C:\WINDOWS\System32\SHELL32.dll LoadedModule[25]=C:\Program Files\Blender Foundation\Blender\avutil-56.dll LoadedModule[26]=C:\WINDOWS\System32\cfgmgr32.dll LoadedModule[27]=C:\WINDOWS\System32\shcore.dll LoadedModule[28]=C:\Program Files\Blender Foundation\Blender\avdevice-58.dll LoadedModule[29]=C:\WINDOWS\System32\bcrypt.dll LoadedModule[30]=C:\Program Files\Blender Foundation\Blender\avformat-58.dll LoadedModule[31]=C:\WINDOWS\System32\windows.storage.dll LoadedModule[32]=C:\Program Files\Blender Foundation\Blender\swscale-5.dll LoadedModule[33]=C:\WINDOWS\System32\profapi.dll LoadedModule[34]=C:\WINDOWS\SYSTEM32\AVIFIL32.dll LoadedModule[35]=C:\WINDOWS\System32\powrprof.dll LoadedModule[36]=C:\WINDOWS\SYSTEM32\OPENGL32.dll LoadedModule[37]=C:\WINDOWS\System32\UMPDC.dll LoadedModule[38]=C:\WINDOWS\System32\kernel.appcore.dll LoadedModule[39]=C:\WINDOWS\System32\cryptsp.dll LoadedModule[40]=C:\WINDOWS\SYSTEM32\WINMM.dll LoadedModule[41]=C:\WINDOWS\SYSTEM32\VERSION.dll LoadedModule[42]=C:\WINDOWS\System32\PSAPI.DLL LoadedModule[43]=C:\WINDOWS\SYSTEM32\SHFOLDER.dll LoadedModule[44]=C:\Program Files\Blender Foundation\Blender\swresample-3.dll LoadedModule[45]=C:\Program Files\Blender Foundation\Blender\VCRUNTIME140.dll LoadedModule[46]=C:\WINDOWS\SYSTEM32\Secur32.dll LoadedModule[47]=C:\WINDOWS\SYSTEM32\AVICAP32.dll LoadedModule[48]=C:\WINDOWS\SYSTEM32\MSACM32.dll LoadedModule[49]=C:\WINDOWS\SYSTEM32\MSVFW32.dll LoadedModule[50]=C:\WINDOWS\SYSTEM32\GLU32.dll LoadedModule[51]=C:\Program Files\Blender Foundation\Blender\libsndfile-1.dll LoadedModule[52]=C:\Program Files\Blender Foundation\Blender\OpenAL32.dll LoadedModule[53]=C:\WINDOWS\SYSTEM32\WINMMBASE.dll LoadedModule[54]=C:\WINDOWS\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.18362.239_none_2a25bd6a466b9e19\COMCTL32.dll LoadedModule[55]=C:\WINDOWS\SYSTEM32\dxcore.dll LoadedModule[56]=C:\WINDOWS\SYSTEM32\SSPICLI.DLL LoadedModule[57]=C:\WINDOWS\system32\uxtheme.dll LoadedModule[58]=C:\WINDOWS\System32\clbcatq.dll LoadedModule[59]=C:\WINDOWS\System32\MMDevApi.dll LoadedModule[60]=C:\WINDOWS\System32\DEVOBJ.dll LoadedModule[61]=C:\WINDOWS\SYSTEM32\AUDIOSES.DLL LoadedModule[62]=C:\WINDOWS\SYSTEM32\wintypes.dll LoadedModule[63]=C:\WINDOWS\SYSTEM32\resourcepolicyclient.dll LoadedModule[64]=C:\WINDOWS\System32\MSCTF.dll LoadedModule[65]=C:\WINDOWS\system32\dataexchange.dll LoadedModule[66]=C:\WINDOWS\system32\d3d11.dll LoadedModule[67]=C:\WINDOWS\system32\dcomp.dll LoadedModule[68]=C:\WINDOWS\system32\dxgi.dll LoadedModule[69]=C:\WINDOWS\system32\twinapi.appcore.dll LoadedModule[70]=C:\WINDOWS\system32\RMCLIENT.dll LoadedModule[71]=C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_fd332b7c7ad5fe7e\nvoglv64.dll LoadedModule[72]=C:\WINDOWS\System32\SETUPAPI.dll LoadedModule[73]=C:\WINDOWS\SYSTEM32\WTSAPI32.dll LoadedModule[74]=C:\WINDOWS\System32\WINTRUST.dll LoadedModule[75]=C:\WINDOWS\System32\MSASN1.dll LoadedModule[76]=C:\WINDOWS\System32\CRYPT32.dll LoadedModule[77]=C:\WINDOWS\SYSTEM32\ntmarta.dll LoadedModule[78]=C:\WINDOWS\SYSTEM32\dwmapi.dll LoadedModule[79]=C:\WINDOWS\SYSTEM32\WINSTA.dll LoadedModule[80]=C:\WINDOWS\SYSTEM32\TextInputFramework.dll LoadedModule[81]=C:\WINDOWS\SYSTEM32\CoreUIComponents.dll LoadedModule[82]=C:\WINDOWS\SYSTEM32\CoreMessaging.dll LoadedModule[83]=C:\WINDOWS\SYSTEM32\iertutil.dll LoadedModule[84]=C:\WINDOWS\system32\explorerframe.dll LoadedModule[85]=C:\WINDOWS\system32\rsaenh.dll LoadedModule[86]=C:\WINDOWS\SYSTEM32\CRYPTBASE.dll LoadedModule[87]=C:\Program Files\Blender Foundation\Blender\2.80\python\lib\_ctypes.pyd LoadedModule[88]=C:\Program Files\Blender Foundation\Blender\2.80\python\lib\_hashlib.pyd LoadedModule[89]=C:\Program Files\Blender Foundation\Blender\2.80\python\lib\libcrypto-1_1-x64.dll LoadedModule[90]=C:\Program Files\Blender Foundation\Blender\2.80\python\lib\_decimal.pyd State[0].Key=Transport.DoneStage1 State[0].Value=1 OsInfo[0].Key=vermaj OsInfo[0].Value=10 OsInfo[1].Key=vermin OsInfo[1].Value=0 OsInfo[2].Key=verbld OsInfo[2].Value=18362 OsInfo[3].Key=ubr OsInfo[3].Value=239 OsInfo[4].Key=versp OsInfo[4].Value=0 OsInfo[5].Key=arch OsInfo[5].Value=9 OsInfo[6].Key=lcid OsInfo[6].Value=1033 OsInfo[7].Key=geoid OsInfo[7].Value=39 OsInfo[8].Key=sku OsInfo[8].Value=48 OsInfo[9].Key=domain OsInfo[9].Value=0 OsInfo[10].Key=prodsuite OsInfo[10].Value=256 OsInfo[11].Key=ntprodtype OsInfo[11].Value=1 OsInfo[12].Key=platid OsInfo[12].Value=10 OsInfo[13].Key=sr OsInfo[13].Value=0 OsInfo[14].Key=tmsi OsInfo[14].Value=116682 OsInfo[15].Key=osinsty OsInfo[15].Value=1 OsInfo[16].Key=iever OsInfo[16].Value=11.239.18362.0-11.0.135 OsInfo[17].Key=portos OsInfo[17].Value=0 OsInfo[18].Key=ram OsInfo[18].Value=65207 OsInfo[19].Key=svolsz OsInfo[19].Value=953 OsInfo[20].Key=wimbt OsInfo[20].Value=0 OsInfo[21].Key=blddt OsInfo[21].Value=190318 OsInfo[22].Key=bldtm OsInfo[22].Value=1202 OsInfo[23].Key=bldbrch OsInfo[23].Value=19h1_release OsInfo[24].Key=bldchk OsInfo[24].Value=0 OsInfo[25].Key=wpvermaj OsInfo[25].Value=0 OsInfo[26].Key=wpvermin OsInfo[26].Value=0 OsInfo[27].Key=wpbuildmaj OsInfo[27].Value=0 OsInfo[28].Key=wpbuildmin OsInfo[28].Value=0 OsInfo[29].Key=osver OsInfo[29].Value=10.0.18362.239.amd64fre.19h1_release.190318-1202 OsInfo[30].Key=buildflightid OsInfo[30].Value=2ABBFE8A-57A7-4ECE-870E-2008A39B7D9D.1 OsInfo[31].Key=edition OsInfo[31].Value=Professional OsInfo[32].Key=ring OsInfo[32].Value=Retail OsInfo[33].Key=expid OsInfo[33].Value=RS:3630 OsInfo[34].Key=containerid OsInfo[35].Key=containertype OsInfo[36].Key=edu OsInfo[36].Value=0 FriendlyEventName=Stopped working ConsentKey=BEX64 AppName=Blender AppPath=C:\Program Files\Blender Foundation\Blender\blender.exe NsPartner=windows NsGroup=windows8 ApplicationIdentity=6820C2187B5E56A34CF5A250CEF8B916 MetadataHash=-246228888 ```

Master James commented

2019-08-27 14:14:31 +02:00

This Event in the Viewer is of the Level: Application Error

Faulting application name: blender.exe, version: 2.8.0.0, time stamp: 0x5d3f1481
Faulting module name: nvoglv64.dll, version: 26.21.14.3602, time stamp: 0x5d57036d
Exception code: 0xc0000409
Fault offset: 0x0000000000f40559
Faulting process id: 0x1dd4
Faulting application start time: 0x01d55ccffdfffd3f
Faulting application path: C:\Program Files\Blender Foundation\Blender\blender.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_fd332b7c7ad5fe7e\nvoglv64.dll
Report Id: 3fb00037-6050-4a70-be8d-4e54009bc607
Faulting package full name: 
Faulting package-relative application ID:

This Event in the Viewer is of the Level: Application Error ``` Faulting application name: blender.exe, version: 2.8.0.0, time stamp: 0x5d3f1481 Faulting module name: nvoglv64.dll, version: 26.21.14.3602, time stamp: 0x5d57036d Exception code: 0xc0000409 Fault offset: 0x0000000000f40559 Faulting process id: 0x1dd4 Faulting application start time: 0x01d55ccffdfffd3f Faulting application path: C:\Program Files\Blender Foundation\Blender\blender.exe Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_fd332b7c7ad5fe7e\nvoglv64.dll Report Id: 3fb00037-6050-4a70-be8d-4e54009bc607 Faulting package full name: Faulting package-relative application ID: ```

Master James commented

2019-08-27 14:27:29 +02:00

I also ran it with --debug-gpu flag and got loads of output there.

GL API other: Buffer detailed info: Buffer object 2 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STREAM_DRAW) will use VIDEO memory as the source for buffer object operations.
GPUTexture: create : TEXTURE_2D, RGBA8, w : 1, h : 1, d : 0, comp : 4, size : 0.00 MiB
GL API other: Buffer detailed info: Buffer object 2 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STREAM_DRAW) will use VIDEO memory as the source for buffer object operations.
GL API other: Buffer detailed info: Buffer object 2 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STREAM_DRAW) will use VIDEO memory as the source for buffer object operations.
GL API other: Buffer detailed info: Buffer object 1 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_DYNAMIC_DRAW) has been mapped WRITE_ONLY in SYSTEM HEAP memory (fast).
GL API other: Texture state usage warning: The texture object (0) bound to texture image unit 0 does not have a defined base level and cannot be used for texture mapping.
GL API other: Buffer detailed info: Buffer object 1 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_DYNAMIC_DRAW) has been mapped WRITE_ONLY in SYSTEM HEAP memory (fast).
GL API other: Buffer detailed info: Buffer object 1 (bound to GL_VERTEX_ATTRIB_ARRAY_BUFFER_BINDING_ARB (0), and GL_ARRAY_BUFFER_ARB, usage hint is GL_DYNAMIC_DRAW) has been mapped WRITE_ONLY in SYSTEM HEAP memory (fast).
G

Maybe this excerpt reveals something interesting to someone in the know?

I also ran it with --debug-gpu flag and got loads of output there. ``` GL API other: Buffer detailed info: Buffer object 2 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STREAM_DRAW) will use VIDEO memory as the source for buffer object operations. GPUTexture: create : TEXTURE_2D, RGBA8, w : 1, h : 1, d : 0, comp : 4, size : 0.00 MiB GL API other: Buffer detailed info: Buffer object 2 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STREAM_DRAW) will use VIDEO memory as the source for buffer object operations. GL API other: Buffer detailed info: Buffer object 2 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STREAM_DRAW) will use VIDEO memory as the source for buffer object operations. GL API other: Buffer detailed info: Buffer object 1 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_DYNAMIC_DRAW) has been mapped WRITE_ONLY in SYSTEM HEAP memory (fast). GL API other: Texture state usage warning: The texture object (0) bound to texture image unit 0 does not have a defined base level and cannot be used for texture mapping. GL API other: Buffer detailed info: Buffer object 1 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_DYNAMIC_DRAW) has been mapped WRITE_ONLY in SYSTEM HEAP memory (fast). GL API other: Buffer detailed info: Buffer object 1 (bound to GL_VERTEX_ATTRIB_ARRAY_BUFFER_BINDING_ARB (0), and GL_ARRAY_BUFFER_ARB, usage hint is GL_DYNAMIC_DRAW) has been mapped WRITE_ONLY in SYSTEM HEAP memory (fast). G ``` Maybe this excerpt reveals something interesting to someone in the know?

Master James commented

2019-08-28 11:19:39 +02:00

I found a way to reproduce this following the Procedural Crystal tutorial.

https://www.youtube.com/watch?v=d-zpR1E84nQ

This file attached when switched to "Rendered" Viewport mode will typically crash Blender.

ProceduralCrystals-01.blend

Here is what one sees in the cmd window.

CUDA error: Illegal instruction in cuCtxSynchronize(), line 1800

Refer to the Cycles GPU rendering documentation for possible solutions:
https://docs.blender.org/manual/en/latest/render/cycles/gpu_rendering.html

CUDA error: Illegal instruction in cuCtxSynchronize(), line 2279
Saved session recovery to 'C:\Users\James\AppData\Local\Temp\quit.blend'
CUDA error: Illegal instruction in cuGraphicsUnregisterResource(pmem.cuPBOresource), line 2055

I thought it not only had to do with displacement but also in Eevee doing large 4096 shadow map settings, but really I guess it's anything pushing the system hard. Maybe my brand new state of the art graphics card is hooped.

I found a way to reproduce this following the Procedural Crystal tutorial. https://www.youtube.com/watch?v=d-zpR1E84nQ This file attached when switched to "Rendered" Viewport mode will typically crash Blender. [ProceduralCrystals-01.blend](https://archive.blender.org/developer/F7707430/ProceduralCrystals-01.blend) Here is what one sees in the cmd window. ``` CUDA error: Illegal instruction in cuCtxSynchronize(), line 1800 Refer to the Cycles GPU rendering documentation for possible solutions: https://docs.blender.org/manual/en/latest/render/cycles/gpu_rendering.html CUDA error: Illegal instruction in cuCtxSynchronize(), line 2279 Saved session recovery to 'C:\Users\James\AppData\Local\Temp\quit.blend' CUDA error: Illegal instruction in cuGraphicsUnregisterResource(pmem.cuPBOresource), line 2055 ``` I thought it not only had to do with displacement but also in Eevee doing large 4096 shadow map settings, but really I guess it's anything pushing the system hard. Maybe my brand new state of the art graphics card is hooped.

Philipp Oeser commented

2019-08-28 13:20:30 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2019-08-28 13:20:30 +02:00

No problems with ProceduralCrystals-01.blend here ( linux, 970m, 430.26 drivers )

But we seem to be dealing with multiple issues here (ProceduralCrystals-01.blend is about cycles rendering)?

first pic seems to be tied to Lookdev [could you provide the corresponding file for us?]
second pic seems to be tied to Eevee rendered view [could you provide the corresponding file for us as well?]

So first we need the files, then we can see if this needs to be separate reports....

No problems with `ProceduralCrystals-01.blend` here ( linux, 970m, 430.26 drivers ) But we seem to be dealing with multiple issues here (`ProceduralCrystals-01.blend` is about cycles rendering)? - first pic seems to be tied to Lookdev [could you provide the corresponding file for us?] - second pic seems to be tied to Eevee rendered view [could you provide the corresponding file for us as well?] So first we need the files, then we can see if this needs to be separate reports....

Master James commented

2019-08-29 11:54:10 +02:00

I am going to have the hardware checked and I think sent back to Asus. The 2080 Ti I had to wait two months for and I guess they rushed these cards out?
I will attempt to report back later.
Still I am thinking maybe there should be a way you assess instability in the graphics card response times on average and pop up or log a warning saying graphics is performing poorly.
The Blender system could have a setting to use 99% by default and let uses tune it down if it's causing the card to fry etc. I'm not sure it seems like not only a good idea to limit issues but to also let the user know it's not Blender but Blender has detected sporadic frame rate etc.
I get green speckles dancing and other obvious indicators.
I have run a few tests on the hardware and it seems more like the problem since your test of the Cycles GPU Crash file above was not a problem. I suppose other then my thoughts above I am a little embarrassed to have brought this to your attention. Still it seemed like only Blender was causing this but then only Blender was pushing the GPU to it's limits. With things like 4096 shadow maps trying to get cycles like quality out of Eevee etc., which still falls short but has potential moving slowly forward.
They say it will take a couple of weeks to replace the card if their testing shows it has issues, so I will be offline until it is replaced.

I am going to have the hardware checked and I think sent back to Asus. The 2080 Ti I had to wait two months for and I guess they rushed these cards out? I will attempt to report back later. Still I am thinking maybe there should be a way you assess instability in the graphics card response times on average and pop up or log a warning saying graphics is performing poorly. The Blender system could have a setting to use 99% by default and let uses tune it down if it's causing the card to fry etc. I'm not sure it seems like not only a good idea to limit issues but to also let the user know it's not Blender but Blender has detected sporadic frame rate etc. I get green speckles dancing and other obvious indicators. I have run a few tests on the hardware and it seems more like the problem since your test of the Cycles GPU Crash file above was not a problem. I suppose other then my thoughts above I am a little embarrassed to have brought this to your attention. Still it seemed like only Blender was causing this but then only Blender was pushing the GPU to it's limits. With things like 4096 shadow maps trying to get cycles like quality out of Eevee etc., which still falls short but has potential moving slowly forward. They say it will take a couple of weeks to replace the card if their testing shows it has issues, so I will be offline until it is replaced.

Philipp Oeser commented

2019-08-29 12:28:19 +02:00

Just another shot in the dark (there was another (unrelated -- was about poor rendering performance) report (also using 436.XX drivers).
I cannot test these 436.XX (not offered for my card/system), but just out of curiosity: have you tried if using 430.XX makes a difference?

Just another shot in the dark (there was another (unrelated -- was about poor rendering performance) report (also using 436.XX drivers). I cannot test these 436.XX (not offered for my card/system), but just out of curiosity: have you tried if using 430.XX makes a difference?

Philipp Oeser commented

2019-08-29 12:30:55 +02:00

I'll set this back to "Needs Information from User" since we are waiting for the card to be replaced (or the drivers test).
But everyone reading this: please dont close this for inactivity (even if it takes longer than the usual week for @MasterJames to reply).

I'll set this back to "Needs Information from User" since we are waiting for the card to be replaced (or the drivers test). But everyone reading this: please dont close this for inactivity (even if it takes longer than the usual week for @MasterJames to reply).

Master James commented

2019-08-30 07:27:10 +02:00

I did have the driver from before and did a clean install of it to see as that was fine as far as I could tell a couple of months ago. Alas no difference and had put back the newest one after checking the previous driver. I can't check the other version number in this moment, but it was something like that.
The guy at the shop said it takes 6 to 8 weeks maybe more so I am screwed for 2 months and he said it doesn't mean the card that comes back will be without issues.
Still they will do an in house testing first so if I dont hear from them, then they also had issues, and that he gave no timeline but I would think I would hear from them within a week if it checked out on a different inhouse system (otherwise they will send it back on warranty). I guess I could have similarly tried it here in different hardware, but I am uncertain it would have even fit my old system (biggest card I have ever seen power consumption requirements etc.).

I did have the driver from before and did a clean install of it to see as that was fine as far as I could tell a couple of months ago. Alas no difference and had put back the newest one after checking the previous driver. I can't check the other version number in this moment, but it was something like that. The guy at the shop said it takes 6 to 8 weeks maybe more so I am screwed for 2 months and he said it doesn't mean the card that comes back will be without issues. Still they will do an in house testing first so if I dont hear from them, then they also had issues, and that he gave no timeline but I would think I would hear from them within a week if it checked out on a different inhouse system (otherwise they will send it back on warranty). I guess I could have similarly tried it here in different hardware, but I am uncertain it would have even fit my old system (biggest card I have ever seen power consumption requirements etc.).

Master James commented

2019-09-18 10:00:08 +02:00

Changed status from 'Open' to: 'Archived'

Master James closed this issue

2019-09-18 10:00:08 +02:00

Master James self-assigned this 2019-09-18 10:00:08 +02:00

Master James commented

2019-09-18 10:00:09 +02:00

Seem it was a hardware problem.

I guess the idea of being able to detect a jamming card and notify the user of intermittent hardware functionality is a worthy endeavor from my perspective.

Seem it was a hardware problem. I guess the idea of being able to detect a jamming card and notify the user of intermittent hardware functionality is a worthy endeavor from my perspective.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

GPU Glitches, Freezing, crashes, speckles, ghosts, etc. #69208