Windows 11 BSOD

To clarify, the thunderbolt port is only used when needed.  I use it to connect to the dock I cited earlier, which enables use of my supplemental monitors.

Right now, as an example, I'm using the machine with nothing plugged into it.  

Thunderbolt may have been a complete coincidence (or, maybe not).  Although, my brother has the exact same laptop, dock, and monitor setup at the office, and has not has any issues (FWIW).

To your point on sending this machine off of a cliff, I am getting close, although I'm still within the warranty window and warranty was extended by 90 days post display replacement.  You run Asus machines yourself and I've had good experience with them over the years, also.  Maybe I just have a lemon.  Before spending more money, I would try to have Asus do something to rectify ... Even if the worst case scenario holds true, my hope is that we're able to narrow in on a possible root cause before I go back into Asus Canada and blindly spray or worse, waste my time.

Remember, aside from some DropBox weirdness, things were working fine after the help you gents gave me a few months ago (I just engineered a car through the 24h of Daytona without issue).  It is more likely that whatever is going on is related to the Uber driver dropping the thing and the subsequent Asus repair...  But, as you can imagine, they weren't exactly the most competent bunch (you guys dummy them), so I feel I need to provide them some direction when/if I go back.

 

I'm still within the warranty window and warranty was extended

Ok, do it.

You are just wasting your own time (and ours) when could have a new machine or something done to it.  I would think once discover your system was run over by Uber or what ever will void your warranty. Be careful.  You want a full new motherboard or system replacement not a repair.

Not that trying to get rid of you but you are continuing to have issues day after day. 

You have Warranty use it as arguing with them daily will run out your warranty if do not get started.

Copy, completely understand where you're coming from.  No offence taken.

I will call them and start that process tomorrow.

In parallel, I would appreciate if @ubuysa could sanity check the MiniDump files I've shared...

Again, similar behavior was documented (fall 2023) before any physical abuse was incurred - turned out to be software/drivers. 

To go through that fight with Asus, be without my (work) computer for weeks, only to end up back here bugging you guys is something I'd like to avoid - for all of our sake

I do run some uncommon motorsports specific pieces of software (you listed a few in a previous post). 

Worried there may be some back-end clash; something that doesn't like Windows 11 or God knows what - Something that won't be resolved with hardware... 

Apologies for the questions and debate.  

Hi, no not a problem, here to help.

Is why mentioned get started arguing with ASUS.  Do not want you warranty to run out on you. They can do that to you.

As this seems to be a problem child you may want to consider a clean new install of Win10 (End of Life Oct 2025) or Win11 to see if that would help the situation

with nice clean system then your Chipset and SATA Drivers followed by the rest can do for you.

Not sure if you have given that a try or a thought, page 6 now so have to go back looking.  So if we say something and it is a repeat I hope will understand.

Before starting that DOE, probably best to wait for @ubuysa's $0.02 and/or a response from Asus...

I have done fresh Windows installs more than once; Did one just the other day...  Hasn't seemed to help.

With respect to Chipset and SATA Drivers...  I don't believe I've done that explicitly, nor did we go down that path in this thread to my knowledge.  We did Intel video drivers and alike, but nothing chipset or SATA related (unless I was oblivious).

If you'll indulge my ignorance & mechanical engineering mindset, you've reminded of something that may be worthwhile to mention:
 

When I first bought the machine (brand new), I had Canada Computers revert it back to Windows 10 to protect against potential motorsport software incompatibility issues.  The blue screen issues were almost immediate (perhaps related, or perhaps defective hardware from the factory).  The original theory was - based on research and what I was told by various 'professionals' - was that laptop hardware is often burned/hard-coded to not be backwards compatible (excuse my terminology).  So, for example, my 4080 and its drivers are forced to Windows 11 and will not work on Windows 10.  Desktop hardware is apparently 'different'.

May be complete BS, but was the theory nearly a year ago.

So, 'upgraded' from Windows 10 to 11.  

My question/hypothesis is, if there's some validity to the above, is it possible that some firmware or <God Knows What> from the Windows 10 install is still present, and is causing some kind of incompatibility?

I would think everything is saved to the SSD, but is it possible that there is conflicting code/drivers/firmware, etc., on the motherboard or some other module that is causing the machine to take a $hit?

So ya you are right did not go down the install path. 

Did provide your Support Page though : https://rog.asus.com/ca-en/laptops/rog-strix/rog-strix-scar-16-2023-series/helpdesk_download/  Model : G634JZ,

 So install Win 11, Disconnect from the net, go into BIOS make sure Fast Boot is turned off.

Turn off MS Fast Start for the following reasons as above : https://www.windowscentral.com/how-disable-windows-10-fast-startup /11 and WHY !!!

Next :

=== So IMHO it is best to after a clean install disconnect from the net and install all your drivers that you have previously downloaded.

Order is important so Chipset, Intel stuff    NOTE : NEW : There is a Hotfix available ROG Keyboard Firmware Update tool     Date : 2024/01/25 ===

Lots of reboots after/during==========

Then

Install peripherals and drive stuff. printer $bleep

I noticed you gave URL to Synapse for touchpad..........no. you have touch drivers on Support Page. Use them. Need nothing else.

There should be nothing that you need else where in the form of drivers.

You can also Stop all MS driver updates : https://www.windowscentral.com/how-disable-automatic-driver-updates-windows-10 /11

&

As well you can roll back a driver : https://www.windowscentral.com/how-roll-back-device-driver-windows-10 /11

Have you thought of installing all your work stuff to a Virtual Box which would prevent corruption and additions to your OS.

Maybe worth looking into.

NO to hypothesis unless not formatting out all Partitions on C:   So there is System Reserved, C: and UEFI Partition.  All 3 must be formatted/ or deleted/merged and formatted for a clean install

@ubuysa  Post # 73

Edited by Pkshadow, 07 February 2024 - 03:57 AM.

Neither of the two most recent dumps (the 0x133 and the 0x3B) were generated by Driver Verifier, they are BSODs that would have happened anyway.

The 0x133 occurred during a networking operation but I'm not able to isolate the driver that caused the 0x133. However, since it was a networking operation then the AX211 WiFi card driver is the most likely, that's Netwtw14.sys, which looks pretty recent dating from Nov 2023.

The 0x3B is another non-canonical memory address reference...

CONTEXT:  ffffc601aaf63900 -- (.cxr 0xffffc601aaf63900)
rax=00ac0000007e0000 rbx=0000000000000000 rcx=fffff80555660780
rdx=ffffe886f32eef98 rsi=ffffe886f32ef400 rdi=fffff80555660760
rip=fffff80554d52348 rsp=ffffe886f32eef58 rbp=ffffe886f32eefd0
 r8=ffff960513e93260  r9=ffff960513e93260 r10=0000000001980000
r11=ffff960513e93250 r12=ffffffffffffffff r13=0000000000000001
r14=ffff960526283080 r15=0000000000000001
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050206
nt!RtlInsertHeadCircularList+0x14:
fffff805`54d52348 4c8b4008        mov     r8,qword ptr [rax+8] ds:002b:00ac0000`007e0008=????????????????
Resetting default scope

Here was see a MOV instruction trying to move a QWORD (8 bytes) from the memory address pointed to by the RAX register plus 8 into the R8 register. The RAX+8 address resolves to a non-canonical address because the address in the RAX register is non-canonical. This is another manifestation of the problem we saw earlier.

Since Driver Verfieir hasn't BSODed any third-party drivers I'm fairly sure that this is a hardware problem. I would RMA it under warranty. Point them at this thread, or at least make all the dumps available to them.
 

,

Edited by ubuysa, 07 February 2024 - 09:15 AM.

Thank you very much @ubuysa & @Pkshadow.

I am initiating the Asus warranty Req. right now.

Coincidently, when I fired up the machine to fill out the Asus form, I entered a BSOD loop.  

Had to do the system restore and alike that @ubuysa warned may transpire.

I was able to attain another MiniDump file...  Saved in the DropBox folder.

May be a novelty at this point, but perhaps this instance was driven by driver verifier? 

At this point, this is an exercise in getting ahead in the event we find ourselves back here post warranty.

Run the SysnativeBSODCollection App and upload the output. I'll take a look at the new dump for you.

You can disable Driver Verifier now: verifier /reset

Edited by ubuysa, 08 February 2024 - 08:32 AM.

Thank you very much, @ubuysa.  Noted for the future.

I took the machine to Asus to begin the warranty process the evening of February 7.  They'll have it for ~7 business days.  A complete replacement is possible (I'll probably have to push for it), but more likely they'll run their own diagnostics and replace the main board.  I may have to play along and trial that, see how it goes, then push for a complete replacement should issues reemerge.  I'll ensure the warranty window is extended/respected and not let to lapse given that this process began while well within the original term.

Regardless, I'll be sure to keep yourself and PKS posted on what transpires.  

You've both been on this rollercoaster with me for a while; I owe it to you to share the findings so that if nothing else, we all learn something that can hopefully be used to help the next person.

Hi, glad to here.  I would suggest if possible if can get a hold of the ASUS Tech/s to push for a new M/B through them before time to get it back.

Yes would have to test it but ask them if replace the M/B for the Burn In Log/results.

@ubuysa @Pkshadow,

An update - just received the machine back from Asus Canada (warranty repair).  I got them to replace the motherboard, although they didn't feel it was necessary (I forced it as a precaution).  I asked them for the Burn In Log/Results, but unfortunately they didn't accommodate this...  They diagnosed the issue as indeed being a faulty RAM chip; one was good, one was bad.  They concluded this by transferring the chips one at a time to a known, good machine.  Also, when they put known 'good' RAM into my machine (prior to replacing the motherboard), they allegedly were able to turn the issue on and off.

I've purchased a new set of Corsair RAM to replace the faulty Kingston set.  Going to see if I can have the Kingston cards exchanged under some kind of manufacturer warranty (they were under a year old).

In any case, HOPEFULLY I am good now.  

I'll keep you guys posted if anything else pops up, but if everything I was told holds true, your assessments were corrected and the issue was indeed faulty RAM.

Wondering if it was the true root cause dating back to the fall and beginning of this thread...

Hi, Great news !

Should be able to RMA the Kingston set, but will only get new ones back.

Not heard of a refund.

(I had to RMA some Corsair 1 x and was not a problem as long as supplied the Mem Test results showing Fail with the RMA Request.

Long tall of it I still have the returned RMA DDR2 with heat spreaders kicking here some where)