Repeated crashes and BSOD on ASUS TUF A15

Anonymous
2021-01-04T15:04:31+00:00

Hello,

Several months ago I bought an gaming laptop, an Asus TUF A15 FA506IV with Windows 10 installed. Everything was fine in the first weeks, but then my computer started to crash and get BSOD randomly, except when I'm playing or using it intensively, which is weird.

I've tried everything, ranging from reinstalling drivers, to a complete reset and windows install.

I've checked RAM, disk and system files integrity, tried multiple repair tools, both Microsoft and unofficial, multiple times, installed every single driver based on Windows Update recommendations/constructor website, even used driver verifier, but nothing has changed since.

The only thing that sometimes changes is the error message of the bluescreen, when there's one. Often the screen only goes completly black, and nothing else happens.

Oh, and I can't show any memory/crash dump since nothing is generated.

Is there anything else to do, or is my computer doomed to be returned to the vendor ?

Specs :

OS : Windows 10 Family 10.0.19042

Product : Asus TUF A15 FA506IV

Memory : 16GB

GPU : NVidia RTX 2060 GDDR6 6GB

CPU : Ryzen 4800H with Radeon Graphics, 2900Mhz, 8 cores, 16 virtual cores

Storage : 500GB SSD Kingston OM8PCP3512F-AB

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

113 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2022-02-20T19:12:09+00:00

    For me it was RAM, after changing the RAM it finally fixed and not crashing since last one month.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-01-20T18:06:05+00:00

    Matías Sepúlveda Pradenas - Couldn't agree more--it's a poorly engineered product. I should have sent it in while still under warranty, but I couldn't be without a computer as all my work is computer-based. Ugh. Finally bought a new computer and now I'm pursuing my issues via Asus' office of the president. We'll see how that goes.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-01-20T13:42:00+00:00

    I ended up taking the notebook to a service center. They replaced the motherboard. Since that, the machine is free of freezing and green screen.

    So, probably a high percentage of the notebooks with issues are hardware related. In any case, a product poorly engineered if you ask me.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-01-20T01:13:22+00:00

    So I've been having this problem since summer of last year. Random black screens, BSOD's, etc. I believe I however may have found the issue and a solution! ...

    Hey Ghostcrafter090,

    Thanks so much for posting this! I'll have to try this out. I may be awhile before I have a chance--I ended up buy in new laptop to replace the very unstable Tuf A17. But when I do, I'll post my results.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-01-18T17:07:38+00:00

    So I've been having this problem since summer of last year. Random black screens, BSOD's, etc. I believe I however may have found the issue and a solution!

    I recently ran Driver Verifier on all non-Microsoft based drivers and kind of left it for 2 weeks.

    One of the issues I've been seeing during crashing (even when a BSOD presents itself), is that the system gets stuck at 0% when generating the minidump, resulting in no debug information being generated (not sure if that's related to the issue, but regardless). I basically just gave up and decided to deal with the crashes. Today however, it crashed, and the stop code was actually the driver verifier doing its thing for once!

    It still didn't generate the minidump, however it listed something other than ntoskrnl.sys, specifically "inpoutx64.sys". After a little research, I found it was non-critical and removed it from the drivers directory in "C:\Windows\System32\drivers". Immediately following this, I tried running Idea (I'm a Minecraft mod developer) and tried running the game (attempting to hit it with load). Upon getting to the loading world screen, the computer crashed with the driver_irql_not_less_or_equal stop code again. It had the driver being listed as afd.sys however.

    After a little research, afd.sys has to do with networking functions with windows, and after a little bit more, found a lot of threads of people having issues with the Realtek wireless Lan driver shipped with the system (specifically with BSOD errors similar in behavior to this issue, that being random crashes and lockups without warning). I rolled back the driver to a previous version and haven't had the problem for a little while now.

    After looking through this thread again, and seeing around what times people here started having issues, and I notice that issues started cropping up right around the same time the driver update for the Realtek driver was rolled out. I believe I may have found the solution ;)

    The version I downgraded the Realtek driver to is 2024.0.8.108.

    If the crashes and lockups return, I'll report it here.

                - Ghost

    < Downgraded Wireless Lan Driver

    Was this answer helpful?

    0 comments