Troubleshooting

This is information about Windows NT 4.0.

See the TechPlanet home page for Product Alerts sent to customers.

For background info, see:

• Windows NT 4.0 bug codes
• Beverly Hills Software
• JSI, Inc.
• MacWindows
• Microsoft’s NT site
• Microsoft collection of knowledge base articles on NT 4
• John Savill’s Windows NT/2000 FAQ

Choose a keyword to go to troubleshooting or other technical information associated with it.

Blue Screen crashes (BSODs)

See also the Installation page.

• Blue screen after installing Intergraph NFS over previous installations of Hummingbird NFS or Legato
• Blue screen crash: Mac Services directory corrupted
• Blue screen crash with stop code: 0x0000000a – IRQL_NOT_LESS_THAN_OR_EQUAL
• Blue screen crash with stop code: 0x00000058 – FTDISK_INTERNAL_ERROR
• Blue screen crash with stop code: 0x00000079
• Blue Screen Crashes (BSODs): 10-Step Cleaning Process for NT 3.51
  This document covers basic driver upgrades for systems exhibiting Blue Screen Crashes (BSOD). This pertains to Alpha Servers running NT 3.51.
• Blue Screen Crashes (BSODs): Enabling Crash Dumps
  This document describes how to set up your system to caputre crash dumps from a blue screen for an Alpha 2100/A running NT 3.51.
• Blue Screen Crashes (BSODs) Action Plan
  This document represents the actions taken when a BSOD occurs.
• Verifying and Collect Crash Dumps (for RC and Service Personnel)
  This document is targeted to RC or Service on how to analyze and collect crash dumps.
• When installing Windows NT 4.0, NT setup blue screens with stop: 0x0000007b inaccessible boot device (Alpha systems only)

bootsector

• Rewriting a bootsector: repair tool for Windows NT

bug codes

• Windows NT 4.0 bug codes

Chkdsk

• Chkdsk registry key information

cloning

• SID # on NT platforms—potential problems with cloning

Disk Administrator

• Disk Adminstrator cannot always save disk configuration

disk fragmentation

• Defragmentation of Hard Disks on Creo X86 Windows-Based Workflow Servers
• Measuring disk fragmentation on your server

drivers

• Where are WFS drivers for Alpha NT 3.5, 4.0?

Emergency Repair Disk

• Creating an Emergency Repair Disk (ERD)

error messages

• Blue screen with STOP 0x0000007f error on Windows NT, 2000, XP and 2003
• Blue screen after installing Intergraph NFS over previous installations of Hummingbird NFS or Legato
• Blue screen crash: Mac Services directory corrupted
• Blue screen crash with stop code: 0x0000000a – IRQL_NOT_LESS_THAN_OR_EQUAL
• Blue screen crash with stop code: 0x00000058 – FTDISK_INTERNAL_ERROR
• Blue screen crash with stop code: 0x00000079
• Error message at startup about initialization of the dynamic link library (Prinergy-specific)
• Overcoming user32.dll initialization failure errors
• When installing Windows NT 4.0, NT setup blue screens with stop: 0x0000007b inaccessible boot device (Alpha systems only)

Event Log

• NT Event Log corruption

files, can’t delete/copy

• Files cannot be deleted, copied
• Windows client can’t classify files that contain illegal NT file system characters (Prinergy-specific)

host names

• Cannot resolve host names

installation

login

• New! Can't login to workstation after installing ProCom

mirror/shadow drives

• Computer will not boot from mirror/shadow drive
• Creo NT Mirror Recovery Procedure

non-English NT

• Failed installation when Windows NT is non-English version (Prinergy-specific)

performance

• Slow application speed with Windows NT 4.0 (Intel systems only)

Performance Monitor

• Network Interface counter unavailable in Performance Monitor

Prinergy-specific

See also the Prinergy troubleshooting page.

• Error message at startup about initialization of the dynamic link library
• Failed installation when Windows NT is non-English version
• Prinergy Administrator fails to start, complaining about LEVT.dll problem
• Upon completion of a proof, annoying message box appears on the server
• Windows client can’t classify files that contain illegal NT file system characters

printing

• Changing the default NT print server spooling directory
• Disabling Print Notification dialog boxes
• HP network port disappears when trying to Add Port from Add Printer Wizard
• Upon completion of a proof, annoying message box appears on the server (Prinergy-specific)
• Windows NT 4.0 SCSI Print Fix for 2/533 Alpha Platforms

ProCom

• New! Can't login to workstation after installing ProCom

RAS

• Determing what you computer you are connecting to when dialing into a system via RAS
• RAS fails to bind properly in the Network Control Panel Applet
• RAS performance problems

registry

• Chkdsk registry key information
• Command shell file name completion
• Searching remote registries

security

• Overcoming user ID conflicts

service packs

• Determining what service pack a system is running
• Windows NT 4.0 Service Pack 4 Procedure

Services for Macintosh

• New! From PlateMaster, I can’t see jobs on my Macintosh for up to 30 minutes after rebooting
• Jumping folders in Mac OS8/Windows NT
• Mac locks up accessing files on NT4
• Services for Macintosh troubleshooting
• New! Some files are missing from the Macintosh, but not from the PlateMaster server after retrieve from tape library or individual DLT drive
• New! Some files are missing on both the Macintosh computer and the PlateMaster server after retrieval from tape library or individual DLT drive

shutdown

• Windows NT hangs on shutdown

startup

• Can’t figure out why application is auto-launching at startup
• During powerup test, system stuck at Read Test (Alpha systems only)
• Error message at startup about initialization of the dynamic link library (Prinergy-specific)
• Problems starting executables

virtual memory

• New! Warning message “Low on Virtual Memory” displays in Windows NT while RIPing in Allegro or Allegro Preview RIP

virus

• virus information page