Windows 10 Pro mavi ekran hatası

Alpkaankoc19

Decapat
Katılım
5 Ekim 2021
Mesajlar
62
Daha fazla  
Cinsiyet
Erkek
Merhabalar, PC'ye Wi-Fi adaptörü takınca mavi ekran veriyor sebebi nedir ve çözümü nedir?
 

Dosya Ekleri

  • 20211009_232202.jpg
    20211009_232202.jpg
    144,4 KB · Görüntüleme: 69
 
SANIRIM OLDU :)
@MayCrasH usta sen bu işin piriymişsin benim sorunuma da el atar mısın ?
WİNDBG SONUÇLARIM ;

Microsoft (R) Windows Debugger Version 10.0.22415.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\AlpKaaN\Desktop\minidump\101021-4062-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 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff804`48a00000 PsLoadedModuleList = 0xfffff804`4962a3d0
Debug session time: Sun Oct 10 01:29:37.791 2021 (UTC + 3:00)
System Uptime: 0 days 0:00:03.464
Loading Kernel Symbols
...............................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`48df5e40 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9a05`58c58d50=000000000000007e
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80457c52061, The address that the exception occurred at
Arg3: ffff9a0558c59d48, Exception Record Address
Arg4: ffff9a0558c59580, Context Record Address

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : AV.Dereference
Value: NullClassPtr

Key : AV.Fault
Value: Read

Key : Analysis.CPU.mSec
Value: 5281

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 80179

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

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

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

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80457c52061

BUGCHECK_P3: ffff9a0558c59d48

BUGCHECK_P4: ffff9a0558c59580

EXCEPTION_RECORD: ffff9a0558c59d48 -- (.exr 0xffff9a0558c59d48)
ExceptionAddress: fffff80457c52061 (netr28ux!RTMPIndicateScanStatus+0x0000000000000229)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000018
Attempt to read from address 0000000000000018

CONTEXT: ffff9a0558c59580 -- (.cxr 0xffff9a0558c59580)
rax=0000000000000000 rbx=ffffb60bc4710000 rcx=fffff80457e03ac0
rdx=0000000000000000 rsi=0000000000000000 rdi=fffff80457dc9158
rip=fffff80457c52061 rsp=ffff9a0558c59f80 rbp=ffff9a0558c5a001
r8=0000000000000000 r9=ffffca80b7180101 r10=ffffb60bbe802d80
r11=ffffb60bc1fe8a30 r12=ffffb60bc6521000 r13=ffffb60bc4a3f628
r14=0000000000000000 r15=000000000000001c
iopl=0 nv up ei pl nz ac po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050216
netr28ux!RTMPIndicateScanStatus+0x229:
fffff804`57c52061 837e1800 cmp dword ptr [rsi+18h],0 ds:002b:00000000`00000018=????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

READ_ADDRESS: fffff804496fb390: 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
0000000000000018

ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek u olamaz %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000018

EXCEPTION_STR: 0xc0000005

STACK_TEXT:
ffff9a05`58c59f80 fffff804`57cb5af5 : 00000000`00000001 00000000`c000000e ffff9a05`58c5a059 000049f4`3c102578 : netr28ux!RTMPIndicateScanStatus+0x229
ffff9a05`58c59ff0 fffff804`57cafb2c : ffffb60b`c4710000 ffffb60b`c4710000 00000000`00000000 ffffb60b`c1ff3c40 : netr28ux!RTUSB_VendorRequest+0x40d
ffff9a05`58c5a0a0 fffff804`57d862ee : 00000000`00000000 00000000`00000000 fffff804`57dc9000 fffff804`00000000 : netr28ux!RTUSBReadMACRegister+0x3c
ffff9a05`58c5a0f0 fffff804`57c3c965 : 00000000`00000000 00000000`00000001 00000000`00000001 fffff804`4bdaa340 : netr28ux!GET_ASIC_VERSION_ID+0x1e
ffff9a05`58c5a130 fffff804`4bddf99c : ffffb60b`c6591060 ffffb60b`c65201a0 ffff9a05`58c5a410 ffffb60b`c6591060 : netr28ux!RTMPInitialize+0x269
ffff9a05`58c5a2b0 fffff804`4be0f51a : 00000000`00000001 00000000`00000000 ffffb60b`c65201a0 ffffb60b`c3bf38c0 : ndis!ndisMInvokeInitialize+0xa0
ffff9a05`58c5a320 fffff804`4bd14e2c : ffffb60b`c6511010 ffffb60b`c6591060 00000000`00000000 01d7bd5d`24cd266f : ndis!ndisMInitializeAdapter+0x9a2
ffff9a05`58c5a9d0 fffff804`4bd03e62 : ffffb60b`c6511010 00000000`00000000 fffff804`4bda9778 ffffb60b`c65201a0 : ndis!ndisInitializeAdapter+0x98
ffff9a05`58c5aa40 fffff804`4bd01a7b : ffffb60b`c65201a0 ffffb60b`c65201a0 fffff804`4bd01980 00000000`00000000 : ndis!ndisPnPStartDevice+0x13a
ffff9a05`58c5aad0 fffff804`4bd019b1 : fffff804`49725440 ffffb60b`c65201a0 ffffb60b`c3103950 00000000`00000000 : ndis!ndisStartDeviceSynchronous+0x73
ffff9a05`58c5ab40 fffff804`48c25975 : ffffb60b`be839140 ffffb60b`be68bcc0 ffffb60b`be68bcc0 ffffb60b`00000000 : ndis!ndisStartDeviceWorkItem+0x31
ffff9a05`58c5ab70 fffff804`48d17e85 : ffffb60b`be839140 00000000`00000080 ffffb60b`be6e0200 44f6ffc6`7c5ee820 : nt!ExpWorkerThread+0x105
ffff9a05`58c5ac10 fffff804`48dfd498 : fffff804`44a24180 ffffb60b`be839140 fffff804`48d17e30 44c0af0f`44f1f7d2 : nt!PspSystemThreadStartup+0x55
ffff9a05`58c5ac60 00000000`00000000 : ffff9a05`58c5b000 ffff9a05`58c55000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: netr28ux!RTMPIndicateScanStatus+229

MODULE_NAME: netr28ux

IMAGE_NAME: netr28ux.sys

IMAGE_VERSION: 5.1.22.0

STACK_COMMAND: .cxr 0xffff9a0558c59580 ; kb

BUCKET_ID_FUNC_OFFSET: 229

FAILURE_BUCKET_ID: AV_netr28ux!RTMPIndicateScanStatus

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {5bb8c45b-6dc9-dc60-3109-b9f7a04a1ea6}

Followup: MachineOwner
---------
 
Son düzenleme:
Bu işin piriyim diyemem, diyebileceğim tek bir insan var ama neyse. Konumuz bu değil.


Sana sabahtan söylediğim gibi, USB adaptörün sürücüsü çökertiyor.
MediaTek 802.1n Wireless Driver yani.

Bana Donanım Kimliği verdiğin takdirde sürücüsünü veririm.
 
Bu işin piriyim diyemem, diyebileceğim tek bir insan var ama neyse. Konumuz bu değil.

Sana sabahtan söylediğim gibi, USB adaptörün sürücüsü çökertiyor.
MediaTek 802.1n Wireless driver yani.

Bana donanım kimliği verdiğin takdirde sürücüsünü veririm.

Evet adaptör çökertiyor. Şöyle bir şey var format atmadan önce bir sıkıntı yoktu. Önceki format dosyasıyla aynı yeni attığım ama bu sefer çökertiyor anlamadım bu işten.
Donanım kimliği;
USB\VID_148F&PID_3070&REV_0101
USB\VID_148F&PID_3070
 

Geri
Yukarı