Author Topic: Windows BSOD When Enabling iRay renderer  (Read 1059 times)

Hello!
We are having random crashes when we enable the iRay renderer. It usually works fine, but we are having instances of BSOD. This occurs randomly, but always immediately after we enable the iRay renderer. Memory dumps generated by Windows 10 show a problem in nvlddmkm.sys.

The computer has the following configuration:
- Substance Painter, version 6.1.0
  Build 6 - 344bc18f5072377822f03825ce298276c8ee1733
- Nvidia driver version is 442.92.

- MSI 570A-PRO
- AMD 3700x
- GIGABYTE 2070 RTX
- 32GB RAM



Here is the dump:

Code: [Select]
Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Can't set dump file contexts
MachineInfo::SetContext failed - Thread: 0000028EDCFC8670  Handle: 1  Id: 1 - Error == 0x8000FFFF

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff800`6d000000 PsLoadedModuleList = 0xfffff800`6d448170
Debug session time: Wed Jun 10 20:22:35.293 2020 (UTC + 2:00)
System Uptime: 1 days 1:55:26.953
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols

Loading unloaded module list
.............
nt!KeBugCheckEx:
fffff800`6d1c2390 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff800`72075b10=0000000000000133
||1:0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff8006d573358, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000

Debugging Details:
------------------

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 3

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-5VHFVEN

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 13

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 80

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8006d573358

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

STACK_TEXT: 
fffff800`72075b08 fffff800`6d23d8b1 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`6d573358 : nt!KeBugCheckEx
fffff800`72075b10 fffff800`6d0b90a7 : 00008937`31a22569 fffff800`6a326180 00000000`00000286 fffff800`72067140 : nt!KeAccumulateTicks+0x181641
fffff800`72075b70 fffff800`6cf5f291 : 00000000`00000000 fffff800`6cfcc000 fffff800`720671c0 fffff800`6cfcc0b0 : nt!KeClockInterruptNotify+0xc07
fffff800`72075f30 fffff800`6d02cc75 : fffff800`6cfcc000 00000000`00000000 00000000`00000000 ffff31f1`e9f13853 : hal!HalpTimerClockIpiRoutine+0x21
fffff800`72075f60 fffff800`6d1c3e1a : fffff800`720671c0 fffff800`6cfcc000 00000000`00000001 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff800`72075fb0 fffff800`6d1c4387 : 00000000`00000050 00000000`00830050 fffff800`720672a0 fffff800`7df16d8c : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff800`72067140 fffff800`7df00465 : fffff800`7df19daf ffff9d09`b9fdd000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff800`720672d8 fffff800`7df19daf : ffff9d09`b9fdd000 00000000`00000000 00000000`00000000 00000000`badf1002 : nvlddmkm+0x110465
fffff800`720672e0 fffff800`7df19ca8 : ffff9d09`00000000 ffff9d09`b9fdd000 00000000`00000000 00000000`00830008 : nvlddmkm+0x129daf
fffff800`72067350 fffff800`7e11e7d5 : 00000000`00000000 00000000`00000000 ffff9d09`b9fdd000 00000000`00000000 : nvlddmkm+0x129ca8
fffff800`72067390 fffff800`7e12765c : ffff9d09`b8eee988 ffff9d09`b9fdd000 ffff9d09`b9ee5110 ffff9d09`b9ee57d0 : nvlddmkm+0x32e7d5
fffff800`720673d0 fffff800`7e11ec88 : ffff9d09`b9ee57d0 fffff800`720674f0 ffff9d09`b9ee57d0 ffff9d09`b9fdd000 : nvlddmkm+0x33765c
fffff800`72067430 fffff800`7e10be7f : ffff9d09`b8eee830 ffff9d09`b9ee5110 ffff9d09`b9ee5110 fffff800`7e0d0589 : nvlddmkm+0x32ec88
fffff800`72067460 fffff800`7e07f36b : 00000000`00000000 fffff800`720674f0 ffff9d09`b8eee830 ffff9d09`b9fdd000 : nvlddmkm+0x31be7f
fffff800`720674c0 fffff800`7e08498c : ffff9d09`b9fd4010 ffff9d09`b0c8c010 ffff9d09`b1642280 fffff800`7df19dd2 : nvlddmkm+0x28f36b
fffff800`72067530 fffff800`7e07eb2e : ffff9d09`b9fdd000 00000000`00000031 00000000`00000020 ffff9d09`b1887050 : nvlddmkm+0x29498c
fffff800`72067570 fffff800`7e07ed3b : ffff9d09`b8346c10 ffff9d09`00000025 ffff9d09`b9fdd000 ffff9d09`b80ca420 : nvlddmkm+0x28eb2e
fffff800`720675c0 fffff800`7e07fa22 : ffff9d09`b9fde298 00000000`00000000 00000000`00000000 fffff800`7df19ed4 : nvlddmkm+0x28ed3b
fffff800`72067640 fffff800`7e2bc10c : 000054e1`5ef52960 000054e1`5ef52960 ffff9d09`b9fdd000 ffff9d09`b1887050 : nvlddmkm+0x28fa22
fffff800`720676a0 fffff800`7df00616 : ffff9d09`b9fdd000 ffff9d09`b1887050 00000000`00000002 00000000`00000000 : nvlddmkm+0x4cc10c
fffff800`720676d0 fffff800`6d0c115a : fffff800`6a328f80 ffff9d09`a77ec000 ffff9d09`ba1f9970 fffff800`6a326180 : nvlddmkm+0x110616
fffff800`720678f0 fffff800`6d0c07af : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x30a
fffff800`72067a30 fffff800`6d1c5ebe : 00000000`00000000 fffff800`6a326180 fffff800`6d591400 ffff9d09`bba460c0 : nt!KiRetireDpcList+0x1ef
fffff800`72067c60 00000000`00000000 : fffff800`72068000 fffff800`72062000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x7e


SYMBOL_NAME:  nvlddmkm+110465

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  110465

FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f97493a5-ea2b-23ca-a808-8602773c2a86}

Followup:     MachineOwner
---------


Have you updated the Nvidia driver. It looks like you have an older version.

Hi!

It is actually the Nvidia Studio Driver - and that is the last version available for it at this time.

Thanks.

Have you tried the Geforce driver?

Hi!

Not yet - 24 hours without crashes, I will see how it goes... I cannot find a pattern for this; maybe it occurs when I am dealing with transparencies and I enable the IRay renderer, but I am not sure yet.

I will update this thread if something comes out.

Thanks for the help!