Windows 10 mavi ekran hatası

Briares

Decapat
Katılım
20 Ağustos 2020
Mesajlar
7

Arkadaşlar Dragon Center denilen 'dandik' program üzerinden driver güncellemesi yaptığım sırada driverı düzgün kuramayıp bilgisayarı yeniden başlattı, daha sonra ise Realtek Audio Console açtığımda mavi ekran verdi. Kaldırıp baştan yükledim bu sorunun önüne geçtim fakat mavi ekran hatasını almaya devam ettim. Driverları setup üzerinden onar dedim, fakat halen mavi ekran almaya devam ediyorum. Minidump dosyalarını paylaştım şimdiden teşekkürler.
 
Son düzenleyen: Moderatör:
Realtek WLAN usb driverini kurun.
Kod:
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: fffff80528681e9d, The address that the exception occurred at
Arg3: ffffc105bd5316f8, Exception Record Address
Arg4: ffffc105bd530f30, Context Record Address

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

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

KEY_VALUES_STRING: 1

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 5874

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-OOL53A3

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 49437

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80528681e9d

BUGCHECK_P3: ffffc105bd5316f8

BUGCHECK_P4: ffffc105bd530f30

EXCEPTION_RECORD:  ffffc105bd5316f8 -- (.exr 0xffffc105bd5316f8)
ExceptionAddress: fffff80528681e9d (rtwlanu!MgntSet_TX_LDPC+0x000000000000002d)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000619f88
Attempt to read from address 0000000000619f88

CONTEXT:  ffffc105bd530f30 -- (.cxr 0xffffc105bd530f30)
rax=0000000000000000 rbx=ffffd9813eb38901 rcx=0000000000000000
rdx=0000000000000008 rsi=fffff805289d0086 rdi=ffffd9814881f4c8
rip=fffff80528681e9d rsp=ffffc105bd531930 rbp=0000000000000000
r8=0000000000000001  r9=0000000000000000 r10=0000000000000000
r11=ffffc105bd531940 r12=0000000000000600 r13=0000000000000000
r14=ffffd9813eb39008 r15=0000000000000002
iopl=0         nv up ei pl nz ac po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050216
rtwlanu!MgntSet_TX_LDPC+0x2d:
fffff805`28681e9d 488bb8889f6100  mov     rdi,qword ptr [rax+619F88h] ds:002b:00000000`00619f88=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

READ_ADDRESS: fffff8051e6fa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8051e60f2e0: Unable to get Flags value from nt!KdVersionBlock
fffff8051e60f2e0: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
0000000000619f88

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:  0000000000619f88

EXCEPTION_STR:  0xc0000005

STACK_TEXT:
ffffc105`bd531930 fffff805`288b5189     : ffffd981`3eb389c0 fffff805`28970a1d fffff805`289d0086 ffffd981`4881f4c8 : rtwlanu!MgntSet_TX_LDPC+0x2d
ffffc105`bd531960 fffff805`288b509e     : ffffd981`3eb389c0 fffff805`28970a98 fffff805`289d0000 00000000`00000600 : rtwlanu!phydm_ra_mask_watchdog+0xd9
ffffc105`bd5319c0 fffff805`2889deb3     : ffffd981`00000000 ffffd981`3eb389c0 fffff805`28970a98 fffff805`289d0000 : rtwlanu!phydm_ra_info_watchdog+0x1e
ffffc105`bd5319f0 fffff805`286ae59c     : 00000000`0000000c fffff805`28970a98 fffff805`289d0000 fffff805`2873e2a0 : rtwlanu!phydm_watchdog+0xab
ffffc105`bd531a20 fffff805`2873421b     : ffffd981`42400000 ffffd981`42400000 ffffd981`414ee050 00000000`00000000 : rtwlanu!HalDmWatchDog+0x1cc
ffffc105`bd531a70 fffff805`2854ec3c     : fffff805`287341a0 fffff805`285fdd80 ffffd981`50e71180 ffffefa4`8be48852 : rtwlanu!RtCheckForHangWorkItemCallback8812+0x7b
ffffc105`bd531aa0 fffff805`20699b41     : ffffd981`414ddbb0 00000000`00000600 fffff805`20699b30 ffffd981`38c61c90 : rtwlanu!Ndis6WorkItemCallback+0x4c
ffffc105`bd531ad0 fffff805`1dc0e815     : 00000000`00000000 ffffd981`414ddbb0 ffffd981`414ee050 fffff805`1fbbc5c0 : ndis!ndisDispatchIoWorkItem+0x11
ffffc105`bd531b00 fffff805`1dcc1f15     : ffffd981`50e71040 ffffd981`50e71040 fffff805`1dc0e6e0 00000000`00000000 : nt!IopProcessWorkItem+0x135
ffffc105`bd531b70 fffff805`1dc66dd5     : ffffd981`50e71040 00000000`00000080 ffffd981`38c80040 00000000`00000000 : nt!ExpWorkerThread+0x105
ffffc105`bd531c10 fffff805`1ddfb4f8     : ffff9d81`a0dc7180 ffffd981`50e71040 fffff805`1dc66d80 00000000`00000246 : nt!PspSystemThreadStartup+0x55
ffffc105`bd531c60 00000000`00000000     : ffffc105`bd532000 ffffc105`bd52c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  rtwlanu!MgntSet_TX_LDPC+2d

MODULE_NAME: rtwlanu

IMAGE_NAME:  rtwlanu.sys

IMAGE_VERSION:  1030.38.712.2019

STACK_COMMAND:  .cxr 0xffffc105bd530f30 ; kb

BUCKET_ID_FUNC_OFFSET:  2d

FAILURE_BUCKET_ID:  AV_rtwlanu!MgntSet_TX_LDPC

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {d549de2a-4d46-c3d4-92a0-954ac217f622}

Followup:     MachineOwner
---------
Kod:
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: fffff80379d31e9d, The address that the exception occurred at
Arg3: ffff8a89bdf1a6f8, Exception Record Address
Arg4: ffff8a89bdf19f30, Context Record Address

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

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

KEY_VALUES_STRING: 1

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 4359

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-OOL53A3

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 10467

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80379d31e9d

BUGCHECK_P3: ffff8a89bdf1a6f8

BUGCHECK_P4: ffff8a89bdf19f30

EXCEPTION_RECORD:  ffff8a89bdf1a6f8 -- (.exr 0xffff8a89bdf1a6f8)
ExceptionAddress: fffff80379d31e9d (rtwlanu!MgntSet_TX_LDPC+0x000000000000002d)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000619f88
Attempt to read from address 0000000000619f88

CONTEXT:  ffff8a89bdf19f30 -- (.cxr 0xffff8a89bdf19f30)
rax=0000000000000000 rbx=ffffb70843b38901 rcx=0000000000000000
rdx=0000000000000009 rsi=fffff8037a080086 rdi=ffffb7084de1f4c8
rip=fffff80379d31e9d rsp=ffff8a89bdf1a930 rbp=0000000000000000
r8=0000000000000001  r9=0000000000000000 r10=0000000000000000
r11=ffff8a89bdf1a940 r12=0000000000000000 r13=0000000000000000
r14=ffffb70843b39009 r15=0000000000000002
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050202
rtwlanu!MgntSet_TX_LDPC+0x2d:
fffff803`79d31e9d 488bb8889f6100  mov     rdi,qword ptr [rax+619F88h] ds:002b:00000000`00619f88=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

READ_ADDRESS: fffff803712fa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8037120f2e0: Unable to get Flags value from nt!KdVersionBlock
fffff8037120f2e0: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
0000000000619f88

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:  0000000000619f88

EXCEPTION_STR:  0xc0000005

STACK_TEXT:
ffff8a89`bdf1a930 fffff803`79f65189     : ffffb708`43b389c0 fffff803`7a020a1e fffff803`7a080086 ffffb708`4de1f4c8 : rtwlanu!MgntSet_TX_LDPC+0x2d
ffff8a89`bdf1a960 fffff803`79f6509e     : ffffb708`43b389c0 fffff803`7a020a98 fffff803`7a080000 00000000`00000000 : rtwlanu!phydm_ra_mask_watchdog+0xd9
ffff8a89`bdf1a9c0 fffff803`79f4deb3     : ffffb708`00000000 ffffb708`43b389c0 fffff803`7a020a98 fffff803`7a080000 : rtwlanu!phydm_ra_info_watchdog+0x1e
ffff8a89`bdf1a9f0 fffff803`79d5e59c     : 00000000`0000000c fffff803`7a020a98 fffff803`7a080000 fffff803`79dee2a0 : rtwlanu!phydm_watchdog+0xab
ffff8a89`bdf1aa20 fffff803`79de421b     : ffffb708`47a00000 ffffb708`47a00000 ffffb708`46add050 00000000`00000000 : rtwlanu!HalDmWatchDog+0x1cc
ffff8a89`bdf1aa70 fffff803`79bfec3c     : fffff803`79de41a0 ffffb708`46a80d04 ffffb708`3f3d41c0 ffffdfdf`a12560c4 : rtwlanu!RtCheckForHangWorkItemCallback8812+0x7b
ffff8a89`bdf1aaa0 fffff803`75fb9b41     : ffffb708`46aec630 00000000`00000000 fffff803`75fb9b30 ffffb708`3f38aa60 : rtwlanu!Ndis6WorkItemCallback+0x4c
ffff8a89`bdf1aad0 fffff803`7080e815     : 00000000`00000000 ffffb708`46aec630 ffffb708`46add050 fffff803`757bc5c0 : ndis!ndisDispatchIoWorkItem+0x11
ffff8a89`bdf1ab00 fffff803`708c1f15     : ffffb708`3f3d4080 ffffb708`3f3d4080 fffff803`7080e6e0 ffffb708`00000000 : nt!IopProcessWorkItem+0x135
ffff8a89`bdf1ab70 fffff803`70866dd5     : ffffb708`3f3d4080 00000000`00000080 ffffb708`3f277040 000f8067`bcbbbdff : nt!ExpWorkerThread+0x105
ffff8a89`bdf1ac10 fffff803`709fb4f8     : ffffdf80`1dad0180 ffffb708`3f3d4080 fffff803`70866d80 0774ff85`480c7501 : nt!PspSystemThreadStartup+0x55
ffff8a89`bdf1ac60 00000000`00000000     : ffff8a89`bdf1b000 ffff8a89`bdf15000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  rtwlanu!MgntSet_TX_LDPC+2d

MODULE_NAME: rtwlanu

IMAGE_NAME:  rtwlanu.sys

IMAGE_VERSION:  1030.38.712.2019

STACK_COMMAND:  .cxr 0xffff8a89bdf19f30 ; kb

BUCKET_ID_FUNC_OFFSET:  2d

FAILURE_BUCKET_ID:  AV_rtwlanu!MgntSet_TX_LDPC

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {d549de2a-4d46-c3d4-92a0-954ac217f622}

Followup:     MachineOwner
---------
Sorun bilgisayarınıza usb girişinden taktığınız Wİ-Fİ adaptörünün sürücüsü ile ilgili.
 
Son düzenleme:
Anakart driver kısmından bulamadım. Kullandığım anakart MSI X570-A PRO. Kullandığım Wi-Fi adaptörü ise ZyXEL Dual-band Wireless AC1200 USB adapter nwd6605. Driver konsunda yardımcı olursanız sevinirim.
 

Yeni konular

Geri
Yukarı