updated the warnings and suggestion

This commit is contained in:
Shesh
2022-04-14 15:29:43 +05:30
parent e3adc49723
commit 900677ed6d
2 changed files with 1 additions and 3 deletions

View File

@ -106,8 +106,6 @@ If the computer is no longer frozen and now is running in a good state, use the
5. Make sure that there's a paging file (pagefile.sys) on the system drive and that its at least 100 megabytes (MB) over the installed RAM (Initial and Maximum Size). 5. Make sure that there's a paging file (pagefile.sys) on the system drive and that its at least 100 megabytes (MB) over the installed RAM (Initial and Maximum Size).
Additionally, you can use the workaround for [space limitations on the system drive in Windows Server 2008](#space-limitations-on-the-system-drive-in-windows-server-2008).
6. Make sure that there's more available space on the system drive than there is physical RAM. 6. Make sure that there's more available space on the system drive than there is physical RAM.
2. Enable the CrashOnCtrlScroll registry value to allow the system to generate a dump file by using the keyboard. To do this, follow these steps: 2. Enable the CrashOnCtrlScroll registry value to allow the system to generate a dump file by using the keyboard. To do this, follow these steps:

View File

@ -187,4 +187,4 @@ When resetting the size of your data history to a lower value, be sure to turn o
## Related Links ## Related Links
- [Module in PowerShell Gallery](https://www.powershellgallery.com/packages/Microsoft.DiagnosticDataViewer) - [Module in PowerShell Gallery](https://www.powershellgallery.com/packages/Microsoft.DiagnosticDataViewer)
- [Documentation for Diagnostic Data Viewer for PowerShell](/powershell/module/microsoft.diagnosticdataviewer/?view=win10-ps) - [Documentation for Diagnostic Data Viewer for PowerShell](/powershell/module/microsoft.diagnosticdataviewer/?)