Citrix server blue screens

[tpulley]

I am getting a blue screen of death on a newly built Citrix server. OS 2000, sp3 + a some hotfixes. Citrix sp 4. About 3 times a day (give or take a time), the server will crash. It has a stop error Kmode_exception_not_handled
Stop 0x0000001e, 0xc0000005, 0xa00bd537, 0xall 0's, ox allo's. Win32k.sys.

By what I read there were some M/S hot fixes for the win32k.sys (in Sp4), got them. Still happening.

Sent a bug check file to M/S, they say it is because of VDTW30.sys that the server dies.

Anyone here have/had problems with this, like this? Seen a resolution?

Background... This server was originally built (by me) about 3.5 yrs ago. I recently formatted it and reinstalled os and patches, then Citrix back to where it was. Got the blue screens immediately. It ony happens when users are on. It ran fine from Friday till this am. We had a snow day Friday so usage was very light. This am things were back to normal and just as it had been doing mid morning, it blue screened again. Same message it has been giving all along. Any ideas????

 

[itsp1965]

Do you happen to have any third party software (like a Citrix print mgmt util) or hardware (like a modem pool) that talks to the Citrix server at a hardware level?

 

[tpulley]

No. Nothing liek that. This actualy started rebooting before I put apps on it as well. The apps loaded though are office 2k, solomon and cystal reports. That is about it.

 

[itsp1965]

Tpulley I checked the Citrix support site and there could be a variety of reasons as to why you have received this error message. Some are related to what I mentioned regarding third party printing tools and drivers, could be a prob with the video driver. They all mention trying the recommended MS fixes for the prob
To troubleshoot Stop error 0x0000001E
1.
Make sure that you have adequate disk space, especially if you're performing a new installation.

2.
If the Stop error message identifies a specific driver, disable it and contact the manufacturer for an updated driver. If you can't start your computer, try starting in safe mode to remove or disable the driver.

3.
If you have a non-Microsoft-supplied video driver, try switching to the standard VGA driver or to a suitable driver supplied with Windows 2000.

4.
Disable any newly installed drivers.

5.
Verify that you have the latest system BIOS. Your hardware manufacturer can help you determine whether you have the latest version or help you obtain it.

6.
Disable BIOS memory options such as caching or shadowing.

Hope this helps.

 

[jcIT]

I am assuming (you were not clear in your message) you are running win2k sp4 with citrix xp fr 3.

If this is your configuration, then your doomed %-(

There are so many issues with this type of configuration that I would recommend you rethink your installation configuration.

We went through this pain about 4 months ago. 3 server farm, and all 3 servers would just die.

Go back to Win2k sp2 and citrix FR-3. We bit the bullet rebuilt each server and we are now 4 months without so much as a hang-nail.

 

[tpulley]

That doesn't sound good... But I don't fit this same configuration as what you described. I am W2k + sp3, Metaframe 1.8 fr1 + sp4. I did the research before I tackled this and it appeared to me that this was one of the least painful combinations.

M/S has pointed me to a hotfix that may help. It appears that my vdtw30.dll is dated 1999. This even after applying sp4. Not sure what it supposed to be. M/S thinks this is the culprit. Anyone have metaframe 1.8 can tell me what their file vdtw30 is dated?

 

[Belit]

Hi sir, I have exactly the same problem with my server W2000 (SP4), I have a citrix license installed for geet some Ica Clients to my W2000, problem is a lot of time I get a BSOD with this the address 0A00BD537 in w32k.sys.
Do you fix your problem?
How do you fix it?

Thx for responses¡

 

[tpulley]

Yes I have resolved my problem. Thanks for reminding me to post the answer.

A hot fix, ME184W06 (I also reapplied SP4, the Citrix service pack that is) not sure which did it.

Ther sever works flawlessly again.

 

[Belit]

Sorry m8, but I dont find anything with this "ME184W06", what that mean a Citrix Fix? microsoft Fix?, where can I loo for it ?

I dont have Citrix Metaframe, I only use Citrix Device Services, for use with my Thin Clients.

Thx a lot ¡

 

[tpulley]

The fix I mentioned is a hot fix from Citrix. You can get this by searching through Citrix'x web site, downloads, version etc. Hot fixes are resolved issues Microsoft, Citrix (among the few) who write patches to their software. These are usually incorporated into service pack releases. So applying a hotfix relative to SP3 is not neccessary if that was incorporated into the SP4, if you apply SP4.

You are not connecting to a Citrix server? Why use the citrix client? You can connect to a TS with RDP.

 

[Belit]

M8, I use Thin Clients with an Ica Client and connect to my W2000 Server that is running a Citrix Device Services (v1.0) that i get with my Thin Clients, problem seems that Citrix is not supporting Citrix Device Services for Now.
I haven't got problem using it on NT Terminal Server 4.0 but when i go to W200k at least one time on week i get the BSOD with tat message.
Do you know if there's any upgrade to the Citrix Device Services?
All thin client I use are Networkstation and they use a ICA client to connect against my W2000 Server.
DO you know how can i fix my problem?

Thx¡

 

[tpulley]

You mentioned earlier that you have SP4 for Windows Installed. What exactly is your halt message?

You can do a pretty good search of the halt message by going to MS web site and knowledge base. Search on first, win32k.sys, look for the "0A00BD537" + any of the other parameters you can match. These are the keys to discoering what you problem.

One hit I found when researching my problem, it indicated a possible virus. Is your Virus software up to date? Run a complete scan also. Just to verify in your mind that it isn't that....


Troubleshooting these kinds of problems are not easy, but kinda fun.

 

[TserverAdmin]

I have the same problem as Belit. I am running W2k Terminal servers with Citrix Device services installed. If I do a debug on the crash dump it tells me that the file "vdtw30.dll" is responsible for the BSOD.

This file is the "Level 0 thinwire driver for link clients" according to the file properties.

I am looking for the patch me184w06 but I cannot find it anywhere as Citrix does not support CDS anymore.

Hope you can help.

Thanks

 

[tpulley]

Here is a link that implies that the above patch is superceded by this other patch ME183W043.EXE.

http://support.citrix.com/kb/entry!default.jspa?categoryID=124&entryID=2194&fromSearchPage=true

Hotfix readme name: ME183W043.HTM
Hotfix package name: ME183W043.EXE
For: MetaFrame 1.8 for Windows 2000
Replaces: ME183W003, ME183W006, ME183W007, ME183W015, ME183W017, ME183W020, ME183W023, ME183W027,
ME183W030, ME183W033, ME183W036, ME183W038, ME183W041
Date: February 5, 2003
Language supported: English (US)

 

[patrickrouse]

Just a note to jcIT that MFXP FR3 can run just fine on Win2K SP4 if you pay attention to the hotfixes and problems you have. I have a 4 server XPe FR3 & 2000 SP4 that works just fine.

Patrick Rouse
Microsoft MVP - Terminal Server

http://www.workthin.com

 

[TserverAdmin]

Thank You for the response. I just have one problem - it says there on a note at the bottom of that linked page that you can only install me183w043 if you have Metaframe 1.8 installed - I only have the Citrix Device Services installed - nothing else of Citrix.