Windows 10: Desktop Window Manager Stopped working. crash code c0000005

Hi! my name is Vikas and ive been having trouble with my PC for a few days.When id play minecraft after a good 15 minutes the screen would loose video and my fans would go 100% and i went to view all problem reports and had a hilarious 155 Desktop Window Manager crashes but only recently had i gotten the black screen problem.

Heres what reliability history has to reported:



Description

Faulting Application Path: C:\Windows\System32\dwm.exe



Problem signature

Problem Event Name: APPCRASH

Application Name: dwm.exe

Application Version: 10.0.19041.508

Application Timestamp: cd97c98b

Fault Module Name: KERNELBASE.dll

Fault Module Version: 10.0.19041.662

Fault Module Timestamp: ec58f015

Exception Code: e0464645

Exception Offset: 000000000010bd5c

OS Version: 10.0.19042.2.0.0.256.48

Locale ID: 16393

Additional Information 1: 0503

Additional Information 2: 05038a8d0f1df7d435a57df411af2cff

Additional Information 3: 602b

Additional Information 4: 602bee1b8a1cfe9e7b43a379fcfbbc4d



Extra information about the problem

Bucket ID: b5a4c417db5a39f295722cf9dab3ef01 1545347073769205505




and here is what crash dump says WINDBG preview:




Microsoft R Windows Debugger Version 10.0.20153.1000 X86Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Users\vikas\AppData\Local\CrashDumps\dllhost.exe.17572.dmp]User Mini Dump File: Only registers, stack and portions of memory are availableSymbol search path is: srv*Executable search path is: Windows 10 Version 19042 MP 16 procs Free x86 compatibleProduct: WinNt, suite: SingleUserTSEdition build lab: 19041.1.amd64fre.vb_release.191206-1406Machine Nameebug session time: Tue Dec 15 13:47:00.000 2020 UTC + 5:30System Uptime: not availableProcess Uptime: 0 days 0:12:50.000........................................Loading unloaded module list........This dump file has an exception of interest stored in it.The stored exception information can be accessed via .ecxr.44a4.2c70: Access violation - code c0000005 first/second chance not availableFor analysis of this file, run !analyze -veax=00000000 ebx=00000000 ecx=ffffffff edx=03022720 esi=00000000 edi=00000002eip=77bd1bdc esp=04bde450 ebp=04bde490 iopl=0 nv up ei pl nz ac pe nccs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000216ntdll!NtWaitForMultipleObjects+0xc:77bd1bdc c21400 ret 14h0:001> !analyze -v******************************************************************************** ** Exception Analysis ** ********************************************************************************Unable to load image SkypeContext.dll, Win32 error 0n2*** WARNING: Unable to verify timestamp for SkypeContext.dllKEY_VALUES_STRING: 1 Key : AV.Fault Value: Read Key : Analysis.CPU.mSec Value: 1280 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on VIKASINATOR Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 158690 Key : Analysis.Memory.CommitPeak.Mb Value: 231 Key : Analysis.System Value: CreateObject Key : Timeline.Process.Start.DeltaSec Value: 770 Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1 Key : WER.Process.Version Value: 10.0.19041.546ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1NTGLOBALFLAG: 0PROCESS_BAM_CURRENT_THROTTLED: 0PROCESS_BAM_PREVIOUS_THROTTLED: 0APPLICATION_VERIFIER_FLAGS: 0CONTEXT: .ecxreax=641f90b0 ebx=03022720 ecx=ffffffff edx=03022720 esi=03032a00 edi=0302d2a0eip=75c2a772 esp=04bdebc0 ebp=04bdecb4 iopl=0 nv up ei pl zr na pe nccs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010246combase!CStdMarshal::CreateStub+0x112:75c2a772 8b30 mov esi,dword ptr [eax] ds:002b:641f90b0=????????Resetting default scopeEXCEPTION_RECORD: .exr -1ExceptionAddress: 75c2a772 combase!CStdMarshal::CreateStub+0x00000112 ExceptionCode: c0000005 Access violation ExceptionFlags: 00000000NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 641f90b0Attempt to read from address 641f90b0PROCESS_NAME: dllhost.exeREAD_ADDRESS: 641f90b0 ERROR_CODE: NTSTATUS 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.EXCEPTION_CODE_STR: c0000005EXCEPTION_PARAMETER1: 00000000EXCEPTION_PARAMETER2: 641f90b0FAULTING_LOCAL_VARIABLE_NAME: pfNonNDRADDITIONAL_DEBUG_TEXT: Followup set based on attribute [ThreadFinalExh] from Frame:[0] on thread:[2c70] ; Followup set based on attribute [Is_ChosenCrashFollowupThread] from Frame:[0] on thread:[PSEUDO_THREAD]FAULTING_THREAD: ffffffffSTACK_TEXT: 00000000 00000000 SkypeContext.dll!Unloaded+0x0STACK_COMMAND: .ecxr ; ~~[0x2c70]s ; .frame 0 ; ** Pseudo Context ** ManagedPseudo ** Value: eafa7b0 ** ; kbSYMBOL_NAME: SkypeContext.dll!Unloaded+0MODULE_NAME: SkypeContextIMAGE_NAME: SkypeContext.dllFAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_SkypeContext.dll!UnloadedOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x86OSNAME: Windows 10FAILURE_ID_HASH: {ea92feee-2838-7ef4-e9b3-f215f60623bf}Followup: MachineOwner---------0:001> .ecxreax=641f90b0 ebx=03022720 ecx=ffffffff edx=03022720 esi=03032a00 edi=0302d2a0eip=75c2a772 esp=04bdebc0 ebp=04bdecb4 iopl=0 nv up ei pl zr na pe nccs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010246combase!CStdMarshal::CreateStub+0x112:75c2a772 8b30 mov esi,dword ptr [eax] ds:002b:641f90b0=????????0:001> .exr -1ExceptionAddress: 75c2a772 combase!CStdMarshal::CreateStub+0x00000112 ExceptionCode: c0000005 Access violation ExceptionFlags: 00000000NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 641f90b0Attempt to read from address 641f90b0


any help would be greatly appreciated.

:)

 

Multiple Stop Codes: Windows 10 crash

Hey Guys,

Recently, my main desktop Windows 10 machine has started to crash. I think it could be due to the latest 'massive' windows update. But before rolling back to a previous build (I'd prefer to keep the security updates), it'd be good to get some expert help
on what the multiple stop codes I'm getting actually mean and what they may point to.

Initially, I thought it may have been because my system was getting junked up, so I did a clean install of Windows 10 and updated like normal. This did not fix the problem.

Here are the stop codes I've been getting since the clean install and the number of times its occurred:

• BAD_POOL_HEADER (4)
  • Can happen on startup when reaching the desktop.
  • While watching YouTube.
  • While computer was idle on the desktop.
• MEMORY_MANAGEMENT (3)
  • Happens on startup after reaching desktop.
  • Crashed with this stop code when opening chrome.
• KERNEL_SECURITY_CHECK_FAILURE (1)
  • Happen after some time with low system load.
• KMODE_EXCEPTION_NOT_HANDLED (1)
  • On start up.
• IRQL_NOT_LESS_OR_EQUAL (1)
  • Chrome tabs kept crashing immediately before system crash.

Some the processes I've tried to fix or diagnose:

• Ran the windows memory check. Came back all good.
• Ran the driver verifier. This caused drivers to crash when trying log into the desktop. Cause was: USB_Ethernet_Adaptor.sys. The device I use for internet is the TP-Link TL-WN822N Wireless USB adapter. In case that information could help diagnose the problem.

I've included the minidump files from the last few days when the crashes occured, and my system info here: Dropbox - File Deleted

I'd greatly appreciate any tips on how to fix this issue.

Thanks!

Sam.

***Post moved by the moderator to the appropriate forum category.***

 

all games crash!

ive watch my temps and both the cpu and gpu are within normal ranges. when it freezes it simply freezes the image and stops the sound. i must reboot to get back to windows.

 

Desktop Window Manager stopped working, day in, day out...

So my Windows 10 tends to crash on a daily basis. It freezes randomly with a sharp whirring / static sound playing in the speakers. Checking the Reliability Monitor, it turns out that Desktop Window Manager appears to have stopped working. The problem happens
about once or twice per day.

I tried updating the software and drivers, running `sfc scannow`, etc. but none of it helped.

The problem details are:

Description

Faulting Application Path: C:\Windows\System32\dwm.exe

Problem signature

Problem Event Name: APPCRASH

Application Name: dwm.exe

Application Version: 10.0.10586.0

Application Timestamp: 5632d756

Fault Module Name: combase.dll

Fault Module Version: 10.0.10586.0

Fault Module Timestamp: 5632d3ca

Exception Code: c0000005

Exception Offset: 0000000000067e5c

OS Version: 10.0.10586.2.0.0.256.48

Locale ID: 4105

Additional Information 1: 4a22

Additional Information 2: 4a223f60382fa2d34e6a47e2139f1f17

Additional Information 3: ab88

Additional Information 4: ab888da10f9f005aa150bcd5f2273de0