Video Screencast Help
Search Video Help Close Back
to help

BSOD fslx.sys error

Created: 09 Mar 2012 | 5 comments
kremkake's picture
0 0 Votes
Login to vote

Windows XP SP3

- Symantec Workspace Virutalization Agent 6.4.1266

- HP Elite Book 8740w AND 8760w

- 1 - 3 gig of Ram

- Fully updated, all drivers to latest.

- Display adapter ATI Firepro M7820

- Will soon be Virutalizing IE 7, so it would be nice for this too work.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {8, ba348d70, 0, 0}

*** WARNING: Unable to verify timestamp for fslx.sys
*** ERROR: Module load completed but symbols could not be loaded for fslx.sys
*** WARNING: Unable to verify timestamp for SYMDS.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMDS.SYS
*** WARNING: Unable to verify timestamp for Ironx86.SYS
*** ERROR: Module load completed but symbols could not be loaded for Ironx86.SYS
*** WARNING: Unable to verify timestamp for SRTSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for SRTSP.SYS
*** WARNING: Unable to verify timestamp for NAVEX15.SYS
*** ERROR: Module load completed but symbols could not be loaded for NAVEX15.SYS
Probably caused by : fslx.sys ( fslx+62df )

 

HELP!!!!!!!!!!

Comments 5 CommentsJump to latest comment

tkofoed's picture

I have exactly  same problem with

HP 8100 elite small form factor and

HP 8200 elite small form factor.

Same version of SWV client and the minidump has the same errors

So i will follow this thread.

0
Login to vote
  • Actions
Peter van Esch's picture

but installing the latest release, 6.4.1550, resolved our BSODs. 

0
Login to vote
  • Actions
kremkake's picture

Same error peter?  Cause I don't see anywhere in the specs that it fixed this issue, I just want to be absolutely sure.  We average 10 - 15 laptops a day in the hospital.

0
Login to vote
  • Actions
Peter van Esch's picture

But our BSODs were related to the logon & novell client. But hey, give it a try on one, that's the only way to know. I can only tell from our experience that v1550 is much more stable.

0
Login to vote
  • Actions
balachandar_manimala's picture

Hello,

Could you please repro the issue and generate a full memory dump and copy the full stack trace?

Also what is the display driver version.

Regards,

Bala

0
Login to vote
  • Actions