Çö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 7

Mertkrgx

Centipat
Katılım
17 Şubat 2021
Mesajlar
7
Daha fazla  
Cinsiyet
Erkek
Merhabalar,
Daha önceden de mavi ekran hatası alıyordum ancak son zamanlarda bayağı sıklaştığı için buraya sorma gereği duydum.
Bilgisayarımın modeli: HP Pavilion G6.
İşlemci: Intel i5-2430M
Ekran kartı: Radeon HD 6470M.
RAM: 4 GB Samsung.

Son aldığım mavi ekrandaki dump dosyası:

İlgilenenlere şimdiden teşekkürler.
 

Dosya Ekleri

  • WhatsApp Image 2021-02-17 at 15.50.44 (1).jpeg
    WhatsApp Image 2021-02-17 at 15.50.44 (1).jpeg
    205,3 KB · Görüntüleme: 44
Çözüm
1) Apple aygıtınızı bilgisayara USB yoluyla bağlamışsınız bunu yapmayın.

2) Bilgisayara bağlı tüm USB aygıtlarını çıkartın.

3) CPU-Z kaldırın.

Ek: Driver Booster hiç kullandınız mı?

Sorun çözülürse belirtmeyi unutmayın lütfen.

[CODE title="Dökümler"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000008, USBBUGCODE_RESERVED_USBHUB
Arg2: 0000000000000006, USBHUB_TRAP_FATAL_TIMEOUT
Arg3: 0000000000000005, TimeoutCode: Timeout_PCE_Suspend_Action3 - PortData->PortSuspendEvent
Arg4: fffffa8008a9fc80, TimeoutContext - PortData

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

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbport!_DEVICE_EXTENSION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
fffff8000343b0e8: Unable to get Flags value from nt!KdVersionBlock
GetUlongPtrFromAddress: unable to read from fffff800034f6300

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4484

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 52423

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

Key : Analysis.System
Value: CreateObject

Key : WER.OS.Branch
Value: win7sp1_ldr_escrow

Key : WER.OS.Timestamp
Value: 2019-03-20T17:00:00Z

Key : WER.OS.Version
Value: 7.1.7601.24408


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: fe

BUGCHECK_P1: 8

BUGCHECK_P2: 6

BUGCHECK_P3: 5

BUGCHECK_P4: fffffa8008a9fc80

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff880`033c6ad8 fffff880`04f88b98 : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000005 : nt!KeBugCheckEx
fffff880`033c6ae0 fffff800`035326ff : fffffa80`08a97050 00000000`00000001 ffffffff`dc3a58a0 fffff800`034697f8 : usbhub!UsbhHubProcessChangeWorker+0xec
fffff880`033c6b40 fffff800`03287b49 : fffff800`03469700 fffff800`03532601 fffffa80`042e6b00 fffffa80`04e007b0 : nt!IopProcessWorkItem+0x23
fffff880`033c6b70 fffff800`0359a8d0 : edcb482d`e14471c0 fffff880`031de180 00000000`00000080 00000000`00000001 : nt!ExpWorkerThread+0x111
fffff880`033c6c00 fffff800`032f2ba6 : fffff880`031de180 fffffa80`042e6b50 fffff880`031ed140 00000000`00000000 : nt!PspSystemThreadStartup+0x194
fffff880`033c6c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_NAME: usbhub!UsbhHubProcessChangeWorker+ec

MODULE_NAME: usbhub

IMAGE_NAME: usbhub.sys

IMAGE_VERSION: 6.1.7601.24138

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0xFE_usbhub!UsbhHubProcessChangeWorker+ec

OS_VERSION: 7.1.7601.24408

BUILDLAB_STR: win7sp1_ldr_escrow

OSPLATFORM_TYPE: x64

OSNAME: Windows 7

FAILURE_ID_HASH: {a8a8c317-f204-3dc3-af04-e1239637ed25}

Followup: MachineOwner
---------[/CODE]
1) Apple aygıtınızı bilgisayara USB yoluyla bağlamışsınız bunu yapmayın.

2) Bilgisayara bağlı tüm USB aygıtlarını çıkartın.

3) CPU-Z kaldırın.

Ek: Driver Booster hiç kullandınız mı?

Sorun çözülürse belirtmeyi unutmayın lütfen.

[CODE title="Dökümler"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000008, USBBUGCODE_RESERVED_USBHUB
Arg2: 0000000000000006, USBHUB_TRAP_FATAL_TIMEOUT
Arg3: 0000000000000005, TimeoutCode: Timeout_PCE_Suspend_Action3 - PortData->PortSuspendEvent
Arg4: fffffa8008a9fc80, TimeoutContext - PortData

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

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbport!_DEVICE_EXTENSION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
fffff8000343b0e8: Unable to get Flags value from nt!KdVersionBlock
GetUlongPtrFromAddress: unable to read from fffff800034f6300

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4484

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 52423

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

Key : Analysis.System
Value: CreateObject

Key : WER.OS.Branch
Value: win7sp1_ldr_escrow

Key : WER.OS.Timestamp
Value: 2019-03-20T17:00:00Z

Key : WER.OS.Version
Value: 7.1.7601.24408


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: fe

BUGCHECK_P1: 8

BUGCHECK_P2: 6

BUGCHECK_P3: 5

BUGCHECK_P4: fffffa8008a9fc80

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff880`033c6ad8 fffff880`04f88b98 : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000005 : nt!KeBugCheckEx
fffff880`033c6ae0 fffff800`035326ff : fffffa80`08a97050 00000000`00000001 ffffffff`dc3a58a0 fffff800`034697f8 : usbhub!UsbhHubProcessChangeWorker+0xec
fffff880`033c6b40 fffff800`03287b49 : fffff800`03469700 fffff800`03532601 fffffa80`042e6b00 fffffa80`04e007b0 : nt!IopProcessWorkItem+0x23
fffff880`033c6b70 fffff800`0359a8d0 : edcb482d`e14471c0 fffff880`031de180 00000000`00000080 00000000`00000001 : nt!ExpWorkerThread+0x111
fffff880`033c6c00 fffff800`032f2ba6 : fffff880`031de180 fffffa80`042e6b50 fffff880`031ed140 00000000`00000000 : nt!PspSystemThreadStartup+0x194
fffff880`033c6c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_NAME: usbhub!UsbhHubProcessChangeWorker+ec

MODULE_NAME: usbhub

IMAGE_NAME: usbhub.sys

IMAGE_VERSION: 6.1.7601.24138

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0xFE_usbhub!UsbhHubProcessChangeWorker+ec

OS_VERSION: 7.1.7601.24408

BUILDLAB_STR: win7sp1_ldr_escrow

OSPLATFORM_TYPE: x64

OSNAME: Windows 7

FAILURE_ID_HASH: {a8a8c317-f204-3dc3-af04-e1239637ed25}

Followup: MachineOwner
---------[/CODE]
 
Çözüm
Driver Booster hakkında bir bilgim yok kullanmadım ama bugün ve dün sürücüleri güncelleştirmeyi denedim.
Sorunun çözülüp çözülmediğini bilmiyorum lakin şu ana kadar bir sorun olmadı.
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ı