I'm getting the following application error when I shut down my computer. Hopefully someone can tell me what it means, if I need to be worried and how to fix this.
 
DDE Server Window: explorer.exe - Application Error
The instruction at 0x00007FF62E4D8732 referenced memory at
0x0000000000000030. The memory could not be written.
Click OK to terminate the program.

Ugh.
Usually DDE errors indicate a corruption problem either with an app or with Windows itself.
 
First try

• Open an elevated command prompt and run:
  SFC /SCANNOW

 hopefully that will fix the issue.
 
If not, check to see if one of the apps that loads after startup is causing the issue.
You can use MSConfig to temporarily turn off all the extras stuff that load with Windows.

• run MSConfig (just hit start button and type in)
• check "Diagnostic startup" under the General tab
• Click OK and reboot 
• and then check to see if you still have same issue next time you shut down

If issue has gone any you need to figure which of your startup apps is causing the issue.
If issue hasn't gone away you will probably need to reinstall Windows.
 
 
DDE is one way that can be used to have apps communicate. You could easily break it through overuse and the only fix was rebooting.
It was dated before XP was new and most development apps, if they support it, only do so for legacy purposes. 
From Wikipedia: 
Dynamic Data Exchange was first introduced in 1987 with the release of Windows 2.0 as a method of interprocess communication so that one program could communicate with or control another program, somewhat like Sun's RPC (Remote Procedure Call).[1] It used the "Windows Messaging Layer" functionality within Windows. DDE continues to work even in modern versions of Windows, but has been superseded by newer technologies.

If it's not a corrupted or misconfigured application causing the problem the only fix that I know of is a complete reinstall of Windows. If the error only occurs when you shut down Windows it might be something that you just tolerate until you have to do a reimage. I.E. ignore it till you can't.  Keep you backups current!
 
Good luck.
If you do find a fix let us know!

I'm not at my DAW computer right now but after searching for this issue on line, it appears that this is a known issue which is caused by having the Automatically hide the taskbar in desktop mode switched on in the taskbar settings. Users are stating that once this is turned off, the problem goes away. This issue seemed to have started with the Windows 10 anniversary update.
 
I'll try this when I get home and will report back!

Keeping my fingers crossed for you.

Hey The Steven, it worked!  Now that is some weird bug, huh? And based on the Microsoft thread, it's been around since 2015. You'd think Microsoft would have fixed this by now. I guess it's more complex than it appears. Now, I just have to get used to seeing my taskbar visible all the time!
 
Thanks again for your reply and support. It's members like you that make this forum such a special place!

That is an odd one.
Windows 10 was released in July 2015 so it sounds like it may have been there either from the start or early on.
Glad you got it figured out.