prodonjs

updated

2 years ago

P

prodonjs

1 Rookie

•

6 Posts

0

48061

May 20th, 2019 06:00

ASF2 force off - diagnosing a root cause

I have a Latitude E6520. I had not been using it for a while due to the instability I was having with it, but I decided to see if I could get it retooled and worked properly. I bought a new solid-state drive, did a clean install of Windows 10, flashed the BIOS to the latest revision and upgraded all drivers. Still, I randomly experience unexplained shutdowns with no consistent pattern. Typically, the machine shuts down when I am not using it so I don't have any experience into what happens prior to the shutdown.

The machine will sometimes remain stable for days, but other times will shutdown after only a half-hour or so of being in use. The Windows log entries are not helpful as there is nothing shown prior to the shutdown, and only an error message stating that the previous shutdown was unexpected. The BIOS power events show Power Off - ASF2 force off each time the event occurs.

I've scoured search results and this forum for answers but nothing definitive seems to appear. Obviously, this is an older machine but it's hardware specifications are still more than adequate for my needs and I would really like to avoid having to replace it. I'm interested in whether or not there has been anything definitive, preferably from Dell support to address this issue. At the very least, I would love to know how to access any other logs for this alert standard format (which I believe to be what ASF stands for) messaging system which might give insight into the faulty software or hardware components. I appreciate any assistance anyone is able to provide.

  • prodonjs

    1 Rookie

    •

    6 Posts

    30280

    2

    Posted June 18th, 2019 20:00

    For what it's worth, ever since I disabled the C-states in my BIOS, I have been stable (going on 3 weeks now). I'm still not certain of why this would resolve things, but it has been the longest continuous stretch I've had.

  • BobsCooling

    1 Message

    13538

    0

    Posted August 31st, 2019 06:00

    I just bought a Dell Latitude E6430 i7-3740QM. I re-applied thermal paste; the old paste looked dried out. ePSA CPU temperatures were still a little high, so I ran MemTest86. The test failed twice by black screen shutdown, not by memory error detected. The bottom of the case felt quite warm. “ASF2 Force off” messages appeared in the BIOS log each time. I assumed my thermal repairs were not done yet.

    After watching a video of somebody repasting an E6430, I noticed that mine was missing the thermal pad at the far end of the heatsink! I cut out a small square of thermal conducting material to make a new pad, and also re-applied thermal paste. This time my max ePSA test temperature was 80 degrees, from 84 degrees before. A run of 20+ hours of MemTest86 has shown no errors. Fixed!!

    Thermal events may look random if not directly triggered by the user. Windows updates in the middle of the night, and “passive cooling” will downclock the CPU and reduce heat, helping prevent the problem. The OP has several other details that suggest a thermal problem.

    To recap, in my case the “ASF2 Force off” error was caused by a thermal problem, fixed by applying new thermal paste and thermal pads. Not everybody's “ASF2 Force off” errors will come from thermal problems, but it is a good idea to upgrade the paste and the pads on an old laptop anyway.

  • prodonjs

    1 Rookie

    •

    6 Posts

    30418

    0

    Posted June 1st, 2019 06:00

    This issue is incredibly frustrating because there doesn't appear to be any consistency to it. After 10 days of my machine being stable, it powered off early this morning when idle. There were no indications of any activity in my Windows logs. Once again, the only notification was the message in the BIOS events saying ASF2 force off.

    This time, I restored all BIOS settings to their defaults (I don't think I had changed anything anyways) and tried disabling C-states which is something I found in this related post.

  • U2CAMEB4ME

    6 Operator

    •

    6245 Posts

    30412

    0

    Posted June 1st, 2019 08:00

    Welcome to the Dell Community  @prodonjs 

    Have you tried this???

    Go into your BIOS and make note of the "SATA Operation"

    Remove AC, Battery and Base Cover.

    Disconnect BIOS/RTC battery.

    If you have a meter check the battery at this time. "Should be 2 - 3 volts"

    Connect "AC Only" and power-on for just a few seconds.

    Power down remove AC, reconnect BIOS/RTC battery or replace if less than 2 volts then reassemble.

    Best regards,

    U2

  • U2CAMEB4ME

    6 Operator

    •

    6245 Posts

    30404

    0

    Posted June 1st, 2019 09:00

    @prodonjs 

    SATA Operation settings: 

    Before making any BIOS change see what the setting is??? "ATA, AHCI or RAID"

    As for purchasing a replacement battery I would try any local "Mom Pop" computer shop first.

    This can come in handy.

    How to Read Shutdown and Restart Event Logs in Windows:

    https://www.tenforums.com/tutorials/78335-read-shutdown-logs-event-viewer-windows.html

    Let us know what you find.

    U2

  • prodonjs

    1 Rookie

    •

    6 Posts

    30407

    0

    Posted June 1st, 2019 09:00

    Thanks for the response. What should I be looking for with respect to the SATA Operation setting?

    It sounds like your instructions are for validating the CMOS battery. I am inclined to just buy a new one since I believe they're a less than $20 part. Can you recommend a good source? I see a lot that claim to be applicable on eBay/Amazon but I'm reluctant to purchase without knowing if they're reputable.

    The strangest thing to me about my machine's behavior is that most of the other posts that indicate this ASF2 Force Off issue seem to be more regular in frequency, whereby people's systems won't remain on for more than a few minutes. Mine are highly sporadic with days/weeks between shut offs. In addition, they always seem to occur in the middle of the night when the system is not under any kind of load. I've ran through all of the Dell Diagnostic checks both from Windows and from the BIOS and have not seen any failures, nor has the system shut down during those times. That at least leads me to believe that it's not a core hardware component (RAM, SDD, GPU) issue.

    Are you aware of any way to examine logs from the system component that would dictate that the machine shut itself down? That's the one thing I wish I could see to determine where to look for a problem.

  • prodonjs

    1 Rookie

    •

    6 Posts

    30382

    0

    Posted June 2nd, 2019 11:00

    The SATA setting is RAID and that appears to be what the BIOS default was.

    As far as the Windows logs go, the only thing I ever see when these events occur is a 6008 "previous shutdown was unexpected" message. None of the messages that precede those events seem to give any clear pattern as to what was going on in the system that might have led to the shutdown. It feels like the issue is at the chipset/BIOS level so I was hoping there might be a way to access lower-level logs, perhaps through something that the BIOS exposes or something that can be queried through some other tool.

  • LetsFindOut

    13 Posts

    30350

    0

    Posted June 9th, 2019 22:00

    Same here, been having this issue for months before finding out it\s the ASF2 Error....this is embarrassing... Dell?!
  • LetsFindOut

    13 Posts

    30346

    0

    Posted June 9th, 2019 23:00

    I think I might have fixed this issue by downgrading my bios to the corresponding version of my model from here: https://www.dell.com/support/article/us/en/19/sln308587/microprocessor-side-channel-vulnerabilities-cve-2017-5715-cve-2017-5753-cve-2017-5754-impact-on-dell-products?lang=en#affected_products I see you guys just added a fresh Bios update, today 10th of June 2019 for Lattitude e5570. This new update was also manifesting the same shutdown event.  Currently still stable after downgrading Bios from the link Above, will update this message if anything changes.
  • LetsFindOut

    13 Posts

    30248

    0

    Posted June 21st, 2019 04:00

    Thank you!

    Citrix Receiver turned out to be one of the main suspect now. I have managed to upgrade to the latest Bios version again, all I had to do was disable C state in Bios and battle Citrix Receiver out of my system. I say battle out, because it kept stealth installing back and causing the Shut down again.
    So I've also disabled all software not related to Windows in msconfig for Startup.

    Maybe this will help someone - who knew such a passive software could cause this big conflict? Of course Citrix has always been installed and forgotten in the background for the past 3 years, only after updating Windows and Dell Bios a few months ago this started acting up and somehow got related?

    I can still say that my system is in conflict, fans are usually torqued up while the AC adapter is in, even if it\s doing nothing, it has waves of the fan over-doing it's job. At least it not shutting down...yet

    Other things I have did in the Advanced Power Management to get to this stable system environment:

    Processor Power Management:

    Minimum Processor State, Plugged in set at 0%

    System Cooling Policy:

    Plugged in changed to Passive