Link to home
Start Free TrialLog in
Avatar of Danielcmorris
DanielcmorrisFlag for United States of America

asked on

XP Video Driver - Portege r100 - BSOD

I just bought this Portege R100 on craigslist.  It is a fantastic machine, unfortunatly it had Win 2003 Server on it.  The guy I bought it from was making a point with his company, replacing a huge server with this tiny laptop... increasing the speed quite a bit.  When the director saw the servers in the junk pile and saw this little laptop in their place... he agreed to update the servers.  Nice, huh?

Well, back to the point.  Some things didn't work with Win 2003 Server because there were no drivers made yet.  Especially the internal wireless and memory chip reader.  I just wiped it and installed Win XP pro.  This worked great, although I had to install all the drivers manually, since I didn't have the recovery CD (neither did he).  

Everything was great until I tried to install photoshop... I got the blue screen of death...  Hmmm.  I figured there might be a bios issue, so I updated it to the most recent version.  That didn't do it.  I didn't have time to fool with it, so I left it for a day or so.  Later on I tried to read some pics from my digital camera... Bamm!, there it was again.  I couldn't figure it out, I could see all the pics, but when I scrolled down the window it would crash.

Then I realized that there was a movie clip on the camera... all the way at the bottom.  As soon as the window was scrolled that far it crashed.  I realized that the reason I could install Office 200, but not Photoshop was probably some sort of movie file on photoshop, not some Bios file.  It was the VIDEO driver.

I updated the video driver to several different versions.... nothing.  Then, finally I found the right one.  I'm still not sure where it came from, since it was 3am and I thought I had failed, but when I started in the morning it worked fine.

Hurray, it worked!

But then..... Arggggg!  The darn thing wouldn't go into standby when I closed the lid.  It didn't even have that option anymore!  So, Just to test it, I installed one of the improper versions of the video driver.  I got the little exclamation point in the device manager, etc... but there it was, standby and Hybernate was now active.

Hurray, it worked!

But then.... Argggg! the movie issue was back with the BSOD.  Catch22.

So.  Any Ideas?
Machine: Toshiba Portege r100

Driver that is ok with movies:
"Trident Video Accelerator CyberBlade XP (toshiba)"
Driver that is ok with Standby/Hybernate:
"Trident Video Accelerator Cyber XP4 - v6.4823 -104.22_2

here is a link to a screen print of this version: http://morrisdev.com/images/_layout.bmp

Good Luck!

Avatar of Fatal_Exception
Fatal_Exception
Flag of United States of America image

here is the MS article on this:

Sleep and Hibernation Power Scheme Settings Not Displayed After You Remove and Add a Trident Driver

http://support.microsoft.com/default.aspx?scid=kb;en-us;304754&Product=winxp
ASKER CERTIFIED SOLUTION
Avatar of Fatal_Exception
Fatal_Exception
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Danielcmorris

ASKER

I downloaded their latest.... and it seems that it is the same as the one I already had.
oh, by the way.  The problem is actually the preview mode in XP.  When you view the folder as "Tiles" it crashes when there is a .mov file in the folder.  Actually, it doesn't crash until the .mov file is visible.  I guess the part of the driver that creates the preview image of the movie file is messed up
Yea..  I have a troubled feeling that you may be out of luck here...  Especially if MS has written a KB article about it.  I believe you are going to have to decide on which you need more..  You could try creating 2 hardware profiles.  One for each driver, and then select the profile you need from the boot screen when you turn it on.  I am not entirely sure this will work, but it is a suggestion..  :)
As it turns out, the newer version of the Trident Driver (which was "certified" by Microsoft) was causing the problem.  I found an older version of the same driver and it now works.

Thanks for all your help.
Very good..  and Thanks..

FE