Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 10 replies
  • Subscribers 5 subscribers
  • Views 21241 views
  • Users 0 members are here
Options
Suggested
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

vojta

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.
Parents
  • 0

    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
Reply
  • 0

    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
Children
No Data
Unfiltered HTML