【Fixed 2023】11 Ways On How To Fix Critical Error Your Start Menu Isn"T Working Windows 10/11


In this article

Try our Virtual Agent - It can help you quickly identify and fix common Windows boot issues

If you"re not a tư vấn agent or IT professional, you"ll find more helpful information about stop error ("blue screen") messages in Troubleshoot xanh screen errors.

Bạn đang xem: 【fixed 2023】11 ways on how to fix critical error your start menu isn"t working windows 10/11

Applies to: Windows 10

What causes stop errors?

A stop error is displayed as a blue screen that contains the name of the faulty driver, such as any of the following example drivers:


There"s no simple explanation for the cause of stop errors (also known as xanh screen errors or bug kiểm tra errors). Many different factors can be involved. However, various studies indicate that stop errors usually aren"t caused by greenlines.com.vn Windows components. Instead, these errors are related to malfunctioning hardware drivers or drivers that are installed by third-party software. These drivers include video clip cards, wireless network cards, security programs, and so on.

Our analysis of the root causes of crashes indicates that:

70% are caused by third-party driver code.10% are caused by hardware issues.5% are caused by greenlines.com.vn code.15% have unknown causes, because the memory is too corrupted to analyze.


The root cause of stop errors is never a user-mode process. While a user-mode process (such as Notepad or Slack) may trigger a stop error, it is merely exposing the underlying bug which is always in a driver, hardware, or the OS.

General troubleshooting steps

To troubleshoot stop error messages, follow these general steps:

Review the stop error code that you find in the sự kiện logs. Search online for the specific stop error codes khổng lồ see whether there are any known issues, resolutions, or workarounds for the problem.

Make sure that you install the latest Windows updates, cumulative updates, and rollup updates. Khổng lồ verify the update status, refer khổng lồ the appropriate update history for your system. For example:

Make sure that the BIOS and firmware are up-to-date.

Run any relevant hardware and memory tests.

Make sure that there"s sufficient free space on the hard disk. The exact requirement varies, but we recommend 10-15 percent không lấy phí disk space.

Contact the respective hardware or software vendor to update the drivers and applications in the following scenarios:

The error message indicates that a specific driver is causing the problem.You"re seeing an indication of a service that is starting or stopping before the crash occurred. In this situation, determine whether the service behavior is consistent across all instances of the crash.

Memory dump collection

To configure the system for memory dump files, follow these steps:

Select the Taskbar tìm kiếm box, type Advanced system settings, & then press Enter.On the Advanced tab on the System Properties box, select the Settings button that appears in the section Startup và Recovery.In the new window, select the drop-down below the option Write debugging information.Choose Automatic memory dump.Select OK.Restart the computer for the setting khổng lồ take effect.If the hệ thống is virtualized, disable tự động reboot after the memory dump tệp tin is created. This disablement lets you take a snapshot of the server in-state và also if the problem recurs.

The memory dump file is saved at the following locations:

Dump tệp tin typeLocation
(none)%SystemRoot%MEMORY.DMP (inactive, or grayed out)
Small memory dump tệp tin (256 kb)%SystemRoot%Minidump
Kernel memory dump file%SystemRoot%MEMORY.DMP
Complete memory dump file%SystemRoot%MEMORY.DMP
Automatic memory dump file%SystemRoot%MEMORY.DMP
Active memory dump file%SystemRoot%MEMORY.DMP

You can use the greenlines.com.vn Crash Dump tệp tin Checker (DumpChk) tool lớn verify that the memory dump files aren"t corrupted or invalid. For more information, see the following video:

For more information on how to use Dumpchk.exe to check your dump files, see the following articles:

Pagefile settings

For more information on pagefile settings, see the following articles:

Memory dump analysis

Finding the root cause of the crash may not be easy. Hardware problems are especially difficult khổng lồ diagnose because they may cause erratic và unpredictable behavior that can manifest itself in various symptoms.

When a stop error occurs, you should first isolate the problematic components, & then try lớn cause them khổng lồ trigger the stop error again. If you can replicate the problem, you can usually determine the cause.

You can use the tools such as Windows Software Development Kit (SDK) và symbols lớn diagnose dump logs. The next section discusses how to lớn use this tool.

Advanced troubleshooting steps


Advanced troubleshooting of crash dumps can be very challenging if you aren"t experienced with programming & internal Windows mechanisms. We have attempted to lớn provide a brief insight here into some of the techniques used, including some examples. However, to lớn really be effective at troubleshooting a crash dump, you should spend time becoming familiar with advanced debugging techniques. For a video overview, Debugging kernel mode crashes và hangs. Also see the advanced references listed below.

Advanced debugging references

Debugging steps

Locate the memory.dmp file in your Windows directory on the computer that is crashing, & copy that tệp tin to another computer.

Start the install and choose Debugging Tools for Windows. The WinDbg tool is installed.

Go to the File menu & select Symbol file Path to mở cửa the WinDbg tool and set the symbol path.

Select Open Crash Dump, và then xuất hiện the memory.dmp file that you copied.


Under Bugcheck Analysis, select !analyze -v. The command !analyze -v is entered in the prompt at the bottom of the page.

A detailed bug check analysis appears.


Scroll down to the STACK_TEXT section. There will be rows of numbers with each row followed by a colon & some text. That text should tell you what DLL is causing the crash. If applicable, it also says what service is crashing the DLL.

There are many possible causes of a bug check and each case is unique. In the example provided above, the important lines that can be identified from the STACK_TEXT are 20, 21, & 22:

1 : nt!KeBugCheckEx2 : nt!PspCatchCriticalBreak+0xff3 : nt!PspTerminateAllThreads+0x1134cf4 : nt!PspTerminateProcess+0xe05 : nt!NtTerminateProcess+0xa96 : nt!KiSystemServiceCopyEnd+0x137 : nt!KiServiceLinkage8 : nt!KiDispatchException+0x1107fe9 : nt!KiFastFailDispatch+0xe410 : nt!KiRaiseSecurityCheckFailure+0x3d311 : ntdll!RtlpHpFreeWithExceptionProtection$filt$0+0x4412 : ntdll!_C_specific_handler+0x9613 : ntdll!RtlpExecuteHandlerForException+0xd14 : ntdll!RtlDispatchException+0x35815 : ntdll!KiUserExceptionDispatch+0x2e16 : ntdll!RtlpHpVsContextFree+0x11e17 : ntdll!RtlpHpFreeHeap+0x48c18 : ntdll!RtlpHpFreeWithExceptionProtection+0xda19 : ntdll!RtlFreeHeap+0x24a20 : FWPolicyIOMgr!FwBinariesFree+0xa7c221 : mpssvc!FwMoneisDiagEdpPolicyUpdate+0x1584f22 : mpssvc!FwEdpMonUpdate+0x6c23 : ntdll!RtlpWnfWalkUserSubscriptionList+0x29b24 : ntdll!RtlpWnfProcessCurrentDescriptor+0x10525 : ntdll!RtlpWnfNotificationThread+0x8026 : ntdll!TppExecuteWaitCallback+0xe127 : ntdll!TppWorkerThread+0x8d028 : KERNEL32!BaseThreadInitThunk+0x1429 : ntdll!RtlUserThreadStart+0x21This issue is because of the mpssvc service, which is a component of the Windows Firewall. The problem was repaired by disabling the firewall temporarily và then resetting firewall policies.

Xem thêm: Debet – Đường link Download Cổng game Debet APK cho Android và IOS

For more examples, see Debugging examples.

Video resources

The following videos illustrate various troubleshooting techniques for analyzing dump files.

Advanced troubleshooting using Driver Verifier

We estimate that about 75 percent of all stop errors are caused by faulty drivers. The Driver Verifier tool provides several methods lớn help you troubleshoot. These include running drivers in an isolated memory pool (without sharing memory with other components), generating extreme memory pressure, and validating parameters. If the tool encounters errors in the execution of driver code, it proactively creates an exception. It can then further examine that part of the code.


Driver Verifier consumes lots of CPU và can slow down the computer significantly. You may also experience additional crashes. Verifier disables faulty drivers after a stop error occurs, & continues to vày this until you can successfully restart the system and access the desktop. You can also expect khổng lồ see several dump files created.

Don"t try to lớn verify all the drivers at one time. This kích hoạt can degrade performance & make the system unusable. It also limits the effectiveness of the tool.

Use the following guidelines when you use Driver Verifier:

Test any "suspicious" drivers. For example, drivers that were recently updated or that are known to lớn be problematic.If you continue to experience non-analyzable crashes, try enabling verification on all third-party & unsigned drivers.Enable concurrent verification on groups of 10-20 drivers.Additionally, if the computer can"t boot into the desktop because of Driver Verifier, you can disable the tool by starting in Safe mode. This solution is because the tool can"t run in Safe mode.

For more information, see Driver Verifier.

Common Windows stop errors

This section doesn"t contain a danh sách of all error codes, but since many error codes have the same potential resolutions, your best bet is to lớn follow the steps below khổng lồ troubleshoot your error.

The following sections list general troubleshooting procedures for common stop error codes.


Stop error code 0x00000141, or 0x00000117

Contact the vendor of the listed display driver lớn get an appropriate update for that driver.


Stop error code 0x0000000D1

Apply the latest updates for the driver by applying the latest cumulative updates for the system through the greenlines.com.vn Update Catalog website. Update an outdated network driver. Virtualized VMware systems often run "Intel(R) PRO/1000 MT Network Connection" (e1g6032e.sys). You can download this driver from the Intel download Drivers & Software website. Contact the hardware vendor khổng lồ update the network driver for a resolution. For VMware systems, use the VMware integrated network driver instead of Intel"s e1g6032e.sys. For example, use VMware types VMXNET, VMXNET2, or VMXNET3.


Stop error code 0x000000050

If a driver is identified in the stop error message, tương tác the manufacturer for an update. If no updates are available, disable the driver, và monitor the system for stability. Run chkdsk /f /r to lớn detect and repair disk errors. Restart the system before the disk scan begins on a system partition. Liên hệ the manufacturer for any diagnostic tools that they may provide for the hard disk subsystem. Try to reinstall any application or service that was recently installed or updated. It"s possible that the crash was triggered while the system was starting applications và reading the registry for preference settings. Reinstalling the application can fix corrupted registry keys. If the problem persists, and you have run a recent system state backup, try to restore the registry hives from the backup.


Stop error code c000021a Fatal System Error The Windows SubSystem system process terminated unexpectedly with a status of 0xc0000005. The system has been shut down.

Use the System file Checker tool khổng lồ repair missing or corrupted system files. The System file Checker lets users scan for corruptions in Windows system files and restore corrupted files. For more information, see Use the System file Checker tool.


Stop error code 0x000000024

This stop error is commonly caused by corruption in the NTFS file system or bad blocks (sectors) on the hard disk. Corrupted drivers for hard disks (SATA or IDE) can also adversely affect the system"s ability lớn read and write khổng lồ disk. Run any hardware diagnostics that are provided by the manufacturer of the storage subsystem. Use the scan disk tool to verify that there are no file system errors. To vị this step, right-click the drive that you want to lớn scan, select Properties, select Tools, and then select the check now button. Update the NTFS file system driver (Ntfs.sys). Apply the latest cumulative updates for the current operating system that"s experiencing the problem.


Stop error code 0x0000001E

If a driver is identified in the stop error message, disable or remove that driver. Disable or remove any drivers or services that were recently added.

If the error occurs during the startup sequence, & the system partition is formatted by using the NTFS tệp tin system, you might be able to lớn use safe mode to lớn disable the driver in Device Manager. To disable the driver, follow these steps:

Go khổng lồ Settings > Update & security > Recovery.Under Advanced startup, select Restart now.After your PC restarts to the Choose an option screen, select Troubleshoot > Advanced options > Startup Settings > Restart.After the computer restarts, you"ll see a danh sách of options. Press 4 or F4 to start the computer in safe mode. If you intend to use the mạng internet while in safe mode, press 5 or F5 for the Safe Mode with Networking option.


Stop error code 0x00000133

This stop error code is caused by a faulty driver that doesn"t complete its work within the allotted time frame in certain conditions. Khổng lồ help mitigate this error, collect the memory dump tệp tin from the system, và then use the Windows Debugger lớn find the faulty driver. If a driver is identified in the stop error message, disable the driver to isolate the problem. Kiểm tra with the manufacturer for driver updates. Check the system log in event Viewer for other error messages that might help identify the device or driver that"s causing stop error 0x133. Verify that any new hardware that"s installed is compatible with the installed version of Windows. For example, you can get information about required hardware at Windows 10 Specifications. If Windows Debugger is installed, and you have access to lớn public symbols, you can load the c:windowsmemory.dmp file into the debugger. Then refer to lớn Determining the source of Bug check 0x133 (DPC_WATCHDOG_VIOLATION) errors on Windows hệ thống 2012 to find the problematic driver from the memory dump.


Stop error code 0x0000009E

This stop error indicates that a user-mode health check failed in a way that prevents graceful shutdown. Windows restores critical services by restarting or enabling application failover lớn other servers. The Clustering Service incorporates a detection mechanism that may detect unresponsiveness in user-mode components.

This stop error usually occurs in a clustered environment, và the indicated faulty driver is RHS.exe. Kiểm tra the sự kiện logs for any storage failures khổng lồ identify the failing process. Try to update the component or process that"s indicated in the sự kiện logs. You should see the following sự kiện recorded:

Event ID: 4870Source: greenlines.com.vn-Windows-FailoverClusteringDescription: User mode health monitoring has detected that the system isn"t being responsive. The Failover cluster virtual adapter has lost tương tác with the Cluster hệ thống process with a process ID "%1", for "%2" seconds. Recovery action is taken. đánh giá the Cluster logs khổng lồ identify the process & investigate which items might cause the process khổng lồ hang.

For more information, see "0x0000009E" Stop error on cluster nodes in a Windows Server-based multi-node failover cluster environment Also, see the following greenlines.com.vn đoạn phim What to do if a 9E occurs.

Debugging examples

Example 1

This bug check is caused by a driver hang during upgrade, resulting in a bug kiểm tra D1 in NDIS.sys, which is a greenlines.com.vn driver. The IMAGE_NAME tells you the faulting driver, but since this driver is s greenlines.com.vn driver, it can"t be replaced or removed. The resolution method is to lớn disable the network device in device manager & try the upgrade again.