Share via

My computer keeps blue screening

Luke Dronsfield 0 Reputation points
2026-04-26T21:46:56.98+00:00

Hello,

Over the last few days, at seemingly random intervals, my laptop has begun crashing and restarting by itself. This has been both while I have been actively using it and whilst it has been idle. I have checked for potential drivers that may need updating, but all seem to be up to date, as well as optional updates I could install, but these haven't solved it either. After looking at the minidumps, I believed the issue was possibly related to my network adapter driver, but reinstalling the driver made no difference. I am now unsure as to what is causing these blue screens or how to fix them. Any help would be greatly appreciated.

Here is the minidump after my latest crash:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)

This is a very common BugCheck. Usually the exception address pinpoints

the driver/function that caused the problem. Always note this address

as well as the link date of the driver/image that contains this address.

Arguments:

Arg1: ffffffffc0000046, The exception code that was not handled

Arg2: fffff806c0681caf, The address that the exception occurred at

Arg3: fffffe80ba6ae9d0, Exception Record Address

Arg4: fffffe80ba6aea70, Context Record Address

Debugging Details:

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

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec

Value: 1328

Key  : Analysis.Elapsed.mSec

Value: 2075

Key  : Analysis.IO.Other.Mb

Value: 0

Key  : Analysis.IO.Read.Mb

Value: 1

Key  : Analysis.IO.Write.Mb

Value: 0

Key  : Analysis.Init.CPU.mSec

Value: 406

Key  : Analysis.Init.Elapsed.mSec

Value: 2387

Key  : Analysis.Memory.CommitPeak.Mb

Value: 91

Key  : Analysis.Version.DbgEng

Value: 10.0.29547.1002

Key  : Analysis.Version.Description

Value: 10.2602.27.2 amd64fre

Key  : Analysis.Version.Ext

Value: 1.2602.27.2

Key  : Bugcheck.Code.LegacyAPI

Value: 0x1000007e

Key  : Bugcheck.Code.TargetModel

Value: 0x1000007e

Key  : Dump.Attributes.AsUlong

Value: 0x21808

Key  : Dump.Attributes.DiagDataWrittenToHeader

Value: 1

Key  : Dump.Attributes.ErrorCode

Value: 0x0

Key  : Dump.Attributes.KernelGeneratedTriageDump

Value: 1

Key  : Dump.Attributes.LastLine

Value: Dump completed successfully.

Key  : Dump.Attributes.ProgressPercentage

Value: 0

Key  : Failure.Bucket

Value: 0x7E_C0000046_rtwlane711!unknown_function

Key  : Failure.Exception.Code

Value: 0xc0000046

Key  : Failure.Exception.IP.Address

Value: 0xfffff806c0681caf

Key  : Failure.Exception.IP.Module

Value: nt

Key  : Failure.Exception.IP.Offset

Value: 0x281caf

Key  : Failure.Exception.Record

Value: 0xfffffe80ba6ae9d0

Key  : Failure.Hash

Value: {adad48bd-bf5b-5bbe-dc04-b77f1d188e45}

Key  : Faulting.IP.Type

Value: Paged

Key  : Hypervisor.Enlightenments.ValueHex

Value: 0x7497cf94

Key  : Hypervisor.Flags.AnyHypervisorPresent

Value: 1

Key  : Hypervisor.Flags.ApicEnlightened

Value: 1

Key  : Hypervisor.Flags.ApicVirtualizationAvailable

Value: 0

Key  : Hypervisor.Flags.AsyncMemoryHint

Value: 0

Key  : Hypervisor.Flags.CoreSchedulerRequested

Value: 0

Key  : Hypervisor.Flags.CpuManager

Value: 1

Key  : Hypervisor.Flags.DeprecateAutoEoi

Value: 0

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: 1

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: 38670575

Key  : Hypervisor.Flags.ValueHex

Value: 0x24e10ef

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: 0x3f7

Key  : WER.System.BIOSRevision

Value: 1.27.0.0

BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffffc0000046

BUGCHECK_P2: fffff806c0681caf

BUGCHECK_P3: fffffe80ba6ae9d0

BUGCHECK_P4: fffffe80ba6aea70

FILE_IN_CAB: 042626-14703-01.dmp

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

DUMP_FILE_ATTRIBUTES: 0x21808

Kernel Generated Triage Dump

FAULTING_THREAD: ffffc28996d35080

EXCEPTION_RECORD: fffffe80ba6ae9d0 -- (.exr 0xfffffe80ba6ae9d0)

ExceptionAddress: fffff806c0681caf (nt!RtlRaiseStatus+0x000000000000004f)

ExceptionCode: c0000046

ExceptionFlags: 00000081

NumberParameters: 0

CONTEXT: fffffe80ba6aea70 -- (.cxr 0xfffffe80ba6aea70)

rax=0000000000000000 rbx=00000000c0000001 rcx=ffffc289917622e7

rdx=fffff806c06ec8df rsi=0000000000000000 rdi=0000000000000000

rip=fffff806c0681caf rsp=fffffe80ba6ae9b0 rbp=0000000000000004

r8=fffff80657260318 r9=0000000000000100 r10=ffffc28900000001

r11=002faef7bf400100 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=fffffe80ba6af048

iopl=0 nv up ei ng nz na po nc

cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00040282

nt!RtlRaiseStatus+0x4f:

fffff806`c0681caf 80c3ff add bl,0FFh

Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

ERROR_CODE: (NTSTATUS) 0xc0000046 - An attempt to release a mutant object was made by a thread that was not the owner of the mutant object.

EXCEPTION_CODE_STR: c0000046

EXCEPTION_STR: 0xc0000046

IP_IN_PAGED_CODE:

nt!RtlRaiseStatus+4f

fffff806`c0681caf 80c3ff add bl,0FFh

STACK_TEXT:

fffffe80ba6ae9b0 fffff806c06e8636 : ffff2afd32d4cccc 0000000000000000 0000f0000000e000 0000000000000000 : nt!RtlRaiseStatus+0x4f

fffffe80ba6aef50 fffff806c06e80fa : fffff80657336b70 fffff80600000001 ffffc28994210000 0000000000000000 : nt!KeReleaseMutantEx+0x526

fffffe80ba6af010 fffff80657260fc4 : ffffc28994210000 fffff80600000000 ffffc28994210000 fffff806572c1290 : nt!KeReleaseMutex+0x2a

fffffe80ba6af040 ffffc28994210000 : fffff80600000000 ffffc28994210000 fffff806572c1290 ffffc28991754000 : rtwlane711+0x580fc4

fffffe80ba6af048 fffff80600000000 : ffffc28994210000 fffff806572c1290 ffffc28991754000 0000000000000000 : 0xffffc289`94210000

fffffe80ba6af050 ffffc28994210000 : fffff806572c1290 ffffc28991754000 0000000000000000 ffffc2899164dbf0 : 0xfffff806`00000000

fffffe80ba6af058 fffff806572c1290 : ffffc28991754000 0000000000000000 ffffc2899164dbf0 fffff80656f7a355 : 0xffffc289`94210000

fffffe80ba6af060 ffffc28991754000 : 0000000000000000 ffffc2899164dbf0 fffff80656f7a355 0000000000000000 : rtwlane711+0x5e1290

fffffe80ba6af068 0000000000000000 : ffffc2899164dbf0 fffff80656f7a355 0000000000000000 0000000000000006 : 0xffffc289`91754000

SYMBOL_NAME: rtwlane711+580fc4

MODULE_NAME: rtwlane711

IMAGE_NAME: rtwlane711.sys

STACK_COMMAND: .cxr 0xfffffe80ba6aea70 ; kb

BUCKET_ID_FUNC_OFFSET: 580fc4

FAILURE_BUCKET_ID: 0x7E_C0000046_rtwlane711!unknown_function

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {adad48bd-bf5b-5bbe-dc04-b77f1d188e45}

Followup: MachineOwner

Windows for home | Other | Performance and system failures
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sakiko 39,240 Reputation points Independent Advisor
    2026-04-26T23:43:05.03+00:00

    Hello, the information you provided indicates that a driver related to your wireless network is causing the issue.

    This may be due to a faulty Realtek network adapter or a driver malfunction. I recommend that you first visit the device manufacturer's website to download the latest version of the wireless network adapter driver; then, uninstall your current driver and install the newly downloaded version.

    You can locate and uninstall your network adapter driver via the "Programs" section in the Control Panel.

    Additionally, if you have installed any applications that modify network settings (such as proxy software), please uninstall them.

    Was this answer helpful?

    0 comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  3. AI answer

    2026-04-26T21:47:14.8366667+00:00

    The crash dump shows bug check 0x1000007E / 0x7E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, with the failure bucket 0x7E_C0000046_rtwlane711!unknown_function. This is the miniport/network driver rtwlane711.sys, and the stack clearly shows it involved when the kernel raises status 0xC0000046.

    Bug check 0x7E indicates a system thread generated an exception that was not caught by the error handler. In this dump, the exception is raised while the kernel is releasing a synchronization object that the Realtek wireless driver is using, which is consistent with a faulty or incompatible driver.

    Actionable steps based on the dump and standard guidance for 0x7E:

    1. Focus on rtwlane711.sys
      • This driver is identified in the analysis (IMAGE_NAME: rtwlane711.sys, SYMBOL_NAME: rtwlane711+580fc4).
      • Even if Device Manager reports the driver as “up to date”, it can still be buggy or incompatible.
    2. Replace or roll back the wireless/network driver
      • Obtain a different version of the wireless adapter driver directly from the laptop or motherboard vendor support site (not via generic Windows Update if possible).
      • Options:
        • If currently using a vendor-supplied driver, try the latest version from the vendor.
        • If already on the latest, try an earlier stable version (roll back) that matches the device and OS.
      • After installing the alternative version, restart and test with Wi‑Fi enabled to see if blue screens stop.
    3. As a temporary stability test
      • Disable the wireless adapter in Device Manager and run the system for a while using wired Ethernet (if available) or offline.
      • If the blue screens stop when the adapter is disabled, that further confirms the driver as the cause.
    4. General 0x7E troubleshooting
      • Check Event Viewer → System log for additional errors around the time of the crashes that might show related driver or firmware issues.
      • Confirm there are no recent hardware changes and that the wireless adapter and other hardware are supported for the installed Windows version.

    If further analysis is needed, use WinDbg with !analyze on multiple dumps to confirm that rtwlane711.sys is consistently in the stack at the time of the 0x7E bug check.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.