server crashing help

[mattlicentia]

We have a metaframe xpe installation running on two ibm xseries 220 servers, every week or so one of the servers will blue screen with the following error (no sure if i have enough zeros in some places)

stop 0x0000000d1 (0x00000054x000000054x000000002x000000x0b8f42b1a)
Address b8f42b1a BASE AT B8F3E0000 DATE STAM 2A148BD9N TERMDD.SYS
DRIVER IRQL NOT LESS OR EQUAL

at first i thought i could be printer drivers so i disabled all lpt and com port mapping only leaving network printers which are xerox printers and hp with the hp printer using the microsft drivers. There is no regular occurance it just seems to happen. Have even tried doing a daily reboot of the server with no effect.

Please Help

matt

 

[Voyager1]

1. Are you running on Win2K or on NT4 TSE?
2. Has anything changed recently, anything added or removed?
3. What is your service pack level, and have you re-installed the SP lately?

The MS Knowledge Base points to a couple of problems in termdd.sys that were supposedly fixed in NT4 TSE SP4 or greater. Termdd.sys is actually a multiple instance keyboard/mouse handler. I have also seen problems occur before if (not saying this happened) the NT4 service pack was installed, and not the Terminal Server version - they are different.

Hope this helps - post your progress so we can try to help... - Bill

"You can get anything you want out of life, if you'll just help enough other people get what they want" - Zig Ziglar

 

[mattlicentia]

hi

the server is a w2k with service pack 2 and latest hotfixes. Metaframe is a feature release 1. We have being having these probelm since installtion of the metaframe which was about a month ago. The probelms seem to occur when users are on the system and not overnight when the user load is less


matt

 

[CitrixEngineer]

It's almost certainly a driver issue, although it may not be printers this time.

Other drivers that can cause these issues include (but are not limited to) SCSI, NIC and graphics.

I used to see this kind of issue on DELL servers, and resolved it by getting the latest drivers from the manufacturer's websites.

Is there anything else in the bugtrap message that gives any ideas? Lists of other drivers?

I hope this helps

 

[mattlicentia]

the only thing in the bug trap is the termdd.sys.The probelm does not happen at on a regular on predefined basis a server could go for 1 2 weeks without a probelm but when it happens it causes havoc.
Other things to mention:

1)one a two applicaton do cause a application error with dr watson?
2)mcaffee netshield installed virus scan 4.5
3)All printers are network printers have disabled client printing (printers are: xerox4025,xerox2025,xerox4525,techtronix phaser 850n,hp laserjet 4000 (hp using microsft drivers)
4)there is a application which maps lpt ports to network printers

 

[mattlicentia]

The one of the server's has just done it again i thinking on two lines at the moment. The server's (this might be my imagination). The server's seem to be doing this on a regular intervals with this paricular one doing the same thing last monday. It might do this once more next monday and then it may go to another day but then it will happen on the same day a couple more times (not at the exact same time through)

1.Has anyone had any trouble with belkin omnviews with metaframe (just a thought!!!)

p.s i checked all drivers they are the lattest ones!!


Please help this is driving me mad


matt

 

[Jehova]

I suggest investigating the Video end of things. We had no-end of this problem when running with Compaq servers with the Remote Insight Lights Out board (for remote controlling even when powered off). It introduced another video card in the system.

After we ripped those out, we're only really getting blue screens associated with bad print drivers. Anyone know why HP can't just come out with a single driver that works, is stable and is good for all their printers? Sigh.

 

[mattlicentia]

Hi,

i still having no luck, but maybe a bit further foward i contact microsoft as a incident call they told me after looking at the memory.dmp that the blue screen was being caused by a call to wdica.sys and should contact citrix.Any body ever had an issue with this

If not anyone no how to contact citrix on a per incident basis as from what i read they insist you take out a minium 25 indicdent plan which seems to be a bit stupid??


regards

matt