May 13th, 2003, 06:24 PM
BSOD on Win 2k!!! Boot up fails!!!
I was booting up on win 2k on my home machine when I got a BSOD, I tried to reboot and got the same one. I have tried to enter the BIOS and troubleshoot options but have had no luck. I am on a network using Novell netware so that might be part of the problem. This is what is at the top of the screen.
STOP 0x0000001E (0x00000005, 0xed5163bc, 0x00000000, 0x00000008)
Any help would be greatly appreciated.
May 13th, 2003, 06:29 PM
Can you get into Safe mode at all? It's most likely a driver or hardware problem. There was another post with a similar problem recently... search the archives for it. There were a number of good links posted within it. Also, search the Microsoft KB (www.microsoft.com/support) and you should be able to find quite a bit of information to help you at least figure out what the problem is, and maybe even help you correct the problem.
May 13th, 2003, 06:34 PM
Nope, can get into safe mode, I probably have to either boot from a disk (dont have) or wipe the hard drive and reinstall windows.
\"The wise programmer is told about Tao and follows it. The average programmer is told about Tao and searches for it. The foolish programmer is told about Tao and laughs at it.
If it were not for laughter, there would be no Tao.\"
May 13th, 2003, 06:42 PM
A "STOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED" error message indicates that an error condition was detected by the kernel and Windows NT was unable to continue running because of this error condition. The types of problems that can cause a "STOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED" error message are very similar to the problems that cause a "STOP 0x0000000A" error message, such as bad pointers, invalid addresses and other types of access violations. The STOP 0x0000001E bug check identifies an error that occurred in a section of code where no error handling routines exist. Note that most exceptions are generated directly in the section of code that is running.
The top four lines of a STOP 0x0000001E generally appear as:
STOP: 0x0000001E (0xAAAAAAAA,0xBBBBBBBB,0xCCCCCCCC,0xDDDDDDDD) KMODE_EXCEPTION_NOT_HANDLED
AAAAAAAAA from BBBBBBBB (CCCCCCCC,DDDDDDDD)
Address BBBBBBBB has base at XXXXXXXX - MODULE1.SYS Address CCCCCCCC has base at YYYYYYYY - MODULE2.SYS
The four hexadecimal parameters after the STOP code (0xAAAAAAAA, 0xBBBBBBBB, 0xCCCCCCCC, 0xDDDDDDDD) have the following meanings:
0xAAAAAAAA is a code that identifies the exception that was not handled.
0xBBBBBBBB is the address at which the exception occurred.
0xCCCCCCCC is the first parameter of the exception, and sometimes this is another address in code.
0xDDDDDDDD is the second parameter of the exception, which can vary in meaning.
Interpreting the Parameters
Usually the exception address identifies the driver or function that caused the problem. Always note this address and the date of the driver or image that contains this address.
The first parameter is a Windows NT error code, and all error codes are defined in the Ntstatus.h file (which can also be found in the Windows NT 4.0 SDK). The first parameter tells you the type of error.
The second parameter is also important because it tells you in what code module the error occurred. This can frequently point to an individual driver or piece of hardware that is at fault, which will generally be listed on the third line of the STOP screen.
The last two parameters vary depending upon the exception that has occurred. Typically, you can find a description of the parameters included with the name of the error code in the Ntstatus.h file.
If there where no parameters to the error code, these will be 0x00000000.
For example, in the following STOP error message, an access violation (0xC0000005) occurred in module Srv.sys, which is the kernel mode server service:
STOP: 0x0000001E (0xC0000005, 0xFCA733B9, 0x00000000, 0x00000000)
KMODE_EXCEPTION_NOT_HANDLED 0xC0000005 from 0xFCA733B9 (0x0, 0x0)Address FCA733B9 has base at FCA70000 - SRV.SYS
Note that no parameters went with this error code.
How to Troubleshoot a "STOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED" Error Message
Try to replace the driver that is identified in the STOP error message, either with a known good copy from your installation media, or with an updated version from the manufacturer.
Disable the driver that is identified in the STOP error message or any newly installed drivers.
Verify that any new hardware or software is properly installed. Disconnect the new hardware or replace it to see if this resolves the issue.
If you have a video driver that was not supplied with the operating system, try switching to the standard VGA driver or a driver that is compatible with the operating system.
View the following Microsoft Hardware Compatibility List Web site to verify that all your hardware and drivers are compatible with the operating system:
Run any system diagnostics that are supplied by your computer manufacturer, especially a RAM check. If this is a new installation of the hardware or software, contact the manufacturer for any requires updates for drivers or firmware.
Disable all filter drivers, such as remote control software, antivirus programs, backup programs, and so on.
This is from:
Our scars have the power to remind us that our past was real. -- Hannibal Lecter.
Talent is God given. Be humble. Fame is man-given. Be grateful. Conceit is self-given. Be careful. -- John Wooden
May 13th, 2003, 06:53 PM
you should find these useful. moreso the second link.
A memory access violation occurred. Parameter 4 of the Stop error (which is Parameter 1 of the exception) is the address that the driver attempted to access
if you haven't installed any new hardware recently obviously you can't take it out. check the other links on the second link above to try and sort this.
The second parameter in the parameter list is the memory address at which the unhandled exception occurred.
(0x00000005, 0xed5163bc <-the instruction here), 0x00000000, 0x00000008 <-tried to access here))
possibly an invalid instruction? make sure you ram isn't after coming loose?
Hmm...theres something a little peculiar here. Oh i see what it is! the sentence is talking about itself! do you see that? what do you mean? sentences can\'t talk! No, but they REFER to things, and this one refers directly-unambigeously-unmistakably-to the very sentence which it is!