Windows is crashing constantly when using Houdini

Hi RakeshMalik.

Thanks for your reply.

The previous steps ruled out the video card driver and DirectX errors.

We would like to know if there were any issues or blue screen of death during the stress test?

At one point we checked the dump file you provided.

We found errors in dwm.exe.

The dwm.exe is responsible for rendering the Windows desktop effects.

Are you using any third-party software that manages or modifies the desktop (e.g. software that modifies the wallpaper)?

If so, please uninstall or disable such software for the time being.

To eliminate conflicts from other third-party software, I recommend trying a clean boot which starts Windows with a minimal set of drivers and startup programs. It can be used to determine It can be used to determine whether a background service or program is interfering or causing a problem.

These steps of “clean boot” might look complicated at first glance. However, to avoid any trouble for you, please follow them in order and step-by-step.

In a clean boot, just start Houdini and see if you still get the blue screen of death.

We also performed further analysis for the dump file you provided.

We found some errors below.

magdrvamd64.sys.

This is part of the driver for Samsung Magician software, if you are currently using Samsung Magician software, please disable or uninstall it temporarily.

WUDFRd.sys, USBXHCI.sys and ucx01000.sys.

These are related to external USB devices, please keep only the most basic USB devices such as mouse and keyboard and remove all other unnecessary external devices to rule out interference in this area when using Houdini.

Please see if these can alleviate your problem and if the blue screen of death problem occurs again, you can continue to provide me with new dump files.

It's my honor to provide you with some suggestions, and I hope my efforts can bring you some convenience.

Thank you for your understanding and support.

Best regards,

Zev - MSFT | Microsoft Community Support Specialist

None of that worked. I've been keeping the drivers up to date using vendor specific tools, and it hasn't helped. Reinstalling DirectX made no difference. I finally reset windows and started over, and the only change is that I got a blue screen instead of a black screen. Clearly, Microsoft has royally screwed something up somewhere.

And the crashdump after reinstalling STILL shows an error related to the DirectX Graphics kernel.

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true
   EnableRedirectToChakraJsProvider : false

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.297 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 43

Microsoft (R) Windows Debugger Version 10.0.27793.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [E:\tmp\dump\040125-18234-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 26100 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff800`adc00000 PsLoadedModuleList = 0xfffff800`aeaf4920
Debug session time: Tue Apr  1 00:46:11.181 2025 (UTC - 7:00)
System Uptime: 0 days 3:55:13.186
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.............................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000002`65205018).  Type ".hh dbgerr001" for details
Loading unloaded module list
........................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`ae0b54f0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffec82`538dd800=000000000000003b
6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000047, Exception code that caused the BugCheck
Arg2: fffff800ade44fcf, Address of the instruction which caused the BugCheck
Arg3: ffffec82538de1d0, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1250

    Key  : Analysis.Elapsed.mSec
    Value: 9149

    Key  : Analysis.IO.Other.Mb
    Value: 5

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 33

    Key  : Analysis.Init.CPU.mSec
    Value: 625

    Key  : Analysis.Init.Elapsed.mSec
    Value: 8932

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27793.1000

    Key  : Analysis.Version.Description
    Value: 10.2410.02.02 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2410.2.2

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x3b

    Key  : Bugcheck.Code.TargetModel
    Value: 0x3b

    Key  : Dump.Attributes.AsUlong
    Value: 0x21808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x3B_C0000047_dxgkrnl!DxgkGetPresentHistoryInternal

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff800ade44fcf

    Key  : Failure.Exception.IP.Module
    Value: nt

    Key  : Failure.Exception.IP.Offset
    Value: 0x244fcf

    Key  : Failure.Hash
    Value: {bd161d58-4d5a-f322-b36e-6b23e4cd4960}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7497cf94

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 1

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 38670575

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x24e10ef

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0x3f7

BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000047

BUGCHECK_P2: fffff800ade44fcf

BUGCHECK_P3: ffffec82538de1d0

BUGCHECK_P4: 0

FILE_IN_CAB:  040125-18234-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b

DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffa802db36d0c0

CONTEXT:  ffffec82538de1d0 -- (.cxr 0xffffec82538de1d0)
rax=0000000000000000 rbx=00000000c0000001 rcx=ffffa8031be3182e
rdx=ffffec82538de610 rsi=0000000000000001 rdi=00000000000007ff
rip=fffff800ade44fcf rsp=ffffec82538de110 rbp=ffff8080aa565180
 r8=ffffa802e475f000  r9=ffffec82538de448 r10=0000000000000000
r11=ffffa8031be31810 r12=0000000000000000 r13=0000000000000000
r14=0000000000000001 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00040282
nt!RtlRaiseStatus+0x4f:
fffff800`ade44fcf 80c3ff          add     bl,0FFh
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  dwm.exe

STACK_TEXT:  
ffffec82`538de110 fffff800`adf6095f     : ffffa802`e6134000 fffff800`3fba7695 ffffa802`e6134000 ffffa802`e6134000 : nt!RtlRaiseStatus+0x4f
ffffec82`538de6b0 fffff800`3fdeecf5     : ffff970a`d6716a00 ffff970a`d6716a00 ffffec82`538dea10 ffffa802`e5551040 : nt!KeReleaseSemaphore+0x18f
ffffec82`538de710 fffff800`3fb947a7     : 00000000`00000000 00000000`00000000 ffff970a`d7c89010 ffff970a`d0feb880 : dxgkrnl!DxgkGetPresentHistoryInternal+0x695
ffffec82`538de910 fffff800`3fb94621     : ffff970a`d466faf0 00000000`00000000 ffff970a`d466faf0 00000000`00000000 : dxgkrnl!CTokenManager::ProcessDxgkAdapterTokens+0xd7
ffffec82`538df230 fffff800`3fbc2e69     : 00000000`00000000 ffffa802`e4c78fe0 ffff970a`d0feb880 ffffec82`538df3c0 : dxgkrnl!CTokenManager::ProcessTokens+0x201
ffffec82`538df2f0 fffff800`3fb9a2af     : 00000000`00000000 ffffec82`538df4e0 00000000`00000000 fffff800`ae4618e7 : dxgkrnl!CTokenManager::TokenThread+0xb9
ffffec82`538df340 fffff800`ae28ee58     : ffffa802`db36d0c0 00000167`90153ec8 00000000`00000020 00000000`00000000 : dxgkrnl!NtTokenManagerThread+0x14f
ffffec82`538df460 00007ffc`22658674     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000002`656ff9b8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`22658674

SYMBOL_NAME:  dxgkrnl!DxgkGetPresentHistoryInternal+695

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

IMAGE_VERSION:  10.0.26100.3624

STACK_COMMAND:  .cxr 0xffffec82538de1d0 ; kb

BUCKET_ID_FUNC_OFFSET:  695

FAILURE_BUCKET_ID:  0x3B_C0000047_dxgkrnl!DxgkGetPresentHistoryInternal

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {bd161d58-4d5a-f322-b36e-6b23e4cd4960}

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

Hi RakeshMalik,

Thanks for reporting this issue in Microsoft Community.

In your description, you are experiencing a blue screen of death while using Houdini.

I noticed that you were patient enough to analyze the dump file for us and provided a link to download the file. I do understand the distress and chagrin that the blue screen of death while running Houdini is currently causing you.

We downloaded and analyzed your dump file through the link you provided and the results were the same as you mentioned. The problem points to dxgkrnl.sys.

dxgkrnl.sys is part of the DirectX graphics kernel driver, which is primarily responsible for graphics processing and display output.

We can re-download and install DirectX using the link below.

Download DirectX End-User Runtime Web Installer from Official Microsoft Download Center

How to install the latest version of DirectX - Microsoft Support

If the problem still persists, we need to check the drivers for the graphics card.

You can refer to the link below to cleanly uninstall the current graphics card driver using the DDU tool.

https://www.intel.com/content/www/us/en/support/articles/000091878/graphics.html

Disclaimer: This is a non-Microsoft website. The page appears to be providing accurate and safe information. Watch out for ads on the site that may advertise products frequently classified as PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

Then download and install the drivers for your graphics card from the manufacturer's website, depending on the model number of your graphics card.

This will rule out errors from the graphics card driver. Check if the same problem occurs after this.

Errors occurring in the hardware can also lead to Blue Screen of Death (BSOD) on the system.

Hence, we need to check the hardware (graphics card) as well.

You can use a third-party tool or software that you trust to monitor the temperature of your computer's hardware (CPU and GPU) to determine if the blue screen of death is caused by overheating.

You can also use other tools to stress test the GPU to see if a blue screen of death or some other error occurs during the stress test.

The above methods are not the final solution, they are more like a check on this issue for you, please let us know the results after you try them out, they will help to narrow down the cause of the problem, and we will determine the problem for you based on your results and provide further assistance.

If the blue screen of death still occurs, you can continue to provide me with the dump file and I will continue to help you.

It's an honor to provide you with some advice, and I hope my efforts will make things a little easier for you.

Thank you for your understanding and support.

Best regards,

Zev - MSFT | Microsoft Community Support Specialist