Although a system error may occur only when you work with Adobe Reader, Adobe Reader may not necessarily be the cause--it may be the only application that is memory- or processor-intensive enough to expose the problem. Then, try to re-create the problem: -- If the problem doesn't occur, one of the startup items conflicts with Adobe Reader. Then, try to re-create the problem: -- If the problem doesn't recur, then move the icons and shortcuts back to the Startup folder one at a time and restart the computer until you determine which item is causing the conflict. If a TEMP variable doesn't exist, contact your system administrator for assistance. In Windows Explorer, verify that the folder you noted in step 4 exists on a noncompressed disk partition that has at least 50 MB of free space: -- If the folder doesn't exist, create it: Right-click the drive, choose New Folder from the menu, and type the folder name you noted in step 4 (for example, Temp). Move font files, excluding those installed by Windows, from the Fonts folder to the folder you created in step 1. Move a few of the fonts from step 3 back to the Winnt/Fonts folder. Start Adobe Reader, and try to re-create the problem: -- If the problem recurs, then one of the fonts you moved in step 4 may be the cause.
To benefit most from this document, perform the tasks in order. Click the Services Tab, and check Hide All Microsoft Services 7. Reenable startup items one at a time, testing each time until you determine which item is causing the conflict. Do not disable the following required processes: wuauclt.exe, Win Mgmt.exe, WINLOGON. EXE, System Idle Process, System, svchost.exe, spoolsv.exe, SMSS. Then contact that item's developer for an update, if available. Choose Start Control Panel, and double click Add Or Remove Programs. -- If the disk doesn't have enough free space, then create additional space by removing unnecessary files. Remove those fonts from the Fonts folder, and repeat steps 4-6, this time adding only one font at a time.
Added secondary sorting support: You can now get a secondary sorting, by holding down the shift key while clicking the column header.
Be aware that you only have to hold down the shift key when clicking the second/third/fourth column.
With regard to NT systems in which event logs are a feature, there are a couple of indicators.
If, and that's a big if, Privilege Use logging is enabled, event 577 indicates a system time change.
Hint: If these images aren't clear in your browser, click on the picture and it will launch in its own window for more clarity!Continuing to work without restarting the computer may compound the problem. Some applications that run in the background may cause system errors or freezes when running concurrently with Adobe Reader. -- If the problem doesn't occur, then repeat steps 8 with another third-party plug-in. The majority of the Adobe Reader preferences are stored within the registry. In Windows Explorer, go to Documents and Settings\Application Data\Adobe\Acrobat.0 folder and move the Preferences folder to another location (for example, C:\Temp). Intermediate troubleshooting If the tasks in the previous section don't solve the problem, try the following intermediate troubleshooting tasks. Run Detect And Repair while no other applications are running. Initiating this command at other hard drive locations can damage your Operating System. The Error-checking tool repairs bad sectors, lost allocation units and file fragments, cross-linked files, and invalid file names.Since Windows Vista, Microsoft has changed to a new system for event logs called crimson event logging.In the event log we see automatic updates installing and rebooting the server.We thought we turned off automatic udpates prior to the last update/reboot events.