win 2000 blue screen

[omer]

in win2000.i get this error in blue screen occasionally.what is this and how to solve it.

stop:0*0000001E(.........)
(kmode_exception_not_handled)
begining dump of physical memory.completed dump.... contact.....

[Adrian]

<font color=blue> Like once in a blue moon Windows 2000 will crash, resulting in you seing that error, then it will automatically re-boot. Dont worrk its perfectly normal, if however you can recreate this error while you are doing something specific, it might be a problem. </font color=blue>

<font color=red> _____ _____ ____ </font color=red>
<font color=red> " Eat More Cheese " </font color=red>

[Andy-S]

Kmode_exception_not_handled errors are due to an exception occurring which is not handled by the calling function. If the calling function does not handle the exception then it is passed through the stack to see if any previous functions have a handler for it. If not the default kernel exception handler is called and the blue screen is displayed. These issues are typically driver problems. Have you added any new hardware or changed drivers recently?

[Adrian]

<font color=blue> Yep that is so true, make sure you have all the latest drivers compatable with win2000, make sure you install service pack one, and if possible get the latest bios update for your mobo. </font color=blue>

<font color=red> _____ _____ ____ </font color=red>
<font color=red> " Eat More Cheese " </font color=red>

[omer]

yes i've changed my tnt2 drivers from det3 6.31 to det 6.50.i 've upgraded my bios but this problem continues.before and after

<P ID="edit"><FONT class="small">Edited by omer on 02/27/01 11:11.</FONT></P>

[Adrian]

<font color=blue> When does it normally happen, can you recreate it at will. </font color=blue>

<font color=red> _____ _____ ____ </font color=red>
<font color=red> " Eat More Cheese " </font color=red>

[omer]

no i cannot create it on will.it happens at any time.there is no tme for it.

[Adrian]

<font color=blue> Sorry for asking all these questions, but it makes it easier to pinpoint the problem............... Ok did you do a clean install of win2000, whats the latest software you have installed, and are you running service pack 1 </font color=blue>

<font color=red> _____ _____ ____ </font color=red>
<font color=red> " Eat More Cheese " </font color=red>

[omer]

yes i.ve clean istalled two times with formatting.and i've not installed any new software previously .
yes i am running sp#1
<P ID="edit"><FONT class="small">Edited by omer on 02/28/01 07:37.</FONT></P>

[Andy-S]

It definitely sounds like you have a driver problem. Microsoft provide a utility called driver verifier which will run a variety of kernel mode tests on your drivers to ensure that the driver operates as expected. You should test one driver at a time to see if this provides any clues.

Driver verifier is shipped with Windows 2000 and can be started by using verifier.exe which is in the \winnt\system32 folder. When the GUI appears select the "settings" tab and then select the driver you wish to verify. I would check all the 3rd party drivers before the Microsoft one's.

The details of how to use driver verifier are found at http://support.microsoft.com/support/kb/articles/Q244/6/17.ASP

Hope this helps

[arcmicro]

I've had a similar problem, but it was my video drivers. I happened to have another drive to boot from. In which, I went in my System32 folder and deleted the drivers that were causing the problem, and re-installed the TnT2 6.3.1 drivers, and the problem went away. However, this doesn't sound like a video driver problem. What exactly does the screen say when you get this? Your first post mentioned something about memory. Could your memory be bad?(system memory, that is).
If it's not the RAM, it's almost 100% a driver issue....which one, i'm not sure. Wish I could be of more assistance.

[CyberSnoop]

Hmm... I don't get the occasional KMODE_EXCEPTION_NOT_HANDLED, I get it around 3 times a day....

Clean Win2K install, no SP yet, compatible hardware (GeForce 2 MX (Detonator 6.5), Ext. Modem, HP 4100C scanjet, Canon BJC 4310SP - all with latest Win2k drivers)

How, why and how to get rid of it!

Happens randomly, using WinAmp, browsing the Net, with 3D Studio MAX and jest about anything and everything else. Tried a full driver re-install, Win2k re-install (Clean) etc.. still no success....

Help? Please? .... ;)

[Andy-S]

As I stated in a previous post the majority of KMODE blue screens are due to drivers causing exceptions and not providing an exception handler. In your case the easiest way to debug it is to perform a clean re-install of Windows 2000 (including formatting the HDD), add one or two peripherals at a time and run the system for a day to see if the blue screen re-occurs. This should help narrow it down.

[torsion]

I am running win2kpro sp1 and was using the nVidia Detonator3 6.50 from nVidia's website.

I would get BSOD's all day long.
Get newer Detonator drivers from

http://www.the-cad.com/Drivers.htm

All my problems are gone now. Everything works perfect. No more BSOD's. I hope this fix works for everyone else.

I am using Detonator3 7.52, might test some later releases soon. Good Luck.

[torsion]

New 7.58 WHQL certified drives for nVidia and win2kpro.

http://www.m3dzone.com/files.php?directory=Videocards/NVIDIA/Drivers/W2k/

[jvelte]

The information in this article applies to:

- Microsoft Windows NT Server versions 3.1, 3.5, 3.51, 4.0
- Microsoft Windows NT Workstation versions 3.1, 3.5, 3.51, 4.0
- Microsoft Windows 2000 Professional
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
-------------------------------------------------------------------------------

SUMMARY
=======

Windows NT generates a bug check code on a blue screen when a problem is
encountered. These codes can assist you in troubleshooting the problem.

MORE INFORMATION
================

The STOP 0x1E code is a common bug check code. The exception address usually
pinpoints the driver or function that caused the problem. You should note this
address as well as the link date of the driver or image that contains this
address to assist Microsoft Support Engineers if it becomes necessary to contact
Microsoft.

Example
-------

STOP: 0x0000001E (0x80000003, 0xBFC0304, 0x0000000, 0x0000001)
[bug check code] ([1st], [2nd], [3rd], [4th])

Parameter definitions:

1st = The exception code that was not handled
2nd = The address at which the exception occurred
3rd = Parameter 0 of the exception
4th = Parameter 1 of the exception

On non-Intel-based computers, if the address of the exception is 0xBFC0304, the
bug code is the result of a cache-parity error on the CPU. If the problem occurs
frequently, contact the hardware's manufacturer.

Possible Cause and Workaround
-----------------------------

The STOP 1E message may occur after the first reboot during Windows NT or Windows
2000 Setup, or after Setup is finished. Three possible causes of the problem
are:

1. Lack of disk space for installation.

2. Third-party video drivers (and the Microsoft Windows NT or Windows 2000
Win32k.sys driver).

3. System BIOS incompatibilities.

To resolve this issue, use the appropriate method below:

1. Reinstall on another hard disk when disk space is low.

2. Remove the third-party video driver.

3. Upgrade the system BIOS.

This problem should not occur very often. If it occurs repeatedly, make sure a
debugger is connected and the computer is booted with the /debug switch. Refer
to the following Microsoft Knowledge Base article for more information:

ARTICLE-ID: Q148954
TITLE : How To Set Up A Remote Debug Session Using A Modem


J. Velte
MCSE