BSOD Assistance - Windows 10 22H2

ITGuy061 · 18 Mar 2024

Good Day All

I have a device that keeps getting this BSOD :

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid 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: ffff9d01e82be000, memory referenced.
Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE.
bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the processor decided the fault was due to a corrupted PTE.
bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
- ARM64: bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff803951bfb27, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

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

KEY_VALUES_STRING: 1

Key : AV.Type
Value: Read

Key : Analysis.CPU.mSec
Value: 3296

Key : Analysis.Elapsed.mSec
Value: 12292

Key : Analysis.IO.Other.Mb
Value: 1

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 3

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x50

Key : Bugcheck.Code.TargetModel
Value: 0x50

Key : Failure.Bucket
Value: AV_R_(null)_rtwlane601!unknown_function

Key : Failure.Hash
Value: {d653002c-3d9a-13ac-83f3-0292e928643a}

Key : Hypervisor.Enlightenments.Value
Value: 68673420

Key : Hypervisor.Enlightenments.ValueHex
Value: 417df8c

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1

Key : Hypervisor.Flags.ApicEnlightened
Value: 0

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 1

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 1

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1

Key : Hypervisor.Flags.Phase0InitDone
Value: 1

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 1

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 21631230

Key : Hypervisor.Flags.ValueHex
Value: 14a10fe

Key : Hypervisor.Flags.VpAssistPage
Value: 1

Key : Hypervisor.Flags.VsmAvailable
Value: 1

Key : Hypervisor.RootFlags.AccessStats
Value: 1

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 1

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1

Key : Hypervisor.RootFlags.MceEnlightened
Value: 1

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1

Key : Hypervisor.RootFlags.Value
Value: 1015

Key : Hypervisor.RootFlags.ValueHex
Value: 3f7

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1

BUGCHECK_CODE: 50

BUGCHECK_P1: ffff9d01e82be000

BUGCHECK_P2: 0

BUGCHECK_P3: fffff803951bfb27

BUGCHECK_P4: 0

FILE_IN_CAB: 031824-12406-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

READ_ADDRESS: fffff803636fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
ffff9d01e82be000

MM_INTERNAL_CODE: 0

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: fffffe84671214a0 -- (.trap 0xfffffe84671214a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff9d01e82be001 rbx=0000000000000000 rcx=0000000000002f1c
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff803951bfb27 rsp=fffffe8467121630 rbp=fffffe8467121716
r8=0000000000000000 r9=0000000000000000 r10=fffff80362d8dec0
r11=fffffe84671226d0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
rtwlane601+0xafb27:
fffff803`951bfb27 420fb67c3101 movzx edi,byte ptr [rcx+r14+1] ds:00000000`00002f1d=??
Resetting default scope

STACK_TEXT:
fffffe84`671211f8 fffff803`62e3bd2d : 00000000`00000050 ffff9d01`e82be000 00000000`00000000 fffffe84`671214a0 : nt!KeBugCheckEx
fffffe84`67121200 fffff803`62c24660 : 00000000`00000000 00000000`00000000 fffffe84`67121520 00000000`00000000 : nt!MiSystemFault+0x1d87cd
fffffe84`67121300 fffff803`62e0d358 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x400
fffffe84`671214a0 fffff803`951bfb27 : 00000000`00000000 00000000`0000d0f6 ffffd486`0f0100ff fffff803`954b08f0 : nt!KiPageFault+0x358
fffffe84`67121630 00000000`00000000 : 00000000`0000d0f6 ffffd486`0f0100ff fffff803`954b08f0 ffff9d01`e82be001 : rtwlane601+0xafb27

SYMBOL_NAME: rtwlane601+afb27

MODULE_NAME: rtwlane601

IMAGE_NAME: rtwlane601.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: afb27

FAILURE_BUCKET_ID: AV_R_(null)_rtwlane601!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {d653002c-3d9a-13ac-83f3-0292e928643a}

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

I have re-installed all WLAN and BT drivers but still this error occurs
Has anyone perhaps seems this issue ?

- - - Updated - - -

If anyone has any other tips i can try or needs more information i can let you know

FreeBooter · 18 Mar 2024

The rtwlane.sys refers to the Realtek PCIE Wireless LAN PCI-E NIC driver. So when you’re seeing the Blue screen error saying rtwlane.sys, you need to update the Realtek wireless LAN card driver on your computer to fix the issue.

ITGuy061 · 18 Mar 2024

I have done the updates with the official drivers form the laptop manufacturer site but still getting the same error
Is there perhaps something i am missing or somewhere to get either a latest driver or is there a better way to install the driver ?
Just a note : Laptop is a Lenovo 21DJ

FreeBooter · 18 Mar 2024

You can download the driver from device manufacturer website also try older version of driver.

ITGuy061 · 18 Mar 2024

I have done that from the manufacturer site but still gives that BSOD
On the Lenovo site there is only one older version and ive tried that one as well but still i have seen the BSOD , thus i want to try to get an even more up to date version from the Realtek site but that is easier said than done as i am not 100% where to start

FreeBooter · 18 Mar 2024

Check other BSOD memory dump files to make sure its only Wireless card causing the BSOD error.

ITGuy061 · 18 Mar 2024

I can confirm that is the only dump file because last time i reinstalled the dirvers i cleaned the dump file and minidump locations . And when i checked again it was just the one file pointing to the rtwlan dump

FreeBooter · 18 Mar 2024

If the drivers not resolving the BSOD then it could be faulty malfunctioning wireless card that causing the problem.

ITGuy061 · 18 Mar 2024

Yeah i thought so as well but if that were the case wouldnt there be more BSODs and more Dump files ? The issue i have is this : When i reinstall the drivers it will be fine and then all of a sudden i get the bsod and see it points to the same issue

- - - Updated - - -

Is there maybe a different way to re-install the drivers - I have been removing them via device mananger and then running the EXE file from the site ?

FreeBooter · 18 Mar 2024

You should have more dump files if you are getting BSOD error and if these dump files points to same driver then that driver or malfunctioning faulty hardware cause of it.

If new device drivers or system services have been added recently, try removing or updating them. Try to determine what changed in the system that caused the new bug check code to appear.
Look in Device Manager to see if any devices are marked with an exclamation point (!), which indicates a problem. Review the events log displayed in the properties for any faulting device driver. Try to update the related driver.
Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. Look for critical errors in the system log that occurred in the same time window as the blue screen.
If you recently added hardware to the system, try removing or replacing it. Or check with the manufacturer to see if any patches are available.
Install Windows updates.
If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't know what it is you probably are not overclocking.
Use SpeedFan to monitor temperatures in computers, overheating can cause BSOD.
Use Memtest86+ disc to check system memory's (RAM's) for errors.
Use CrystalDiskInfo to check SMART health report of the hard disk drive (HDD).

Open the Command Prompt with administrative privileges and execute bellow commands one at a time.

Code:

Dism /online /cleanup-image /restorehealth



Sfc /scannow


Chkdsk C: /f

For dumps to be produced, The following should be correct

Page file must be on the same drive as your operating system

Page file base allocation size must be greater than installed physical RAM

Windows Error Reporting (WER) system service should be set to MANUAL

Set page file to system managed on the OS drive

Set system crash/recovery options to "kernel memory dump"

User account control must be running.

Sometimes SSD drives with older firmware do not create DMPS (update firmware)

Cleaner applications like Ccleaner delete DMP files so dont run them until you are fixed.

Bad Physical RAM may prevent the data from being saved and written to a file on reboot. If you suspect bad RAM run Memtest from this wiki

Full memory dumps can also be deleted (in win 7) if your HD space is under 25 gigs, but if you configured your system as the above suggests, you should not be generating full dumps.