Hi! i already answered those questions in the previous topic i opened before you merge it here. About point 7, which hadn’t been mentioned before: in the file I was talking about, which is very big, yes, I’m probably exceeding 80%. I have an RTX 5080 with 16 GB. That said, I’ve always exceeded that and have never had these kinds of problems.
On the other hand, I was just working with a very small file and it also crashes, so no, it’s not because of that. Needless to say, this didn’t happen in previous versions.
I think I may have found what is causing the crashes. As I suspected, I believe it is related to an internet connection issue.
I used D5 all day without any crashes and couldn’t understand why, until I realized that I was using it without being logged in. As soon as I logged in, it crashed again almost immediately.
If this is indeed the cause, I hope this information helps the developers fix the issue. As a recommendation for others experiencing the same problem, I suggest trying to log out and work that way to see if the crashes stop.
I know that users with the Pro version will see “Pro only” watermarks on some objects, but I think it’s still preferable to work with those watermarks rather than having the program crash unexpectedly every five minutes. If needed, you could simply log back in when it’s time to render.
Until an official fix or patch is released, this might be worth trying. Internet connections are never perfectly continuous; there are always tiny micro-interruptions lasting milliseconds, and it would make sense if that could cause crashes at random moments, which might vary depending on the day or time.
I hope this helps. It has worked for me throughout yesterday and today.
Reinstalling a lower version of D5 should not cause you to lose your library, favorites, or custom materials. However, if your project uses features available only in version 3.0, you may encounter limitations when opening it in an older version.
In such cases, a prompt window may appear notifying you that certain features are not supported in that version. Alternatively, those features may simply disappear. Additionally, assets introduced in newer versions may not display correctly in older versions and could appear as white boxes.
It’s definitely Turbo Mode on my end. I’ve been working crash free for a couple of days with it off but this morning I updated my BIOS and it turned on Turbo Mode. I thought to give it a shot but it crashed D5 within 5 minutes. Trying to tune other things like tweaking XMP settings for RAM. Won’t make that much a difference. As for the cause of what appears to be a Turbo Mode bug on my end with D5 is unknown to me at this time. Same thing happened years ago.
Turbo Mode is like an easy form of overclocking where it raises the CPU speed within limits above its rated speed. My CPU (i9 10900K) is rated at 3.7 GHz and with Turbo Mode off it stays planted below that rated speed. With it on it will rise belod 5.0 GHz depending on load. The only issue with Turbo Mode on on my machine is with D5 Render.
@gusrobatto 100% true, if you have a Intel processor or certain motherboards it’s called “Intel turbo boost” I did what you said and it’s been 2 days without crashes so far. “THANK YOU”
There appears to be quite a few bugs with version 3.0.1 - while I’ve not recently experienced silent crashes, I’ve noticed a distinct drop in D5’s ability to handle large complex models (circa 8B faces) which is no different to what I was working on when version 3.0.0 was released and previous 2.11 and earlier versions. Some key things I’ve noticed and some momentary (yet less ideal work arounds).
When syncing large linked models from Revit into the D5 workspace there is a functional limit to the size of models its able to sync before crashing, however if you export the model(s) as a .d5a file I’ve managed to load all models without crashes occurring, this is less than optimal as in version 2.11 I was able to load all the same models flawlessly.
As mentioned earlier in the thread, materials have been appearing as white after reopening the D5 project (in my specific use case Grassland 03 was one of the main offenders which still hasn’t resolved - Base colour map icon was displaying initially as a white square, recently its reverted to a duotone grey square but unfortunately as far as I’m aware there is no way to reload the missing D5 base colour map.
Stability when rendering videos at 30fps, 1080p and approx 1min in length have on occasions crashed when rendering the full video (not an image sequence) - my assessment on this may in part be due to the complexity of the scene being rendered at the time of the crash (high poly count, lots of vegetation etc) the fact still remains this is a significant downgrade from version 2.11 which was much more stable from my experience.
This has significantly impacted deadlines and output for jobs I’m working on and would hope to see a more stable hotfix published soon.
I wanted to provide an update regarding my recent experience with D5 crashes.
After extensive communication with D5 support and a review of my project files, their final assessment was that my current GPU (RTX 3060 Ti 8GB) lacks sufficient VRAM to handle the project’s complexity. They recommended upgrading to a GPU with minimum 12GB of VRAM, which currently costs approximately €1,000+.
I found this assessment unsatisfactory, especially since many users with more powerful hardware are facing the same issues.
Before committing to an upgrade, today I decided to test the “Turbo Mode-off” settings suggested by Gus (I am also using an Asus Z490M-Plus motherboard with a I9 109000@2,80GHz CPU). I am happy to report that I have worked for nearly 5 hours straight without a single crash (both actively working in D5 and leaving in stand-by).
While it may be too early to claim a permanent fix, this adjustment seems to be working for me effectively so far, so I highly recommend others facing similar issues try this setting before investing in new hardware or try anything else.
Gus, man, I’m not sure how you discovered this, but thank you—you’ve been a lifesaver!
Thanks Daniele. Something I figured out about 3 years ago with D5. Right now I’m experimenting with Turbo Mode on but I set Asus Multicore Enhancement to Disabled - Enforce All Limits. Just fired up D5 Render and I’ll see if it crashes. Looking for a workaround to keep Turbo Mode on.
Setting
ASUS Multi-Core Enhancement (MCE) to "Disabled - Enforce All Limits" forces your CPU to adhere strictly to Intel’s official power, current, and thermal guidelines. This prevents the motherboard from automatically overriding manufacturer specifications, typically resulting in lower power consumption, reduced heat output, and standard factory performance levels. It is the recommended setting if you prioritize system stability and longevity over maximum benchmark scores.
Took 10 minutes longer to render 6 scenes with Turbo Mode on with Disabled - Enforce All Limits than with Turbo mode off with MCE on Auto. I didn’t test overall performance like running Sketchup and D5 at the same time.
I’m trying it now with ASUS Multi-Core Enhancement (MCE) set to Disabled - Enforce All Limits with Turbo Mode enabled to see if I get any crashes. Since I discounted any GPU issues I installed the latest Nvidia driver for my RTX 5070.
24 hours later:
Crashed this morning after a whole 24 hours of no crashes and I put it through some ropes including opening random files and rendering.
Crashed after a rendering. Just random after closing the rendering window. Tried the same file and scene again. Another crash. Tried it a third time. Crashing stopped. Then I thought it might be from watching a Youtube video and while running the video there was no crash. GPU and GPU temperatures are nominal at the time.
These came back after creating a new scene using a section plane. I’m now fiddling with a previous version of the file and scene(s) to see what happens.
This is with Turbo Mode on with Disabled - Enforce All Limits.
Went back several times. Totally random. No crash at the moment.
You can bipass the Turbo Mode BIOS setting in Windows through Power Plan with " Maximum processor state to 99%."
Lately the support team has suggested me to turn off the Turbo Mode and switch back to the previous GPU drivers (not the latest version).
As I alredy explained to the support, disabling this mode negatively impacts my computer’s overall performance and slows down other essential software in my workflow, so it’s not the best solution in my case.
I also recently updated from Windows10 to Windows11, but crashes still happens.
@gusrobatto "You can bipass the Turbo Mode BIOS setting in Windows through Power Plan with "Maximum processor state** to 99%: does this manage to improve the system performance rather than turning the turbo mode completely off?
daniele I wasn’t able to gauge or bench mark a change with Turbo Mode off. There should be since turning it off limits the CPU to its rated base speed. Turbo Mode allows it to go above that. It’s sort of an easy and safe overclocking of sorts.
I’ve been running it with Turbo Mode on with Asus Multicore Enhancement to Disabled. It was running fine but then I got a series of crashes. I basically did nothing other than delete my Nvidia caches and restarted and they stopped. Turbo Mode off remains more stable.
Yes, turning down the CPU to 99% will disable Turbo Mode within Windows. You can then toggle back and forth depending on your tasks. This is easier than having to go into BIOS to change it.
D5 has a “Turbo Mode bug” and I hope they work on fixing it. Perhaps not affecting all users but enough that it should be addressed.
If you’re experiencing crashes, could you please check which CPU model you’re using first? Some specific CPU models may be related to this issue. You can check more details here: Does the CPU have a big impact on D5? | User Manual
If the issue still persists, please try the following:
Attempt 1: Turn off Turbo Mode in your BIOS. Attempt 2: Update your graphics driver to version 591.59, or try rolling it back to version 566.36. You can download the drivers here: Download The Latest Official NVIDIA Drivers
If none of these work, please let me know so we can investigate further. Thank you for your patience.
I tried the following drivers:
552.44
591.74
581.57
560.94 (current)
I’ve noticed that this often happens when I zoom in on a detail (for example, when tweaking a texture) and then zoom out using the mouse wheel; the program freezes and crashes without displaying an error message.
In the BIOS of my motherboard (MSI Z97-G43), the option to disable Turbo Boost isn’t enabled, but it seems I’ve effectively disabled it via the MSI Intel Extreme Tuning Utility.
It didn’t help; the program still crashes.
The program crashes on my second computer as well (i5-14400F, 64GB, RTX 4070 12GB, Win10).
Since the release of versions 3.0/3.01, working in D5 Render has become completely unusable.
True Displacement is highly performance-intensive, and Remesh does not work properly.
Reloading edited SketchUp models (directly from the file) into a project often results in errors in the model (scattered gray parts of the model).
D5 Render is becoming completely unusable for serious professional work.
Features have taken precedence over stability, but without stability, features are useless to us.
D5 Team, wake up please.
Suggestion: Is it possible to use mini/full dump files to diagnose problems or crashes?
I’ve tried both Attempt 1 and Attempt 2, but the issues are still persisting. This is becoming quite frustrating, especially as it’s affecting my deadlines—I’m currently unable to confidently commit timelines to my clients.
Given that we are using the Pro paid version, it’s disappointing that these issues remain unresolved across recent updates. Software stability should ideally be addressed at the developer level, rather than requiring repeated system-side adjustments.
Could you please advise on a reliable resolution or escalate this further from your end?
Thank you for the update. Could you please collect and share your most recent log files with us after trying the workaround? This will help our team investigate the issue more thoroughly. We’re really sorry for the inconvenience, and we’re actively working to troubleshoot this.
You may send the files to support@d5techs.com, and please tag me in the email as well. Also, include the link to this forum post for reference so our team can track your case more easily. Thank you for your cooperation and patience.
