Microsoft KB Archive/99246

= Q&A: Error Messages =

PSS ID Number: 99246

Article Last Modified on 11/20/2003

-

The information in this article applies to:


 * Microsoft Windows NT Server 3.1
 * Microsoft Windows NT Workstation 3.1
 * Microsoft Windows NT Advanced Server 3.1

-



This article was previously published under Q99246



SUMMARY
The following information is also included in the Windows NT and Windows NT Advanced Server Frequently Asked Questions (FAQ) document that is available in the WINNT forum. More information on this topic may be available from Microsoft Information Services. Microsoft Information Services are available on the World Wide Web by connecting to http://www.microsoft.com. The FTP site is located at ftp.microsoft.com.

This article contains the Common Error Messages section, including the following topics:


 * Error 0000001E
 * NTVDM Error
 * Error 0x00000069 or 0x00000067
 * System Error F002
 * Setup Fails with SCSI Read Request Error
 * LogErrorEntry Error (UniqueId=300)



Error 0000001E
Question:

What should I do about error 0001E?

Answer:

This error is caused by an exception error that is not handled at any level. It generally refers to a file system problem. Run CHKDSK or another similar utility on the drive in question. If your hardware is on the hardware compatibility list, please submit a bug report.

NTVDM Error
Question:

When I run MS-DOS or Windows 3.1 applications, I receive the following error message. Why?

Insufficient memory or Disk Error in NTVDM or NTVDM Error's.

Answer:

Try the following:


 * Increase the page file size to at least 20MB.
 * Make sure the video card is on the hardware compatibility list (1193HW.DOC). If it is not, try using the standard VGA driver.
 * Verify that the WOWEXEC.EXE is not corrupted by copying over a clean copy.

Error 0x00000069 or 0x00000067
Question:

I get Error 0x00000069. What should I do?

Answer:

This is an initialization error that occurs when Windows NT tries to talk with the hard drive controller. It can be caused by many things. Try the following work arounds:


 * Slow down the DMA transfer rate on the controller.
 * Make sure both ends of the SCSI bus are terminated.
 * Make sure there are no IRQ, or memory address conflicts.
 * Make sure you are not using a faulty or unsupported driver.
 * Make sure NTDETECT.COM is in the root of the boot drive partition. Missing Windows NT files can also cause Error 69.

System Error F002
Question:

What is System Error F002?

Answer:

System Error F002 is usually generated when there is a faulty piece of hardware, like a bad memory chip. It can also be caused by a hardware incompatibility caused by one of the following:


 * Memory parity errors
 * Adapter asserting an I/O channel check on the bus, (VGA or network cards)
 * Math coprocessor error

If any of these occur, run your computer manufacturer's system diagnostic utilities.

Setup Fails with SCSI Read Request Error
Question:

Why do I get the following error during Windows NT Setup:

SCSI read request failed Arc status 8 Srb status 0084

Answer:

AutoCheck is unable to resolve file system or FAT problems on the drive. Run a diagnostic utility such as CHKDSK on the file system and fix any problems you find. Afterwards, reinstall Windows NT.

LogErrorEntry Error (UniqueId=300)
Question:

What should I do about a LogErrorEntry error with UniqueId 300?

Answer:

If you receive the following error during the installation of Windows NT on a machine with an Adaptec 1542b card, remove the BUSLOGIC.SYS file from the Setup disk and reinstall.

LogErrorEntry: logging SCSI error packet. ErrorCode=Internal adapter error. PathId=0,TargetID=0,Lun=0,UniqueId=300.

Additional query words: prodnt

Keywords: kbother KB99246

Technology: kbWinNT310Search kbWinNTAdvSerSearch kbWinNTAdvServ310 kbWinNTS310 kbWinNTS310search kbWinNTsearch kbWinNTSsearch kbWinNTW310 kbWinNTW310Search kbWinNTWsearch

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© 2004 Microsoft Corporation. All rights reserved.