- This topic is empty.
2. March 2007 at 15:41 #308
We have rolled out 200+ Wyse V90’s. A handful of these are experiencing an issue where working on a word document inside of a terminal server causes a BSOD. It’s not limited to a specific document and it only happens when working in Word.
Has anyone experienced this?2. March 2007 at 21:50 #9152
Wow, that’s a weird one. So a remote applications causes a local BSOD?
What is the stop error on the thin client? Also is the doc being worked under a locally mapped storage device (USB Key).
I have seen a case where the terminal had no received the full image, maybe try a full image load on the problem devices,
-TT16. March 2007 at 17:43 #9271
Sorry for the late reply.. been busy sorting out some issues with these winterms…
Yeah it definately is a weird one.. I can’t seem to replicate it here but yet I’m getting more and more users calling with the same issue. I have Wyse looking into it but we have no resolution yet…
There has been a couple different stop errors but the most common being 0x0000008e and 0x0000000A. The documents are located in a mapped network drive.
Although the stop codes are different, they all occur while the user is using Microsoft Word inside one of our terminal servers.16. March 2007 at 20:10 #9272
I am not the only one experiencing this…17. March 2007 at 23:19 #9276
Thats a good find, its a shame the user in the other post did not find a resolution. As a matter if interest what version of firmware is on the client (Wyse build number like 395) and what is the version and service pack of the Server and Office?
Give there are not loads of people with this is must be a particular combination.
-TT19. March 2007 at 17:38 #9285
The firmware is one that Wyse sent to me that has an additional partition so I could install McAfee VirusScan Enterprise.
Version 3.03 – Needs to be updated with Cl #
Windows 2003 Server SP1
Office 2003 SP219. March 2007 at 18:14 #9286
Found another person having a very similar issue…
I beleive that is Dutch so here is a horrible translation via altavista.19. March 2007 at 20:11 #9288
Thanks for the info, not sure about the Dutch one being the same.
Just as a matter of interest, did you try loading a clean image from wyse.com (not the 2 partion one support sent you).
I am interested to see if this has the same issue, I wonder if the image you were given has a problem with it. If this works there are instrusctions on this site on how to create a 2 partion image and install McAfee AV.
I would be really interested to see how this goes and if you have discovered a wierd Windows bug!
-TT19. March 2007 at 21:26 #9290
thanks for the replies TT
its nice to at least have suggestions.
which is more than I have received from Wyse recently…
I really hope they didn’t give me a bad image… I don’t even want to think about reimaging all these machines… especially since we can’t image over the network.
If all else fails I will try configuring a clean image from scratch and test it out. I actually talked to the author of the McAfee article “Bob F” over at wyse. Ironically that article was posted a couple days after i spoke with him 😀19. March 2007 at 22:02 #9291
We have 35 V90s with XPe and they were all getting BSOD for some users. We seem to have solved the issue by installing RDP client 6.0 from
It doesn’t say it works with XPe, and WYSE doesn’t seem to say anything about the updated RDP client. I installed in on Friday morning and reimaged 5 units. We haven’t had any BSODs from the newly reimaged units while there are still problems with the units with RDP 5.2.
The only adverse effect we’ve seen is that users are asked to log in twice because of server authentication in RDP 6.0. The first log in is pretty irrelevant as it connects no matter the info entered (we have it set to connect even if authentication fails). The second login is the server login that we had before. I told the users just to hit enter at the first login and they didn’t complain since they can actually work now.20. March 2007 at 3:58 #9296
Great info, thanks for this Jeffz. Maybe try it out and see how you get on tjsel?
As an FYI MS have not blessed RDP6 for XPe (hence no Wyse version) but it works well for me, I run it as it spans RDP sessions across 2 monitors – nice 🙂20. March 2007 at 22:54 #9304
Latest update: we got a new unit today from WYSE. They say they changed out a chip. I’ll keep you posted.23. March 2007 at 16:45 #9332
We have been testing the V90 unit sent by WYSE that has a chip swapped out. So far no BSOD.23. March 2007 at 21:32 #9333
That’s great news! To help out tjsel do you know what chip was changed in the unit? (or can you find out). I am thinking maybe the EPROM that holds the BIOS but I have not seen this as an issue. Maybe you could send tjsel a private message on who it was as Wyse you are dealing with as they seam to have the fix.
Let us know how you get on and thanks for your help,
-TT26. March 2007 at 15:33 #9339
Thanks for all the help guys.
We have an engineer from Wyse coming to the office tommorow to take a look at our issue. Jeffz if you have any additional info I could give to the engineer that would be great.
- You must be logged in to reply to this topic.