Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

"Page Fault" Error at Startup

After installation of SGN FDE with POA we occassionaly and intermitently see "Page Fault" error prior to POA login screen. We see this across multiple models of laptops. Everything points to a USB device or docking station poor loading or not being supported. The resolutoin is either reboot and/or use of hot keys prior to POA. Is anybody else experiencing this? Could Sophos provide more descriptive error on this?

:144


This thread was automatically locked due to age.
  • ticed this.  After talking with Sophos Support they have confirmed it as a known issue with lpatops in docking stations and attached USB devices.  Our "fix" right now is to unplug all USB devices from the docking station and reboot.  Once you get the POA scree, reattach the USB devices.  If you any better resolutions please let me know.  I have an open ticket with support, but help is slow coming.

    :238
  • Hey gents,

    using the POA Hot Keys is also worthwhile having a look at. Please see here for more info:

    http://www.sophos.com/support/knowledgebase/article/107781.html

    The USB ones and Shift F9 are the ones to give a try in this situation.

    Regards

    Dan

    :343
  • We have the same problem, tried all the hotkeys to no avail. Even unplugging all USB devices from the docking station doesn't help, only sollution we have is to remove the Laptop from the docking station before PoA then to place it back on afterwards, Hardly ideal!

    Going to log a support call now, so i'll keep you's posted.....

    :690
  • Hi Dave,

    Great, please do share your solution with everyone!

    Cheers,

    Lil

    :703
  • We are also having the same problem the only fix is to take the machine out of the docking station and load up or swap docking stations for newer ones which is not good. Any fixes would be brilliant

    :711

  • Dave_M wrote:

    We have the same problem, tried all the hotkeys to no avail. Even unplugging all USB devices from the docking station doesn't help, only sollution we have is to remove the Laptop from the docking station before PoA then to place it back on afterwards, Hardly ideal!

    Going to log a support call now, so i'll keep you's posted.....


    Quick thought, is the BIOS on the docking station current? Any hardware information (make / model / version / BIOS version) will be useful.

    Also, please share your findings. Thanks! :smileyhappy:

    :729
  • We have seen this behavior, starting with SGN 5.40. Sometimes taking the machine off of the docking station remediates this issue, sometimes multiple reboots are required to get to a usable operating system but I have seen a 100% success rate replacing the memory in affected machines.This has been observed on both desktops (Obviously without docking stations) and laptops.

    We have gone the route of removing USB devices and eliminating the docking station from the testing with mixed results.

    I haven't seen any POA hotkeys that affect this bug, but it's been awhile since I've seen this problem.

    Could the POA environment be tempermental about the memory segments that it uses to load the Windows bootloader? Can that be translated to how the docking station interfaces with the rest of the machine? Just a thought.

    :863
  • Hi all,

    a good practice is to deaktivate the "USB legacy" support in the BIOS an let the POA handel this stuff - with POA Keys

    "USB" on and "USB20" on.

    We made good experiences with DELL Laptops .. just deaktivating the USB legacy support in BIOS.

    Maybe this helps with your problem - please let us know ;-)

    cheers

    :966
  • Was there any overall solution about this fault?

    We are experiencing the problem on brand new E5410 laptops from Dell.

    Thank you

    :9249
  • Ive had this issue for the past two months and we've tried everything from changing hard drives to hotkeys... What did work was checking the RAM, Take out each stick of RAM and test each one individually, the one that beeps is usually the bad one. In my cause it was just the pins on the RAM needed to be cleaned with the ol' eraser technique. after that sophos POA fired right up, i also used the 'shift'+ F6 'ATA hotkey' (i dont know if that would have to apply to all your machines, but it did in my case) Let me know if this works out for any of you guys. thanks

    :29465