Çözüldü BUGCODE_USB_DRIVER mavi ekran hatası

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.
İşletim sistemi
Windows 10

MrKemal421

Decapat
Katılım
9 Nisan 2023
Mesajlar
85
Çözümler
1
Daha fazla  
Cinsiyet
Erkek
RAM
6
SSD veya HDD modeli
James Donkey 120 GB
Ekran kartı
Nvidia GTS 250 1GB
Anakart
Asus M3N78-EH
Merhaba bilgisyarıma yeni aldığım TP-Link Wi-Fi adaptörünü kurduğumdan beri mavi ekran hatası alıyorum. Format attım bir iki gün normal çalıştı fakat tekrar aynı şekilde mavi ekran almaya devam ettim. Yardımcı olursanız sevinirim.

Mini dump dosyaları
 
Çözüm
Arg1 değerine bakılırsa Microsoft için donanımsal bir hata olarak gözüküyor, kısaca taktığın adaptör bozuk.
Rich (BB code):
BUGCODE_USB_DRIVER (fe)
USB Driver BugCheck, first parameter is USB BugCheck code.
Arguments:
Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
using a physical memory address that was not allocated by
the USBport driver.
Arg2: ffffa70f9f8bd1a0, Device extension pointer of the host controller
Arg3: 0000000010de077e, PCI Vendor,Product id for the controller
Arg4: ffffa70fab3642d8, Pointer to Endpoint data structure

0x5Device extension pointer of the host controllerPCI vendor, product id for the controllerPointer to endpoint data structureA hardware failure has occurred because of a bad physical address found in a hardware data structure.

Taktığın adaptörün sürücülerine bakmak için de donanım kimliğini paylaş. Sürücülerini güncelleyelim.

Bunu indirip oluşan linki paylaş.
Arg1 değerine bakılırsa Microsoft için donanımsal bir hata olarak gözüküyor, kısaca taktığın adaptör bozuk.
Rich (BB code):
BUGCODE_USB_DRIVER (fe)
USB Driver BugCheck, first parameter is USB BugCheck code.
Arguments:
Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
using a physical memory address that was not allocated by
the USBport driver.
Arg2: ffffa70f9f8bd1a0, Device extension pointer of the host controller
Arg3: 0000000010de077e, PCI Vendor,Product id for the controller
Arg4: ffffa70fab3642d8, Pointer to Endpoint data structure

0x5Device extension pointer of the host controllerPCI vendor, product id for the controllerPointer to endpoint data structureA hardware failure has occurred because of a bad physical address found in a hardware data structure.

Taktığın adaptörün sürücülerine bakmak için de donanım kimliğini paylaş. Sürücülerini güncelleyelim.

Bunu indirip oluşan linki paylaş.
 
Çözüm
Arg1 değerine bakılırsa Microsoft için donanımsal bir hata olarak gözüküyor, kısaca taktığın adaptör bozuk.
Rich (BB code):
BUGCODE_USB_DRIVER (fe)
USB Driver BugCheck, first parameter is USB BugCheck code.
Arguments:
Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
using a physical memory address that was not allocated by
the USBport driver.
Arg2: ffffa70f9f8bd1a0, Device extension pointer of the host controller
Arg3: 0000000010de077e, PCI Vendor,Product id for the controller
Arg4: ffffa70fab3642d8, Pointer to Endpoint data structure

0x5Device extension pointer of the host controllerPCI vendor, product id for the controllerPointer to endpoint data structureA hardware failure has occurred because of a bad physical address found in a hardware data structure.

Taktığın adaptörün sürücülerine bakmak için de donanım kimliğini paylaş. Sürücülerini güncelleyelim.

Bunu indirip oluşan linki paylaş.
Merhaba konuda belirtmeyi unutmuşum bu sabah bilgisayar iki defa durduk yere direk kapandı. 2x4 gb ram vardı biri arızalanmış rami çıkarttım herhalde şuan öyle bir sıkıntı yok. Yine de çözüm için etkili olur belki

 
Merhaba konuda belirtmeyi unutmuşum bu sabah bilgisayar iki defa durduk yere direk kapandı. 2x4 gb ram vardı biri arızalanmış rami çıkarttım herhalde şuan öyle bir sıkıntı yok. Yine de çözüm için etkili olur belki

Adaptör için son sürücü bu:


Yükle ve bir süre o şekilde kullan. USB Hataları kesilecek mi bir bak bakalım.
 
Kod:
BUGCODE_USB_DRIVER (fe)
USB Driver BugCheck, first parameter is USB BugCheck code.
Arguments:
Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
    using a physical memory address that was not allocated by
    the USBport driver.
Arg2: ffff9f0f278511a0, Device extension pointer of the host controller
Arg3: 0000000010de077e, PCI Vendor,Product id for the controller
Arg4: ffff9f0f27682be8, Pointer to Endpoint data structure

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 22077

    Key  : Analysis.Elapsed.mSec
    Value: 34432

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 0

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xfe

    Key  : Failure.Bucket
    Value: 0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot

    Key  : Failure.Hash
    Value: {5539ea26-939a-447a-4fd6-8b5926f84092}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  fe

BUGCHECK_P1: 5

BUGCHECK_P2: ffff9f0f278511a0

BUGCHECK_P3: 10de077e

BUGCHECK_P4: ffff9f0f27682be8

FILE_IN_CAB:  112023-10375-01.dmp

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  chrome.exe

DPC_STACK_BASE:  FFFFF8006629EFB0

STACK_TEXT:
fffff800`6629e8e8 fffff800`67d9de94     : 00000000`000000fe 00000000`00000005 ffff9f0f`278511a0 00000000`10de077e : nt!KeBugCheckEx
fffff800`6629e8f0 fffff800`67df8c06     : 00000000`cfe30180 ffffc880`530c9080 ffff9f0f`27682e88 00000000`00000000 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x17354
fffff800`6629e940 fffff800`67df8b5b     : ffff9f0f`27682be8 00000000`00000002 ffff9f0f`27682e88 00000000`00000002 : usbehci!EHCI_sMode_PollEndpointSlot+0x7a
fffff800`6629e9f0 fffff800`67dfd5de     : ffff9f0f`278511a0 ffff9f0f`27851050 00000000`00000000 00000000`ffffffff : usbehci!EHCI_sMode_PollEndpoint+0x5f
fffff800`6629ea40 fffff800`67d80ed4     : 00000000`865cee06 ffff9f0f`278511a0 00000000`00000000 ffff9f0f`278511a0 : usbehci!EHCI_PollEndpoint+0x2e
fffff800`6629ea70 fffff800`67d80b58     : 00000000`ffffffff ffff9f0f`27851050 ffff9f0f`27851b90 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x1b4
fffff800`6629ead0 fffff800`67d86e1c     : ffff9f0f`27851b90 00000000`865cee16 00000000`00000002 ffff9f0f`25d17040 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x218
fffff800`6629eb30 fffff800`5fac166e     : fffff800`6629ecb0 ffff9f0f`25dda000 fffff800`6629ee80 fffff800`5e222180 : USBPORT!USBPORT_Xdpc_Worker_HcIntDpc+0x18c
fffff800`6629ebb0 fffff800`5fac0954     : fffff800`5e222180 00000000`00000000 00000000`0000002a 00000000`0022759b : nt!KiExecuteAllDpcs+0x30e
fffff800`6629ed20 fffff800`5fc05c25     : 00000000`00000000 fffff800`5e222180 ffffc880`5237d780 00000000`00000000 : nt!KiRetireDpcList+0x1f4
fffff800`6629efb0 fffff800`5fc05a10     : ffff9f0f`333f3080 fffff800`5fb251fa 00000000`00000000 ffffdd0c`cd622cc0 : nt!KxRetireDpcList+0x5
ffffdd0c`cd622c00 fffff800`5fc05195     : 00000000`00000000 fffff800`5fbfee41 00000272`19070000 00000000`00000000 : nt!KiDispatchInterruptContinue
ffffdd0c`cd622c30 fffff800`5fbfee41     : 00000272`19070000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterruptBypass+0x25
ffffdd0c`cd622c40 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiChainedDispatch+0xb1


SYMBOL_NAME:  usbehci!EHCI_sMode_PollEndpointSlot+7a

MODULE_NAME: usbehci

IMAGE_NAME:  usbehci.sys

IMAGE_VERSION:  10.0.19041.3684

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  7a

FAILURE_BUCKET_ID:  0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5539ea26-939a-447a-4fd6-8b5926f84092}

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

Merhaba tekrardan aynı hatayı aldım kesin adaptörde diyorsanız garantiye yollayacağım
 
Kod:
BUGCODE_USB_DRIVER (fe)
USB Driver BugCheck, first parameter is USB BugCheck code.
Arguments:
Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
 using a physical memory address that was not allocated by
 the USBport driver.
Arg2: ffff9f0f278511a0, Device extension pointer of the host controller
Arg3: 0000000010de077e, PCI Vendor,Product id for the controller
Arg4: ffff9f0f27682be8, Pointer to Endpoint data structure

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

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 22077

 Key : Analysis.Elapsed.mSec
 Value: 34432

 Key : Analysis.IO.Other.Mb
 Value: 0

 Key : Analysis.IO.Read.Mb
 Value: 0

 Key : Analysis.IO.Write.Mb
 Value: 0

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

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

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

 Key : Bugcheck.Code.LegacyAPI
 Value: 0xfe

 Key : Failure.Bucket
 Value: 0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot

 Key : Failure.Hash
 Value: {5539ea26-939a-447a-4fd6-8b5926f84092}

 Key : WER.OS.Branch
 Value: vb_release

 Key : WER.OS.Version
 Value: 10.0.19041.1

BUGCHECK_CODE: fe

BUGCHECK_P1: 5

BUGCHECK_P2: ffff9f0f278511a0

BUGCHECK_P3: 10de077e

BUGCHECK_P4: ffff9f0f27682be8

FILE_IN_CAB: 112023-10375-01.dmp

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: chrome.exe

DPC_STACK_BASE: FFFFF8006629EFB0

STACK_TEXT:
fffff800`6629e8e8 fffff800`67d9de94 : 00000000`000000fe 00000000`00000005 ffff9f0f`278511a0 00000000`10de077e : nt!KeBugCheckEx
fffff800`6629e8f0 fffff800`67df8c06 : 00000000`cfe30180 ffffc880`530c9080 ffff9f0f`27682e88 00000000`00000000 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x17354
fffff800`6629e940 fffff800`67df8b5b : ffff9f0f`27682be8 00000000`00000002 ffff9f0f`27682e88 00000000`00000002 : usbehci!EHCI_sMode_PollEndpointSlot+0x7a
fffff800`6629e9f0 fffff800`67dfd5de : ffff9f0f`278511a0 ffff9f0f`27851050 00000000`00000000 00000000`ffffffff : usbehci!EHCI_sMode_PollEndpoint+0x5f
fffff800`6629ea40 fffff800`67d80ed4 : 00000000`865cee06 ffff9f0f`278511a0 00000000`00000000 ffff9f0f`278511a0 : usbehci!EHCI_PollEndpoint+0x2e
fffff800`6629ea70 fffff800`67d80b58 : 00000000`ffffffff ffff9f0f`27851050 ffff9f0f`27851b90 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x1b4
fffff800`6629ead0 fffff800`67d86e1c : ffff9f0f`27851b90 00000000`865cee16 00000000`00000002 ffff9f0f`25d17040 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x218
fffff800`6629eb30 fffff800`5fac166e : fffff800`6629ecb0 ffff9f0f`25dda000 fffff800`6629ee80 fffff800`5e222180 : USBPORT!USBPORT_Xdpc_Worker_HcIntDpc+0x18c
fffff800`6629ebb0 fffff800`5fac0954 : fffff800`5e222180 00000000`00000000 00000000`0000002a 00000000`0022759b : nt!KiExecuteAllDpcs+0x30e
fffff800`6629ed20 fffff800`5fc05c25 : 00000000`00000000 fffff800`5e222180 ffffc880`5237d780 00000000`00000000 : nt!KiRetireDpcList+0x1f4
fffff800`6629efb0 fffff800`5fc05a10 : ffff9f0f`333f3080 fffff800`5fb251fa 00000000`00000000 ffffdd0c`cd622cc0 : nt!KxRetireDpcList+0x5
ffffdd0c`cd622c00 fffff800`5fc05195 : 00000000`00000000 fffff800`5fbfee41 00000272`19070000 00000000`00000000 : nt!KiDispatchInterruptContinue
ffffdd0c`cd622c30 fffff800`5fbfee41 : 00000272`19070000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterruptBypass+0x25
ffffdd0c`cd622c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiChainedDispatch+0xb1

SYMBOL_NAME: usbehci!EHCI_sMode_PollEndpointSlot+7a

MODULE_NAME: usbehci

IMAGE_NAME: usbehci.sys

IMAGE_VERSION: 10.0.19041.3684

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 7a

FAILURE_BUCKET_ID: 0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {5539ea26-939a-447a-4fd6-8b5926f84092}

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

Merhaba tekrardan aynı hatayı aldım kesin adaptörde diyorsanız garantiye yollayacağım

0x5 hatası, yani donanımsal denilen hata aynı devam ediyor. Tabii artık iş garantiye geldiği için 1 farklı öneri daha yapacağım.

Adaptörü çıkar, Aygıt Yöneticisi'nden sürücüsünü kaldırıp farklı bir USB portuna tak. Sonra son sürücüyü tekrar kur ve bir süre de öyle kullan.

Evet, hatayı tekrar alırsan buraya yaz. Konuyu kapatalım.

Bu ihtimalde, USB portunun sıkıntılı oluşundan kaynaklandığı ihtimali için söylediğim bir şey.
 

Technopat Haberler

Yeni konular

Geri
Yukarı