It's a disk controller card.
Reapplying a service pack shouldn't hurt, as long as you're aware that
subsequent security and other fixes (updates) that you applied may also
need to be reapplied.
NTOSKRNL may be the process identified in your BSOD, but I believe that
its misbehavior can be caused by other processes with intimate (somewhat
privileged) relationships to the OS nucleus. Certain hardware drivers
are an example of that circumstance. One cannot, unless I'm really
mistaken, blame the NT kernel code for all errors it is involved in. In
the case of that controller card driver, the driver was causing the
exact ntoskrnl 1E error you report; the error did not occur with the
newer driver supplied by Promise when they analyzed the reported problem.
There's a chance that some other driver-type software is causing your
problem, particularly if it was written before SP4 availability. Worth
looking into.
Paul wrote:
> we don't have one of those cards....by the way, what type of card is it?
>
> since the process in question is ntoskrnl.exe, would reapplying the service
> pack help?
>
> thanks for responding
>
>
>
> "Dan Seur" wrote:
>
>
>>Do you have a Promise UDMA66 PCI card? If so, a problem with their
>>drivers and SP4 surfaced about 3 years ago, yielding the 1E error. Try
>>the latest drivers.
>>
>>It's time-consuming, but you might scan the hits from Googling for
>>"error 1e" - no quotes. Something might ring a bell...
>>
>>Paul wrote:
>>
>>
>>>We have a Win2k terminal server w/sp4. The server is blue screening almost
>>>every day. Sometimes twice a day. The server has plenty of hardware
>>>resources - nothing is being maxed out. The server is a Proliant ML370 G3
>>>dual processor machine. I have worked with HP support and updated every
>>>possible driver, firmware, and bios. the HP tech says it's an operating
>>>system issue. The process referenced in the blue screen is ntoskrnl.exe.
>>>The hexidecimal#s caught by HPs log is the following: 0x00000001E:
>>>(0xc0000044,0x804a475c,0x00000000,0x00000000). Would reapplying service
>>>pack 4 help? Any advice would be great....thanks
>>>
>>>
>>>
>>>---
>>>avast! Antivirus: Inbound message clean.
>>>Virus Database (VPS): 0615-2, 04/12/2006
>>>Tested on: 4/13/2006 3:26:34 PM
>>>avast! - copyright (c) 1988-2004 ALWIL Software.
>>>http://www.avast.com
>>>
>>>
>>>
>>
>>
>>
>>---
>>avast! Antivirus: Outbound message clean.
>>Virus Database (VPS): 0615-2, 04/12/2006
>>Tested on: 4/13/2006 3:34:49 PM
>>avast! - copyright (c) 1988-2004 ALWIL Software.
>>http://www.avast.com
>>
>>
>>
>>
>
>
>
> ---
> avast! Antivirus: Inbound message clean.
> Virus Database (VPS): 0615-2, 04/12/2006
> Tested on: 4/13/2006 5:02:40 PM
> avast! - copyright (c) 1988-2004 ALWIL Software.
> http://www.avast.com
>
>
>
---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 0615-2, 04/12/2006
Tested on: 4/13/2006 5:17:47 PM
avast! - copyright (c) 1988-2004 ALWIL Software.
http://www.avast.com
Similar Threads
