Your location:Tech News>OS>Windows 2000>Windows 2000 troubleshooting at a glance

Latest News

Windows 2000 troubleshooting at a glance



The launch of Win2000 marks the operating system has reached a new stage but because there are too many (I heard that there are 6 Ten thousand terrible?) various problems followed in the process of using the following is a list of the problems I encountered in practice I hope to help you a little bit.

1 when the security log is full suspend the computer take the following steps:

(1) Open Event Viewer.

(2) In the console tree right-click on 'Security Log' then click 'Properties.'

(3) In the 'General' tab click 'overwrite events older than n days' or 'do not overwrite events (clear log manually).'

(4) Click 'Start' click 'Run' type regedit enter 'HKEY_LOCAL_MacHINESYSTEM CurrentControlSetControlLsa' right-click on the 'CrashOnAuditFail' create 'REG_DWord' type a value of '1.'

(5) Restart your computer.


(1): Incorrectly editing the registry may severely damage your system. Before making changes to the registry you should at least back up any useful data on your computer.

(2): After the end of this process when the security log is full Windows 2000 will stop responding with an 'audit failure' message. When Windows 2000 is stopped to recover the security log must be cleared.


(1): You must be logged on as an administrator or a member of the management group to complete the process.

(2): To open Event Viewer click the 'Start' point to 'Settings' then click 'Control Panel.' Double-click 'Administrative Tools' and then double-click 'Event Viewer'.

(3) If the Windows 2000 Security log is full suspended due you must restart your system if you need to use the full log off in the future you must repeat the process.

2. Resume when Windows 2000 stops

(1) Restart the computer and log in with an account in the system administrator group.

(2) Open the 'Event Viewer' Archive currently logged security events (if required) and then clear all events from the security log.

(3) Open the Registry Editor and locate the following registry key: 'HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlLsa'
Right-click on the 'Lsa' created from the pop-up menu 'EG_DWORD' type value '1' Delete and replace the CrashOnAuditFail value. Exit the registry editor and restart the computer.


(1) If you previously configured with CrashOnAuditFail = 1 registry and the security log is full Windows 2000 will stop responding with an 'audit failure' message. If this happens use the steps above.

(2) To start the 'Registry Editor' click 'Start' click 'Run' type regedit and then click 'OK.' In the backup set contains the system status data

(3) To capture registry changes during the backup process to ensure the backup program is running.

3 find the memory bottleneck

use of memory resources following counters to identify bottlenecks in performance tools:

(1) System Processor Queue Length

(2) Memory Pages / sec

4 to find disk bottleneck

identified using the following counter tool performance bottlenecks disk resources:

(1) PhysicalDisk% disk Time and% Idle Time

(2) PhysicalDisk disk Reads / sec and disk Writes / sec

(3) PhysicalDisk Avg.Disk Queue Length

(4) LogicalDisk% Free Space

also monitor memory counters to determine if there is excessive paging the disk usage tension.

Note: Unlike the physical disk counter data the logical disk counter data is not collected by the operating system by default. To obtain performance counter data for logical drives or storage volumes you must type diskperf -yv at the command prompt. This causes the disk performance statistics driver used to collect disk performance data to report data on logical drives and storage volumes. By default the operating system uses the diskperf -yd command to include physical drive data. For more information about using the diskperf command type diskperf -? at the command prompt.

5 to find a processor bottleneck

counter use of processor resources following a bottleneck identification tool performance:

(1) Processor Interrupts / sec

(2) Processor% Processor Time

(3) Process ( process )% Processor Time

(4) System Processor Queue Length

6. Find network bottlenecks

Use the following counters in the performance tool to identify the network resources that have bottlenecks:

< br> (1) Network Interface Bytes Total / sec Bytes Sent / sec and Bytes Received / sec

(2) Protocol_layer_object Segments Received / sec Segments Sent / sec Frames Sent / sec and Frames Received / sec For NWLink performance objects counters related to frames only report zero. Use datagram-based counters for these objects.

(3) Server Bytes Total / sec Bytes Received / sec and Bytes Sent / sec

(4) Network Segment% Network Utilization

?Optimizing NTFS system under Windows 2000

Recommend article

Relate article