Submitting crash.log titled: (just submitted and it was numbered 436)
Saturday, January 25, 2025 4:36:51 PM - 27426 KB.
Windows 11 Pro (new install, fully updated), DO 13.12.4 (Beta) x64 (Build 9151)
Just upgraded old 11 year old Windows 10 PC for update to Windows 11. Was transferring about 183GB of folders & files to the new PC from a FreeNAS box. t was a bit over half way through the copy. Had already copied a couple of TB of data between old PC/NAS and new PC without any problems, this is the first crash. Popup said something about ADVAPI32.dll being the problem or something like that, sorry I didn't copy the exact message.
My first attempt at submitting a crash.log, hope this helps. I have used DO for many years and really have not experienced many (if any) problems at all, it just works, great program! So I'm not sure if it's Win 11, my new PC or Do that caused the crash. I've done many things similar to this (and lots of synchronizing) over the years on Win 7 & 10 with old PC and never had a problem. Thanks for a great program!
The crash dump shows something "impossible" happened, where Opus asked Windows to release a region (and object used to mask out areas when drawing on the screen) and Windows instead called an API involved with looking up user details.
This is probably an error outside of Opus, either with something else incorrectly hooking APIs within Opus and other processes, or some kind of memory/hardware error (e.g. could happen due to overclocking the CPU or memory too much, or the random failures recent Intel CPU generations have started showing).
Could it have been caused by something else I was doing at the time, which I was doing? However, got completely side tracked by the error and had to restart to get things going again. After that I don't remember exactly what else I was doing at the time? It's been fine since, with the exception of a few copy errors that were easily resolved with a retry. I don't recall having many of those before either but really have never before moved this much stuff around either?
This PC does have one of the newer Intel CPUs that has (or had) the (supposedly now resolved) problems? Bios was updated to latest version at startup which was also said to improve the settings for these CPUs. Nothing is (or will be) overclocked, just going with the basic default settings. I'll pay closer attention to it going forward.
Your reply got me thinking about my whole new setup so I did some further checking and there were a couple of BIOS settings I had changed, per recommendations. Maybe this will also help someone else?
I think the culprit was setting memory to XMPI, supposedly the recommended setting to match the memory I have. A couple of other things were set to 'Auto' thinking the BIOS knew better than I did, but apparently not? I reset everything to 'Factory Optimized Defaults' and all has been well since with no more copy errors either. The intent was not to overclock, but to set everything up to match the new motherboard to it's hardware. So much for that...
Thanks for pointing me in the right direction with the crash report.
