Windows 10: Computer is crashing once a day with a bug check error

I have a Dell Optiplex 7020 with an i5, 8 GB ram, 240 GB SSD on Windows 10 version 2004 that keeps crashing daily with a bug check error. I have insured that all the drivers are up-to-day, ran sfc /scannow as well as dism /online /cleanup-image /restorehealth and chkdsk /f. I also ran Dell memory and Microsoft memory diagnostics and both pass fine. All the fans are running fine and I've checked the cpu for overheat issues max temp is 72°C. Still, the computer drops to a BSOD about once a day. Based on the recent memory.dmp, here's the analysis. Any ideas?


Microsoft R Windows Debugger Version 10.0.20153.1000 AMD64

Copyright 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 Location

Deferred srv*

Symbol search path is: srv*

Executable search path is:

Page 200202ba8 too large to be in the dump file.

Windows 10 Kernel Version 19041 MP 4 procs Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Edition build lab: 19041.1.amd64fre.vb_release.191206-1406

Machine Name:

Kernel base = 0xfffff802`47a00000 PsLoadedModuleList = 0xfffff802`4862a310

Debug session time: Tue Jul 28 08:21:56.799 2020 UTC - 6:00

System Uptime: 0 days 1:33:12.108

Loading Kernel Symbols

...............................................................

................................................................

...........................................................

Loading User Symbols

...............................................

Loading unloaded module list

.............

For analysis of this file, run <link alt="!analyze -v" cmd="!analyze -v"><u>!analyze -v</u></link>

nt!KeBugCheckEx:

fffff802`47dddb60 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8982`e0a99940=00000000000000ef

3: kd&gt; !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************


CRITICAL_PROCESS_DIED ef

A critical system process died

Arguments:

Arg1: ffffde8b2bf6e300, Process object or thread object

Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.

Arg3: 0000000000000000

Arg4: 0000000000000000



Debugging Details:

------------------



KEY_VALUES_STRING: 1



Key : Analysis.CPU.mSec

Value: 4343



Key : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on ST-1



Key : Analysis.DebugData

Value: CreateObject



Key : Analysis.DebugModel

Value: CreateObject



Key : Analysis.Elapsed.mSec

Value: 4370



Key : Analysis.Memory.CommitPeak.Mb

Value: 226



Key : Analysis.System

Value: CreateObject



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



ADDITIONAL_XML: 1



OS_BUILD_LAYERS: 1



BUGCHECK_CODE: ef



BUGCHECK_P1: ffffde8b2bf6e300



BUGCHECK_P2: 0



BUGCHECK_P3: 0



BUGCHECK_P4: 0



PROCESS_NAME: svchost.exe



CRITICAL_PROCESS: svchost.exe



ERROR_CODE: NTSTATUS 0x235c1080 - &lt;Unable to get error code text&gt;



BLACKBOXBSD: 1 <link alt="!blackboxbsd" cmd="!blackboxbsd"><u>!blackboxbsd</u></link>




BLACKBOXNTFS: 1 <link alt="!blackboxntfs" cmd="!blackboxntfs"><u>!blackboxntfs</u></link>




BLACKBOXPNP: 1 <link alt="!blackboxpnp" cmd="!blackboxpnp"><u>!blackboxpnp</u></link>




BLACKBOXWINLOGON: 1



STACK_TEXT:

ffff8982`e0a99938 fffff802`48317712 : 00000000`000000ef ffffde8b`2bf6e300 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx

ffff8982`e0a99940 fffff802`4820b43f : 00000000`00000000 fffff802`47c74921 00000000`00000002 fffff802`47c74cbb : nt!PspCatchCriticalBreak+0x10e

ffff8982`e0a999e0 fffff802`4804e820 : ffffde8b`00000000 00000000`00000000 ffffde8b`2bf6e300 ffffde8b`2bf6e738 : nt!PspTerminateAllThreads+0x1bc80f

ffff8982`e0a99a50 fffff802`4804e61c : ffffde8b`2bf6e300 00000000`00000000 000000dd`17cff7fc 000001e1`52fc0000 : nt!PspTerminateProcess+0xe0

ffff8982`e0a99a90 fffff802`47def478 : ffffde8b`2bf6e300 ffffde8b`235c1080 ffff8982`e0a99b80 ffffde8b`2bf6e300 : nt!NtTerminateProcess+0x9c

ffff8982`e0a99b00 00007ffe`fbbeb314 : 00007ffe`fbc61643 00007ffe`fbc8ff74 000000dd`17cff7c0 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28

000000dd`17cfbf68 00007ffe`fbc61643 : 00007ffe`fbc8ff74 000000dd`17cff7c0 00000000`00000000 00007ffe`fbb50000 : ntdll!NtTerminateProcess+0x14

000000dd`17cfbf70 00007ffe`fbbf231d : 00007ffe`fbc8ff74 00000000`00000008 00007ffe`fbb50000 00007ffe`fbb62536 : ntdll!TppWorkerpInnerExceptionFilter+0x5b

000000dd`17cfbfa0 00007ffe`fbbdb686 : 000000dd`17cfc048 000000dd`17cfc088 00007ffe`fbb62536 000000dd`17cfc0f0 : ntdll!TppWorkerThread$filt$3+0x19

000000dd`17cfbfe0 00007ffe`fbbea97e : 00007ffe`fbc90034 000000dd`17cfccb0 000000dd`17cff7c0 000000dd`17cfc600 : ntdll!_C_specific_handler+0x96

000000dd`17cfc050 00007ffe`fbbf00ef : 00000000`00000000 000000dd`17cfc5f0 000000dd`17cfccb0 00000000`00000000 : ntdll!_GSHandlerCheck_SEH+0x6a

000000dd`17cfc080 00007ffe`fbb9b474 : 000000dd`17cfccb0 00000000`00000000 00000000`00000000 000000dd`17cfc0f0 : ntdll!RtlpExecuteHandlerForException+0xf

000000dd`17cfc0b0 00007ffe`fbbeec1e : 000000dd`17cfc8f8 00000000`00000000 00000000`000006bf 00000000`00000000 : ntdll!RtlDispatchException+0x244

000000dd`17cfc7c0 00007ffe`fbb5e255 : 00007ffe`fbb5e1f4 00000000`00000000 00000000`000006bf 000000dd`17cfd050 : ntdll!KiUserExceptionDispatch+0x2e

000000dd`17cfcec8 00007ffe`fbb5e1f4 : 00000000`00000000 00000000`000006bf 000000dd`17cfd050 000000dd`17cfd038 : ntdll!RtlpFindMessageInTable+0x39

000000dd`17cfced0 00007ffe`f94d4559 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlFindMessage+0x94

000000dd`17cfcf50 00007ffe`f94d4457 : 00000000`00000000 00000000`00001200 00000000`00000000 00000000`000006bf : KERNELBASE!BaseDllFormatMessage+0xf5

000000dd`17cfd0d0 00007ffe`fb323508 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : KERNELBASE!FormatMessageW+0x37

000000dd`17cfd120 00007ffe`fb3237ba : 000000dd`17cfd210 00000000`00000000 00000000`00000000 00000000`00000000 : combase!GetMessageForHr+0x34 [onecore\com\combase\winrt\error\error.cpp @ 166]

000000dd`17cfd170 00007ffe`fb3228de : 00000000`00000000 000000dd`17cfd700 00000000`00000001 00000000`00000000 : combase!GetMessageParameters+0xae [onecore\com\combase\winrt\error\error.cpp @ 239]

000000dd`17cfd1b0 00007ffe`fb35d361 : 000000dd`17cfd850 000000dd`17cfdc00 000000dd`17cfd6d8 00000000`800706bf : combase!SendReport+0xce [onecore\com\combase\winrt\error\error.cpp @ 420]

000000dd`17cfd6a0 00007ffe`fb35ceed : 00000000`00000000 000000dd`17cfdc00 000000dd`17cfd850 00007ffe`f6669432 : combase!RoOriginateError+0x51 [onecore\com\combase\winrt\error\error.cpp @ 590]

000000dd`17cfd6e0 00007ffe`f667c333 : 000000dd`800706bf 00000000`00000000 000000dd`17cfdce0 00000000`00000000 : combase!OriginateOrTransformError+0xcd [onecore\com\combase\winrt\error\errorprivate.cpp @ 52]

000000dd`17cfd730 00007ffe`f6676f9d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : rpcss!RaiseRoOriginateOnWilExceptions+0x13

000000dd`17cfd760 00007ffe`f6676df5 : 00007ffe`f66769d5 00000000`80070600 000000dd`17cfee29 00007ffe`f6734620 : rpcss!wil::details::LogFailure+0x169

000000dd`17cfd7d0 00007ffe`f6676ccc : 00000000`00000000 000001e1`533126d0 000001e1`533126d0 00007ffe`f9c15c4f : rpcss!wil::details::ReportFailure+0x95

000000dd`17cfed10 00007ffe`f6676c70 : 00000000`00000000 000000dd`17cfedf0 00000000`00001388 00007ffe`f9c1e0ec : rpcss!wil::details::ReportFailure_Win32+0x50

000000dd`17cfed70 00007ffe`f6676c25 : 00000000`00001388 000000dd`17cfee29 00007ffe`f6734620 00000000`00000250 : rpcss!wil::details::in1diag3::Return_Win32+0x20

000000dd`17cfedc0 00007ffe`f66769d5 : 00000000`00000000 000000dd`17cfeea0 00000000`00000000 00000000`00000000 : rpcss!CFastBH::BindWithTimeout+0x13d

000000dd`17cfee90 00007ffe`f6676906 : 00000000`00000000 00000000`00000000 00000000`00000000 000001e1`5339e320 : rpcss!CFastBH::CreateFromBindingHandle+0xa9

000000dd`17cfef90 00007ffe`f66766a7 : 00000000`00000000 00000000`00000000 00000000`00000000 000001e1`53a8b7a0 : rpcss!CFastBH::GetOrCreateWithTimeout+0x36

000000dd`17cfefd0 00007ffe`f664acfc : 00000000`00000000 000001e1`5302c600 00000000`00000013 000001e1`53a8b700 : rpcss!CServerOxid::EnsureRundownHandle+0xbb

000000dd`17cff040 00007ffe`f664b5a3 : 000001e1`5302c600 000001e1`53a8b7a0 00000000`00000000 000001e1`5302c600 : rpcss!CServerOxid::RundownOids+0x160

000000dd`17cff130 00007ffe`f664b191 : 000000dd`17cff1f0 000001e1`533fa500 000001e1`53c02608 00007ffe`f6737270 : rpcss!CServerOxid::FastRundownOids+0x2d3

000000dd`17cff1b0 00007ffe`f664a33f : 000001e1`530b0180 00000000`00000000 000001e1`53a469c0 00000000`00000000 : rpcss!CProcess::FastRundownAllProcesses+0x1d1

000000dd`17cff250 00007ffe`f6638e57 : 000001e1`53a469c0 00000000`00000000 000005a8`00001538 00000000`00000000 : rpcss!CProcess::Rundown+0x53f

000000dd`17cff380 00007ffe`f9becfb8 : 000001e1`53a1c220 00000000`00000000 000000dd`17cff660 00007ffe`f9bc7754 : rpcss!PHPROCESS_rundown+0xa7

000000dd`17cff3b0 00007ffe`f9becefd : 00000000`00000000 00000000`00000000 00000000`00000014 00007ffe`f9c09138 : RPCRT4!NDRSRundownContextHandle+0x1c

000000dd`17cff400 00007ffe`f9bed222 : 000001e1`530b3300 000000dd`17cff660 000001e1`530b3398 000001e1`5305da40 : RPCRT4!DestroyContextHandlesForGuard+0x111

000000dd`17cff460 00007ffe`f9bed0a4 : 000001e1`00000000 00000000`00000001 00000000`00000000 00007ffe`f9bed785 : RPCRT4!LRPC_SASSOCIATION::~LRPC_SASSOCIATION+0x15a

000000dd`17cff4b0 00007ffe`f9bc48bb : 000001e1`530b3300 00007ffe`f9bed479 000001e1`530b33f8 000000dd`17cff660 : RPCRT4!LRPC_SASSOCIATION::`vector deleting destructor'+0x14

000000dd`17cff4e0 00007ffe`f9bed3eb : 00000000`00000000 00000000`00000000 000001e1`530b3300 00000000`00000000 : RPCRT4!LRPC_SCALL_BROKEN_FLOW::FreeObject+0x1b

000000dd`17cff510 00007ffe`f9c054a5 : 000001e1`53019000 00000000`00000000 00000000`000000f0 000001e1`530bb260 : RPCRT4!LRPC_SASSOCIATION::MessageReceivedWithClosePending+0x7f

000000dd`17cff560 00007ffe`f9c09ce2 : 0000d112`3a97c236 000001e1`530bb260 000001e1`53019108 000000dd`17cff938 : RPCRT4!LRPC_ADDRESS:rocessIO+0x5e5

000000dd`17cff6a0 00007ffe`fbb8f220 : 00000000`00000000 00000000`00000000 000000dd`17cff938 00007ffe`fbbc7e22 : RPCRT4!LrpcIoComplete+0xc2

000000dd`17cff740 00007ffe`fbb62536 : 00000000`00000000 000001e1`53019100 00000000`00000000 000001e1`53abe590 : ntdll!TppAlpcpExecuteCallback+0x260

000000dd`17cff7c0 00007ffe`fa5e6fd4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!TppWorkerThread+0x456

000000dd`17cffac0 00007ffe`fbb9cec1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : KERNEL32!BaseThreadInitThunk+0x14

000000dd`17cffaf0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21





SYMBOL_NAME: ntdll!NtTerminateProcess+14



MODULE_NAME: <link alt="lmvm ntdll" cmd="lmvm ntdll"><u>ntdll</u></link>



IMAGE_NAME: ntdll.dll



STACK_COMMAND: .thread ; .cxr ; kb



BUCKET_ID_FUNC_OFFSET: 14



FAILURE_BUCKET_ID: 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_235c1080_ntdll!NtTerminateProcess



OS_VERSION: 10.0.19041.1



BUILDLAB_STR: vb_release



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



FAILURE_ID_HASH: {1a10b327-67b9-89cc-a9a6-d4227d5a3cca}



Followup: MachineOwner

:)

 

Computer Crashing Once Per Day

I recently upgraded my computer. I ran Windows off the old SSD and everything was working well. I then purchased a Western Digital SN550 Blue 1TB NVMe SSD and installed windows, I have a MSI B450I motherboard (Micro ITX)and a AMD 3600 processor. Ever
since then I have had BSODs once per day. It normally happens when I watch You Tube or start up a game. Once it crashes and reboots, it doesn't happpen for the rest of the day. Once i shut down my computer the next day when I am watching a video or start
up a game it crashes again.

The main errors I keep getting are listed below. I have tested the memory multiple times, updated my drivers, and removed all programs I do not use. I'm out of ideas, thanks in advance. I have also turned off fast startup.

On Wed 7/8/2020 12:14:42 PM your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\MEMORY.DMP

This was probably caused by the following module: ntkrnlmp.exe (nt!memset+0x44BAB)

Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80637245A6B, 0x0, 0xFFFFFFFFFFFFFFFF)

Error: KMODE_EXCEPTION_NOT_HANDLED

Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.

This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Tue 7/7/2020 12:32:58 PM your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\Minidump\070720-12593-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x1C23A0)

Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80771FC972F, 0xFFFFAD817B17F930, 0x0)

Error: SYSTEM_SERVICE_EXCEPTION

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Mon 7/6/2020 11:59:25 AM your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\Minidump\070620-12125-01.dmp

This was probably caused by the following module: classpnp.sys (0xFFFFF8006BCF8A10)

Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8006BCF8A10, 0x1, 0x2)

Error: KMODE_EXCEPTION_NOT_HANDLED

file path: C:\WINDOWS\system32\drivers\classpnp.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: SCSI Class System Dll

Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.

This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.

The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

 

Bug check error: 0x00000133 on Windows 10

Hi,

Thank you for posting in Microsoft Community and being part of Windows 10.

I understand your concern about accessing your device after performing a bug check, we will help you with this issue.

Do let us know the following to assist you better with this issue:

• Are you able to boot the device to desktop?
• What is the complete error message along with error code of this issue?
• What is the make and model of your device?

If you are able to log-in to the desktop, try few of the below troubleshooting steps and check if it helps.

Step 1: Run Memory Diagnostic Tool.

Follow the below steps:

• Press Windows key and type
  Memory Diagnostic.
• Select Windows Memory Diagnostics
  and click on Restart now and check for problems.
• Follow the on-screen instructions.

Step 2: Run the Power Troubleshooter


Power troubleshooter find and fix problems with your computer's power settings to conserve power and extent battery life

• 
  Type Troubleshooting in the
  Search bar on the desktop and press Enter.
  
• 
  In the Troubleshooting window, click on
  View All on the left pane.
  
• 
  Click on Power.
  
• 
  Click Next and follow the on-screen instructions to complete the troubleshooting process.
  

Step 3: I suggest you to check for the pending updates on your device install them and check if it helps.

Steps:

• Connect to the internet.
• Press Windows key and type
  updates.
• Click on Check for updates.
• Under Windows Updates, click on
  Check for updates.
• Try to install the updates being shown.

Hope it helps. Kindly update the status of this issue, we will be happy to assist you further.

 

My computer crashes frequently when starting a fullscreen application or bluestacks

Hi Anantha,

Thank you for contacting Microsoft Community.

The VIDEO_TDR_ ERROR bug check has a value of 0x00000116. This indicates that an attempt to reset the display driver and recover from a timeout failed.

I suggest you to remove all the external devices except mouse and keyboard, restart the computer and check whether the issue persists or not.

If still the issue persist then follow the below steps and check if it helps.

Step 1: I suggest you to install all the latest pending Windows updates as below and check if it helps.

• Go to “settings” and click on “update and security”.
• Under tab “Windows update”, click on the icon “check for updates”.
• Then once you find the pending updates install it and check.

Step 2: Also I suggest you to update all the drivers (Display drivers) from the device manager and check if it helps.

• Press ‘Windows+X’ and go to ‘Device Manager’.
• Then you can right click on each driver and update it.
• Restart the computer and check if it helps.

Hope this information is helpful and do let us know if you need further assistance. We will be glad to assist.