Windows 10: The Desktop Window Manager process has exited. Process exit code: 0xe0464645, Restart...

crash debug here https://drive.google.com/file/d/1a6TbMJqdGvcsM2kTBKnt5sSFVC8RzkHk/view?usp=sharing one crash debug two https://drive.google.com/file/d/1oA0-Ijq5vt-hz--_tjDLxfG7Kq-iSncY/view?usp=drive_link

:)

 

Computer will randomly crash without a BSOD or Error and stays powered

Did that stuff with DDU step by step and had another crash just now while playing a game.

Saw a return of previous errors in the Event Manager.

• 1 instance of Critical: "Kernel-Power"
  
• 2 instances of Error: "Application Error", "Faulting application name: dwm.exe"
  
• 1 instance of Error: "EventLog"
  
• 1 instance of Warning: "Dwminit", "The Desktop Window Manager process has exited. (Process exit code: 0xe0464645, Restart count: 1, Primary display device ID: NVIDIA GeForce RTX 3080)"
  

 

Desktop Window Manager process has exited cause a beep?

I had this event several times (very rare only few times a year I suppose) where my laptop makes a beep sound similar to dialing sound in those old landline phones.

It is quite unique sound and I am quite sure it is not hardware disconnect sound or sticky keys activation sound(disabled sticky keys a while back).

It happened just few minutes ago. So I decided to investigate.

The quick beep happened just after my main screen temporary went black (windows and taskbar disappeared, mouse still present but lag a lot, move very slow, secondary monitor was still playing Video on VLC without any abnormalities.

The event lasted few seconds up to half a minute before my main screen returned to what it was displaying.

I decide to investigate and checked the Event Viewer where I found at about same timeframe there was a error and warning.

0:03:07

Error:

Faulting application name: dwm.exe, version: 10.0.16299.15, time stamp: 0x7f22d77c

Faulting module name: CoreMessaging.dll, version: 10.0.16299.192, time stamp: 0x11d927fa

Exception code: 0xc0000602

Fault offset: 0x000000000006ac52

Faulting process id: 0x4ec

Faulting application start time: 0x01d38e510bff2b4d

Faulting application path: C:\WINDOWS\system32\dwm.exe

Faulting module path: C:\WINDOWS\system32\CoreMessaging.dll

Report Id: 6853937b-4a79-49ed-b851-62685fddd6b6

Faulting package full name:

Faulting package-relative application ID:

0:03:23

The Desktop Window Manager process has exited. (Process exit code: 0xc0000602, Restart count: 1, Primary display device ID: Intel(R) HD Graphics 4000)

0:03:23

The Desktop Window Manager has registered the session port.

A minute later at 00:04:34 and 00:04:35

Two Windows error Reporting entry related to dwm.exe were also present.

So, I assume the Desktop Window Manager (dwm.exe) Crash was the cause of the beep?

I think the crash might have something to do with my laptop is an old Dell 7720 running on a i7-3610QM, it wasn't designed to run Windows 10 (it shipped with Win 7)

 

Is there a way to continue giving input after terminating process with Ctrl + C and getting exit code?

I'm using Powershell from Windows Terminal. When I run some CMD process (such as serving file on local server) and quiet with Ctrl + C, It outputs Process exited with code ****** and stops taking input after that. So I have to open new terminal tab, CD into
working directory and cont. every time. Is there a way to continue giving input after terminating process with Ctrl + C and getting exit code?