topic Re: STOP: 0x0000001E in ntoskrnl.exe in ProLiant Servers (ML,DL,SL)

STOP: 0x0000001E in ntoskrnl.exe

Shawn_115 — Thu, 10 Nov 2005 14:13:16 GMT

I have two ISA servers ML530 running Windows 2000 Advanced Server, SP4 with all latest MS Updates and running PSP 7.40a. This is becoming quite a pain as the error is happening quite frequently.

Any help would be appreciated. I've attached a screen cap of the Stop Message.

Re: STOP: 0x0000001E in ntoskrnl.exe

Igor Karasik — Thu, 10 Nov 2005 15:47:51 GMT

Try to use
http://support.microsoft.com/kb/192463/
to match the exception address to the driver name.
If you be able to determine faulty driver - you have chance.

Re: STOP: 0x0000001E in ntoskrnl.exe

Oleg Koroz — Fri, 11 Nov 2005 00:42:34 GMT

http://support.microsoft.com/search/default.aspx?spid=global&query=0x0000001E+%280xC0000005+and+Ntoskrnl.exe&catalog=LCID%3D1033&pwt=false&title=false&kt=BOOLEAN&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=14&y=11

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=PSD_EL040429_CW02

http://h18023.www1.hp.com/support/files/server/us/download/23331.html

Re: STOP: 0x0000001E in ntoskrnl.exe

Thomas Bianco — Fri, 11 Nov 2005 11:21:46 GMT

stop 1e (AKA KMODE_EXCEPTION_NOT_HANDLED) means something in the kernel did something it shouldn't have, and the system doesn't know how to handle it.

start with drivers, 90% of kernel problems are drivers, update any need ones and remove any you don't use.

Re: STOP: 0x0000001E in ntoskrnl.exe

Shawn_115 — Mon, 21 Nov 2005 14:54:46 GMT

I've tried the dumpchk / pstat but everything just points back to the kernel. So I am at a dead stop as there is nothing in MS Knowledge Base nor have I been able to find anything in HP's website.

While I agree it's probably a driver, there has to be a way pin point it. These are production servers and I don't have the ability to take them offline uninstall all the drivers and re-install the support pack *hoping* that fixes the issue.

Any further suggestions or guidance would be appreciated.

Re: STOP: 0x0000001E in ntoskrnl.exe

Shawn_115 — Mon, 21 Nov 2005 14:57:25 GMT

Oh I have updated the firmware using the Firmware CD, but the only thing that updated was the hard disk firmware because all other firmwares were up to date.

Re: STOP: 0x0000001E in ntoskrnl.exe

Joshua Small_2 — Tue, 22 Nov 2005 00:52:30 GMT

What (if any) antivirus are you running? Some obsolete scanners can do this.

Are you using Veritas backup exec? There are known issues there.

If you say two different servers are doing this, it is most likely related to some piece of software you are running.

To be safe, it may be worth launching the Insight Offline Diagnostics and checking the hardware.

Re: STOP: 0x0000001E in ntoskrnl.exe

Shawn_115 — Tue, 22 Nov 2005 10:37:46 GMT

I am running the latest version of Symantec Anti-virus Corporate Edition. (10.0.1.1000) and I am running zero backups on these servers (that sounds scary, but it's not).

Re: STOP: 0x0000001E in ntoskrnl.exe

Cory Berends_1 — Wed, 30 Nov 2005 13:30:53 GMT

Shawn were able to figure this out. I have 12 Citrix servers that do this to me as well. All HP BL30p. The only thing I can see if that I have Symantec Antivirus Corporate Editon like you do.

Thanks
Cory B.

Re: STOP: 0x0000001E in ntoskrnl.exe

The Spartan — Fri, 02 Dec 2005 03:22:36 GMT

Hi,

Try disabling hyperthreading option in the bios.

Re: STOP: 0x0000001E in ntoskrnl.exe

Cory Berends_1 — Fri, 02 Dec 2005 07:23:19 GMT

Hyperthreading is already turned off, any other ideas?

Re: STOP: 0x0000001E in ntoskrnl.exe

Shawn_115 — Fri, 02 Dec 2005 14:08:36 GMT

Hyperthreading is not available on my servers. (too old)

I still have never resolved this but I've been having some other bigger issues as of late so it's not the highest priorities since they seem to have been more stable lately.

However, I have noticed that the likely hood of a BSOD/ASR greatly increases during while attempting to make a Terminal Services connecting. Particularly on one of the servers.