Windows 10: Reproducible way to kill Windows 10 pro

Working remotely has been a must lately. Remote desktop through a VPN has been working great except in one scenario. I have seen this same exact issue on two different Windows 10 pro systems.


While connected via RDP, if I start a full or custom Windows Security virus scan on the remote PC, after a while 30 - 60 min more or less the remote system will lose it's RDP connection. In this first case, the remote system was not responsive at all and had to be forced shutdown. On the second system, one scan finished without an issue. Although, the scan was started and soon after RPD was intentionally logged off. A few days a later, another scan was started on this second system while RDP was connected and sure enough after about 30 to 60 minutes maybe a little more RDP was lost and could not be reconnected. In this case the remote system was still responsive locally. An attempt to manually restart this second system ended up causing a BSOD. I suspect the first system experienced something similar but the screen was dead as well.



Here is the dump file analysis from the second system.

Microsoft R Windows Debugger Version 10.0.19528.1000 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\MEMORY.DMP]Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.************* Path validation summary **************Response Time ms LocationDeferred srv*Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 18362 MP 4 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS18362.1.amd64fre.19h1_release.190318-1202Machine Name:Kernel base = 0xfffff800`5d000000 PsLoadedModuleList = 0xfffff800`5d448170Debug session time: Fri May 22 14:54:03.030 2020 UTC - 4:00System Uptime: 0 days 5:05:12.766Loading Kernel Symbols...................................................................Page 9c094 not present in the dump file. Type ".hh dbgerr004" for details...........................................................................................................................Loading User SymbolsLoading unloaded module list...................For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff800`5d1c2390 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff800`622679f0=000000000000009f0: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DRIVER_POWER_STATE_FAILURE 9fA driver has failed to complete a power IRP within a specific time.Arguments:Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp subsystem.Arg2: 000000000000012c, Timeout in seconds.Arg3: ffffce0004aac040, The thread currently holding on to the Pnp lock.Arg4: fffff80062267a20, nt!TRIAGE_9F_PNP on Win7 and higherDebugging Details:------------------Implicit thread is now ffffce00`04aac040KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 5 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on RAFFI-PC Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 5 Key : Analysis.Memory.CommitPeak.Mb Value: 61 Key : Analysis.System Value: CreateObjectADDITIONAL_XML: 1BUGCHECK_CODE: 9fBUGCHECK_P1: 4BUGCHECK_P2: 12cBUGCHECK_P3: ffffce0004aac040BUGCHECK_P4: fffff80062267a20DRVPOWERSTATE_SUBCODE: 4FAULTING_THREAD: ffffce0004aac040BLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1PROCESS_NAME: SystemLOCK_ADDRESS: fffff8005d4629c0 -- !locks fffff8005d4629c0Resource @ nt!PiEngineLock 0xfffff8005d4629c0 Exclusively owned Contention Count = 55 NumberOfExclusiveWaiters = 2 Threads: ffffce0004aac040-01<*> Threads Waiting On Exclusive Access: ffffce0006438040 ffffce0003bc40c0 1 total locksPNP_TRIAGE_DATA: Lock address : 0xfffff8005d4629c0 Thread Count : 1 Thread address: 0xffffce0004aac040 Thread wait : 0x119731STACK_TEXT: ffffdf8d`683e2070 fffff800`5d11507d : ffffa800`85040180 00000047`fffffffe ffffa800`ffffffff 00000000`00000001 : nt!KiSwapContext+0x76ffffdf8d`683e21b0 fffff800`5d113f04 : ffffce00`04aac040 00000000`00000000 ffffce00`00000000 ffffe50c`00000000 : nt!KiSwapThread+0xbfdffffdf8d`683e2250 fffff800`5d1136a5 : 00000000`00000001 fffff800`00000000 ffffce00`03bcc500 00000000`00000000 : nt!KiCommitThreadWait+0x144ffffdf8d`683e22f0 fffff800`619b9920 : ffffce00`01c725b0 fffff800`00000000 ffffce00`01c71100 fffff800`00000000 : nt!KeWaitForSingleObject+0x255ffffdf8d`683e23d0 fffff800`619acb89 : 00000000`00000008 ffffdf8d`683e2470 00000000`00000004 00000000`00000000 : ndis!KWaitEventBase<wistd::integral_constant<enum _EVENT_TYPE,0> >::Wait+0x28ffffdf8d`683e2410 fffff800`619abefd : ffffe50c`30071d90 fffff800`619abee0 ffffe50c`30091158 fffff800`6196c6d8 : ndis!Ndis::BindEngine::ApplyBindChanges+0x10915ffffdf8d`683e2460 fffff800`619a7933 : ffffe50c`30071dd0 fffff800`619abee0 ffffe50c`30091158 ffffce00`01c711a0 : ndis!<lambda_adb42f86cf839cbbe3c588eaa9665cd9>::<lambda_invoker_cdecl>+0x1dffffdf8d`683e2490 fffff800`619a7879 : 00000000`00000000 fffff800`6196c6d8 00000000`00000000 ffffe50c`30091150 : ndis!NDIS_BIND_DRIVER_BASE::ForEachLink+0xa3ffffdf8d`683e24e0 fffff800`619a768b : 00000000`00000000 ffffce00`065a1388 00000000`00000010 fffff800`618bb7b5 : ndis!NDIS_BIND_DRIVER_BASE::SetRunningDriverIsReady+0x41ffffdf8d`683e2510 fffff800`619d9934 : ffffce00`065a1010 ffffdf8d`683e2628 ffffdf8d`683e2628 ffffce00`065a1058 : ndis!NDIS_BIND_PROTOCOL_DRIVER::SetRunningDriver+0x63ffffdf8d`683e2560 fffff800`619327c6 : ffffce00`065a1010 fffff800`61985050 fffff800`61985050 fffff800`6196d790 : ndis!NdisDeregisterProtocol+0xd4ffffdf8d`683e25d0 fffff800`644c111a : fffff800`644c9000 fffff800`00000000 ffffce00`04cb4020 ffffdf8d`683e26b0 : ndis!NdisDeregisterProtocolDriver+0x66ffffdf8d`683e2620 fffff800`644cc484 : 00000000`000000e7 ffffdf8d`683e26a8 00000000`00000008 00000000`00000000 : raspppoe!RasPppoeCleanup+0x66ffffdf8d`683e2650 fffff800`619b7d73 : ffffce00`04cb4020 ffffce00`04cb4020 fffff800`61985050 ffffce00`06599670 : raspppoe!MpUnload+0x44ffffdf8d`683e2680 fffff800`6193cdd4 : ffffce00`06599670 00000000`00000000 ffffce00`06599670 ffffce00`06599670 : ndis!ndisMInvokeDriverUnload+0x67ffffdf8d`683e26c0 fffff800`5d765db7 : ffffce00`06599670 00000000`00000000 ffffdf8d`683e2880 ffffe50c`458ce490 : ndis!ndisMUnloadEx+0x94ffffdf8d`683e2720 fffff800`5d7314be : ffffce00`065997c0 00000000`00000000 fffff800`5d78c601 ffffce00`06599670 : nt!IopUnloadDriver+0x20fffffdf8d`683e2850 fffff800`5d171fc4 : ffffce00`063c59a0 0000170c`39f8db60 00000000`0000000a 00000000`00000000 : nt!PnpUnloadAttachedDriver+0xa6ffffdf8d`683e28a0 fffff800`5d7310bf : ffffce00`063c59a0 fffff800`00000000 00000000`00000000 fffff800`5d462920 : nt!PnpRemoveLockedDeviceNode+0x240ffffdf8d`683e2900 fffff800`5d730d5a : ffffce00`063c59a0 ffffdf8d`683e2980 00000000`00000000 00000000`00000000 : nt!PnpDeleteLockedDeviceNode+0x8bffffdf8d`683e2940 fffff800`5d732641 : ffffce00`062bcdf0 00000000`00000002 ffffce00`06404890 00000000`00000000 : nt!PnpDeleteLockedDeviceNodes+0x76ffffdf8d`683e29c0 fffff800`5d730484 : 00000000`00000000 ffffdf8d`683e2a40 ffffce00`062bcdf0 00000000`00000000 : nt!PipRemoveDevicesInRelationList+0x8dffffdf8d`683e2a10 fffff800`5d72fe61 : ffffce00`06404890 00000000`00000001 ffffce00`06404890 00000000`00000007 : nt!PnpDelayedRemoveWorker+0x114ffffdf8d`683e2a50 fffff800`5d171a14 : 00000000`00000007 00000000`00000001 00000000`00000000 ffffce00`063f99a0 : nt!PnpChainDereferenceComplete+0xfdffffdf8d`683e2a80 fffff800`5d72f60a : 00000000`00000008 ffffdf8d`683e2b89 00000000`00000003 00000000`00000001 : nt!PnpIsChainDereferenced+0xacffffdf8d`683e2b00 fffff800`5d708b4e : ffffdf8d`683e2c50 ffffce00`063f9900 ffffdf8d`683e2c00 ffffe50c`00000008 : nt!PnpProcessQueryRemoveAndEject+0x2a2ffffdf8d`683e2bf0 fffff800`5d5d69b8 : ffffe50c`347dde50 ffffe50c`47148e10 ffffe50c`47148e10 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0xeaffffdf8d`683e2c20 fffff800`5d0f43b5 : ffffce0f`ff268cf0 ffffce00`04aac040 ffffce0f`ff268cf0 ffffce0f`ff268cf0 : nt!PnpDeviceEventWorker+0x2d8ffffdf8d`683e2cb0 fffff800`5d06bcd5 : ffffce00`04aac040 00000000`00000080 ffffce0f`ff27b080 00000000`00000020 : nt!ExpWorkerThread+0x105ffffdf8d`683e2d50 fffff800`5d1c9998 : ffffa800`84f87180 ffffce00`04aac040 fffff800`5d06bc80 00000000`02000001 : nt!PspSystemThreadStartup+0x55ffffdf8d`683e2da0 00000000`00000000 : ffffdf8d`683e3000 ffffdf8d`683dd000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28STACK_COMMAND: .thread 0xffffce0004aac040 ; kbSYMBOL_NAME: raspppoe!RasPppoeCleanup+66MODULE_NAME: raspppoeIMAGE_NAME: raspppoe.sysBUCKET_ID_FUNC_OFFSET: 66FAILURE_BUCKET_ID: 0x9F_4_raspppoe!RasPppoeCleanupOS_VERSION: 10.0.18362.1BUILDLAB_STR: 19h1_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {e9804e85-a9ce-852f-0dee-ef9be593a2a4}Followup: MachineOwner---------

:)

 

kill dwm.exe windows 10 pro 64bit

I found this link

What is dwm.exe and why is it using so much memory?

With this note: "The steps below only work for Windows Vista and Windows 7. Desktop Windows Manager is not displayed in the Services window on Windows 8 and Windows 10, and therefore cannot be turned off or disabled."

These links have suggestions for improving performance:

dwm.exe Desktop Window Manager High CPU on Windows 10 [Solved] - Driver Easy
Fix: Dwm.exe issues in Windows 10
I would start here:

 

Windows 10 Tweaks

Pressing “Windows+Pause Break” (it’s up there next to scroll lock) opens the “System” Window.

Windows 10: In the new version of Windows, Explorer has a section called Quick Access. This includes your frequent folders and recent files. Explorer defaults to opening this page when you open a new window. If you’d rather open the usual This PC, with links to your drives and library folders, follow these steps:

• Open a new Explorer window.
• Click View in the ribbon.
• Click Options.
• Under General, next to “Open File Explorer to:” choose “This PC.”
• Click OK

credit to Lifehacker.

 

Can't upgrade from Windows 10 Home to Pro

Hi Bill,

Thank you for posting your query in Microsoft Community. We apologize for the inconvenience caused and will assist you in the best possible ways.

I suggest you to download and create an installation media for Windows 10 Pro form the link provided below:

Download Windows 10

After the installation media is created, suggest you to upgrade to Windows 10 Pro from the installation media. When the upgrade asks for product key, enter the product key purchased for Windows 10 Pro. If it does not accept, suggest you to skip the activation
step. After the Operating System is installed, suggest you to activate by phone by following the steps below:

• Press “Windows key + R” and type “slui 4” and press Enter.
• Select the Region from the list and click Next.
• Call the Toll-Free number provided on top and can activate via phone.

Hope this helps. Keep us posted on the status for further assistance.