Bugcheck on NT 4 sp6a

[duguy]

Last night my BDC got the following error : The computer has rebooted from a bugcheck. The bugcheck was 0x0000001e [0xc0000005, ox80192949, 0x00000001, 0x02022295], Microsoft Windows NT [v15.1381]. A full dump was not saved.
The only new thing installed was MS's security fix for wm_timer last Saturday.
Can any help!

 

[Guntha]

I am having the same problem on a Proliant ML350 running SP6 and Exchange 5.5 SP4. I have found minimal info and most of it says bad newly installed Hardware although I havent added, removed or changed anything in this server for over a year? Anyone else have this problem that has been able to fix?

Thanks
Alex

 

[F1lby]

Have you tried reapplying SP6a (as long as you're happy that the hardware isn't bad)?.

SP6A performs a lot of fixes if NT has gone sour.

 

[duguy]

I believe my servers problem had to do with heat. Since I changed the AC in the server room the server has been up and running fine. Hope it continues!

 

[Sanjiv123]

This happened Wednesday on our BDC running NT4 Server sp6a with Exchange Server 5.5 sp4.

Event ID 4188
Source SysMgmt
Type Error


The Compaq System Management Driver has detected that the system encountered
an NT bugcheck prior to this boot. The bugcheck data was: STOP: 0x0000000A
(0x00000114, 0x00000002, 0x00000000, 0xF1F85BBE).

Any help appreciated !

 

[Guntha]

Anyone? Server seems to reboot itself every 10-13 days with the bugcheck error.

Alex

 

[zoeythecat]

What is the exact event you see in event viewer? Do you have any possible failing hardware problems such as power supply on the server going? Any warning lights on your server?

 

[Guntha]

same as Ssanji - I called Compaq and they are no help. I applied the latest SP's for Exchange and for NT (per Compaq) and the server still does this every 2 weeks or so. I have read that it can be attributed to Motherboard or RAM you'd think with the "next business day" support they would have had their a**es out here?



The Compaq System Management Driver has detected that the system encountered
an NT bugcheck prior to this boot. The bugcheck data was: STOP: 0x0000000A
(0x00000114, 0x00000002, 0x00000000, 0xF1F85BBE).

 

[zoeythecat]

Is there an event id number in event viewer related to this error message? Could be memory, could be a number of things. Have you tried reseating the RAM?

 

[OzDog]

Guys,

We have Citrix servers doing a Stop 0x1E. We have found the problem, but can't stop it.

Our problem is to do with printing (may not help you, but for what it's worth...). HP had some driver issues - they made fundamental changes in a release of some print drivers - and the differences caused Stop 0x1e and 0x0a errors.

Our solution - put up with it until we upgrade to Win2K. Cheers,
Sam

Please let members know if you found their posts helpful.

 

[mrosenblum]

Having same issue with Compaq Proliant. WinNT4.0 Sp6a, Exch 5.5 sp4. Here is the error:

The Compaq System Management Driver has detected that the system encountered a bugcheck prior to this boot. The bugcheck data was: STOP: 0xC000021A (0xE205D528, 0xC0000005, 0x00000000, 0x00000000).

Any thoughts? No real changes lately with exception of McAfee VirusScan 7.0 Enterprise about a month ago.

This is the third time in a month that this has happend.
Michael

 

[zoeythecat]

The obvious question I would think would be the MCAFEE VirusScan 7.0 because you say it started happening at that poing. Contact MCAFEE to see if they can help you. Perhaps there are some settings that you have checked that could be causing this.

 

[F1lby]

Try disabling as many services as possible... gives you fewer items to blame.
Mcafee AV is a likely contender for NT bombing out..

 

[OzDog]

mrosenblum,

We have found the Proliant System Services (surveyor, shutdown manager, network agents etc etc) have caused instability within our systems, and as such have disabled them.

Worth a try...

Cheers,
Sam

Please let members know if you found their posts helpful.

 

[zemper]

Had this happening regularly on a Proliant 1850R. Turned out to be a hardware (system board) problem but took a long time before the system actually gave us a hardware error. Finally after weeks of this problem the problem got worse (server would crash with Bugcheck error after being up for a few minutes) and we started getting a processor failure message. Until the hardware error occured we were not sure if it was hardware or OS problem.

Ensuring we were on latest SP's and Support Packs did not help.

I also think heat may cause the problem. Odd that it seems to be happening on Compaq Servers the most. Anyone having this issue on non-Compaq hardware?

 

[zoeythecat]

I have Dell Servers in my current environment. We have had a few servers for several years without these type of problems happening. In my last environment we had all Compaq Proliant Servers and strangely we did have these type of errors from time to time.

Does not give me a warm feeling about Compaq Servers

 

[mrosenblum]

Removing Virus Scan would be a great idea, but it's not really a possibility. I did upgrade all of the Compaq Insight manager software, and this week have not crashed. (fingers crossed). I'll keep you informed if it goes again. Next step will be to follow OzDog's advice, and completely remove the Compaq software. Gee, then I'll have a white box.... :-(

Michael

 

[Wiggy999]

We have Dell PowerEdge servers and suddenly are getting a similar crash/bugcheck :

0x0000001e 90x0000005,0x801b485a,0x00000000,0x000005b5

Looking at the check, it does seem to be print related, as it crashes trying to execute either HPRASDD.DLL (an HP print driver : RASDD.DLL: deals with printer languages based on raster (bitmap)images, including PCL and most dot matrix printer languages, or at the NT driver (RASDD.DLL). It sounds like maybe a corrupt print job could be the cause? Yikes... Our PDC has crashed once or twice a week lately with the same bugcheck. No other changes made to the system, NT 4.0 SP6a.

 

[Wiggy999]

Update : I ran the update for the WM_Timer patch (328310i)and our PDC hasn't crashed since. Maybe that's the fix ???

 

[HJallab]

I have compaq proliant 1850R, and I got the error server crahes and after I reboot it works for minutes and crashes a gain. I formatted it and I installed Win2000 server and applied SP3, but it still the same it crashes after few minutes. It seems to be a hardeware problem.

Can any one help ?