Windows 10: System frequently reboots without warning, unable to determine root cause

Since May 29, 2020, my computer has been randomly rebooting with no root cause I've been able to identify. Prior to that point in time, it was completely stable.





I've done a memory check with both the Windows Memory checker and Memtest86+. Neither of these applications have found any issues with the installed RAM.


I've installed WinDbg Preview and done core analysis on the DMP files, but they don't really give much useful to go on. If I uninstall what it claims is the "culprit" application, the next dump just reports a different application.


For the crash on 12/03 @ 9:32 AM, I have this trace:


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

IRQL_NOT_LESS_OR_EQUAL aAn attempt was made to access a pageable or completely invalid address at aninterrupt request level IRQL that is too high. This is usuallycaused by drivers using improper addresses.If a kernel debugger is available get the stack backtrace.Arguments:Arg1: fffffffffffffcff, memory referencedArg2: 00000000000000ff, IRQLArg3: 0000000000000078, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation only on chips which support this level of statusArg4: fffff800243276dc, address which referenced memoryDebugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2359 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on Q-PC Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 2365 Key : Analysis.Memory.CommitPeak.Mb Value: 81 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.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: aBUGCHECK_P1: fffffffffffffcffBUGCHECK_P2: ffBUGCHECK_P3: 78BUGCHECK_P4: fffff800243276dcREAD_ADDRESS: fffffffffffffcff BLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1PROCESS_NAME: SystemTRAP_FRAME: ffffc304cc86f460 -- .trap 0xffffc304cc86f460NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000rip=fffff800243276dc rsp=ffffc304cc86f5f0 rbp=0000000000000000 r8=0000000000000002 r9=0000000000000200 r10=0000000000000004r11=0000000000000000 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up di pl zr na po ncnt!PpmIdleExecuteTransition+0x55c:fffff800`243276dc 7414 je nt!PpmIdleExecuteTransition+0x572 fffff800`243276f2 [br=1]Resetting default scopeSTACK_TEXT: ffffc304`cc86f318 fffff800`24407169 : 00000000`0000000a ffffffff`fffffcff 00000000`000000ff 00000000`00000078 : nt!KeBugCheckExffffc304`cc86f320 fffff800`24403469 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`28b7fd0b : nt!KiBugCheckDispatch+0x69ffffc304`cc86f460 fffff800`243276dc : ffff950b`22cb4318 00000000`00000000 000002c5`2d827b7a 000002c5`2d827b7a : nt!KiPageFault+0x469ffffc304`cc86f5f0 fffff800`24327004 : 00000000`00000000 00001f80`00000008 00000000`00000003 00000000`00000002 : nt!PpmIdleExecuteTransition+0x55cffffc304`cc86f9f0 fffff800`243f8d34 : ffffffff`00000000 ffffdb01`bb8e1440 ffff950b`28716080 00000000`000008ee : nt!PoIdle+0x374ffffc304`cc86fb60 00000000`00000000 : ffffc304`cc870000 ffffc304`cc869000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54SYMBOL_NAME: nt!PpmIdleExecuteTransition+55cMODULE_NAME: ntIMAGE_NAME: ntkrnlmp.exeSTACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 55cFAILURE_BUCKET_ID: AV_nt!PpmIdleExecuteTransitionOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {0ced0187-972d-f83e-de87-663d75806c32}Followup: MachineOwner---------

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


For the crash on 12/26, I have this trace:

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

SYSTEM_SERVICE_EXCEPTION 3bAn exception happened while executing a system service routine.Arguments:Arg1: 00000000c0000005, Exception code that caused the bugcheckArg2: fffff8044ba52e60, Address of the instruction which caused the bugcheckArg3: ffff9009cb7aedd0, Address of the context record for the exception that caused the bugcheckArg4: 0000000000000000, zero.Debugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1921 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on Q-PC Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 1917 Key : Analysis.Memory.CommitPeak.Mb Value: 79 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.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: 3bBUGCHECK_P1: c0000005BUGCHECK_P2: fffff8044ba52e60BUGCHECK_P3: ffff9009cb7aedd0BUGCHECK_P4: 0CONTEXT: ffff9009cb7aedd0 -- .cxr 0xffff9009cb7aedd0rax=0000000000000103 rbx=0000000000012017 rcx=ffffac079a05db40rdx=ffff9009cb7af930 rsi=0000000000040000 rdi=ffffac079a05db40rip=fffff8044ba52e60 rsp=ffff9009cb7af7d8 rbp=ffff9009cb7afa80 r8=0000000000000000 r9=ffff9009cb7af940 r10=0000000000000001r11=000000000000014c r12=0000000000000000 r13=0000000000000003r14=ffffac079a05db90 r15=0000000000000001iopl=0 nv up ei pl zr na po nccs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00250246nt!IoGetRelatedDeviceObject:fffff804`4ba52e60 488b4110 mov rax,qword ptr [rcx+10h] ds:002b:ffffac07`9a05db50=0000000000000000Resetting default scopeBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1PROCESS_NAME: GalaxyCommunication.exeSTACK_TEXT: ffff9009`cb7af7d8 fffff804`4bdfcabb : 00000000`00000000 00000000`00012017 ffff9009`cb7afa80 ffffac07`9a05db40 : nt!IoGetRelatedDeviceObjectffff9009`cb7af7e0 fffff804`4bdfc7e6 : 00000000`00000001 00000000`000002ec 00000000`00000001 00000000`00000000 : nt!IopXxxControlFile+0x2bbffff9009`cb7af920 fffff804`4bc071b5 : 00000000`006cfda0 00000000`77934660 00000000`007cf664 00000000`00000000 : nt!NtDeviceIoControlFile+0x56ffff9009`cb7af990 00000000`77931cfc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x2500000000`006cea28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77931cfcSYMBOL_NAME: nt!IopXxxControlFile+2bbMODULE_NAME: ntIMAGE_NAME: ntkrnlmp.exeSTACK_COMMAND: .cxr 0xffff9009cb7aedd0 ; kbBUCKET_ID_FUNC_OFFSET: 2bbFAILURE_BUCKET_ID: 0x3B_c0000005_nt!IopXxxControlFileOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {657bb511-7f5c-7ddc-acd3-e126b6d359c8}Followup: MachineOwner---------

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

:)

 

method to determine exactly what caused a particular update?

Two suggested articles from Microsoft....

• Fix Windows Update errors
• Troubleshoot problems updating Windows 10

Whether you find the exact cause will determine the level of troubleshooting you go through.

 

Continual System Reboot

There is a possibility that this issue might have occurred due to corrupt system files in the system.

So to diagnose whether there are no corruptions, we suggest you to try the following methods and check if it helps.

Method 1: Run inbuilt system maintenance troubleshooter and check if it works.
Please follow the steps given below.

• 
  Type Troubleshooting in search bar and click
  Troubleshooting.
  
• 
  Now click on view all option.
  
• 
  Click on System maintenance and follow the prompts to run the troubleshooter.
  

Method 2: We suggest you to perform clean boot and check if any third party apps are causing the issue.
Placing the computer in a clean boot state can reduce software conflicts and help identify the root cause of the issue.

Please refer to the article below for steps to perform a clean boot.

How to perform a clean boot in Windows

Once you are done with the troubleshooting, perform the steps in "How to reset the computer to start as usual after troubleshooting with clean boot "to reset computer as usual.

Let us know the result.

 

Intel Announces Root Cause of Meltdown, Spectre Patch Reboot Issue Identified

Intel has finally come around towards reporting on the state of the reboot issues that have been plaguing Intel systems ever since the company started rolling out patches to customers. These patches, which aimed to mitigate security vulnerabilities present in Intel's chips, ended up causing a whole slew of other problems for Intel CPU deployment managers. As a result of Intel's investigation, the company has ascertained that there were, in fact, problems with the patch implementation, and is now changing its guidelines: where before users were encouraged to apply any issued updates as soon as possible, the company now states that "OEMs, cloud service providers, system manufacturers, software vendors and end users stop deployment of current versions, as they may introduce higher than expected reboots and other unpredictable system behavior." A full transcription of the Intel press release follows.








"As we start the week, I want to provide an update on the reboot issues we reported Jan. 11. We have now identified the root cause for Broadwell and Haswell platforms, and made good progress in developing a solution to address it. Over the weekend, we began rolling out an early version of the updated solution to industry partners for testing, and we will make a final release available once that testing has been completed.

Based on this, we are updating our guidance for customers and partners:

• We recommend that OEMs, cloud service providers, system manufacturers, software vendors and end users stop deployment of current versions, as they may introduce higher than expected reboots and other unpredictable system behavior. For the full list of platforms, see the Intel.com Security Center site.
• We ask that our industry partners focus efforts on testing early versions of the updated solution so we can accelerate its release. We expect to share more details on timing later this week.
• We continue to urge all customers to vigilantly maintain security best practice and for consumers to keep systems up-to-date.

I apologize for any disruption this change in guidance may cause. The security of our products is critical for Intel, our customers and partners, and for me, personally. I assure you we are working around the clock to ensure we are addressing these issues.

I will keep you updated as we learn more and thank you for your patience."