Bilgisayar açılışında mavi ekran

Katılım
20 Haziran 2017
Mesajlar
822
Makaleler
1
Çözümler
5
Yer
Ásgard
Daha fazla  
Cinsiyet
Erkek
Meslek
Part time God of wisdom, poetry, death, divination, and magic
Arkadaşlar merhaba. Son 2-3 gündür açılışta mavi ekran alıyorum. Yakın zamanda ekran kartı güncellemelerini ve Windows 10 2004 Ekim güncellemesini yaptım. Rica etsem minidump dosyalarını (2 tane) inceleyebilir misiniz?


 
Bluetooth sürücüleriniz de güncel değil ise güncelleyin. Bluetooth ile kullandığınız cihazlar var ise bir kereliğine onlar olmadan başlatmayı deneyin.

Güncel veya yüklü değil ise çipset sürücüsünü yükleyin.

Sürücünün destek listesinde böyle yazıyor. Sizdeki model 4600H. "Ryzen 4000 Series" gibi bir şey yazmıyor fakat "AMD Ryzen™ Mobile Processor with Radeon™ Graphics" yazıyor. Bu durumda yine de uyumlu olur mu, tam emin olamadım. Linkini aşağıya bırakıyorum yüklemek istersiniz diye.

AMD Ryzen™ 5000 Series Desktop Processor
3rd Gen AMD Ryzen™ Threadripper™ Processors
3rd Gen AMD Ryzen™ Desktop Processor
2nd Gen AMD Ryzen™ Threadripper™ Processor
2nd Gen AMD Ryzen™ Desktop Processor
AMD Ryzen™ Desktop Processor
AMD Ryzen™ Threadripper™ Processor
AMD Ryzen™ Desktop Processor with Radeon™ Graphics
AMD Ryzen™ Mobile Processor with Radeon™ Graphics
7th-Gen AMD A-Series Processors
AMD B350 Chipset
AMD A320 Chipset
AMD X370 Chipset
AMD X399 Chipset
AMD B450 Chipset
AMD X470 Chipset
AMD X570 Chipset
AMD B550 Chipset
AMD A520 Chipset
AMD TRX40 Chipset

 
Son düzenleme:
  • Anladığım kadarıyla bir kablosuz adaptör yardımıyla Xbox 360 kontrolcüsü kullanıyorsunuz. Sorun çıkarmış gibi görünüyor, bir süre kullanmayın.
  • Samsung Magician'ı kaldırın.
  • Bluetooth sürücülerinizi güncelleyin.
  • Çipset sürücülerinizi güncelleyin diyeceğim fakat AMD'nin sürücü sayfasında FP6 soket yapısıyla ilgili bir şey görünmüyor.
  • MemTest86 yaparsanız iyi olur ama şimdilik yapmanız gerekmiyor.
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: fffff8078266a234, The address that the exception occurred at
Arg3: ffffb28c50a9f3e8, Exception Record Address
Arg4: ffffb28c50a9ec20, 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: 6343

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 10435

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

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

BUGCHECK_P3: ffffb28c50a9f3e8

BUGCHECK_P4: ffffb28c50a9ec20

EXCEPTION_RECORD:  ffffb28c50a9f3e8 -- (.exr 0xffffb28c50a9f3e8)
ExceptionAddress: fffff8078266a234 (USBXHCI!UsbDevice_SetDeviceDisabled+0x0000000000000058)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000049
Attempt to read from address 0000000000000049

CONTEXT:  ffffb28c50a9ec20 -- (.cxr 0xffffb28c50a9ec20)
rax=fffff807826b28a0 rbx=ffffe00161b95d10 rcx=0000000000000001
rdx=0000000000000004 rsi=ffffe001525f8198 rdi=0000000000000001
rip=fffff8078266a234 rsp=ffffb28c50a9f620 rbp=0000000000000004
r8=000000000000000c  r9=000000000000003a r10=ffffe00152548184
r11=ffffb28c50a9f678 r12=0000000000000003 r13=0000000000000000
r14=fffff807826c0460 r15=fffff807826c0460
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00050206
USBXHCI!UsbDevice_SetDeviceDisabled+0x58:
fffff807`8266a234 488b4948        mov     rcx,qword ptr [rcx+48h] ds:002b:00000000`00000049=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

READ_ADDRESS: fffff807662fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8076620f340: Unable to get Flags value from nt!KdVersionBlock
fffff8076620f340: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
0000000000000049

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

EXCEPTION_STR:  0xc0000005

STACK_TEXT:
ffffb28c`50a9f620 fffff807`8266a160     : ffffe001`525f8160 00000000`00000004 ffffe001`525f8198 fffff807`826c0460 : USBXHCI!UsbDevice_SetDeviceDisabled+0x58
ffffb28c`50a9f680 fffff807`8266abdd     : ffffe001`525f8198 00000000`00000004 00000000`00000004 ffffb28c`00000000 : USBXHCI!DeviceSlot_DisableAllDeviceSlots+0x44
ffffb28c`50a9f6b0 fffff807`82673d63     : 00000000`00000000 00000000`00000004 00001ffe`ada42588 00000000`00000004 : USBXHCI!DeviceSlot_D0EntryCleanupState+0x81
ffffb28c`50a9f700 fffff807`6a9c8a0e     : 00000001`0bb80bec ffffe001`52713da8 ffffe001`525bda70 00000000`00000660 : USBXHCI!Controller_WdfEvtDeviceD0Entry+0x163
ffffb28c`50a9f790 fffff807`6a9c6f81     : ffffe001`52713da8 00000000`000001a4 ffffe001`5a0f000e ffffb28c`50a9f888 : Wdf01000!FxPnpDeviceD0Entry::InvokeClient+0x2e [minkernel\wdf\framework\shared\irphandlers\pnp\pnpcallbacks.cpp @ 93]
ffffb28c`50a9f7f0 fffff807`6a9c7dfd     : ffffe001`52713870 ffffb28c`50a9f960 00000000`00000660 00000000`00000000 : Wdf01000!FxPrePostCallback::InvokeStateful+0x69 [minkernel\wdf\framework\shared\irphandlers\pnp\cxpnppowercallbacks.cpp @ 275]
ffffb28c`50a9f830 fffff807`6a9c25f5     : 00000000`00000300 00000000`00000020 ffffe001`52713870 00000000`00000301 : Wdf01000!FxPkgPnp::PowerWaking+0x3d [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 3549]
ffffb28c`50a9f860 fffff807`6a9c23aa     : ffffb28c`50a9faa0 ffffe001`52713870 ffffe001`52713870 00000000`00100000 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x155 [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 1699]
ffffb28c`50a9f9c0 fffff807`6a9c1ad8     : ffffe001`52713a78 ffffb28c`50a9fac0 ffffb28c`50a9faa0 ffffe001`00000000 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0xea [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 1615]
ffffb28c`50a9fa40 fffff807`6a9c6792     : ffffe001`52713a50 ffffe001`52713a70 00000000`00000000 00000000`00000000 : Wdf01000!FxPkgPnp::_PowerProcessEventInner+0x68 [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 1447]
ffffb28c`50a9fa80 fffff807`6a9c66ec     : 00000000`00000000 ffffe001`4ff57690 00000000`00000000 fffff807`6a9c66e0 : Wdf01000!FxEventQueue::EventQueueWorker+0x9a [minkernel\wdf\framework\shared\irphandlers\pnp\eventqueue.cpp @ 277]
ffffb28c`50a9fad0 fffff807`6581aad5     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff807`73f153f0 : Wdf01000!FxThreadedEventQueue::_WorkItemCallback+0xc [minkernel\wdf\framework\shared\irphandlers\pnp\eventqueue.cpp @ 437]
ffffb28c`50a9fb00 fffff807`659035f5     : ffffe001`62d90040 ffffe001`62d90040 fffff807`6581a9a0 00000000`00000000 : nt!IopProcessWorkItem+0x135
ffffb28c`50a9fb70 fffff807`658a2ae5     : ffffe001`62d90040 00000000`00000080 ffffe001`4ced0200 00000000`00000001 : nt!ExpWorkerThread+0x105
ffffb28c`50a9fc10 fffff807`659fbbf8     : fffff807`63fbb180 ffffe001`62d90040 fffff807`658a2a90 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffb28c`50a9fc60 00000000`00000000     : ffffb28c`50aa0000 ffffb28c`50a9a000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  USBXHCI!UsbDevice_SetDeviceDisabled+58

MODULE_NAME: USBXHCI

IMAGE_NAME:  USBXHCI.SYS

IMAGE_VERSION:  10.0.19041.508

STACK_COMMAND:  .cxr 0xffffb28c50a9ec20 ; kb

BUCKET_ID_FUNC_OFFSET:  58

FAILURE_BUCKET_ID:  AV_USBXHCI!UsbDevice_SetDeviceDisabled

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {47988abd-6b08-02ef-d2f7-500a8cad3c75}

Followup:     MachineOwner
---------

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: 000002b000000472, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80621530293, address which referenced memory

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5812

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 41141

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

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

BUGCHECK_P1: 2b000000472

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff80621530293

WRITE_ADDRESS: fffff80621efb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80621e0f340: Unable to get Flags value from nt!KdVersionBlock
fffff80621e0f340: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
000002b000000472

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  fffffa060c4e65f0 -- (.trap 0xfffffa060c4e65f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=000000000000000f rsi=0000000000000000 rdi=0000000000000000
rip=fffff80621530293 rsp=fffffa060c4e6780 rbp=000000000000001d
r8=0000000000000000  r9=ffffbb0275183140 r10=fffff80621530240
r11=ffff8f7de8a00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KeAcquireSpinLockRaiseToDpc+0x53:
fffff806`21530293 f0480fba2b00    lock bts qword ptr [rbx],0 ds:00000000`00000000=????????????????
Resetting default scope

STACK_TEXT:
fffffa06`0c4e64a8 fffff806`21606569     : 00000000`0000000a 000002b0`00000472 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffffa06`0c4e64b0 fffff806`21602869     : 00000000`00000000 00000000`00000001 00000000`00140001 00000000`00000020 : nt!KiBugCheckDispatch+0x69
fffffa06`0c4e65f0 fffff806`21530293     : 000044fd`99132d28 fffff806`243b2ae5 ffffbb02`663f2dd0 ffffbb02`66ecd2d0 : nt!KiPageFault+0x469
fffffa06`0c4e6780 fffff806`3ba57e9a     : 000002b0`00000472 00000000`0000000f ffffbb02`669c6a10 fffff806`3ba569c8 : nt!KeAcquireSpinLockRaiseToDpc+0x53
fffffa06`0c4e67b0 fffff806`3ba8592d     : ffffbb02`66971150 00000000`00000000 ffffbb02`698f9660 00000000`00000004 : USBXHCI!ESM_AddEvent+0x2a
fffffa06`0c4e67f0 fffff806`3ba81c1c     : ffffbb02`66efc470 00000000`00000000 00000000`00000000 fffff806`3baf762f : USBXHCI!DeviceSlot_ControllerResetPreReset+0x61
fffffa06`0c4e6820 fffff806`3ba837d8     : ffffbb02`669c6a10 fffff806`3baa2901 00000000`ebe40011 000044fd`99639698 : USBXHCI!Controller_InternalReset+0x124
fffffa06`0c4e6880 fffff806`3bb0d5d1     : 00000000`00000000 00000000`00000000 00000000`00000050 00000000`000005fa : USBXHCI!Controller_UcxEvtReset+0x58
fffffa06`0c4e68e0 fffff806`3baf757a     : 00000000`ebe40011 00000000`00000000 00000000`00000004 00000000`00000000 : ucx01000!ControllerResetStateEntryFunc_CallHCDToReset1+0x11
fffffa06`0c4e6910 fffff806`3bb0c777     : 00000000`00000002 fffff806`3baa2998 fffff806`3bab0460 ffffbb02`670f0360 : ucx01000!StateMachineEngine_EventAdd+0x26a
fffffa06`0c4e6970 fffff806`3ba8190c     : 00000000`00000002 fffff806`3baa2998 fffff806`3bab0460 00000000`00000000 : ucx01000!UcxControllerNeedsReset+0x37
fffffa06`0c4e69a0 fffff806`3ba82fa7     : ffffbb02`670f0360 fffffa06`0c4e6a80 ffffbb02`670f0360 fffffa06`0c4e6a80 : USBXHCI!Controller_InitiateRecovery+0x16c
fffffa06`0c4e6a40 fffff806`243bc6a7     : ffffbb02`670f0260 ffffbb02`00000004 00000000`00000004 00000000`00000000 : USBXHCI!Controller_TelemetryReportWorker+0x317
fffffa06`0c4e6ac0 fffff806`2141aad5     : ffffbb02`66ebfdb0 00000000`00000000 ffffbb02`66960a80 fffff806`243bc5c0 : Wdf01000!FxWorkItem::WorkItemThunk+0xe7 [minkernel\wdf\framework\shared\core\fxworkitem.cpp @ 431]
fffffa06`0c4e6b00 fffff806`215035f5     : ffffbb02`75183140 ffffbb02`75183140 fffff806`2141a9a0 00000000`00000000 : nt!IopProcessWorkItem+0x135
fffffa06`0c4e6b70 fffff806`214a2ae5     : ffffbb02`75183140 00000000`00000080 ffffbb02`612cb200 00000000`00000001 : nt!ExpWorkerThread+0x105
fffffa06`0c4e6c10 fffff806`215fbbf8     : ffff9f81`cea79180 ffffbb02`75183140 fffff806`214a2a90 00000000`00000004 : nt!PspSystemThreadStartup+0x55
fffffa06`0c4e6c60 00000000`00000000     : fffffa06`0c4e7000 fffffa06`0c4e1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  USBXHCI!ESM_AddEvent+2a

MODULE_NAME: USBXHCI

IMAGE_NAME:  USBXHCI.SYS

IMAGE_VERSION:  10.0.19041.508

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  2a

FAILURE_BUCKET_ID:  AV_USBXHCI!ESM_AddEvent

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {66ca21ee-0eb2-5aa3-c5f6-e20354548b1f}

Followup:     MachineOwner
---------
 
Bluetooth sürücüleriniz de güncel değil ise güncelleyin. Bluetooth ile kullandığınız cihazlar var ise bir kereliğine onlar olmadan başlatmayı deneyin.

Güncel veya yüklü değil ise çipset sürücüsünü yükleyin.

Sürücünün destek listesinde böyle yazıyor. Sizdeki model 4600H. "Ryzen 4000 Series" gibi bir şey yazmıyor fakat "AMD Ryzen™ Mobile Processor with Radeon™ Graphics" yazıyor. Bu durumda yine de uyumlu olur mu, tam emin olamadım. Linkini aşağıya bırakıyorum yüklemek istersiniz diye.

AMD Ryzen™ 5000 Series Desktop Processor
3rd Gen AMD Ryzen™ Threadripper™ Processors
3rd Gen AMD Ryzen™ Desktop Processor
2nd Gen AMD Ryzen™ Threadripper™ Processor
2nd Gen AMD Ryzen™ Desktop Processor
AMD Ryzen™ Desktop Processor
AMD Ryzen™ Threadripper™ Processor
AMD Ryzen™ Desktop Processor with Radeon™ Graphics
AMD Ryzen™ Mobile Processor with Radeon™ Graphics
7th-Gen AMD A-Series Processors
AMD B350 Chipset
AMD A320 Chipset
AMD X370 Chipset
AMD X399 Chipset
AMD B450 Chipset
AMD X470 Chipset
AMD X570 Chipset
AMD B550 Chipset
AMD A520 Chipset
AMD TRX40 Chipset

  • Anladığım kadarıyla bir kablosuz adaptör yardımıyla Xbox 360 kontrolcüsü kullanıyorsunuz. Sorun çıkarmış gibi görünüyor, bir süre kullanmayın.
  • Samsung Magician'ı kaldırın.
  • Bluetooth sürücülerinizi güncelleyin.
  • Çipset sürücülerinizi güncelleyin diyeceğim fakat AMD'nin sürücü sayfasında FP6 soket yapısıyla ilgili bir şey görünmüyor.
  • MemTest86 yaparsanız iyi olur ama şimdilik yapmanız gerekmiyor.
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: fffff8078266a234, The address that the exception occurred at
Arg3: ffffb28c50a9f3e8, Exception Record Address
Arg4: ffffb28c50a9ec20, 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: 6343

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 10435

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

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

BUGCHECK_P3: ffffb28c50a9f3e8

BUGCHECK_P4: ffffb28c50a9ec20

EXCEPTION_RECORD:  ffffb28c50a9f3e8 -- (.exr 0xffffb28c50a9f3e8)
ExceptionAddress: fffff8078266a234 (USBXHCI!UsbDevice_SetDeviceDisabled+0x0000000000000058)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000049
Attempt to read from address 0000000000000049

CONTEXT:  ffffb28c50a9ec20 -- (.cxr 0xffffb28c50a9ec20)
rax=fffff807826b28a0 rbx=ffffe00161b95d10 rcx=0000000000000001
rdx=0000000000000004 rsi=ffffe001525f8198 rdi=0000000000000001
rip=fffff8078266a234 rsp=ffffb28c50a9f620 rbp=0000000000000004
r8=000000000000000c  r9=000000000000003a r10=ffffe00152548184
r11=ffffb28c50a9f678 r12=0000000000000003 r13=0000000000000000
r14=fffff807826c0460 r15=fffff807826c0460
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00050206
USBXHCI!UsbDevice_SetDeviceDisabled+0x58:
fffff807`8266a234 488b4948        mov     rcx,qword ptr [rcx+48h] ds:002b:00000000`00000049=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

READ_ADDRESS: fffff807662fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8076620f340: Unable to get Flags value from nt!KdVersionBlock
fffff8076620f340: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
0000000000000049

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

EXCEPTION_STR:  0xc0000005

STACK_TEXT:
ffffb28c`50a9f620 fffff807`8266a160     : ffffe001`525f8160 00000000`00000004 ffffe001`525f8198 fffff807`826c0460 : USBXHCI!UsbDevice_SetDeviceDisabled+0x58
ffffb28c`50a9f680 fffff807`8266abdd     : ffffe001`525f8198 00000000`00000004 00000000`00000004 ffffb28c`00000000 : USBXHCI!DeviceSlot_DisableAllDeviceSlots+0x44
ffffb28c`50a9f6b0 fffff807`82673d63     : 00000000`00000000 00000000`00000004 00001ffe`ada42588 00000000`00000004 : USBXHCI!DeviceSlot_D0EntryCleanupState+0x81
ffffb28c`50a9f700 fffff807`6a9c8a0e     : 00000001`0bb80bec ffffe001`52713da8 ffffe001`525bda70 00000000`00000660 : USBXHCI!Controller_WdfEvtDeviceD0Entry+0x163
ffffb28c`50a9f790 fffff807`6a9c6f81     : ffffe001`52713da8 00000000`000001a4 ffffe001`5a0f000e ffffb28c`50a9f888 : Wdf01000!FxPnpDeviceD0Entry::InvokeClient+0x2e [minkernel\wdf\framework\shared\irphandlers\pnp\pnpcallbacks.cpp @ 93]
ffffb28c`50a9f7f0 fffff807`6a9c7dfd     : ffffe001`52713870 ffffb28c`50a9f960 00000000`00000660 00000000`00000000 : Wdf01000!FxPrePostCallback::InvokeStateful+0x69 [minkernel\wdf\framework\shared\irphandlers\pnp\cxpnppowercallbacks.cpp @ 275]
ffffb28c`50a9f830 fffff807`6a9c25f5     : 00000000`00000300 00000000`00000020 ffffe001`52713870 00000000`00000301 : Wdf01000!FxPkgPnp::PowerWaking+0x3d [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 3549]
ffffb28c`50a9f860 fffff807`6a9c23aa     : ffffb28c`50a9faa0 ffffe001`52713870 ffffe001`52713870 00000000`00100000 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x155 [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 1699]
ffffb28c`50a9f9c0 fffff807`6a9c1ad8     : ffffe001`52713a78 ffffb28c`50a9fac0 ffffb28c`50a9faa0 ffffe001`00000000 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0xea [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 1615]
ffffb28c`50a9fa40 fffff807`6a9c6792     : ffffe001`52713a50 ffffe001`52713a70 00000000`00000000 00000000`00000000 : Wdf01000!FxPkgPnp::_PowerProcessEventInner+0x68 [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 1447]
ffffb28c`50a9fa80 fffff807`6a9c66ec     : 00000000`00000000 ffffe001`4ff57690 00000000`00000000 fffff807`6a9c66e0 : Wdf01000!FxEventQueue::EventQueueWorker+0x9a [minkernel\wdf\framework\shared\irphandlers\pnp\eventqueue.cpp @ 277]
ffffb28c`50a9fad0 fffff807`6581aad5     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff807`73f153f0 : Wdf01000!FxThreadedEventQueue::_WorkItemCallback+0xc [minkernel\wdf\framework\shared\irphandlers\pnp\eventqueue.cpp @ 437]
ffffb28c`50a9fb00 fffff807`659035f5     : ffffe001`62d90040 ffffe001`62d90040 fffff807`6581a9a0 00000000`00000000 : nt!IopProcessWorkItem+0x135
ffffb28c`50a9fb70 fffff807`658a2ae5     : ffffe001`62d90040 00000000`00000080 ffffe001`4ced0200 00000000`00000001 : nt!ExpWorkerThread+0x105
ffffb28c`50a9fc10 fffff807`659fbbf8     : fffff807`63fbb180 ffffe001`62d90040 fffff807`658a2a90 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffb28c`50a9fc60 00000000`00000000     : ffffb28c`50aa0000 ffffb28c`50a9a000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  USBXHCI!UsbDevice_SetDeviceDisabled+58

MODULE_NAME: USBXHCI

IMAGE_NAME:  USBXHCI.SYS

IMAGE_VERSION:  10.0.19041.508

STACK_COMMAND:  .cxr 0xffffb28c50a9ec20 ; kb

BUCKET_ID_FUNC_OFFSET:  58

FAILURE_BUCKET_ID:  AV_USBXHCI!UsbDevice_SetDeviceDisabled

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {47988abd-6b08-02ef-d2f7-500a8cad3c75}

Followup:     MachineOwner
---------

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: 000002b000000472, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80621530293, address which referenced memory

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5812

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 41141

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

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

BUGCHECK_P1: 2b000000472

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff80621530293

WRITE_ADDRESS: fffff80621efb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80621e0f340: Unable to get Flags value from nt!KdVersionBlock
fffff80621e0f340: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
000002b000000472

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  fffffa060c4e65f0 -- (.trap 0xfffffa060c4e65f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=000000000000000f rsi=0000000000000000 rdi=0000000000000000
rip=fffff80621530293 rsp=fffffa060c4e6780 rbp=000000000000001d
r8=0000000000000000  r9=ffffbb0275183140 r10=fffff80621530240
r11=ffff8f7de8a00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KeAcquireSpinLockRaiseToDpc+0x53:
fffff806`21530293 f0480fba2b00    lock bts qword ptr [rbx],0 ds:00000000`00000000=????????????????
Resetting default scope

STACK_TEXT:
fffffa06`0c4e64a8 fffff806`21606569     : 00000000`0000000a 000002b0`00000472 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffffa06`0c4e64b0 fffff806`21602869     : 00000000`00000000 00000000`00000001 00000000`00140001 00000000`00000020 : nt!KiBugCheckDispatch+0x69
fffffa06`0c4e65f0 fffff806`21530293     : 000044fd`99132d28 fffff806`243b2ae5 ffffbb02`663f2dd0 ffffbb02`66ecd2d0 : nt!KiPageFault+0x469
fffffa06`0c4e6780 fffff806`3ba57e9a     : 000002b0`00000472 00000000`0000000f ffffbb02`669c6a10 fffff806`3ba569c8 : nt!KeAcquireSpinLockRaiseToDpc+0x53
fffffa06`0c4e67b0 fffff806`3ba8592d     : ffffbb02`66971150 00000000`00000000 ffffbb02`698f9660 00000000`00000004 : USBXHCI!ESM_AddEvent+0x2a
fffffa06`0c4e67f0 fffff806`3ba81c1c     : ffffbb02`66efc470 00000000`00000000 00000000`00000000 fffff806`3baf762f : USBXHCI!DeviceSlot_ControllerResetPreReset+0x61
fffffa06`0c4e6820 fffff806`3ba837d8     : ffffbb02`669c6a10 fffff806`3baa2901 00000000`ebe40011 000044fd`99639698 : USBXHCI!Controller_InternalReset+0x124
fffffa06`0c4e6880 fffff806`3bb0d5d1     : 00000000`00000000 00000000`00000000 00000000`00000050 00000000`000005fa : USBXHCI!Controller_UcxEvtReset+0x58
fffffa06`0c4e68e0 fffff806`3baf757a     : 00000000`ebe40011 00000000`00000000 00000000`00000004 00000000`00000000 : ucx01000!ControllerResetStateEntryFunc_CallHCDToReset1+0x11
fffffa06`0c4e6910 fffff806`3bb0c777     : 00000000`00000002 fffff806`3baa2998 fffff806`3bab0460 ffffbb02`670f0360 : ucx01000!StateMachineEngine_EventAdd+0x26a
fffffa06`0c4e6970 fffff806`3ba8190c     : 00000000`00000002 fffff806`3baa2998 fffff806`3bab0460 00000000`00000000 : ucx01000!UcxControllerNeedsReset+0x37
fffffa06`0c4e69a0 fffff806`3ba82fa7     : ffffbb02`670f0360 fffffa06`0c4e6a80 ffffbb02`670f0360 fffffa06`0c4e6a80 : USBXHCI!Controller_InitiateRecovery+0x16c
fffffa06`0c4e6a40 fffff806`243bc6a7     : ffffbb02`670f0260 ffffbb02`00000004 00000000`00000004 00000000`00000000 : USBXHCI!Controller_TelemetryReportWorker+0x317
fffffa06`0c4e6ac0 fffff806`2141aad5     : ffffbb02`66ebfdb0 00000000`00000000 ffffbb02`66960a80 fffff806`243bc5c0 : Wdf01000!FxWorkItem::WorkItemThunk+0xe7 [minkernel\wdf\framework\shared\core\fxworkitem.cpp @ 431]
fffffa06`0c4e6b00 fffff806`215035f5     : ffffbb02`75183140 ffffbb02`75183140 fffff806`2141a9a0 00000000`00000000 : nt!IopProcessWorkItem+0x135
fffffa06`0c4e6b70 fffff806`214a2ae5     : ffffbb02`75183140 00000000`00000080 ffffbb02`612cb200 00000000`00000001 : nt!ExpWorkerThread+0x105
fffffa06`0c4e6c10 fffff806`215fbbf8     : ffff9f81`cea79180 ffffbb02`75183140 fffff806`214a2a90 00000000`00000004 : nt!PspSystemThreadStartup+0x55
fffffa06`0c4e6c60 00000000`00000000     : fffffa06`0c4e7000 fffffa06`0c4e1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  USBXHCI!ESM_AddEvent+2a

MODULE_NAME: USBXHCI

IMAGE_NAME:  USBXHCI.SYS

IMAGE_VERSION:  10.0.19041.508

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  2a

FAILURE_BUCKET_ID:  AV_USBXHCI!ESM_AddEvent

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {66ca21ee-0eb2-5aa3-c5f6-e20354548b1f}

Followup:     MachineOwner
---------

Teşekkürler hocam. BT sürücüsünü Intel Driver & Support Assistant ile güncelledim. Bağlı aygıtlardan gamepadi kaldırdım. Chipset konusu ayrı bir muamma gibi duruyor. FP6 için chipset yok sanırım. Ama FP5 chipsetleri içinde isim isim işlemci belirtilmemiş. Ne yapacağımı bilemedim. Sınavlar bitene kadar sıkıntı çıkarmaz umarım. Güz tatilinde temiz kurulum yaparım.

Kablo ile oynarım bir süre. PS4 kolu olduğu için DS4 kullanıyorum. O da Xbox 360 kolu olarak gösteriyor aygıtı.

Yardımcı olduğunuz için çok teşekkürler. Eğer yine sorun yaşarsam buradan bildiririm.
***

@yika38 @Ma'at

Arkadaşlar bilgisayarı kapatıp yeniden açınca yeniden mavi ekran hatası aldım.
 
Son düzenleme:
Hızlı başlatmayı kapatmayı deneyebilir misiniz? Bu sitede nasıl yapılacağı belirtilmiş.

Bluetooth sürücüsünü tamamen kaldırın, öyle kurmayı deneyin bir de.
Ders bitince deneyeyim hemen. Teşekkür ederim.
 
Denediniz mi hocam? Denediyseniz sonuç nedir?

Hızlı başlatma açıkken ve kapalıyken uzun kullanımda (40-50 dakika) aç kapa yaparak denedim. Sorun çıkarmadı. Tek umudum midterm haftasında mavi ekran yememek. İlginiz ve takibiniz için teşekkür ederim.
 
Uyarı! Bu konu 5 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

Technopat Haberler

Geri
Yukarı