If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
06
fatal exception at 06 what is this?
|
#2
|
|||
|
|||
06
fatal exception at 06 what is this?
That is an error that occurred with DOS and Windows 3.1. It hasn't been happening with Windows 95, 98, or later, possibly because people no longer need to use EMM386. THis is the message I used to send to people who had EMM error 06. This error could indicate that there's a bad spot on the harddisk that has corrupted a part of that program. Since this is easy to correct, I suggest that you start there. Run ScanDisk and tell it to do a surface scan; I'd run it two or three times, just to make sure. If ScanDisk finds any bad spots, you then have to reinstall the affected programs. The next most likely cause is a bad memory chip. If you have an analysis program (such as AMIDiag) run it two or three times. Unfortunately, memory errors tend to be intermittent, so these analysis programs may fail to find a defective chip. In that case, you may have to resort to swapping chips in an out of the machine. If you recently installed a peripheral card, you should check to make surethat its jumpers or switches are set correctly. In particular, if the computer contains a network card, then the EMM386 line in Config.sys must exclude the address range used by the RAM on the network card. To test whether this is an issue, add X=A000-EFFF to the EMM386 line in Config.sys. If this exclusion corrects the problem, you will then have to find the correct addresses to exclude -- by consulting the literature that came with the card or by running its configuration program. Here's an article from MSKB that explains some alternatives. Title: Windows Err Msg: EMM386 Exception Error #6 Document Number: Q94279 Publ Date: 22-FEB-1994 -------------------------------------------------------------------------- The information in this article applies to: - Microsoft Windows operating system version 3.1 - Microsoft Windows for Workgroups version 3.1 -------------------------------------------------------------------------- SUMMARY ======= You may receive the following error message while running an MS-DOS-based application under Windows or Windows for Workgroups: EMM386 Exception Error #6 This error message indicates that an MS-DOS-based application has caused the processor to execute an invalid instruction. Although the error message is provided by EMM386.EXE, it is not the cause, nor is it directly related to the problem. The error is probably caused by a corrupt .EXE file or a bad memory chip. MORE INFORMATION ================ When Windows starts, it turns off EMM386.EXE but leaves its error handler installed. When the CPU notifies Windows of a problem, it passes the error to the default handler, which in this case is EMM386.EXE. EMM386 Exception Error #6 indicates an "invalid opcode." According to "Microsoft's 80386/80486 Programming Guide" second edition (pages 122-123), this error can be caused by either of the following: - The processor tries to decode a bit pattern that does not correspond to any legal machine instruction. - The processor tries to execute an instruction that contains invalid operands. Both situations indicate the same thing--the CPU is trying to execute instructions, but is being given random values from the wrong memory location. This can be caused by one of the following: - The application gave an invalid jump instruction, causing a jump to an invalid memory location. - The application gave a correct jump, but the memory it jumped to is corrupted. The most likely cause of these problems is either a corrupted .EXE file or a bad memory chip. If the problem occurs on more than one distinct program, it is probably caused by a bad memory chip. For example, if the problem occurs when you choose Open from the File menu in Microsoft Windows Write and Microsoft Windows Notepad, the error is probably being caused by a corrupted common dialog box .DLL file (COMMDLG.DLL). But if the problem occurs in two applications that do not share any .DLL files, the error is likely caused by a bad memory chip. Bill Starbuck (MVP) |
#3
|
|||
|
|||
06
What Are Fatal Exception Errors
http://support.microsoft.com?kbid=150314 How to fix a fatal exception error.: http://www.computerhope.com/issues/ch000223.htm http://www.aumha.org/kbefe.htm http://www.colba.net/~hlebo49/fatlexer.htm -- Glen Ventura, MS MVP W95/98 Systems http://dts-l.org/goodpost.htm wrote in message ... fatal exception at 06 what is this? |
#4
|
|||
|
|||
06
Most of these error messages have been exhaustively
discussed in the newsgroups, so before posting a new enquiry, try doing a search of past posts in Google Groups. See this page for information on how to do it. http://www.pcbuyerbeware.co.uk/Software.htm#google Eric, http://www.pcbuyerbeware.co.uk/ -----Original Message----- fatal exception at 06 what is this? . |
Thread Tools | |
Display Modes | |
|
|