[German]I'm going to combine some problem reports in the Windows Server environment into one collective post. A blog reader informed me yesterday that Microsoft OneDrive was crashing under Windows Server 2016. And I got a report about OneDrive issues during the weekend. I also saw a report on the patchmanagement.org mailing list about a boot loop on Windows Server 2019 in connection with the April 2025 security updates. The question is whether there are more people affected.
Advertising
OneDrive crashes
German blog reader Robert contacted me by email on April 27, 2025 because he was facing OneDrive issues within his environment. He runs a Windows Server 2016 with all patches and accesses this machine via RDP. He has now noticed that the OneDrive client is crashing on this machine. Specifically, it looks like the client is crashing with the error code 0xc0000374. This error code stands for a corruption in the heap (STATUS_HEAP_CORRUPTION).
Crash in ntdll.dll reported
The error occurs repeatedly under Windows in connection with faulty software (duplicate memory sharing in the heap or similar). The problem is that the error message usually refers to a library file ntdll.dll called up by an application (such as OneDrive in the above case). This is therefore not very informative.
Analyzing the Event Viewer will therefore usually not help (see also the following explanations). Microsoft has this article which contains some tips.
- One recommendation is to check for updates (of the software) and also to ensure that the .NET Framework versions are up to date.
- The recommendation to look through the event log will usually (in my opinion) not provide any major insight.
At the end of the day, all that remains for developers or experienced administrators is to analyze the crash dump using a debugger in the hope of finding the cause.
The situation on the affected system
Robert is not yet in a position to evaluate a crash dump using a debugger. He wrote about the error: "Maybe it will go away, but several attempts led to this message in the event log":
Advertising
"Name of the faulty application: OneDrive.exe, version: 25.60.330.3, timestamp: 0xcf4872a9
Name of the faulty module: ntdll.dll, version: 10.0.14393.7426, timestamp: 0x66f6017b
Exception code: 0xc0000374
Error offset: 0x000d8ee1
ID of the faulty process: 0x95b8
Start time of the faulty application: 0x01dbb752801ba6ad
Path of the faulty application: C:\Program Files (x86)\Microsoft OneDrive\OneDrive.exe
Path of the faulty module: C:\Windows\SYSTEM32\ntdll.dll
Berichtskennung: d3da4a58-69fd-4d0b-a07e-eb4a3ae05ab7
Full name of the faulty package:
Application ID that is relative to the bad package:"
Event ID: 1000
It must be related to the machine (Windows Server 2016 with all patches and RDP). The same version of the OneDrive client is installed and working on his Windows 10 22H2. In any case, nothing can be done with the above message. Question: Has anyone else in the readership experienced this OneDrive crash?
Addendum: Robert commented now, that the issues has been gone – it was probably related to the issue reported below.
OneDrive issues on April 26, 2025?
Just read at German site Dr. Windows the article OneDrive Störung? Alle Ordner weg und dann wieder da, dated April 26, 2025. Martin Geuß received on this date (3:44 a.m. CET) a message, that all his OneDrive folders has been gone. The email told him "Many files were recently deleted from your OneDrive".
However, the OneDrive client immediately started processing alleged changes. The counter rose to over 136,000 files deleted, which is pretty much the total number of files in Martin's OneDrive. But one hour later, the counter dropped slowly, and now, all files are back, without changing something from the user's side. Other users confirm errors in OneDrive during the last few days. However, this may have been something other than the case above.
Reboot loop with Windows Server 2019
On patchmanagement.org there is this entry from April 16, 2025, where someone got into a reboot loop after the April 2025 updates with Windows Server 2019. According to the administrator, he was able to solve this within 20 hours with numerous MS support sessions (without revealing the cause).
Another system administrator suggested disconnecting the network interface card (NIC) when this happens. That worked for him. Has anyone else experienced a reboot loop like this after the April 2025 patchday?
Advertising
