Skip to content

Commit 7be38bc

Browse files
author
Simonx Xu
committed
Update troubleshoot-stop-errors-guidance.md
1 parent 8d20a6f commit 7be38bc

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

support/windows-server/performance/troubleshoot-stop-errors-guidance.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.custom:
1616

1717
This solution is designed to help you troubleshoot Stop error scenarios.
1818

19-
There's no simple explanation for the cause of Stop errors (also known as blue screen errors or bug check errors). Many factors might be involved, and the cause is not always obvious. For example, you might be using new hardware or third-party software that isn't compatible with your Windows device.
19+
There's no simple explanation for the cause of Stop errors (also known as blue screen errors or bug check errors). Many factors might be involved, and the cause isn't always obvious. For example, you might be using new hardware or third-party software that isn't compatible with your Windows device.
2020

2121
## Troubleshooting checklist
2222

@@ -25,14 +25,14 @@ There's no simple explanation for the cause of Stop errors (also known as blue s
2525
3. Contact the respective hardware or software vendor to update the drivers and applications in the following scenarios:
2626

2727
- The error message indicates that a specific driver is causing the problem.
28-
- You are seeing an indication of a service that is starting or stopping before the failure occurred. In this situation, determine whether the service behavior is consistent across all instances of the failure.
28+
- You're seeing an indication of a service that is starting or stopping before the failure occurred. In this situation, determine whether the service behavior is consistent across all instances of the failure.
2929
- You have made any software or hardware changes.
3030

3131
4. Make sure that you install the latest Windows updates, cumulative updates, and rollup updates.
3232
5. Make sure that the BIOS and firmware are up-to-date.
3333
6. Run any relevant hardware and memory tests.
3434
7. Run an anti-malware software scan such as [Microsoft Defender](/defender-endpoint/microsoft-defender-offline).
35-
8. If the problem occurrs after installing a new piece of software, remove the new software. If you can't boot to normal mode, you can try from [Safe Mode](https://support.microsoft.com/windows/windows-startup-settings-1af6ec8c-4d4a-4b23-adb7-e76eef0b847f).
35+
8. If the problem occurs after installing a new piece of software, remove the new software. If you can't boot to normal mode, you can try from [Safe Mode](https://support.microsoft.com/windows/windows-startup-settings-1af6ec8c-4d4a-4b23-adb7-e76eef0b847f).
3636

3737
> [!NOTE]
3838
> Some software can't be removed from Safe Mode.
@@ -64,7 +64,7 @@ Stop error code:
6464
6565
This error code indicates that the executing code had an exception, and the thread that was below it is a system thread. Follow these steps:
6666

67-
1. If new device drivers or system services have been added recently, try removing or updating them.
67+
1. If new device drivers or system services have been added recently, try removing or updating them.
6868
2. Look in Device Manager to see whether any devices are marked with an exclamation point (!) to indicate a problem. Review the events log that's displayed in the properties for any faulting device driver. Try to update the related driver.
6969
3. Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that's causing the error. Look for critical errors in the system log that occurred around the same time as the Stop error.
7070
4. If you recently added hardware to the system, try removing or replacing it. Or check with the manufacturer to see whether any updates are available.

0 commit comments

Comments
 (0)