Unsolved
1 Rookie
•
3 Posts
0
42
February 11th, 2025 09:20
Blue screen after restart
Hello!
My problem is as follow: my PC from work doesn't have a Wi-Fi card and I can't run an Ethernet cable to it. So my boss bought me this "TP-Link Wireless MU-MIMO USB Adapter". When I'm leaving work I shut down the PC, the next morning I power it up and after that I do a normal restart, because I want to have a "fresh" cache memory without some blocked registry and whatnot from past day.
After restart I get the blue screen and then I have to select if I want to "repair the PC", "continue" etc. This happens only after the PC is shut down. I work on this PC for a year now and this problem started like 2 months ago, after some Windows update or Bios update, I don't know which one.
- Windows, Bios are up-to-date;
- run Dell's "Diagnostic" from Bios and it came back without problems;
- uninstalled the Wireless Adapter from device manager, restart, plugged it back in, same problem;
- Wireless Adapter is as it is, it doesn't have any software updates.
I understand that is a problem with the Wireless Adapter, but is there a way to get rid of this problem without changing the brand? I mean, I don't know if with another brand for the Wireless Adapter I wouldn't have the same problem.
Ionut.Poh
1 Rookie
•
3 Posts
0
February 11th, 2025 09:22
Because this site doesn't let me write more than 1000 words, I have to put this one here:
After some searching I managed to get to this:
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : false
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.031 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 42
Microsoft (R) Windows Debugger Version 10.0.27725.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\021125-13859-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*https://msdl.microsoft.com/download/symbols
Symbol search path is: srv*https://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 26100 MP (32 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff803`dc800000 PsLoadedModuleList = 0xfffff803`dd6f47b0
Debug session time: Tue Feb 11 08:13:26.996 2025 (UTC + 2:00)
System Uptime: 0 days 23:57:13.040
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
............................
For analysis of this file, run !analyze -v
ndis!memcpy+0x17:
fffff803`7030b517 4c8919 mov qword ptr [rcx],r11 ds:002b:00000000`00000000=????????????????
31: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8037030b517, The address that the exception occurred at
Arg3: ffffbc89616ff2c8, Exception Record Address
Arg4: ffffbc89616feab0, Context Record Address
Debugging Details:
------------------
Ionut.Poh
1 Rookie
•
3 Posts
0
February 11th, 2025 09:23
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullPtr
Key : AV.Fault
Value: Write
Key : Analysis.CPU.mSec
Value: 1109
Key : Analysis.Elapsed.mSec
Value: 11324
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 1
Key : Analysis.Init.CPU.mSec
Value: 265
Key : Analysis.Init.Elapsed.mSec
Value: 10633
Key : Analysis.Memory.CommitPeak.Mb
Value: 114
Key : Analysis.Version.DbgEng
Value: 10.0.27725.1000
Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre
Key : Analysis.Version.Ext
Value: 1.2408.27.1
Key : Bugcheck.Code.LegacyAPI
Value: 0x1000007e
Key : Bugcheck.Code.TargetModel
Value: 0x1000007e
Key : Dump.Attributes.AsUlong
Value: 21808
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 0
Key : Failure.Bucket
Value: AV_wdiwifi!CAdapter::CompleteOidRequest
Key : Failure.Hash
Value: {ba3e9a21-72bc-ba10-0a91-c62cd5f3ea49}
Key : Hypervisor.Enlightenments.ValueHex
Value: 7417df84
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: 55185662
Key : Hypervisor.Flags.ValueHex
Value: 34a10fe
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
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff8037030b517
BUGCHECK_P3: ffffbc89616ff2c8
BUGCHECK_P4: ffffbc89616feab0
FILE_IN_CAB: 021125-13859-01.dmp
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
DUMP_FILE_ATTRIBUTES: 0x21808
Kernel Generated Triage Dump
FAULTING_THREAD: ffff988d1aaca040
EXCEPTION_RECORD: ffffbc89616ff2c8 -- (.exr 0xffffbc89616ff2c8)
ExceptionAddress: fffff8037030b517 (ndis!memcpy+0x0000000000000017)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000000
Attempt to write to address 0000000000000000
CONTEXT: ffffbc89616feab0 -- (.cxr 0xffffbc89616feab0)
rax=0000000000000000 rbx=ffffbc89616ff630 rcx=0000000000000000
rdx=679b5bff33330100 rsi=ffff988d4169a1a0 rdi=ffff988d7fd1d870
rip=fffff8037030b517 rsp=ffffbc89616ff508 rbp=0000000000000000
r8=000000000000000c r9=0000000000000044 r10=1fffff006e04a3dc
r11=3333010000003333 r12=0000000000000000 r13=ffff988d5f4d6960
r14=ffff988d4160d9b0 r15=0000000000000002
iopl=0 nv up ei ng nz na po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050287
ndis!memcpy+0x17:
fffff803`7030b517 4c8919 mov qword ptr [rcx],r11 ds:002b:00000000`00000000=????????????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
WRITE_ADDRESS: fffff803dd7c34b0: 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
0000000000000000
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000001
EXCEPTION_PARAMETER2: 0000000000000000
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
ffffbc89`616ff508 fffff803`70251f93 : 00000000`00000008 ffffbc89`616ff598 00000000`00000008 ffffbc89`616ff5a0 : ndis!memcpy+0x17
ffffbc89`616ff510 fffff803`702386c1 : ffff988d`7fd1d870 00000000`00000000 ffffbc89`616ff630 fffff803`70220000 : ndis!ndisOidPostEthMulticastList+0xb3
ffffbc89`616ff550 fffff803`70239d1c : ffff988d`4169a100 00000000`00000000 00000000`00000000 ffff988d`4169a1a0 : ndis!ndisOidRequestComplete+0x131
ffffbc89`616ff5f0 fffff803`7023a340 : ffff988d`4169a1a0 ffff988d`4169e328 00000000`00000000 00000000`00000000 : ndis!ndisMOidRequestCompleteInternal+0xdc
ffffbc89`616ff690 fffff803`7241bc10 : ffff988d`7fd1d870 ffff988d`7fd1d870 00000000`00000000 ffff988d`5c3f6b70 : ndis!ndisMRawOidRequestComplete+0x90
ffffbc89`616ff6c0 fffff803`7241bb1a : ffff988d`5c3f6b70 ffff988d`5c3f6c40 ffff988d`00000000 ffff988d`7e3ebfd0 : wdiwifi!CAdapter::CompleteOidRequest+0xe8
ffffbc89`616ff720 fffff803`724556e8 : ffff988d`41661d20 ffff988d`4169e359 fffff803`724fc040 ffff988d`4169e368 : wdiwifi!CConnectionQualityOidJob::OnOidJobCompletedEvent+0x1a
ffffbc89`616ff750 fffff803`7240db2d : ffff988d`75b0e4b0 00000000`00000001 ffff988d`5c3f6e10 ffff988d`4169e328 : wdiwifi!COidJobNotificationHandler::OnOperationCompleted+0x18
ffffbc89`616ff780 fffff803`7240d87a : fffff803`724fc040 ffff988d`4169e330 00000000`00000000 ffff393d`cb4f54b5 : wdiwifi!EventQueue::ProcessEventQueueUntilEmpty+0x12d
ffffbc89`616ff800 fffff803`7244fb02 : ffff988d`80a02150 ffff988d`80a021c0 ffff988d`80a021f0 00000000`00000000 : wdiwifi!EventQueue::OnWorkItemCallback+0x5a
ffffbc89`616ff840 fffff803`6edf98f3 : ffff988d`80a02150 ffff393d`cb4f5ba5 fffff803`dd704d48 fffff803`dca567ca : wdiwifi!CWdfWorkItemContext::s_WdfWorkItemCallback+0x42
ffffbc89`616ff870 fffff803`6edf97b9 : 000084e8`00000000 ffff988d`80a02150 00000000`00000000 ffff988d`1a7df040 : Wdf01000!FxWorkItem::WorkItemHandler+0xd7 [minkernel\wdf\framework\shared\core\fxworkitem.cpp @ 374]
ffffbc89`616ff8b0 fffff803`dca54d52 : ffff988d`5f9f49e0 ffff988d`5f9f49e0 00000000`00000000 fffff803`dcb70b56 : Wdf01000!FxWorkItem::WorkItemThunk+0x29 [minkernel\wdf\framework\shared\core\fxworkitem.cpp @ 439]
ffffbc89`616ff8f0 fffff803`dcb705a0 : ffff988d`1aaca040 00000000`00000000 ffff988d`1aaca040 ffffbc89`616ffa80 : nt!IopProcessWorkItem+0x2c2
ffffbc89`616ff980 fffff803`dcc5594a : ffff988d`1aaca040 ffff988d`1aaca040 fffff803`dcb70300 ffff988d`1a720a80 : nt!ExpWorkerThread+0x2a0
ffffbc89`616ffb30 fffff803`dce79fb4 : ffffaa01`38cd1180 ffff988d`1aaca040 fffff803`dcc558f0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
ffffbc89`616ffb80 00000000`00000000 : ffffbc89`61700000 ffffbc89`616f9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34
SYMBOL_NAME: wdiwifi!CAdapter::CompleteOidRequest+e8
MODULE_NAME: wdiwifi
IMAGE_NAME: wdiwifi.sys
IMAGE_VERSION: 10.0.26100.3037
STACK_COMMAND: .cxr 0xffffbc89616feab0 ; kb
BUCKET_ID_FUNC_OFFSET: e8
FAILURE_BUCKET_ID: AV_wdiwifi!CAdapter::CompleteOidRequest
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {ba3e9a21-72bc-ba10-0a91-c62cd5f3ea49}
Followup: MachineOwner
---------
mazzinia_
4 Operator
•
1.4K Posts
0
February 11th, 2025 13:24
Hello,
you could maybe try to remove the driver , reboot , reinstall the driver