Windows 10: PC keeps restarting

Hi My pc keeps restarting.

I have

CPU: AMD Ryzen 7 3800XT
Motherboard: ASUS TUF GAMING X570-PLUS Wi-Fi
Memory: G.SKILL Trident Z Neo Series 16GB2 x 8GB DDR4 3600Mhz CL16 Dual Channel Memory Kit 1.35V

GPU: EVGA RTX 3070


The Bug check analysis says


KMODE_EXCEPTION_NOT_HANDLED 1eThis is a very common bugcheck. Usually the exception address pinpointsthe driver/function that caused the problem. Always note this addressas well as the link date of the driver/image that contains this address.Arguments:Arg1: ffffffffc0000005, The exception code that was not handledArg2: fffff80745a74425, The address that the exception occurred atArg3: fffffd0656096bc8, Parameter 0 of the exceptionArg4: ffff9b00097a2920, Parameter 1 of the exceptionDebugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 3578 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-IKK0JSQ Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 6780 Key : Analysis.Memory.CommitPeak.Mb Value: 87 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: 1eBUGCHECK_P1: ffffffffc0000005BUGCHECK_P2: fffff80745a74425BUGCHECK_P3: fffffd0656096bc8BUGCHECK_P4: ffff9b00097a2920WRITE_ADDRESS: fffff80733cfb390: Unable to get MiVisibleStateUnable to get NonPagedPoolStartUnable to get NonPagedPoolEndUnable to get PagedPoolStartUnable to get PagedPoolEndfffff80733c0f330: Unable to get Flags value from nt!KdVersionBlockfffff80733c0f330: Unable to get Flags value from nt!KdVersionBlockunable to get nt!MmSpecialPagesInUse ffff9b00097a2920 EXCEPTION_PARAMETER1: fffffd0656096bc8EXCEPTION_PARAMETER2: ffff9b00097a2920BLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: AVGSvc.exeTRAP_FRAME: 8f0b1729834b132d -- .trap 0x8f0b1729834b132dUnable to read trap frame at 8f0b1729`834b132dBAD_STACK_POINTER: ffff9b00097a20a8STACK_TEXT: ffff9b00`097a20a8 fffff807`3350ed9f : 00000000`0000001e ffffffff`c0000005 fffff807`45a74425 fffffd06`56096bc8 : nt!KeBugCheckExffff9b00`097a20b0 fffff807`33411c86 : ffff9b00`097a2920 fffff807`33303845 fffffd06`56096e00 fffff807`45a74425 : nt!KiFatalFilter+0x1fffff9b00`097a20f0 fffff807`333cc052 : fffff807`00000002 fffff807`330d8e34 fffffd06`56093000 fffffd06`56099000 : nt!KeExpandKernelStackAndCalloutInternal$filt$0+0x16ffff9b00`097a2130 fffff807`333fe942 : fffff807`330d8e34 ffff9b00`097a2710 fffff807`333cbfb0 00000000`00000000 : nt!_C_specific_handler+0xa2ffff9b00`097a21a0 fffff807`3332bf97 : ffff9b00`097a2710 00000000`00000000 fffffd06`560978b0 fffff807`33354488 : nt!RtlpExecuteHandlerForException+0x12ffff9b00`097a21d0 fffff807`3332ab86 : fffffd06`56096bc8 ffff9b00`097a2e20 fffffd06`56096bc8 ffffb102`4da721b0 : nt!RtlDispatchException+0x297ffff9b00`097a28f0 fffff807`333f6912 : 30343937`3f743b47 0800e9a6`4764a9a1 8f0b1729`834b132d b43b858b`b87b85a5 : nt!KiDispatchException+0x186ffff9b00`097a2fb0 fffff807`333f68e0 : fffff807`33407ba5 ffffb101`46d86680 fffffd06`56096b90 fffffd06`56096bf8 : nt!KxExceptionDispatchOnExceptionStack+0x12fffffd06`56096a88 fffff807`33407ba5 : ffffb101`46d86680 fffffd06`56096b90 fffffd06`56096bf8 fffffd06`56096e98 : nt!KiExceptionDispatchOnExceptionStackContinuefffffd06`56096a90 fffff807`33403d43 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x125fffffd06`56096c70 fffff807`45a74425 : 00000000`00000011 ffffb102`4da721b0 fffffd06`56097170 00000000`00000000 : nt!KiPageFault+0x443fffffd06`56096e00 fffff807`37368cee : 00000000`00000000 fffffd06`56096f09 badbadfa`badbadfa fffffd06`56097208 : Ndu!NduOutboundTransportClassify+0x2b5fffffd06`56096ea0 fffff807`374a0684 : fffffd06`560970c0 ffffb102`47028680 00000000`00000000 00000000`0000004f : NETIO!KfdClassify2+0x19efffffd06`56096f70 fffff807`374948bd : fffffd06`00000000 80000001`66190963 00000000`00000002 00000000`00000001 : tcpip!WfpProcessOutTransportStackIndication+0x90cfffffd06`560972a0 fffff807`3749393b : ffffb102`3fb40988 fffffd06`56097670 ffffb102`3fb408a8 00000000`00000004 : tcpip!IppInspectLocalDatagramsOut+0x87dfffffd06`56097570 fffff807`375bdff9 : ffffb102`47427000 ffffb102`47427004 fffff807`37659230 ffffb102`4b906c20 : tcpip!IppSendDatagramsCommon+0x41bfffffd06`560976f0 fffff807`3776873f : ffffb102`47427080 fffffd06`56097a60 ffffb102`3a4f7000 fffff807`3335460e : tcpip!IppInspectInjectTlSend+0x179fffffd06`56097820 fffff807`33354488 : fffffd06`56097a60 ffffb102`3a4f70c0 00000000`00000003 00000000`00000000 : fwpkclnt!FwppInjectionStackCallout+0x9ffffffd06`560978b0 fffff807`333543fd : fffff807`377686a0 fffffd06`56097a60 ffffb102`394f5910 fffff807`3758f263 : nt!KeExpandKernelStackAndCalloutInternal+0x78fffffd06`56097920 fffff807`3776a2b4 : 00000000`00000000 ffffb102`4b906c20 00000000`00000002 fffff807`0000000f : nt!KeExpandKernelStackAndCalloutEx+0x1dfffffd06`56097960 fffff807`37768658 : 00000000`00000004 fffffd06`56097aa0 fffffd06`56097aa0 ffffb102`47028680 : fwpkclnt!NetioExpandKernelStackAndCallout+0x58fffffd06`560979a0 fffff807`37769f23 : ffffb102`00000000 ffffb102`46006700 00000000`00000000 ffffb102`4326dee8 : fwpkclnt!FwppInjectTransportSendAsync+0x588fffffd06`56097ba0 fffff807`4552aca2 : ffffb102`48b1d3e0 ffffb102`47f7d700 00000000`00000000 ffffb102`48b1d3e0 : fwpkclnt!FwpsInjectTransportSendAsync0+0x63fffffd06`56097c10 ffffb102`48b1d3e0 : ffffb102`47f7d700 00000000`00000000 ffffb102`48b1d3e0 fffffd06`56097cc0 : avgStm+0xaca2fffffd06`56097c18 ffffb102`47f7d700 : 00000000`00000000 ffffb102`48b1d3e0 fffffd06`56097cc0 ffffb102`47930002 : 0xffffb102`48b1d3e0fffffd06`56097c20 00000000`00000000 : ffffb102`48b1d3e0 fffffd06`56097cc0 ffffb102`47930002 fffff807`00000001 : 0xffffb102`47f7d700SYMBOL_NAME: Ndu!NduOutboundTransportClassify+2b5MODULE_NAME: NduIMAGE_NAME: Ndu.sysIMAGE_VERSION: 10.0.19041.1030STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 2b5FAILURE_BUCKET_ID: 0x1E_c0000005_STACKPTR_ERROR_Ndu!NduOutboundTransportClassifyOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {63910737-ea4e-e75d-e79f-6296ef230e3e}Followup: MachineOwner

:)

 

PC keeps restarting

Hi,

We appreciate you for being part of Windows 10.

Have you made any changes prior to the issue?

The PC may restart automatically if the updates are being installed. If the updates are installed properly then follow the below methods and check if the issue persist.

Method 1:

I suggest you to disable automatic restart under system failure.
This prevents Windows from automatically restarting if an error causes Windows to fail.
Follow the below steps.

• 
  Press Windows + E keys on the keyboard to open File Explorer.
  
• 
  Right click on My Computer/This PC and Select
  Properties.
  
• 
  Click on Advanced system settings
  on the left navigation pane. (Enter the admin credentials if prompted)
  
• 
  Click on the Advanced
  tab.
  
• 
  Under the Startup and Recovery,
  select Settings.
  
• 
  Uncheck the option
  Automatic Restart under System failure.
  
• 
  Click on OK button and close the window.
  

Try to use the computer now for some time. Check if the computer is restarting now.

If the issue persist, follow the below method.

Method 2:

• 
  Press ‘Windows + X’ Keys on the keyboard.
  
• 
  Click on ‘Command Prompt (Admin)’ to bring up an elevated command prompt.
  
  Note: Click ‘Yes’ if it prompts for permission.
  
• 
  In the command prompt type in the following commands one by one and then press
  Enter.
  

sfc /scannow

Dism /online /cleanup-image /restorehealth

Note: If you are not able to repair some files after performing SFC scan, I suggest you to refer to the point 3 “Windows Resource Protection found corrupt files but was unable to fix some of them. Details
are included in the CBS.Log %WinDir%\Logs\CBS\CBS.log”. Under the section “Run the System File Checker tool (SFC.exe)”
to repair the corrupted files after performing SFC scan.

Use the System File Checker tool to repair missing or corrupted system files

Use the System File Checker tool to repair missing or corrupted system files

If the issue persist, follow the below method.

Method 3:

I will suggest you to check if the issue occurs in Safe Mode with Networking. Follow the below steps:

Step 1:

To start Windows 10 in safe mode:

• Search for Settings from the taskbar and select it from the search results.
• Select Update & security and click on Recovery.
• Go to Advanced startup and select
  Restart now.
• After your PC restarts to the Choose an option screen, select Troubleshoot
  > Advanced options > Startup Settings >Restart.
• After your PC restarts, select a startup setting as Safe Mode with Networking by pressing the corresponding number.

If the issue does not persists in Safe Mode, then perform a Clean Boot to check if any third party application is causing the issue, as Clean Boot helps in eliminating software conflicts.

Step 2:

Put the computer in Clean Boot and check if it helps.

A clean boot is performed to start Windows by using a minimal set of drivers and startup programs. This helps eliminate software conflicts that occur when you install a program or an update or when you run a program in Windows.

I would suggest you to refer the below Microsoft help article on How to Perform Clean boot.

https://support.microsoft.com/en-us/kb/929135

The steps for Windows 8.1 applies well to Windows 10 also.

Disclaimer: Please reset the computer to start as usual after troubleshooting with clean boot by referring above article.

I hope the above information helps. Kindly let us know if you need any further assistance with Windows. We are glad to assist you.

Thank you.

 

W10 PC Keeps Restarting

Hi Dave,

A corrupted Windows system files after the update is one of the possible reasons why your computer keeps restarting. For us to assist you better, kindly answer the questions below:

• What troubleshooting steps have you done so far?
• Do you have a third-party security software installed?
• Are you receiving any error messages?
• Are you able to boot to desktop?

Meanwhile, you can try running your computer in safe mode and check if you will experience the same issue. Safe mode starts Windows in a basic state, using a limited set of files and drivers. You can follow the steps in this

link.

We'll be looking forward to your response.

 

PC windows 10 keeps restarting

Hello Cynthia,

We regret for the inconvenience. Let me assist you.

Before we proceed further, let us know a few more details on the below questions.

• What is the make and model of the PCs you are using?
• Did you make any changes to the PC prior to the issue?

As an initial recommendation, I suggest you to boot the computer in safe mode with networking, and check if the issue still persists. This is a diagnostic step towards identifying and isolating the possible cause/s of the issue.

Safe Mode With Networking:

Safe mode is a troubleshooting option for Windows that starts your computer in a limited state. Only the basic files and drivers necessary to run Windows are started. The words
Safe Mode appear in the corners of your monitor to identify which Windows mode you're using.

Refer: Start your PC in safe
mode in Windows 10

Refer to the section From the Sign-in screen

If you are able to start the PC normally this time. Use the following steps to disable automatic restart in Windows on system failure.

• At "Start" -> "This PC" --> right click on "Properties", and then tap "Advanced system settings".
• In Advanced, click on "Settings" for Startup and Recovery.
• In the Startup and Recovery window, uncheck the Automatically restart check box.
• Click OK.
• 
  Now if the computer generates an error, it should not automatically restart
  

Once this is done, reboot the computer in normal mode and check.

Let us know the updated status and the required information for us to be able to assist you further.

Thank you.