Multiple blue screens

Question

Last up until last November my inspiron laptop which is just out of warranty started getting blue screens. Since then I've performed multiple clean installs using the windows 11 usb install downloaded from the windows website. I turn install the latest drivers from the Dell website. This usually works for a while but then after several cumulative windows updates i start getting all sorts of blue screens service exception and more commonly irql not less equal than errors. Sometimes the laptop just starts crashing too. I feel like I've tried everything. Memtest86 doesn't come up with errors and all hardware tests are fine. Before i move to using an operating system like ubunto, just wondering if anyone can help?

Thanks

Mike

Answer 1

Thanks i had a bluetooth issue a while back. I'm having trouble providing the minidump file. Let's assume it is the network adaptor, where would i find the correct drivers? Dell has some but that's what I've been using. Would it better to go to realtek website?

Also this issue seems to occur after a windows update, maybe that's a coincidence?

Thanks

Mike

Answer 2

Thanks for sharing the minidump analysis.

The minidump analysis indicates rtwlane.sys as a cause of the BSOD which is related to the RealTek Network adapter but I need the actual file to verify it.

Answer 3

I've also tried dism restore health.

Chkdisk

Scan sfc

Answer 4

Hi Dyari,

Thanks for getting touch. Please find mini dump analysis via WinDBG:

Loading Dump File [C:\Windows\Minidump\052224-9515-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 22621 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Edition build lab: 22621.2506.amd64fre.ni_release_svc_prod3.231018-1809 Kernel base = 0xfffff80309c00000 PsLoadedModuleList = 0xfffff8030a813130 Debug session time: Wed May 22 23:53:00.908 2024 (UTC + 1:00) System Uptime: 0 days 0:12:41.518 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ .................... Loading User Symbols Loading unloaded module list ....... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff8030a017f80 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffa90c42a47110=000000000000000a 2: kd> !analyze -v ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high.  This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 0000000100e422e8, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff8030a021d6b, address which referenced memory Debugging Details: ------------------ KEY_VALUES_STRING: 1    Key  : Analysis.CPU.mSec    Value: 1968    Key  : Analysis.Elapsed.mSec    Value: 2734    Key  : Analysis.IO.Other.Mb    Value: 0    Key  : Analysis.IO.Read.Mb    Value: 0    Key  : Analysis.IO.Write.Mb    Value: 0    Key  : Analysis.Init.CPU.mSec    Value: 249    Key  : Analysis.Init.Elapsed.mSec    Value: 4046    Key  : Analysis.Memory.CommitPeak.Mb    Value: 96    Key  : Bugcheck.Code.LegacyAPI    Value: 0xa    Key  : Bugcheck.Code.TargetModel    Value: 0xa    Key  : Failure.Bucket    Value: AV_rtwlane!unknown_function    Key  : Failure.Hash    Value: {393a0fa0-37e7-f00b-a441-ba760fd931f1}    Key  : WER.OS.Branch    Value: ni_release_svc_prod3    Key  : WER.OS.Version    Value: 10.0.22621.2506 BUGCHECK_CODE:  a BUGCHECK_P1: 100e422e8 BUGCHECK_P2: 2 BUGCHECK_P3: 0 BUGCHECK_P4: fffff8030a021d6b FILE_IN_CAB:  052224-9515-01.dmp READ_ADDRESS: fffff8030a91c4a8: 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 0000000100e422e8 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT:  1 PROCESS_NAME:  System TRAP_FRAME:  ffffa90c42a47250 -- (.trap 0xffffa90c42a47250) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=ffffa90c42a47c30 rbx=0000000000000000 rcx=ffffe500ca151180 rdx=0000000000000082 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8030a021d6b rsp=ffffa90c42a473e0 rbp=004fe07fbcbbbdff r8=0000000000000000 r9=0000000000000000 r10=0000000000000082 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0         nv up ei ng nz na po nc nt!SwapContext+0x47b: fffff8030a021d6b 833d7605820000 cmp     dword ptr [nt!KiCpuTracingFlags (fffff8030a8422e8)],0 ds:fffff8030a8422e8=???????? Resetting default scope STACK_TEXT:   ffffa90c42a47108 fffff8030a02de29     : 000000000000000a 0000000100e422e8 0000000000000002 0000000000000000 : nt!KeBugCheckEx ffffa90c42a47110 fffff8030a029289     : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiBugCheckDispatch+0x69 ffffa90c42a47250 fffff8030a021d6b     : 004fe07fbcbbbdff ffff99010ff84d00 0000000000400000 ffffe50000000000 : nt!KiPageFault+0x489 ffffa90c42a473e0 fffff8030a021886     : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!SwapContext+0x47b ffffa90c42a47420 fffff80309e3aa05     : ffffe500ca151180 0000000000000000 ffff99010b91f200 0000000000000000 : nt!KiSwapContext+0x76 ffffa90c42a47560 fffff80309e3cbe7     : 000000000000001b 0000000000000000 0000000000000000 0000000000000000 : nt!KiSwapThread+0xab5 ffffa90c42a476b0 fffff80309e3eb06     : 0000000000000000 0000000000000001 ffffa90c00000000 0000000000000000 : nt!KiCommitThreadWait+0x137 ffffa90c42a47760 fffff8033a49ae8c     : fffff8033a5e1000 0000000000000001 ffffffffffffffd1 fffff8033a14ec9c : nt!KeWaitForSingleObject+0x256 ffffa90c42a47b00 fffff8033a5e1000     : 0000000000000001 ffffffffffffffd1 fffff8033a14ec9c 0000000000000000 : rtwlane+0x49ae8c ffffa90c42a47b08 0000000000000001     : ffffffffffffffd1 fffff8033a14ec9c 0000000000000000 0000000000040297 : rtwlane+0x5e1000 ffffa90c42a47b10 ffffffffffffffd1     : fffff8033a14ec9c 0000000000000000 0000000000040297 ffff99010f8b10e0 : 0x1 ffffa90c42a47b18 fffff8033a14ec9c     : 0000000000000000 0000000000040297 ffff99010f8b10e0 fffff8033a14ec67 : 0xffffffffffffffd1 ffffa90c42a47b20 0000000000000000     : 0000000000040297 ffff99010f8b10e0 fffff8033a14ec67 ffff990112000000 : rtwlane+0x14ec9c SYMBOL_NAME:  rtwlane+49ae8c MODULE_NAME: rtwlane IMAGE_NAME:  rtwlane.sys STACK_COMMAND:  .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET:  49ae8c FAILURE_BUCKET_ID:  AV_rtwlane!unknown_function OS_VERSION:  10.0.22621.2506 BUILDLAB_STR:  ni_release_svc_prod3 OSPLATFORM_TYPE:  x64 OSNAME:  Windows 10 FAILURE_ID_HASH:  {393a0fa0-37e7-f00b-a441-ba760fd931f1} Followup:     MachineOwner --------- NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2402.24001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\atlmfc.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2402.24001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\ObjectiveC.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2402.24001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\concurrency.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2402.24001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\cpp_rest.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2402.24001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Kernel.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2402.24001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\stl.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2402.24001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Data.Json.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2402.24001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Geolocation.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2402.24001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Sensors.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2402.24001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Media.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2402.24001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\windows.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2402.24001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\winrt.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2402.24001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Usb4Kd.natvis'

Answer 5

Hi Mike,

I'm Dyari. Thanks for reaching out. I will be happy to assist you in this regard.

Please go to C:\Windows\Minidump and copy any minidump files you find to your desktop. Afterward, share these files through OneDrive or Google Drive so we can analyze them and identify the specific file that's causing the crash.

https://answers.microsoft.com/en-us/windows/for...