Blue Screen O' Death error

[danno74]

Haven't seen one of these in awhile. Can anyone give me any clues?

"ADDRESS80444D33 BAS AT 80400000, DATESTAMP 39760637 NTOSKRNL.EXE"
"KMODE_EXCEPTION_NOT_HANDLED"

Also, I found where Windows put the memory dump ( I think), in c:\winnt\minidump, does anyone know how these are read? I can look at it in notepad, but that's garbled. If not no biggie.

 

[Grymz]

Here's microsoft's take on your error

http://support.microsoft.com/defaul...port/kb/articles/Q294/7/28.ASP&NoWebContent=1

if that doesn't let us know

 

[danno74]

It does not include the in Win32k.sys portion in the error we get. And it wasn't upon restart, it was in the middle of using W2K. Would this make a difference?

 

[Grymz]

Well it might I did find this about the error without the win32k.sys

We're using Win2K workstations in a network with a Microsoft Small Business Server (SBS) 4.5 server and a Win2K server. After we installed SP4 on some workstations, they all started to produce a blue screen, with the message Stop 0x00000001e (0xc00000005,0xbfeaed16, 0x00000000, 0x00000000) KMODE_EXCEPTION_NOT_HANDLED Address: bfeaed16 base at bfeae000, datestamp 3e25bc59 - mup.sys.
• The Microsoft article "List of Networking Fixes in Windows 2000 Service Pack 4" (

http://support.microsoft.com/?kbid=815023)

explains that SP4 replaces mup.sys to solve a buffer overflow security vulnerability. I've seen articles in several newsgroups linking this problem with the Novell client. In the past, we've used a Novell server, and therefore a Novell client was installed on these systems. We uninstalled the Novell client and shut down the Novell server. Today, I found the following post in the newsgroups:

”There's a problem with the mup.sys in SP4. As a temporary workaround, set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Mup\DisableDFS to 0. This gets rid of the blue screen." Microsoft is supposedly working on a fix (updated MUP) according to another poster. I haven't been able to test these solutions because we uninstalled all SP4 installations.

 

[bcastner]

My guess is faulty RAM.
The Windows kernel detected an illegal or unknown processor instruction. A Stop 0x1E condition can be caused by invalid memory and access violations similar to those that generate Stop 0xA errors. This default Windows error handler typically intercepts these problems if error-handling routines are not present in the code itself.

http://support.microsoft.com/?kbid=183169

http://support.microsoft.com/?kbid=195857