ASUS TUF FA706IU.316 - NEW UBER issue, notebook is unusable! Black screen freezes

[xeromist]

If you reinstalled Windows and it happened again I'm inclined to think it's *not* a software issue. (Unless you installed a bunch of questionable software immediately). A fresh install with a minimum of drivers and software is unlikely to have this kind of issue.

As to what hardware? Not sure, but the only hardware you can self-service is the memory and storage so CPU/GPU/Motherboard would all require RMA to resolve.

[Afamocc]

Mmm you are true, but I still want to check everything. Under the conditions described (never failing under heavy load, no errors, etc) I wanna be 100% sure it's not software related.
For example, now, as I wrote yesterday, I installed the drivers from AMD website.
I kept the PC on all day - NO issues. Then, as I went away, it crashed while it was going to sleep - I saw the screen going black for a sec and then rebooting.

Just like the last time: after the drivers update, it never fails for a whole day. When it does, the first thing is the reboot with this error:
"The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xfffff80700000000, 0x0000000000000000, 0xfffff80750a94282, 0x0000000000000002). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 7c16cc0b-4acc-448e-8311-0c678bf027c3."

Then, until I update chipset drivers again, it will randomly fail. the memory.dmp is 1 GB big - look at what I read after I analyze it with WinDbg:
"PAGE_FAULT_IN_NONPAGED_AREA (50)
nvalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: fffff80700000000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80750a94282, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : AV.Type
Value: Read

Key : Analysis.CPU.mSec
Value: 3092

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 3159

Key : Analysis.Init.CPU.mSec
Value: 874

Key : Analysis.Init.Elapsed.mSec
Value: 22228

Key : Analysis.Memory.CommitPeak.Mb
Value: 75

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


FILE_IN_CAB: MEMORY.DMP

BUGCHECK_CODE: 50

BUGCHECK_P1: fffff80700000000

BUGCHECK_P2: 0

BUGCHECK_P3: fffff80750a94282

BUGCHECK_P4: 2

READ_ADDRESS: fffff80700000000

MM_INTERNAL_CODE: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: Discord.exe

TRAP_FRAME: ffffd88dc0eed0c0 -- (.trap 0xffffd88dc0eed0c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80700000000 rbx=0000000000000000 rcx=ffffaf0e71de8000
rdx=0000000000000200 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80750a94282 rsp=ffffd88dc0eed250 rbp=ffffd88dc0eed2a0
r8=0000000000000008 r9=0000000000000000 r10=ffffaf0e71fe6590
r11=ffffd88dc0eed9c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!EtwpEventWriteFull+0xae2:
fffff807`50a94282 0fb700 movzx eax,word ptr [rax] ds:fffff807`00000000=????
Resetting default scope

Anyone sees the problem here? I've looked up online but I find no reason in this ...is it a driver failing? Or wrong memory memory means SSD damaged?

UPDATE: hey, this other thing I just noticed may be relevant to the issue...I wanted to open the AMD software utility adrenalin, because it also has an error monitoring feature...it also shows all driver versions installed. Well, I try to open it, and I get "The Version of AMD Radeon Software You Have Launched Is Not Compatible with Your Currently Installed AMD Graphics Driver"! I now stopped Windows Update from installing drivers for my AMD Radeon graphics (systempropertiesadvanced.exe > NO)

UPDATE: BSOD happened again with AMD Graphics, Chipset Driver
Version V26.20.14048.2 ....

[xeromist]

Page fault in a non paged area is a memory error. I would strongly encourage you to take out your extra stick and see if the problem keeps happening. You'll have to do that anyway if you ever decide to send it to ASUS so you might as well try it now.

[Afamocc]

Page fault in a non paged area is a memory error. I would strongly encourage you to take out your extra stick and see if the problem keeps happening. You'll have to do that anyway if you ever decide to send it to ASUS so you might as well try it now.

I removed it....then HELL started I had to format everything... here's what happened:

I removed the ram card I had added (a long time ago). Then when I reinstalled I was getting "critical process died" error. No way to boot on safe mode, or to to roll back upgrades, or any other option that was offered there.

Driver verified, I had already diasabled it.

I had to do a clean win10 install formatting everything.

I then removed the ram stick I added and started using the notebook.

I just got the bsod 'driver irql not less or equal', failed 'netwtw04.sys'.

I'm so depressed...so it's not the ram stick I added... don't know what to do...could it be a ssd damaged issue? Or the original ram stick is faulty? I ll try later the other ram stick to see if it,s that....

EDIT: same error with the other ram stick

[Afamocc]

Edit: got now a unexpected kernel mode trap error. I don,t know what to think anymore..

I add this info: when the freeze happens, the HDD light is totally off. I checked it with many tools and it is healthy.
I suppose it s something related to Motherboard or CPU...the very feared HW issue...although very strange given the situation

Edit 21: we are back to the black screen screen random freeze. No issue under heavy loading. The BSOD have disappeared completely, maybe it was some driver missing, the pc did some updates.

Back to the start...the freeze is signaled by the HDD light turned always off as well. Like the notebook would disconnect all I/O devices. What component would do that? BIOS? I see others with the same issue, but BIOS is already updated and re-installed.

23: Got another BSOD, always Ntfs.sys:

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff8025bce8267, Address of the instruction which caused the BugCheck
Arg3: ffff89038832b180, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for Ntfs.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3531

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 64866

Key : Analysis.Init.CPU.mSec
Value: 624

Key : Analysis.Init.Elapsed.mSec
Value: 16304

Key : Analysis.Memory.CommitPeak.Mb
Value: 75

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


FILE_IN_CAB: 020522-9546-01.dmp

BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8025bce8267

BUGCHECK_P3: ffff89038832b180

BUGCHECK_P4: 0

CONTEXT: ffff89038832b180 -- (.cxr 0xffff89038832b180)
rax=ffff8e81a32157a2 rbx=ffffa18f676c5180 rcx=fffff8025bc94820
rdx=ffffa18f676c64f0 rsi=ffff89038832c190 rdi=ffff8e81a315ba10
rip=fffff8025bce8267 rsp=ffff89038832bb80 rbp=0000000000000008
r8=0000000000000000 r9=000000000000005c r10=0000000000320020
r11=ffff89038832bca8 r12=ffffa18f676c64f0 r13=ffffa18f78c12bb8
r14=ffff89038832bef0 r15=ffff8e81a315ba10
iopl=0 nv up ei ng nz na pe cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050283
Ntfs+0xe8267:
fffff802`5bce8267 0fb710 movzx edx,word ptr [rax] ds:002b:ffff8e81`a32157a2=0057
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: firefox.exe

STACK_TEXT:
ffff8903`8832bb80 00000000`00000000 : ffff8e81`a1400000 00000000`00000001 ffff8e81`a1400340 00000000`00000040 : Ntfs+0xe8267


SYMBOL_NAME: Ntfs+e8267

MODULE_NAME: Ntfs

IMAGE_NAME: Ntfs.sys

STACK_COMMAND: .cxr 0xffff89038832b180 ; kb

BUCKET_ID_FUNC_OFFSET: e8267

FAILURE_BUCKET_ID: 0x3B_c0000005_Ntfs!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {295ea5f8-4818-74e6-5ff2-8c3321f15313}

Followup: MachineOwner
---------

[syyyap]

does BSOD happen during powering on? try unplug the power before powering on from sleep/hibernation. i have to do this else get BSOD dpc watchdog violation...