I'm Freezing (or my Daz is)
chris_340dad5b
Posts: 52
I am running Daz 4.21 Pro on a Dell XPS 8940 with 64 gigs of ram and NVIDIA RTX 2060. All drivers are updated and it has worked fine for a year now.
Suddenly, a few days ago, Daz (and only Daz, no other program) began having sort of mini-strokes where it would freeze for a few seconds at random times and now it has progressed to the point where it totally freezes and goes to a glazed wite screen. I can't reopen it and I can't even kill it. Even Task Manager cannot close it. It responds to nothing.
Can I re-install Daz and will that help? What will happen to all my data and folders if I can't get Daz to do a backup of my settings?
Comments
I checked my LOG files finally and I see this WARNIG popping up all through the log:
2023-04-03 14:03:47.908 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - PLUG:PLUGIN :: 0.0 PLUG plug error: Library C:\Program Files\DAZ 3D\DAZStudio4\libs\iray\libnvindex_application_layer_application_layer.dll: symbol "mi_plugin_factory" not found.
What Viewport Drawstyle are you using?
It freezes on everything. including texture shaded and NVIDIA Iray. It freezes while I am looking at the content library or working on a project. It freezes with that darn red hourglass and then the screen goes frosty white and I cannot turn it off, even with Task Manager. I have to restart the computer. This is the recent listings in my LOGFILE:
2023-04-03 16:41:43.454 [VERBOSE] :: Total class factories: 2172
2023-04-03 16:41:43.458 [INFO] :: Creating Script Engine...
2023-04-03 16:41:43.549 [WARNING] :: 3DConnexion Plug-in Error: Could not create Device, CoCreateInstance failed
2023-04-03 16:41:43.549 [INFO] :: 3D mouse support library could not be loaded.
2023-04-03 16:41:43.560 [INFO] :: Creating Main Window...
2023-04-03 16:41:43.570 [INFO] :: Creating Viewport Manager...
2023-04-03 16:41:43.641 [INFO] :: Successfully created OpenGL viewport for Viewport1.
2023-04-03 16:41:43.729 [INFO] :: Successfully created OpenGL viewport for Viewport2.
2023-04-03 16:41:43.776 [INFO] :: Successfully created OpenGL viewport for Viewport3.
2023-04-03 16:41:43.820 [INFO] :: Successfully created OpenGL viewport for Viewport4.
2023-04-03 16:41:44.045 [INFO] :: Creating Action Manager...
2023-04-03 16:41:44.173 [INFO] :: Creating Pane Manager...
2023-04-03 16:41:44.872 [INFO] :: Successfully created OpenGL viewport for AuxViewportView.
2023-04-03 16:42:03.681 [WARNING] :: QFile::flush: No file engine. Is IODevice open?
2023-04-03 16:42:03.830 [INFO] :: RenderQueue: we_restarted_DS: FALSE
2023-04-03 16:42:03.830 [INFO] :: Loading Actions: C:/Users/plotg/AppData/Roaming/DAZ 3D/Studio4/actions.dsx
2023-04-03 16:42:03.861 [INFO] :: Loading Custom Actions: C:/Users/plotg/AppData/Roaming/DAZ 3D/Studio4/customactions.dsx
2023-04-03 16:42:04.144 [INFO] :: Loading Menus: C:/Users/plotg/AppData/Roaming/DAZ 3D/Studio4/menus.dsx
2023-04-03 16:42:04.206 [INFO] :: Loading ToolBars: C:/Users/plotg/AppData/Roaming/DAZ 3D/Studio4/toolbars.dsx
2023-04-03 16:42:04.289 [INFO] :: Executing startup script...
2023-04-03 16:42:04.413 [INFO] :: Started in: C:/Program Files/DAZ 3D/DAZStudio4
2023-04-03 16:42:04.413 [INFO] :: DAZ Studio started
2023-04-03 16:42:04.413 [INFO] :: Creating Pixel Buffer
2023-04-03 16:42:04.434 [INFO] :: Pixel buffer - Width: 1024 Height: 1024
2023-04-03 16:42:04.437 [INFO] :: Compiling OpenGL Shader...
2023-04-03 16:42:04.441 [INFO] :: Fragment Shader:
Fragment Shader compiled successfully.
Linking Shader:
Shader Program successfully linked.
2023-04-03 16:42:04.442 [INFO] :: Loading Layout: C:/Users/plotg/AppData/Roaming/DAZ 3D/Studio4/layout.dsx
Is Task Manager otherwise working normally or is this a full system freeze? Have you tried a clean driver install?
It is only DAZ that I am having problems with. I would reinstall daz but I am worried I will lose all my groups and installations.
Reinstalling will not affect user settings, but I doubt it will help either. It's possible that some setting has changed (Edit>Preferences>Interface tab would be the place to start), or that a silent driver update is the issue (it may be worth trying to roll back to a slightly older version if you have the latest). Of course it could also be a hardware issue that only DS is triggering.