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

Erdem Ozzer

Femtopat
Katılım
5 Nisan 2021
Mesajlar
20
Daha fazla  
Cinsiyet
Erkek
Şirket bilgisayarında böyle bir sorun ile karşılaştım fakat sorunu çözemedim.
Normalde yavaş olmayan bilgisayar son zamanlarda aşırı yavaşladı ve takılmaya başladı.
Takılmaya başlayınca da mavi ekran vermeye başladı.


Minidump dosyasının linkini bıraktım yukarıda.

İşletim sistemim:
Windows 10
 
Çözüm
Sorunun kaynağı sisteme takılı Wi-Fi aygıtı. Wi-Fi aygıtınızın sürücüsünü güncelleyin ve öyle deneyin. Yine olmazsa Wi-Fi aygıtını farklı bir USB portuna takın ya da bu aygıtı bilgisayara hiç takmayın.

Sorun çözülürse de 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: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
using a physical memory address that was not allocated by
the USBport driver.
Arg2: ffff81017dec01a0, Device extension pointer of the host controller
Arg3: 0000000010de077e, PCI Vendor,Product id for the controller
Arg4: ffff81017d3628e8, Pointer to Endpoint data structure

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

*** WARNING: Unable to verify timestamp for usbehci.sys
*************************************************************************
*** ***
*** ***
*** 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: usbehci!_DEVICE_DATA ***
*** ***
*************************************************************************
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 12780

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 49801

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

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

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

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

BUGCHECK_P1: 5

BUGCHECK_P2: ffff81017dec01a0

BUGCHECK_P3: 10de077e

BUGCHECK_P4: ffff81017d3628e8

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff802`32a6d6d8 fffff802`3441de94 : 00000000`000000fe 00000000`00000005 ffff8101`7dec01a0 00000000`10de077e : nt!KeBugCheckEx
fffff802`32a6d6e0 fffff802`34478c06 : 00000000`dfed4100 ffff9780`84539080 ffff8101`7d362b88 fffff802`2a9c2180 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x17354
fffff802`32a6d730 00000000`dfed4100 : ffff9780`84539080 ffff8101`7d362b88 fffff802`2a9c2180 ffff8101`7d362b88 : usbehci+0x8c06
fffff802`32a6d738 ffff9780`84539080 : ffff8101`7d362b88 fffff802`2a9c2180 ffff8101`7d362b88 00000000`dfed4100 : 0xdfed4100
fffff802`32a6d740 ffff8101`7d362b88 : fffff802`2a9c2180 ffff8101`7d362b88 00000000`dfed4100 00000000`00000282 : 0xffff9780`84539080
fffff802`32a6d748 fffff802`2a9c2180 : ffff8101`7d362b88 00000000`dfed4100 00000000`00000282 fffff802`2fd0ff11 : 0xffff8101`7d362b88
fffff802`32a6d750 ffff8101`7d362b88 : 00000000`dfed4100 00000000`00000282 fffff802`2fd0ff11 fffff802`2a9c2180 : 0xfffff802`2a9c2180
fffff802`32a6d758 00000000`dfed4100 : 00000000`00000282 fffff802`2fd0ff11 fffff802`2a9c2180 00000000`0000000d : 0xffff8101`7d362b88
fffff802`32a6d760 00000000`00000282 : fffff802`2fd0ff11 fffff802`2a9c2180 00000000`0000000d 00000000`00000000 : 0xdfed4100
fffff802`32a6d768 fffff802`2fd0ff11 : fffff802`2a9c2180 00000000`0000000d 00000000`00000000 ffff9780`84539080 : 0x282
fffff802`32a6d770 fffff802`34478b5b : ffff8101`7d3628e8 fffff802`2ff61f43 ffff8101`7d362b88 fffff802`336b18e4 : nt!KiExitDispatcher+0x141
fffff802`32a6d7e0 ffff8101`7d3628e8 : fffff802`2ff61f43 ffff8101`7d362b88 fffff802`336b18e4 0000001c`8d41028e : usbehci+0x8b5b
fffff802`32a6d7e8 fffff802`2ff61f43 : ffff8101`7d362b88 fffff802`336b18e4 0000001c`8d41028e ffff8101`7ddb5100 : 0xffff8101`7d3628e8
fffff802`32a6d7f0 fffff802`3447d5de : ffff8101`7dec01a0 ffff8101`7dec0050 fffff780`00000320 00000000`ffffffff : nt!PpmIdleUpdateConcurrency+0x73
fffff802`32a6d830 ffff8101`7dec01a0 : ffff8101`7dec0050 fffff780`00000320 00000000`ffffffff ffff8101`7dec01a0 : usbehci+0xd5de
fffff802`32a6d838 ffff8101`7dec0050 : fffff780`00000320 00000000`ffffffff ffff8101`7dec01a0 fffff802`34400ed4 : 0xffff8101`7dec01a0
fffff802`32a6d840 fffff780`00000320 : 00000000`ffffffff ffff8101`7dec01a0 fffff802`34400ed4 ffff8101`7dec0050 : 0xffff8101`7dec0050
fffff802`32a6d848 00000000`ffffffff : ffff8101`7dec01a0 fffff802`34400ed4 ffff8101`7dec0050 ffff8101`7dec01a0 : 0xfffff780`00000320
fffff802`32a6d850 ffff8101`7dec01a0 : fffff802`34400ed4 ffff8101`7dec0050 ffff8101`7dec01a0 00000000`00000000 : 0xffffffff
fffff802`32a6d858 fffff802`34400ed4 : ffff8101`7dec0050 ffff8101`7dec01a0 00000000`00000000 ffff8101`7dec01a0 : 0xffff8101`7dec01a0
fffff802`32a6d860 fffff802`34400b58 : 00000000`ffffffff ffff8101`7dec0050 ffff8101`7dec0b90 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x1b4
fffff802`32a6d8c0 fffff802`34406e1c : ffff8101`7dec0b90 00000000`8b016a16 00000000`00000002 ffff8101`7d3d3500 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x218
fffff802`32a6d920 fffff802`2fd230ce : fffff802`32a6daa0 ffff8101`7d3d4000 fffff802`32a6dc70 fffff802`2a9c2180 : USBPORT!USBPORT_Xdpc_Worker_HcIntDpc+0x18c
fffff802`32a6d9a0 fffff802`2fd223b4 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e
fffff802`32a6db10 fffff802`2fdfa7fe : 00000000`00000000 fffff802`2a9c2180 fffff802`30727a00 ffff8101`84edc040 : nt!KiRetireDpcList+0x1f4
fffff802`32a6dda0 00000000`00000000 : fffff802`32a6e000 fffff802`32a68000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME: usbehci+8c06

MODULE_NAME: usbehci

IMAGE_NAME: usbehci.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 8c06

FAILURE_BUCKET_ID: 0xFE_INVALID_PHYSICAL_ADDR_usbehci!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {82ae6620-d7a6-c9e8-dfb8-8487dd2d429b}

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

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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: ffff94085e22d1a0, Device extension pointer of the host controller
Arg3: 0000000010de077e, PCI Vendor,Product id for the controller
Arg4: ffff9408672922d8, Pointer to Endpoint data structure

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

*** WARNING: Unable to verify timestamp for usbehci.sys
*************************************************************************
*** ***
*** ***
*** 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: usbehci!_DEVICE_DATA ***
*** ***
*************************************************************************
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 14734

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 53871

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

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

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

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

BUGCHECK_P1: 5

BUGCHECK_P2: ffff94085e22d1a0

BUGCHECK_P3: 10de077e

BUGCHECK_P4: ffff9408672922d8

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff803`5dc6d6d8 fffff803`5f79de94 : 00000000`000000fe 00000000`00000005 ffff9408`5e22d1a0 00000000`10de077e : nt!KeBugCheckEx
fffff803`5dc6d6e0 fffff803`5ea08c06 : 00000000`df663180 ffffcb81`98186080 ffff9408`67292458 00000000`00000000 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x17354
fffff803`5dc6d730 00000000`df663180 : ffffcb81`98186080 ffff9408`67292458 00000000`00000000 ffff9408`67292458 : usbehci+0x8c06
fffff803`5dc6d738 ffffcb81`98186080 : ffff9408`67292458 00000000`00000000 ffff9408`67292458 00000000`df663180 : 0xdf663180
fffff803`5dc6d740 ffff9408`67292458 : 00000000`00000000 ffff9408`67292458 00000000`df663180 00000000`00000000 : 0xffffcb81`98186080
fffff803`5dc6d748 00000000`00000000 : ffff9408`67292458 00000000`df663180 00000000`00000000 00000000`00000000 : 0xffff9408`67292458


SYMBOL_NAME: usbehci+8c06

MODULE_NAME: usbehci

IMAGE_NAME: usbehci.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 8c06

FAILURE_BUCKET_ID: 0xFE_INVALID_PHYSICAL_ADDR_usbehci!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {82ae6620-d7a6-c9e8-dfb8-8487dd2d429b}

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

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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: ffffb004da43a1a0, Device extension pointer of the host controller
Arg3: 0000000010de077e, PCI Vendor,Product id for the controller
Arg4: ffffb004da4f7be8, Pointer to Endpoint data structure

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

*** WARNING: Unable to verify timestamp for usbehci.sys
*************************************************************************
*** ***
*** ***
*** 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: usbehci!_DEVICE_DATA ***
*** ***
*************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 10171

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 61995

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

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

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

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

BUGCHECK_P1: 5

BUGCHECK_P2: ffffb004da43a1a0

BUGCHECK_P3: 10de077e

BUGCHECK_P4: ffffb004da4f7be8

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: steam.exe

DPC_STACK_BASE: FFFFF80733A74FB0

STACK_TEXT:
fffff807`33a748e8 fffff807`3477de94 : 00000000`000000fe 00000000`00000005 ffffb004`da43a1a0 00000000`10de077e : nt!KeBugCheckEx
fffff807`33a748f0 fffff807`347d8c06 : 00000000`dfeec180 ffffd801`535e7080 ffffb004`da4f7d68 00000000`00000000 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x17354
fffff807`33a74940 00000000`dfeec180 : ffffd801`535e7080 ffffb004`da4f7d68 00000000`00000000 ffffb004`da4f7d68 : usbehci+0x8c06
fffff807`33a74948 ffffd801`535e7080 : ffffb004`da4f7d68 00000000`00000000 ffffb004`da4f7d68 00000000`dfeec180 : 0xdfeec180
fffff807`33a74950 ffffb004`da4f7d68 : 00000000`00000000 ffffb004`da4f7d68 00000000`dfeec180 00000000`00000005 : 0xffffd801`535e7080
fffff807`33a74958 00000000`00000000 : ffffb004`da4f7d68 00000000`dfeec180 00000000`00000005 00000000`00000000 : 0xffffb004`da4f7d68


SYMBOL_NAME: usbehci+8c06

MODULE_NAME: usbehci

IMAGE_NAME: usbehci.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 8c06

FAILURE_BUCKET_ID: 0xFE_INVALID_PHYSICAL_ADDR_usbehci!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {82ae6620-d7a6-c9e8-dfb8-8487dd2d429b}

Followup: MachineOwner
---------[/CODE]
Sorunun kaynağı sisteme takılı Wi-Fi aygıtı. Wi-Fi aygıtınızın sürücüsünü güncelleyin ve öyle deneyin. Yine olmazsa Wi-Fi aygıtını farklı bir USB portuna takın ya da bu aygıtı bilgisayara hiç takmayın.

Sorun çözülürse de 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: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
using a physical memory address that was not allocated by
the USBport driver.
Arg2: ffff81017dec01a0, Device extension pointer of the host controller
Arg3: 0000000010de077e, PCI Vendor,Product id for the controller
Arg4: ffff81017d3628e8, Pointer to Endpoint data structure

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

*** WARNING: Unable to verify timestamp for usbehci.sys
*************************************************************************
*** ***
*** ***
*** 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: usbehci!_DEVICE_DATA ***
*** ***
*************************************************************************
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 12780

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 49801

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

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

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

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

BUGCHECK_P1: 5

BUGCHECK_P2: ffff81017dec01a0

BUGCHECK_P3: 10de077e

BUGCHECK_P4: ffff81017d3628e8

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff802`32a6d6d8 fffff802`3441de94 : 00000000`000000fe 00000000`00000005 ffff8101`7dec01a0 00000000`10de077e : nt!KeBugCheckEx
fffff802`32a6d6e0 fffff802`34478c06 : 00000000`dfed4100 ffff9780`84539080 ffff8101`7d362b88 fffff802`2a9c2180 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x17354
fffff802`32a6d730 00000000`dfed4100 : ffff9780`84539080 ffff8101`7d362b88 fffff802`2a9c2180 ffff8101`7d362b88 : usbehci+0x8c06
fffff802`32a6d738 ffff9780`84539080 : ffff8101`7d362b88 fffff802`2a9c2180 ffff8101`7d362b88 00000000`dfed4100 : 0xdfed4100
fffff802`32a6d740 ffff8101`7d362b88 : fffff802`2a9c2180 ffff8101`7d362b88 00000000`dfed4100 00000000`00000282 : 0xffff9780`84539080
fffff802`32a6d748 fffff802`2a9c2180 : ffff8101`7d362b88 00000000`dfed4100 00000000`00000282 fffff802`2fd0ff11 : 0xffff8101`7d362b88
fffff802`32a6d750 ffff8101`7d362b88 : 00000000`dfed4100 00000000`00000282 fffff802`2fd0ff11 fffff802`2a9c2180 : 0xfffff802`2a9c2180
fffff802`32a6d758 00000000`dfed4100 : 00000000`00000282 fffff802`2fd0ff11 fffff802`2a9c2180 00000000`0000000d : 0xffff8101`7d362b88
fffff802`32a6d760 00000000`00000282 : fffff802`2fd0ff11 fffff802`2a9c2180 00000000`0000000d 00000000`00000000 : 0xdfed4100
fffff802`32a6d768 fffff802`2fd0ff11 : fffff802`2a9c2180 00000000`0000000d 00000000`00000000 ffff9780`84539080 : 0x282
fffff802`32a6d770 fffff802`34478b5b : ffff8101`7d3628e8 fffff802`2ff61f43 ffff8101`7d362b88 fffff802`336b18e4 : nt!KiExitDispatcher+0x141
fffff802`32a6d7e0 ffff8101`7d3628e8 : fffff802`2ff61f43 ffff8101`7d362b88 fffff802`336b18e4 0000001c`8d41028e : usbehci+0x8b5b
fffff802`32a6d7e8 fffff802`2ff61f43 : ffff8101`7d362b88 fffff802`336b18e4 0000001c`8d41028e ffff8101`7ddb5100 : 0xffff8101`7d3628e8
fffff802`32a6d7f0 fffff802`3447d5de : ffff8101`7dec01a0 ffff8101`7dec0050 fffff780`00000320 00000000`ffffffff : nt!PpmIdleUpdateConcurrency+0x73
fffff802`32a6d830 ffff8101`7dec01a0 : ffff8101`7dec0050 fffff780`00000320 00000000`ffffffff ffff8101`7dec01a0 : usbehci+0xd5de
fffff802`32a6d838 ffff8101`7dec0050 : fffff780`00000320 00000000`ffffffff ffff8101`7dec01a0 fffff802`34400ed4 : 0xffff8101`7dec01a0
fffff802`32a6d840 fffff780`00000320 : 00000000`ffffffff ffff8101`7dec01a0 fffff802`34400ed4 ffff8101`7dec0050 : 0xffff8101`7dec0050
fffff802`32a6d848 00000000`ffffffff : ffff8101`7dec01a0 fffff802`34400ed4 ffff8101`7dec0050 ffff8101`7dec01a0 : 0xfffff780`00000320
fffff802`32a6d850 ffff8101`7dec01a0 : fffff802`34400ed4 ffff8101`7dec0050 ffff8101`7dec01a0 00000000`00000000 : 0xffffffff
fffff802`32a6d858 fffff802`34400ed4 : ffff8101`7dec0050 ffff8101`7dec01a0 00000000`00000000 ffff8101`7dec01a0 : 0xffff8101`7dec01a0
fffff802`32a6d860 fffff802`34400b58 : 00000000`ffffffff ffff8101`7dec0050 ffff8101`7dec0b90 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x1b4
fffff802`32a6d8c0 fffff802`34406e1c : ffff8101`7dec0b90 00000000`8b016a16 00000000`00000002 ffff8101`7d3d3500 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x218
fffff802`32a6d920 fffff802`2fd230ce : fffff802`32a6daa0 ffff8101`7d3d4000 fffff802`32a6dc70 fffff802`2a9c2180 : USBPORT!USBPORT_Xdpc_Worker_HcIntDpc+0x18c
fffff802`32a6d9a0 fffff802`2fd223b4 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e
fffff802`32a6db10 fffff802`2fdfa7fe : 00000000`00000000 fffff802`2a9c2180 fffff802`30727a00 ffff8101`84edc040 : nt!KiRetireDpcList+0x1f4
fffff802`32a6dda0 00000000`00000000 : fffff802`32a6e000 fffff802`32a68000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME: usbehci+8c06

MODULE_NAME: usbehci

IMAGE_NAME: usbehci.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 8c06

FAILURE_BUCKET_ID: 0xFE_INVALID_PHYSICAL_ADDR_usbehci!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {82ae6620-d7a6-c9e8-dfb8-8487dd2d429b}

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

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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: ffff94085e22d1a0, Device extension pointer of the host controller
Arg3: 0000000010de077e, PCI Vendor,Product id for the controller
Arg4: ffff9408672922d8, Pointer to Endpoint data structure

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

*** WARNING: Unable to verify timestamp for usbehci.sys
*************************************************************************
*** ***
*** ***
*** 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: usbehci!_DEVICE_DATA ***
*** ***
*************************************************************************
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 14734

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 53871

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

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

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

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

BUGCHECK_P1: 5

BUGCHECK_P2: ffff94085e22d1a0

BUGCHECK_P3: 10de077e

BUGCHECK_P4: ffff9408672922d8

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff803`5dc6d6d8 fffff803`5f79de94 : 00000000`000000fe 00000000`00000005 ffff9408`5e22d1a0 00000000`10de077e : nt!KeBugCheckEx
fffff803`5dc6d6e0 fffff803`5ea08c06 : 00000000`df663180 ffffcb81`98186080 ffff9408`67292458 00000000`00000000 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x17354
fffff803`5dc6d730 00000000`df663180 : ffffcb81`98186080 ffff9408`67292458 00000000`00000000 ffff9408`67292458 : usbehci+0x8c06
fffff803`5dc6d738 ffffcb81`98186080 : ffff9408`67292458 00000000`00000000 ffff9408`67292458 00000000`df663180 : 0xdf663180
fffff803`5dc6d740 ffff9408`67292458 : 00000000`00000000 ffff9408`67292458 00000000`df663180 00000000`00000000 : 0xffffcb81`98186080
fffff803`5dc6d748 00000000`00000000 : ffff9408`67292458 00000000`df663180 00000000`00000000 00000000`00000000 : 0xffff9408`67292458


SYMBOL_NAME: usbehci+8c06

MODULE_NAME: usbehci

IMAGE_NAME: usbehci.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 8c06

FAILURE_BUCKET_ID: 0xFE_INVALID_PHYSICAL_ADDR_usbehci!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {82ae6620-d7a6-c9e8-dfb8-8487dd2d429b}

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

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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: ffffb004da43a1a0, Device extension pointer of the host controller
Arg3: 0000000010de077e, PCI Vendor,Product id for the controller
Arg4: ffffb004da4f7be8, Pointer to Endpoint data structure

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

*** WARNING: Unable to verify timestamp for usbehci.sys
*************************************************************************
*** ***
*** ***
*** 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: usbehci!_DEVICE_DATA ***
*** ***
*************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 10171

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 61995

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

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

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

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

BUGCHECK_P1: 5

BUGCHECK_P2: ffffb004da43a1a0

BUGCHECK_P3: 10de077e

BUGCHECK_P4: ffffb004da4f7be8

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: steam.exe

DPC_STACK_BASE: FFFFF80733A74FB0

STACK_TEXT:
fffff807`33a748e8 fffff807`3477de94 : 00000000`000000fe 00000000`00000005 ffffb004`da43a1a0 00000000`10de077e : nt!KeBugCheckEx
fffff807`33a748f0 fffff807`347d8c06 : 00000000`dfeec180 ffffd801`535e7080 ffffb004`da4f7d68 00000000`00000000 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x17354
fffff807`33a74940 00000000`dfeec180 : ffffd801`535e7080 ffffb004`da4f7d68 00000000`00000000 ffffb004`da4f7d68 : usbehci+0x8c06
fffff807`33a74948 ffffd801`535e7080 : ffffb004`da4f7d68 00000000`00000000 ffffb004`da4f7d68 00000000`dfeec180 : 0xdfeec180
fffff807`33a74950 ffffb004`da4f7d68 : 00000000`00000000 ffffb004`da4f7d68 00000000`dfeec180 00000000`00000005 : 0xffffd801`535e7080
fffff807`33a74958 00000000`00000000 : ffffb004`da4f7d68 00000000`dfeec180 00000000`00000005 00000000`00000000 : 0xffffb004`da4f7d68


SYMBOL_NAME: usbehci+8c06

MODULE_NAME: usbehci

IMAGE_NAME: usbehci.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 8c06

FAILURE_BUCKET_ID: 0xFE_INVALID_PHYSICAL_ADDR_usbehci!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {82ae6620-d7a6-c9e8-dfb8-8487dd2d429b}

Followup: MachineOwner
---------[/CODE]
 
Çözüm
Güncellemek istersem Wi-Fi aygıtını aygıt yöneticisinde nasıl bulabilirim?

Eki Görüntüle 1061793

Aradığım Wi-Fi aygıtı bu sanırım.

Ayrıca farklı bir Wi-Fi aygıtı takınca interneti kullanamıyorum hiçbir şekilde bağlanamıyor.

1623241645951.png
 
Son düzenleyen: Moderatör:
Siz en iyisi aygıtın modeline göre internetten sürücüsünü indirin. Olmadı Wi-Fi aygıtını çıkarırsınız ve Ethernet ile kullanırsınız.

Aygıt kimliğini aratıp birçok siteye baktım fakat nasıl kurulduğunu tam anlayamadım. Kurulum konusunda bir fikriniz var mı?
PCI\VEN_10EC&DEV_8168&SUBSYS_816810EC&REV_10
Aygıt kimliğim bu.
 
Aşağıdan indirip alttaki rehbere göre kurulumunu yapın ve Wi-Fi aygıtını çıkarmayı unutmayın. Sorun da çözülürse belirtin lütfen.


 
Aşağıdan indirip alttaki rehbere göre kurulumunu yapın ve Wi-Fi aygıtını çıkarmayı unutmayın. Sorun da çözülürse belirtin lütfen.



Deneyeceğim, Microsoft Update Catalog sayfasında 1. mi yoksa 2. Setup'ımı indirmeliyim?
Ayrıca yükle seçeneğine bastığımda yüklenmiyor ben mi bir şeyi yanlış yapıyorum?

Aşağıdan indirip alttaki rehbere göre kurulumunu yapın ve Wi-Fi aygıtını çıkarmayı unutmayın. Sorun da çözülürse belirtin lütfen.



Videodaki adımların hepsini uyguladım ve sorunum çözüldü.
Fakat başka bir aygıtda ünlem gösteriyor mavi ekran hatasını tekrar verecek mi test edip geri dönüş yapacağım.
PCI\VEN_00EC&DEV_0168&SUBSYS_02000010&REV_10

1623270249232.png

Aşağıdan indirip alttaki rehbere göre kurulumunu yapın ve Wi-Fi aygıtını çıkarmayı unutmayın. Sorun da çözülürse belirtin lütfen.


Hala mavi ekran alıyorum.
Üstteki görselde belirttiğim gibi bu sefer Etherney Denetleyicinde ünlem var
 
Son düzenleme:

Geri
Yukarı