koray123612
Femtopat
- Katılım
- 13 Ocak 2021
- Mesajlar
- 16
Daha fazla
- Cinsiyet
- Erkek
Gamepadimi bağlarken mavi ekran hatasını alıyorum çözümü var mı?
Minidump Dosyalarını Paylaşın
Minidump dosyaları, bilgisayarınız mavi ekran verdiğinde belleğin ufak bir dökümünü barındıran dosyalardır. Bunları analiz ederek mavi ekran hatalarının nedenini öğrenebiliriz. Minidump dosyaları C:\Windows\Minidump klasöründe bulunur ve DMP uzantılıdır. Bu dosyaları sizden istediğimizde...www.technopat.net
Bluetooth'la gamepad bağlarken mavi ekran alıyorum.Minidump Dosyalarını Paylaşın
Minidump dosyaları, bilgisayarınız mavi ekran verdiğinde belleğin ufak bir dökümünü barındıran dosyalardır. Bunları analiz ederek mavi ekran hatalarının nedenini öğrenebiliriz. Minidump dosyaları C:\Windows\Minidump klasöründe bulunur ve DMP uzantılıdır. Bu dosyaları sizden istediğimizde...www.technopat.net
Minidump Dosyalarını Paylaşın
Minidump dosyaları, bilgisayarınız mavi ekran verdiğinde belleğin ufak bir dökümünü barındıran dosyalardır. Bunları analiz ederek mavi ekran hatalarının nedenini öğrenebiliriz. Minidump dosyaları C:\Windows\Minidump klasöründe bulunur ve DMP uzantılıdır. Bu dosyaları sizden istediğimizde...www.technopat.net
Herkese açık oldu mu?Dosyayı erişime açın. @Ma'at bakacaktır.
Windows'u etkinleştirmedim, ondan olabilir mi sorun?Windows 10 sürümünü güncelle. Çok eski bir sürüm kullanıyorsunuz. Galiba 2016 senesinden kalma bir sürüm.
Windows sürümünü güncelledikten sonra "sfc /scannow" rehberini uygula.
Minidump dosyasında bluetooth ve gamepad ile alakalı mavi ekran aldığınız belli oluyor.
@Ma'at hocam daha detaylı size bir çözüm sunucaktır.
Sanmıyorum. Denildiği gibi çok eski bir Windows sürümü kullanıyorsunuz. İlk olarak onu güncelleştirin. 20H2 sürümüne temiz kurulum yaparsanız harika olur.Windows'u etkinleştirmedim, ondan olabilir mi sorun?
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: fffff80f7dd61452, The address that the exception occurred at
Arg3: ffffde00a5c44a18, Exception Record Address
Arg4: ffffde00a5c44260, Context Record Address
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullClassPtr
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 3327
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on RTX
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 63548
Key : Analysis.Memory.CommitPeak.Mb
Value: 86
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: rs2_release
Key : WER.OS.Timestamp
Value: 2017-03-17T18:34:00Z
Key : WER.OS.Version
Value: 10.0.15063.0
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff80f7dd61452
BUGCHECK_P3: ffffde00a5c44a18
BUGCHECK_P4: ffffde00a5c44260
EXCEPTION_RECORD: ffffde00a5c44a18 -- (.exr 0xffffde00a5c44a18)
ExceptionAddress: fffff80f7dd61452 (Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x0000000000000066)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000092
Attempt to read from address 0000000000000092
CONTEXT: ffffde00a5c44260 -- (.cxr 0xffffde00a5c44260)
rax=ffff8a0d36a4e020 rbx=0000000000000018 rcx=ffff8a0d36a4e058
rdx=0000000000000000 rsi=0000000000000000 rdi=ffff8a0d33a01a00
rip=fffff80f7dd61452 rsp=ffffde00a5c44c50 rbp=0000000000000018
r8=0000000000000000 r9=0000000000000001 r10=0000000000000000
r11=0000000000000000 r12=0000000000000002 r13=ffff8a0d344076e0
r14=ffff8a0d36a4e020 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x66:
fffff80f`7dd61452 8a8692000000 mov al,byte ptr [rsi+92h] ds:002b:00000000`00000092=??
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: fffff803669ff358: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80366958ff0: Unable to get Flags value from nt!KdVersionBlock
0000000000000092
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000092
EXCEPTION_STR: 0xc0000005
LOCK_ADDRESS: fffff80366982f20 -- (!locks fffff80366982f20)
Cannot get _ERESOURCE type
Resource @ nt!PiEngineLock (0xfffff80366982f20) Available
1 total locks
PNP_TRIAGE_DATA:
Lock address : 0xfffff80366982f20
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0
STACK_TEXT:
ffffde00`a5c44c50 fffff80f`7dd607c1 : 00000000`00000000 ffffde00`a5c44d90 ffff8a0d`318899a6 00000000`00000000 : Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x66 [minkernel\wdf\framework\shared\targets\usb\fxusbinterface.cpp @ 835]
ffffde00`a5c44c90 fffff80f`7dd62f54 : 00000000`00000000 00000000`00000000 ffff8a0d`31889930 ffff8a0d`33a01a02 : Wdf01000!FxUsbDevice::SelectConfig+0x575 [minkernel\wdf\framework\shared\targets\usb\fxusbdevice.cpp @ 1783]
ffffde00`a5c44ea0 fffff80f`7dd5c0d2 : 00000000`00000020 00000000`00000000 ffff8a0d`33749b70 00000000`00000000 : Wdf01000!FxUsbDevice::SelectConfigMulti+0x298 [minkernel\wdf\framework\shared\targets\usb\km\fxusbdevicekm.cpp @ 1062]
ffffde00`a5c45060 fffff80f`8039888f : ffff8a0d`33a01a50 00000000`00000020 000075f2`cc8b6488 00000000`c0000023 : Wdf01000!imp_WdfUsbTargetDeviceSelectConfig+0x352 [minkernel\wdf\framework\shared\targets\usb\fxusbdeviceapi.cpp @ 890]
ffffde00`a5c450e0 fffff80f`8039651d : 00000000`00000000 000075f2`cc8b6488 ffff8a0d`33749e60 ffff8a0d`32924180 : WinUSB!WinUSB_SelectConfiguration+0x9f
ffffde00`a5c45160 fffff80f`7dd09c18 : ffff8a0d`332fec18 ffff8a0d`332fe700 00000000`00000000 00000602`00000008 : WinUSB!WinUSB_PrepareHardware+0x1bd
ffffde00`a5c451b0 fffff80f`7dcf619f : ffff8a0d`332fe690 fffff80f`7dcf3161 ffff8a0d`325f6ac0 ffff8a0d`332fe690 : Wdf01000!FxPnpDevicePrepareHardware::InvokeClient+0x28 [minkernel\wdf\framework\shared\irphandlers\pnp\pnpcallbacks.cpp @ 347]
ffffde00`a5c45200 fffff80f`7dcfc40a : ffff8a0d`325f6ac0 ffff8a0d`332fe7e0 00000000`00000000 ffff8a0d`325f6ac0 : Wdf01000!FxPkgPnp::PnpPrepareHardware+0xff [minkernel\wdf\framework\shared\irphandlers\pnp\pnpstatemachine.cpp @ 3572]
ffffde00`a5c45250 fffff80f`7dcf63c9 : ffff8a0d`332fe601 00000000`00000100 ffff8a0d`332fe690 00000000`00000108 : Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0x7a [minkernel\wdf\framework\shared\irphandlers\pnp\pnpstatemachine.cpp @ 1399]
ffffde00`a5c45290 fffff80f`7dcf357f : ffff8a0d`332fe7e8 fffff80f`00000000 ffff8a0d`332fe7c0 00000000`00000000 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0x1a9 [minkernel\wdf\framework\shared\irphandlers\pnp\pnpstatemachine.cpp @ 1150]
ffffde00`a5c45340 fffff80f`7dd0945a : 00000000`00000000 fffff803`666f1250 00000000`00000008 ffffde00`a5c45478 : Wdf01000!FxPkgPnp::PnpProcessEvent+0x12f [minkernel\wdf\framework\shared\irphandlers\pnp\pnpstatemachine.cpp @ 933]
ffffde00`a5c453e0 fffff80f`7dcd752e : ffff8a0d`33749b70 00000000`00000000 00000000`00000000 ffff8a0d`332fe690 : Wdf01000!FxPkgPnp::_PnpStartDevice+0x4a [minkernel\wdf\framework\shared\irphandlers\pnp\fxpkgpnp.cpp @ 1862]
ffffde00`a5c45440 fffff80f`7dcd6b95 : ffff8a0d`32924180 ffff8a0d`33749b70 ffff8a0d`332fe690 ffffde00`a5c45528 : Wdf01000!FxPkgPnp::Dispatch+0xee [minkernel\wdf\framework\shared\irphandlers\pnp\fxpkgpnp.cpp @ 670]
ffffde00`a5c454e0 fffff803`66a8d912 : ffff8a0d`325f6ac0 ffff8a0d`30627a04 00000000`00000000 fffff803`66967230 : Wdf01000!FxDevice::DispatchWithLock+0x155 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1430]
ffffde00`a5c455d0 fffff803`6664343c : ffff8a0d`325a1cc0 00000000`00000000 ffff8a0d`30627a50 fffff803`00000000 : nt!PnpAsynchronousCall+0xea
ffffde00`a5c45610 fffff803`666f0cf8 : 00000000`00000000 ffff8a0d`325a1cc0 fffff803`666f1250 fffff803`666f1250 : nt!PnpSendIrp+0x54
ffffde00`a5c45680 fffff803`66b06cd7 : ffff8a0d`334809a0 ffff8a0d`30627a50 00000000`00000000 00000000`00000200 : nt!PnpStartDevice+0x88
ffffde00`a5c45710 fffff803`66b06027 : ffff8a0d`334809a0 ffffde00`a5c458e0 00000000`00000000 ffff8a0d`33480902 : nt!PnpStartDeviceNode+0xdb
ffffde00`a5c457a0 fffff803`66a54944 : ffff8a0d`334809a0 00000000`00000001 00000000`00000001 ffff8a0d`334809a0 : nt!PipProcessStartPhase1+0x53
ffffde00`a5c457e0 fffff803`66cc25f2 : ffff8a0d`334809a0 fffff803`66681059 fffff803`66a16200 00000000`00000000 : nt!PipProcessDevNodeTree+0x428
ffffde00`a5c45a60 fffff803`667d3987 : ffff8a01`00000003 00000000`00000000 fffff803`00000000 ffff8a0d`33aa4aa0 : nt!PiRestartDevice+0xba
ffffde00`a5c45ab0 fffff803`6665bca8 : ffff8a0d`38d71700 fffff803`669819c0 fffff803`66a16380 fffff803`66a16380 : nt!PnpDeviceActionWorker+0xe32d7
ffffde00`a5c45b80 fffff803`666faa37 : 00000000`00000000 00000000`00000080 ffff8a0d`3027a040 ffff8a0d`38d71700 : nt!ExpWorkerThread+0xd8
ffffde00`a5c45c10 fffff803`6678f876 : ffffde00`9de07180 ffff8a0d`38d71700 fffff803`666fa9f0 00000000`00000000 : nt!PspSystemThreadStartup+0x47
ffffde00`a5c45c60 00000000`00000000 : ffffde00`a5c46000 ffffde00`a5c40000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
SYMBOL_NAME: WinUSB!WinUSB_SelectConfiguration+9f
MODULE_NAME: WinUSB
IMAGE_NAME: WinUSB.SYS
IMAGE_VERSION: 10.0.15063.413
STACK_COMMAND: .cxr 0xffffde00a5c44260 ; kb
BUCKET_ID_FUNC_OFFSET: 9f
FAILURE_BUCKET_ID: AV_WinUSB!WinUSB_SelectConfiguration
OS_VERSION: 10.0.15063.0
BUILDLAB_STR: rs2_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {ac85bd58-6492-3f38-ae2d-47d0f754ee4a}
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: fffff80d3e081452, The address that the exception occurred at
Arg3: ffff84802c98ca68, Exception Record Address
Arg4: ffff84802c98c2b0, Context Record Address
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullClassPtr
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 2155
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on RTX
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 27492
Key : Analysis.Memory.CommitPeak.Mb
Value: 86
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: rs2_release
Key : WER.OS.Timestamp
Value: 2017-03-17T18:34:00Z
Key : WER.OS.Version
Value: 10.0.15063.0
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff80d3e081452
BUGCHECK_P3: ffff84802c98ca68
BUGCHECK_P4: ffff84802c98c2b0
EXCEPTION_RECORD: ffff84802c98ca68 -- (.exr 0xffff84802c98ca68)
ExceptionAddress: fffff80d3e081452 (Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x0000000000000066)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000092
Attempt to read from address 0000000000000092
CONTEXT: ffff84802c98c2b0 -- (.cxr 0xffff84802c98c2b0)
rax=ffffd6853714a020 rbx=0000000000000018 rcx=ffffd6853714a058
rdx=0000000000000000 rsi=0000000000000000 rdi=ffffd685371a0400
rip=fffff80d3e081452 rsp=ffff84802c98cca0 rbp=0000000000000018
r8=0000000000000000 r9=0000000000000001 r10=0000000000000000
r11=0000000000000000 r12=0000000000000002 r13=ffffd68532a11650
r14=ffffd6853714a020 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x66:
fffff80d`3e081452 8a8692000000 mov al,byte ptr [rsi+92h] ds:002b:00000000`00000092=??
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: fffff80283df0358: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80283d49ff0: Unable to get Flags value from nt!KdVersionBlock
0000000000000092
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000092
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
ffff8480`2c98cca0 fffff80d`3e0807c1 : 00000000`00000000 ffff8480`2c98cde0 ffffd685`366a9986 00000000`00000000 : Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x66 [minkernel\wdf\framework\shared\targets\usb\fxusbinterface.cpp @ 835]
ffff8480`2c98cce0 fffff80d`3e082f54 : 00000000`00000000 00000000`00000000 ffffd685`366a9910 ffffd685`371a0402 : Wdf01000!FxUsbDevice::SelectConfig+0x575 [minkernel\wdf\framework\shared\targets\usb\fxusbdevice.cpp @ 1783]
ffff8480`2c98cef0 fffff80d`3e07c0d2 : 00000000`00000001 00000000`00000000 ffff8480`2c98d188 00000000`00000002 : Wdf01000!FxUsbDevice::SelectConfigMulti+0x298 [minkernel\wdf\framework\shared\targets\usb\km\fxusbdevicekm.cpp @ 1062]
ffff8480`2c98d0b0 fffff802`83381b17 : ffffd685`371a0470 00000000`00000020 ffff9a0f`c9b994a0 ffffd685`35b53850 : Wdf01000!imp_WdfUsbTargetDeviceSelectConfig+0x352 [minkernel\wdf\framework\shared\targets\usb\fxusbdeviceapi.cpp @ 890]
ffff8480`2c98d130 ffffd685`371a0470 : 00000000`00000020 ffff9a0f`c9b994a0 ffffd685`35b53850 00000004`00000020 : libusbK+0x1b17
ffff8480`2c98d138 00000000`00000020 : ffff9a0f`c9b994a0 ffffd685`35b53850 00000004`00000020 00000000`00000002 : 0xffffd685`371a0470
ffff8480`2c98d140 ffff9a0f`c9b994a0 : ffffd685`35b53850 00000004`00000020 00000000`00000002 ffff9a0f`c9b994a0 : 0x20
ffff8480`2c98d148 ffffd685`35b53850 : 00000004`00000020 00000000`00000002 ffff9a0f`c9b994a0 00000000`00000000 : 0xffff9a0f`c9b994a0
ffff8480`2c98d150 00000004`00000020 : 00000000`00000002 ffff9a0f`c9b994a0 00000000`00000000 fffff80d`3e098200 : 0xffffd685`35b53850
ffff8480`2c98d158 00000000`00000002 : ffff9a0f`c9b994a0 00000000`00000000 fffff80d`3e098200 fffff802`83381598 : 0x00000004`00000020
ffff8480`2c98d160 ffff9a0f`c9b994a0 : 00000000`00000000 fffff80d`3e098200 fffff802`83381598 0000297a`ca145ff8 : 0x2
ffff8480`2c98d168 00000000`00000000 : fffff80d`3e098200 fffff802`83381598 0000297a`ca145ff8 ffffd685`349caa00 : 0xffff9a0f`c9b994a0
SYMBOL_NAME: libusbK+1b17
MODULE_NAME: libusbK
IMAGE_NAME: libusbK.sys
STACK_COMMAND: .cxr 0xffff84802c98c2b0 ; kb
BUCKET_ID_FUNC_OFFSET: 1b17
FAILURE_BUCKET_ID: AV_libusbK!unknown_function
OS_VERSION: 10.0.15063.0
BUILDLAB_STR: rs2_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {29796159-6aaf-3bad-0beb-c83156b37c01}
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: fffff807dece1452, The address that the exception occurred at
Arg3: ffffce81876b8a68, Exception Record Address
Arg4: ffffce81876b82b0, Context Record Address
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullClassPtr
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 2187
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on RTX
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 36821
Key : Analysis.Memory.CommitPeak.Mb
Value: 85
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: rs2_release
Key : WER.OS.Timestamp
Value: 2017-03-17T18:34:00Z
Key : WER.OS.Version
Value: 10.0.15063.0
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff807dece1452
BUGCHECK_P3: ffffce81876b8a68
BUGCHECK_P4: ffffce81876b82b0
EXCEPTION_RECORD: ffffce81876b8a68 -- (.exr 0xffffce81876b8a68)
ExceptionAddress: fffff807dece1452 (Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x0000000000000066)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000092
Attempt to read from address 0000000000000092
CONTEXT: ffffce81876b82b0 -- (.cxr 0xffffce81876b82b0)
rax=ffffab834bb55c80 rbx=0000000000000018 rcx=ffffab834bb55cb8
rdx=0000000000000000 rsi=0000000000000000 rdi=ffffab8348eea000
rip=fffff807dece1452 rsp=ffffce81876b8ca0 rbp=0000000000000018
r8=0000000000000000 r9=0000000000000001 r10=0000000000000000
r11=0000000000000000 r12=0000000000000002 r13=ffffab834a6b9b30
r14=ffffab834bb55c80 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246
Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x66:
fffff807`dece1452 8a8692000000 mov al,byte ptr [rsi+92h] ds:002b:00000000`00000092=??
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: fffff8029d469358: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8029d3c2ff0: Unable to get Flags value from nt!KdVersionBlock
0000000000000092
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000092
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
ffffce81`876b8ca0 fffff807`dece07c1 : 00000000`00000000 ffffce81`876b8de0 ffffab83`4b3feaf6 00000000`00000000 : Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x66 [minkernel\wdf\framework\shared\targets\usb\fxusbinterface.cpp @ 835]
ffffce81`876b8ce0 fffff807`dece2f54 : 00000000`00000000 00000000`00000000 ffffab83`4b3fea80 ffffab83`48eea002 : Wdf01000!FxUsbDevice::SelectConfig+0x575 [minkernel\wdf\framework\shared\targets\usb\fxusbdevice.cpp @ 1783]
ffffce81`876b8ef0 fffff807`decdc0d2 : 00000000`00000001 00000000`00000000 ffffce81`876b9188 00000000`00000002 : Wdf01000!FxUsbDevice::SelectConfigMulti+0x298 [minkernel\wdf\framework\shared\targets\usb\km\fxusbdevicekm.cpp @ 1062]
ffffce81`876b90b0 fffff802`9c4c1b17 : ffffab83`48eea020 00000000`00000020 ffff950c`673086b0 ffffab83`4b4ca400 : Wdf01000!imp_WdfUsbTargetDeviceSelectConfig+0x352 [minkernel\wdf\framework\shared\targets\usb\fxusbdeviceapi.cpp @ 890]
ffffce81`876b9130 ffffab83`48eea020 : 00000000`00000020 ffff950c`673086b0 ffffab83`4b4ca400 00000004`00000020 : libusbK+0x1b17
ffffce81`876b9138 00000000`00000020 : ffff950c`673086b0 ffffab83`4b4ca400 00000004`00000020 00000000`00000002 : 0xffffab83`48eea020
ffffce81`876b9140 ffff950c`673086b0 : ffffab83`4b4ca400 00000004`00000020 00000000`00000002 ffff950c`673086b0 : 0x20
ffffce81`876b9148 ffffab83`4b4ca400 : 00000004`00000020 00000000`00000002 ffff950c`673086b0 00000000`00000000 : 0xffff950c`673086b0
ffffce81`876b9150 00000004`00000020 : 00000000`00000002 ffff950c`673086b0 00000000`00000000 fffff807`decf8200 : 0xffffab83`4b4ca400
ffffce81`876b9158 00000000`00000002 : ffff950c`673086b0 00000000`00000000 fffff807`decf8200 fffff802`9c4c1598 : 0x00000004`00000020
ffffce81`876b9160 ffff950c`673086b0 : 00000000`00000000 fffff807`decf8200 fffff802`9c4c1598 0000547c`b6c04ff8 : 0x2
ffffce81`876b9168 00000000`00000000 : fffff807`decf8200 fffff802`9c4c1598 0000547c`b6c04ff8 ffffab83`4bba2900 : 0xffff950c`673086b0
SYMBOL_NAME: libusbK+1b17
MODULE_NAME: libusbK
IMAGE_NAME: libusbK.sys
STACK_COMMAND: .cxr 0xffffce81876b82b0 ; kb
BUCKET_ID_FUNC_OFFSET: 1b17
FAILURE_BUCKET_ID: AV_libusbK!unknown_function
OS_VERSION: 10.0.15063.0
BUILDLAB_STR: rs2_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {29796159-6aaf-3bad-0beb-c83156b37c01}
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: fffff80754a91452, The address that the exception occurred at
Arg3: ffffa580796e6a68, Exception Record Address
Arg4: ffffa580796e62b0, Context Record Address
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullClassPtr
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 2358
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on RTX
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 26571
Key : Analysis.Memory.CommitPeak.Mb
Value: 86
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: rs2_release
Key : WER.OS.Timestamp
Value: 2017-03-17T18:34:00Z
Key : WER.OS.Version
Value: 10.0.15063.0
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff80754a91452
BUGCHECK_P3: ffffa580796e6a68
BUGCHECK_P4: ffffa580796e62b0
EXCEPTION_RECORD: ffffa580796e6a68 -- (.exr 0xffffa580796e6a68)
ExceptionAddress: fffff80754a91452 (Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x0000000000000066)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000092
Attempt to read from address 0000000000000092
CONTEXT: ffffa580796e62b0 -- (.cxr 0xffffa580796e62b0)
rax=ffffdf0a1400ba60 rbx=0000000000000018 rcx=ffffdf0a1400ba98
rdx=0000000000000000 rsi=0000000000000000 rdi=ffffdf0a129f7600
rip=fffff80754a91452 rsp=ffffa580796e6ca0 rbp=0000000000000018
r8=0000000000000000 r9=0000000000000001 r10=0000000000000000
r11=0000000000000000 r12=0000000000000002 r13=ffffdf0a10f4c830
r14=ffffdf0a1400ba60 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246
Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x66:
fffff807`54a91452 8a8692000000 mov al,byte ptr [rsi+92h] ds:002b:00000000`00000092=??
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: fffff801cf65d358: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff801cf5b6ff0: Unable to get Flags value from nt!KdVersionBlock
0000000000000092
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000092
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
ffffa580`796e6ca0 fffff807`54a907c1 : 00000000`00000000 ffffa580`796e6de0 ffffdf0a`128b31e6 00000000`00000000 : Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x66 [minkernel\wdf\framework\shared\targets\usb\fxusbinterface.cpp @ 835]
ffffa580`796e6ce0 fffff807`54a92f54 : 00000000`00000000 00000000`00000000 ffffdf0a`128b3170 ffffdf0a`129f7602 : Wdf01000!FxUsbDevice::SelectConfig+0x575 [minkernel\wdf\framework\shared\targets\usb\fxusbdevice.cpp @ 1783]
ffffa580`796e6ef0 fffff807`54a8c0d2 : 00000000`00000001 00000000`00000000 ffffa580`796e7188 00000000`00000002 : Wdf01000!FxUsbDevice::SelectConfigMulti+0x298 [minkernel\wdf\framework\shared\targets\usb\km\fxusbdevicekm.cpp @ 1062]
ffffa580`796e70b0 fffff801`e4281b17 : ffffdf0a`129f7620 00000000`00000020 ffff8d08`4ab779e0 ffffdf0a`12825170 : Wdf01000!imp_WdfUsbTargetDeviceSelectConfig+0x352 [minkernel\wdf\framework\shared\targets\usb\fxusbdeviceapi.cpp @ 890]
ffffa580`796e7130 ffffdf0a`129f7620 : 00000000`00000020 ffff8d08`4ab779e0 ffffdf0a`12825170 00000004`00000020 : libusbK+0x1b17
ffffa580`796e7138 00000000`00000020 : ffff8d08`4ab779e0 ffffdf0a`12825170 00000004`00000020 00000000`00000002 : 0xffffdf0a`129f7620
ffffa580`796e7140 ffff8d08`4ab779e0 : ffffdf0a`12825170 00000004`00000020 00000000`00000002 ffff8d08`4ab779e0 : 0x20
ffffa580`796e7148 ffffdf0a`12825170 : 00000004`00000020 00000000`00000002 ffff8d08`4ab779e0 00000000`00000000 : 0xffff8d08`4ab779e0
ffffa580`796e7150 00000004`00000020 : 00000000`00000002 ffff8d08`4ab779e0 00000000`00000000 fffff807`54aa8200 : 0xffffdf0a`12825170
ffffa580`796e7158 00000000`00000002 : ffff8d08`4ab779e0 00000000`00000000 fffff807`54aa8200 fffff801`e4281598 : 0x00000004`00000020
ffffa580`796e7160 ffff8d08`4ab779e0 : 00000000`00000000 fffff807`54aa8200 fffff801`e4281598 000020f5`f0192ff8 : 0x2
ffffa580`796e7168 00000000`00000000 : fffff807`54aa8200 fffff801`e4281598 000020f5`f0192ff8 ffffdf0a`128fd100 : 0xffff8d08`4ab779e0
SYMBOL_NAME: libusbK+1b17
MODULE_NAME: libusbK
IMAGE_NAME: libusbK.sys
STACK_COMMAND: .cxr 0xffffa580796e62b0 ; kb
BUCKET_ID_FUNC_OFFSET: 1b17
FAILURE_BUCKET_ID: AV_libusbK!unknown_function
OS_VERSION: 10.0.15063.0
BUILDLAB_STR: rs2_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {29796159-6aaf-3bad-0beb-c83156b37c01}
Followup: MachineOwner
---------
Sanmıyorum. Denildiği gibi çok eski bir Windows sürümü kullanıyorsunuz. İlk olarak onu güncelleştirin. 20H2 sürümüne temiz kurulum yaparsanız harika olur.
Windows 10 Türkçe İndirme ve Kurulum | Technopat Sosyal
Bunun haricinde USB yüzünden mavi ekran hataları da almaktasınız. Laptopun kendi ağ kartından mı Bluetooth kullanıyorsunuz yoksa harici bir adaptör mü var?
Kod:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: fffff80f7dd61452, The address that the exception occurred at Arg3: ffffde00a5c44a18, Exception Record Address Arg4: ffffde00a5c44260, Context Record Address Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : AV.Dereference Value: NullClassPtr Key : AV.Fault Value: Read Key : Analysis.CPU.mSec Value: 3327 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on RTX Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 63548 Key : Analysis.Memory.CommitPeak.Mb Value: 86 Key : Analysis.System Value: CreateObject Key : WER.OS.Branch Value: rs2_release Key : WER.OS.Timestamp Value: 2017-03-17T18:34:00Z Key : WER.OS.Version Value: 10.0.15063.0 ADDITIONAL_XML: 1 OS_BUILD_LAYERS: 1 BUGCHECK_CODE: 7e BUGCHECK_P1: ffffffffc0000005 BUGCHECK_P2: fffff80f7dd61452 BUGCHECK_P3: ffffde00a5c44a18 BUGCHECK_P4: ffffde00a5c44260 EXCEPTION_RECORD: ffffde00a5c44a18 -- (.exr 0xffffde00a5c44a18) ExceptionAddress: fffff80f7dd61452 (Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x0000000000000066) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000092 Attempt to read from address 0000000000000092 CONTEXT: ffffde00a5c44260 -- (.cxr 0xffffde00a5c44260) rax=ffff8a0d36a4e020 rbx=0000000000000018 rcx=ffff8a0d36a4e058 rdx=0000000000000000 rsi=0000000000000000 rdi=ffff8a0d33a01a00 rip=fffff80f7dd61452 rsp=ffffde00a5c44c50 rbp=0000000000000018 r8=0000000000000000 r9=0000000000000001 r10=0000000000000000 r11=0000000000000000 r12=0000000000000002 r13=ffff8a0d344076e0 r14=ffff8a0d36a4e020 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x66: fffff80f`7dd61452 8a8692000000 mov al,byte ptr [rsi+92h] ds:002b:00000000`00000092=?? Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System READ_ADDRESS: fffff803669ff358: Unable to get MiVisibleState Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd fffff80366958ff0: Unable to get Flags value from nt!KdVersionBlock 0000000000000092 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s. EXCEPTION_CODE_STR: c0000005 EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000092 EXCEPTION_STR: 0xc0000005 LOCK_ADDRESS: fffff80366982f20 -- (!locks fffff80366982f20) Cannot get _ERESOURCE type Resource @ nt!PiEngineLock (0xfffff80366982f20) Available 1 total locks PNP_TRIAGE_DATA: Lock address : 0xfffff80366982f20 Thread Count : 0 Thread address: 0x0000000000000000 Thread wait : 0x0 STACK_TEXT: ffffde00`a5c44c50 fffff80f`7dd607c1 : 00000000`00000000 ffffde00`a5c44d90 ffff8a0d`318899a6 00000000`00000000 : Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x66 [minkernel\wdf\framework\shared\targets\usb\fxusbinterface.cpp @ 835] ffffde00`a5c44c90 fffff80f`7dd62f54 : 00000000`00000000 00000000`00000000 ffff8a0d`31889930 ffff8a0d`33a01a02 : Wdf01000!FxUsbDevice::SelectConfig+0x575 [minkernel\wdf\framework\shared\targets\usb\fxusbdevice.cpp @ 1783] ffffde00`a5c44ea0 fffff80f`7dd5c0d2 : 00000000`00000020 00000000`00000000 ffff8a0d`33749b70 00000000`00000000 : Wdf01000!FxUsbDevice::SelectConfigMulti+0x298 [minkernel\wdf\framework\shared\targets\usb\km\fxusbdevicekm.cpp @ 1062] ffffde00`a5c45060 fffff80f`8039888f : ffff8a0d`33a01a50 00000000`00000020 000075f2`cc8b6488 00000000`c0000023 : Wdf01000!imp_WdfUsbTargetDeviceSelectConfig+0x352 [minkernel\wdf\framework\shared\targets\usb\fxusbdeviceapi.cpp @ 890] ffffde00`a5c450e0 fffff80f`8039651d : 00000000`00000000 000075f2`cc8b6488 ffff8a0d`33749e60 ffff8a0d`32924180 : WinUSB!WinUSB_SelectConfiguration+0x9f ffffde00`a5c45160 fffff80f`7dd09c18 : ffff8a0d`332fec18 ffff8a0d`332fe700 00000000`00000000 00000602`00000008 : WinUSB!WinUSB_PrepareHardware+0x1bd ffffde00`a5c451b0 fffff80f`7dcf619f : ffff8a0d`332fe690 fffff80f`7dcf3161 ffff8a0d`325f6ac0 ffff8a0d`332fe690 : Wdf01000!FxPnpDevicePrepareHardware::InvokeClient+0x28 [minkernel\wdf\framework\shared\irphandlers\pnp\pnpcallbacks.cpp @ 347] ffffde00`a5c45200 fffff80f`7dcfc40a : ffff8a0d`325f6ac0 ffff8a0d`332fe7e0 00000000`00000000 ffff8a0d`325f6ac0 : Wdf01000!FxPkgPnp::PnpPrepareHardware+0xff [minkernel\wdf\framework\shared\irphandlers\pnp\pnpstatemachine.cpp @ 3572] ffffde00`a5c45250 fffff80f`7dcf63c9 : ffff8a0d`332fe601 00000000`00000100 ffff8a0d`332fe690 00000000`00000108 : Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0x7a [minkernel\wdf\framework\shared\irphandlers\pnp\pnpstatemachine.cpp @ 1399] ffffde00`a5c45290 fffff80f`7dcf357f : ffff8a0d`332fe7e8 fffff80f`00000000 ffff8a0d`332fe7c0 00000000`00000000 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0x1a9 [minkernel\wdf\framework\shared\irphandlers\pnp\pnpstatemachine.cpp @ 1150] ffffde00`a5c45340 fffff80f`7dd0945a : 00000000`00000000 fffff803`666f1250 00000000`00000008 ffffde00`a5c45478 : Wdf01000!FxPkgPnp::PnpProcessEvent+0x12f [minkernel\wdf\framework\shared\irphandlers\pnp\pnpstatemachine.cpp @ 933] ffffde00`a5c453e0 fffff80f`7dcd752e : ffff8a0d`33749b70 00000000`00000000 00000000`00000000 ffff8a0d`332fe690 : Wdf01000!FxPkgPnp::_PnpStartDevice+0x4a [minkernel\wdf\framework\shared\irphandlers\pnp\fxpkgpnp.cpp @ 1862] ffffde00`a5c45440 fffff80f`7dcd6b95 : ffff8a0d`32924180 ffff8a0d`33749b70 ffff8a0d`332fe690 ffffde00`a5c45528 : Wdf01000!FxPkgPnp::Dispatch+0xee [minkernel\wdf\framework\shared\irphandlers\pnp\fxpkgpnp.cpp @ 670] ffffde00`a5c454e0 fffff803`66a8d912 : ffff8a0d`325f6ac0 ffff8a0d`30627a04 00000000`00000000 fffff803`66967230 : Wdf01000!FxDevice::DispatchWithLock+0x155 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1430] ffffde00`a5c455d0 fffff803`6664343c : ffff8a0d`325a1cc0 00000000`00000000 ffff8a0d`30627a50 fffff803`00000000 : nt!PnpAsynchronousCall+0xea ffffde00`a5c45610 fffff803`666f0cf8 : 00000000`00000000 ffff8a0d`325a1cc0 fffff803`666f1250 fffff803`666f1250 : nt!PnpSendIrp+0x54 ffffde00`a5c45680 fffff803`66b06cd7 : ffff8a0d`334809a0 ffff8a0d`30627a50 00000000`00000000 00000000`00000200 : nt!PnpStartDevice+0x88 ffffde00`a5c45710 fffff803`66b06027 : ffff8a0d`334809a0 ffffde00`a5c458e0 00000000`00000000 ffff8a0d`33480902 : nt!PnpStartDeviceNode+0xdb ffffde00`a5c457a0 fffff803`66a54944 : ffff8a0d`334809a0 00000000`00000001 00000000`00000001 ffff8a0d`334809a0 : nt!PipProcessStartPhase1+0x53 ffffde00`a5c457e0 fffff803`66cc25f2 : ffff8a0d`334809a0 fffff803`66681059 fffff803`66a16200 00000000`00000000 : nt!PipProcessDevNodeTree+0x428 ffffde00`a5c45a60 fffff803`667d3987 : ffff8a01`00000003 00000000`00000000 fffff803`00000000 ffff8a0d`33aa4aa0 : nt!PiRestartDevice+0xba ffffde00`a5c45ab0 fffff803`6665bca8 : ffff8a0d`38d71700 fffff803`669819c0 fffff803`66a16380 fffff803`66a16380 : nt!PnpDeviceActionWorker+0xe32d7 ffffde00`a5c45b80 fffff803`666faa37 : 00000000`00000000 00000000`00000080 ffff8a0d`3027a040 ffff8a0d`38d71700 : nt!ExpWorkerThread+0xd8 ffffde00`a5c45c10 fffff803`6678f876 : ffffde00`9de07180 ffff8a0d`38d71700 fffff803`666fa9f0 00000000`00000000 : nt!PspSystemThreadStartup+0x47 ffffde00`a5c45c60 00000000`00000000 : ffffde00`a5c46000 ffffde00`a5c40000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 SYMBOL_NAME: WinUSB!WinUSB_SelectConfiguration+9f MODULE_NAME: WinUSB IMAGE_NAME: WinUSB.SYS IMAGE_VERSION: 10.0.15063.413 STACK_COMMAND: .cxr 0xffffde00a5c44260 ; kb BUCKET_ID_FUNC_OFFSET: 9f FAILURE_BUCKET_ID: AV_WinUSB!WinUSB_SelectConfiguration OS_VERSION: 10.0.15063.0 BUILDLAB_STR: rs2_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {ac85bd58-6492-3f38-ae2d-47d0f754ee4a} Followup: MachineOwner --------- ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: fffff80d3e081452, The address that the exception occurred at Arg3: ffff84802c98ca68, Exception Record Address Arg4: ffff84802c98c2b0, Context Record Address Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : AV.Dereference Value: NullClassPtr Key : AV.Fault Value: Read Key : Analysis.CPU.mSec Value: 2155 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on RTX Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 27492 Key : Analysis.Memory.CommitPeak.Mb Value: 86 Key : Analysis.System Value: CreateObject Key : WER.OS.Branch Value: rs2_release Key : WER.OS.Timestamp Value: 2017-03-17T18:34:00Z Key : WER.OS.Version Value: 10.0.15063.0 ADDITIONAL_XML: 1 OS_BUILD_LAYERS: 1 BUGCHECK_CODE: 7e BUGCHECK_P1: ffffffffc0000005 BUGCHECK_P2: fffff80d3e081452 BUGCHECK_P3: ffff84802c98ca68 BUGCHECK_P4: ffff84802c98c2b0 EXCEPTION_RECORD: ffff84802c98ca68 -- (.exr 0xffff84802c98ca68) ExceptionAddress: fffff80d3e081452 (Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x0000000000000066) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000092 Attempt to read from address 0000000000000092 CONTEXT: ffff84802c98c2b0 -- (.cxr 0xffff84802c98c2b0) rax=ffffd6853714a020 rbx=0000000000000018 rcx=ffffd6853714a058 rdx=0000000000000000 rsi=0000000000000000 rdi=ffffd685371a0400 rip=fffff80d3e081452 rsp=ffff84802c98cca0 rbp=0000000000000018 r8=0000000000000000 r9=0000000000000001 r10=0000000000000000 r11=0000000000000000 r12=0000000000000002 r13=ffffd68532a11650 r14=ffffd6853714a020 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x66: fffff80d`3e081452 8a8692000000 mov al,byte ptr [rsi+92h] ds:002b:00000000`00000092=?? Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System READ_ADDRESS: fffff80283df0358: Unable to get MiVisibleState Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd fffff80283d49ff0: Unable to get Flags value from nt!KdVersionBlock 0000000000000092 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s. EXCEPTION_CODE_STR: c0000005 EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000092 EXCEPTION_STR: 0xc0000005 STACK_TEXT: ffff8480`2c98cca0 fffff80d`3e0807c1 : 00000000`00000000 ffff8480`2c98cde0 ffffd685`366a9986 00000000`00000000 : Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x66 [minkernel\wdf\framework\shared\targets\usb\fxusbinterface.cpp @ 835] ffff8480`2c98cce0 fffff80d`3e082f54 : 00000000`00000000 00000000`00000000 ffffd685`366a9910 ffffd685`371a0402 : Wdf01000!FxUsbDevice::SelectConfig+0x575 [minkernel\wdf\framework\shared\targets\usb\fxusbdevice.cpp @ 1783] ffff8480`2c98cef0 fffff80d`3e07c0d2 : 00000000`00000001 00000000`00000000 ffff8480`2c98d188 00000000`00000002 : Wdf01000!FxUsbDevice::SelectConfigMulti+0x298 [minkernel\wdf\framework\shared\targets\usb\km\fxusbdevicekm.cpp @ 1062] ffff8480`2c98d0b0 fffff802`83381b17 : ffffd685`371a0470 00000000`00000020 ffff9a0f`c9b994a0 ffffd685`35b53850 : Wdf01000!imp_WdfUsbTargetDeviceSelectConfig+0x352 [minkernel\wdf\framework\shared\targets\usb\fxusbdeviceapi.cpp @ 890] ffff8480`2c98d130 ffffd685`371a0470 : 00000000`00000020 ffff9a0f`c9b994a0 ffffd685`35b53850 00000004`00000020 : libusbK+0x1b17 ffff8480`2c98d138 00000000`00000020 : ffff9a0f`c9b994a0 ffffd685`35b53850 00000004`00000020 00000000`00000002 : 0xffffd685`371a0470 ffff8480`2c98d140 ffff9a0f`c9b994a0 : ffffd685`35b53850 00000004`00000020 00000000`00000002 ffff9a0f`c9b994a0 : 0x20 ffff8480`2c98d148 ffffd685`35b53850 : 00000004`00000020 00000000`00000002 ffff9a0f`c9b994a0 00000000`00000000 : 0xffff9a0f`c9b994a0 ffff8480`2c98d150 00000004`00000020 : 00000000`00000002 ffff9a0f`c9b994a0 00000000`00000000 fffff80d`3e098200 : 0xffffd685`35b53850 ffff8480`2c98d158 00000000`00000002 : ffff9a0f`c9b994a0 00000000`00000000 fffff80d`3e098200 fffff802`83381598 : 0x00000004`00000020 ffff8480`2c98d160 ffff9a0f`c9b994a0 : 00000000`00000000 fffff80d`3e098200 fffff802`83381598 0000297a`ca145ff8 : 0x2 ffff8480`2c98d168 00000000`00000000 : fffff80d`3e098200 fffff802`83381598 0000297a`ca145ff8 ffffd685`349caa00 : 0xffff9a0f`c9b994a0 SYMBOL_NAME: libusbK+1b17 MODULE_NAME: libusbK IMAGE_NAME: libusbK.sys STACK_COMMAND: .cxr 0xffff84802c98c2b0 ; kb BUCKET_ID_FUNC_OFFSET: 1b17 FAILURE_BUCKET_ID: AV_libusbK!unknown_function OS_VERSION: 10.0.15063.0 BUILDLAB_STR: rs2_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {29796159-6aaf-3bad-0beb-c83156b37c01} Followup: MachineOwner --------- ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: fffff807dece1452, The address that the exception occurred at Arg3: ffffce81876b8a68, Exception Record Address Arg4: ffffce81876b82b0, Context Record Address Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : AV.Dereference Value: NullClassPtr Key : AV.Fault Value: Read Key : Analysis.CPU.mSec Value: 2187 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on RTX Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 36821 Key : Analysis.Memory.CommitPeak.Mb Value: 85 Key : Analysis.System Value: CreateObject Key : WER.OS.Branch Value: rs2_release Key : WER.OS.Timestamp Value: 2017-03-17T18:34:00Z Key : WER.OS.Version Value: 10.0.15063.0 ADDITIONAL_XML: 1 OS_BUILD_LAYERS: 1 BUGCHECK_CODE: 7e BUGCHECK_P1: ffffffffc0000005 BUGCHECK_P2: fffff807dece1452 BUGCHECK_P3: ffffce81876b8a68 BUGCHECK_P4: ffffce81876b82b0 EXCEPTION_RECORD: ffffce81876b8a68 -- (.exr 0xffffce81876b8a68) ExceptionAddress: fffff807dece1452 (Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x0000000000000066) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000092 Attempt to read from address 0000000000000092 CONTEXT: ffffce81876b82b0 -- (.cxr 0xffffce81876b82b0) rax=ffffab834bb55c80 rbx=0000000000000018 rcx=ffffab834bb55cb8 rdx=0000000000000000 rsi=0000000000000000 rdi=ffffab8348eea000 rip=fffff807dece1452 rsp=ffffce81876b8ca0 rbp=0000000000000018 r8=0000000000000000 r9=0000000000000001 r10=0000000000000000 r11=0000000000000000 r12=0000000000000002 r13=ffffab834a6b9b30 r14=ffffab834bb55c80 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246 Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x66: fffff807`dece1452 8a8692000000 mov al,byte ptr [rsi+92h] ds:002b:00000000`00000092=?? Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System READ_ADDRESS: fffff8029d469358: Unable to get MiVisibleState Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd fffff8029d3c2ff0: Unable to get Flags value from nt!KdVersionBlock 0000000000000092 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s. EXCEPTION_CODE_STR: c0000005 EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000092 EXCEPTION_STR: 0xc0000005 STACK_TEXT: ffffce81`876b8ca0 fffff807`dece07c1 : 00000000`00000000 ffffce81`876b8de0 ffffab83`4b3feaf6 00000000`00000000 : Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x66 [minkernel\wdf\framework\shared\targets\usb\fxusbinterface.cpp @ 835] ffffce81`876b8ce0 fffff807`dece2f54 : 00000000`00000000 00000000`00000000 ffffab83`4b3fea80 ffffab83`48eea002 : Wdf01000!FxUsbDevice::SelectConfig+0x575 [minkernel\wdf\framework\shared\targets\usb\fxusbdevice.cpp @ 1783] ffffce81`876b8ef0 fffff807`decdc0d2 : 00000000`00000001 00000000`00000000 ffffce81`876b9188 00000000`00000002 : Wdf01000!FxUsbDevice::SelectConfigMulti+0x298 [minkernel\wdf\framework\shared\targets\usb\km\fxusbdevicekm.cpp @ 1062] ffffce81`876b90b0 fffff802`9c4c1b17 : ffffab83`48eea020 00000000`00000020 ffff950c`673086b0 ffffab83`4b4ca400 : Wdf01000!imp_WdfUsbTargetDeviceSelectConfig+0x352 [minkernel\wdf\framework\shared\targets\usb\fxusbdeviceapi.cpp @ 890] ffffce81`876b9130 ffffab83`48eea020 : 00000000`00000020 ffff950c`673086b0 ffffab83`4b4ca400 00000004`00000020 : libusbK+0x1b17 ffffce81`876b9138 00000000`00000020 : ffff950c`673086b0 ffffab83`4b4ca400 00000004`00000020 00000000`00000002 : 0xffffab83`48eea020 ffffce81`876b9140 ffff950c`673086b0 : ffffab83`4b4ca400 00000004`00000020 00000000`00000002 ffff950c`673086b0 : 0x20 ffffce81`876b9148 ffffab83`4b4ca400 : 00000004`00000020 00000000`00000002 ffff950c`673086b0 00000000`00000000 : 0xffff950c`673086b0 ffffce81`876b9150 00000004`00000020 : 00000000`00000002 ffff950c`673086b0 00000000`00000000 fffff807`decf8200 : 0xffffab83`4b4ca400 ffffce81`876b9158 00000000`00000002 : ffff950c`673086b0 00000000`00000000 fffff807`decf8200 fffff802`9c4c1598 : 0x00000004`00000020 ffffce81`876b9160 ffff950c`673086b0 : 00000000`00000000 fffff807`decf8200 fffff802`9c4c1598 0000547c`b6c04ff8 : 0x2 ffffce81`876b9168 00000000`00000000 : fffff807`decf8200 fffff802`9c4c1598 0000547c`b6c04ff8 ffffab83`4bba2900 : 0xffff950c`673086b0 SYMBOL_NAME: libusbK+1b17 MODULE_NAME: libusbK IMAGE_NAME: libusbK.sys STACK_COMMAND: .cxr 0xffffce81876b82b0 ; kb BUCKET_ID_FUNC_OFFSET: 1b17 FAILURE_BUCKET_ID: AV_libusbK!unknown_function OS_VERSION: 10.0.15063.0 BUILDLAB_STR: rs2_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {29796159-6aaf-3bad-0beb-c83156b37c01} Followup: MachineOwner --------- ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: fffff80754a91452, The address that the exception occurred at Arg3: ffffa580796e6a68, Exception Record Address Arg4: ffffa580796e62b0, Context Record Address Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : AV.Dereference Value: NullClassPtr Key : AV.Fault Value: Read Key : Analysis.CPU.mSec Value: 2358 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on RTX Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 26571 Key : Analysis.Memory.CommitPeak.Mb Value: 86 Key : Analysis.System Value: CreateObject Key : WER.OS.Branch Value: rs2_release Key : WER.OS.Timestamp Value: 2017-03-17T18:34:00Z Key : WER.OS.Version Value: 10.0.15063.0 ADDITIONAL_XML: 1 OS_BUILD_LAYERS: 1 BUGCHECK_CODE: 7e BUGCHECK_P1: ffffffffc0000005 BUGCHECK_P2: fffff80754a91452 BUGCHECK_P3: ffffa580796e6a68 BUGCHECK_P4: ffffa580796e62b0 EXCEPTION_RECORD: ffffa580796e6a68 -- (.exr 0xffffa580796e6a68) ExceptionAddress: fffff80754a91452 (Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x0000000000000066) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000092 Attempt to read from address 0000000000000092 CONTEXT: ffffa580796e62b0 -- (.cxr 0xffffa580796e62b0) rax=ffffdf0a1400ba60 rbx=0000000000000018 rcx=ffffdf0a1400ba98 rdx=0000000000000000 rsi=0000000000000000 rdi=ffffdf0a129f7600 rip=fffff80754a91452 rsp=ffffa580796e6ca0 rbp=0000000000000018 r8=0000000000000000 r9=0000000000000001 r10=0000000000000000 r11=0000000000000000 r12=0000000000000002 r13=ffffdf0a10f4c830 r14=ffffdf0a1400ba60 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246 Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x66: fffff807`54a91452 8a8692000000 mov al,byte ptr [rsi+92h] ds:002b:00000000`00000092=?? Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System READ_ADDRESS: fffff801cf65d358: Unable to get MiVisibleState Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd fffff801cf5b6ff0: Unable to get Flags value from nt!KdVersionBlock 0000000000000092 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s. EXCEPTION_CODE_STR: c0000005 EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000092 EXCEPTION_STR: 0xc0000005 STACK_TEXT: ffffa580`796e6ca0 fffff807`54a907c1 : 00000000`00000000 ffffa580`796e6de0 ffffdf0a`128b31e6 00000000`00000000 : Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x66 [minkernel\wdf\framework\shared\targets\usb\fxusbinterface.cpp @ 835] ffffa580`796e6ce0 fffff807`54a92f54 : 00000000`00000000 00000000`00000000 ffffdf0a`128b3170 ffffdf0a`129f7602 : Wdf01000!FxUsbDevice::SelectConfig+0x575 [minkernel\wdf\framework\shared\targets\usb\fxusbdevice.cpp @ 1783] ffffa580`796e6ef0 fffff807`54a8c0d2 : 00000000`00000001 00000000`00000000 ffffa580`796e7188 00000000`00000002 : Wdf01000!FxUsbDevice::SelectConfigMulti+0x298 [minkernel\wdf\framework\shared\targets\usb\km\fxusbdevicekm.cpp @ 1062] ffffa580`796e70b0 fffff801`e4281b17 : ffffdf0a`129f7620 00000000`00000020 ffff8d08`4ab779e0 ffffdf0a`12825170 : Wdf01000!imp_WdfUsbTargetDeviceSelectConfig+0x352 [minkernel\wdf\framework\shared\targets\usb\fxusbdeviceapi.cpp @ 890] ffffa580`796e7130 ffffdf0a`129f7620 : 00000000`00000020 ffff8d08`4ab779e0 ffffdf0a`12825170 00000004`00000020 : libusbK+0x1b17 ffffa580`796e7138 00000000`00000020 : ffff8d08`4ab779e0 ffffdf0a`12825170 00000004`00000020 00000000`00000002 : 0xffffdf0a`129f7620 ffffa580`796e7140 ffff8d08`4ab779e0 : ffffdf0a`12825170 00000004`00000020 00000000`00000002 ffff8d08`4ab779e0 : 0x20 ffffa580`796e7148 ffffdf0a`12825170 : 00000004`00000020 00000000`00000002 ffff8d08`4ab779e0 00000000`00000000 : 0xffff8d08`4ab779e0 ffffa580`796e7150 00000004`00000020 : 00000000`00000002 ffff8d08`4ab779e0 00000000`00000000 fffff807`54aa8200 : 0xffffdf0a`12825170 ffffa580`796e7158 00000000`00000002 : ffff8d08`4ab779e0 00000000`00000000 fffff807`54aa8200 fffff801`e4281598 : 0x00000004`00000020 ffffa580`796e7160 ffff8d08`4ab779e0 : 00000000`00000000 fffff807`54aa8200 fffff801`e4281598 000020f5`f0192ff8 : 0x2 ffffa580`796e7168 00000000`00000000 : fffff807`54aa8200 fffff801`e4281598 000020f5`f0192ff8 ffffdf0a`128fd100 : 0xffff8d08`4ab779e0 SYMBOL_NAME: libusbK+1b17 MODULE_NAME: libusbK IMAGE_NAME: libusbK.sys STACK_COMMAND: .cxr 0xffffa580796e62b0 ; kb BUCKET_ID_FUNC_OFFSET: 1b17 FAILURE_BUCKET_ID: AV_libusbK!unknown_function OS_VERSION: 10.0.15063.0 BUILDLAB_STR: rs2_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {29796159-6aaf-3bad-0beb-c83156b37c01} Followup: MachineOwner ---------
Sanmıyorum. Denildiği gibi çok eski bir Windows sürümü kullanıyorsunuz. İlk olarak onu güncelleştirin. 20H2 sürümüne temiz kurulum yaparsanız harika olur.
Windows 10 Türkçe İndirme ve Kurulum | Technopat Sosyal
Bunun haricinde USB yüzünden mavi ekran hataları da almaktasınız. Laptopun kendi ağ kartından mı Bluetooth kullanıyorsunuz yoksa harici bir adaptör mü var?
Kod:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: fffff80f7dd61452, The address that the exception occurred at Arg3: ffffde00a5c44a18, Exception Record Address Arg4: ffffde00a5c44260, Context Record Address Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : AV.Dereference Value: NullClassPtr Key : AV.Fault Value: Read Key : Analysis.CPU.mSec Value: 3327 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on RTX Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 63548 Key : Analysis.Memory.CommitPeak.Mb Value: 86 Key : Analysis.System Value: CreateObject Key : WER.OS.Branch Value: rs2_release Key : WER.OS.Timestamp Value: 2017-03-17T18:34:00Z Key : WER.OS.Version Value: 10.0.15063.0 ADDITIONAL_XML: 1 OS_BUILD_LAYERS: 1 BUGCHECK_CODE: 7e BUGCHECK_P1: ffffffffc0000005 BUGCHECK_P2: fffff80f7dd61452 BUGCHECK_P3: ffffde00a5c44a18 BUGCHECK_P4: ffffde00a5c44260 EXCEPTION_RECORD: ffffde00a5c44a18 -- (.exr 0xffffde00a5c44a18) ExceptionAddress: fffff80f7dd61452 (Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x0000000000000066) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000092 Attempt to read from address 0000000000000092 CONTEXT: ffffde00a5c44260 -- (.cxr 0xffffde00a5c44260) rax=ffff8a0d36a4e020 rbx=0000000000000018 rcx=ffff8a0d36a4e058 rdx=0000000000000000 rsi=0000000000000000 rdi=ffff8a0d33a01a00 rip=fffff80f7dd61452 rsp=ffffde00a5c44c50 rbp=0000000000000018 r8=0000000000000000 r9=0000000000000001 r10=0000000000000000 r11=0000000000000000 r12=0000000000000002 r13=ffff8a0d344076e0 r14=ffff8a0d36a4e020 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x66: fffff80f`7dd61452 8a8692000000 mov al,byte ptr [rsi+92h] ds:002b:00000000`00000092=?? Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System READ_ADDRESS: fffff803669ff358: Unable to get MiVisibleState Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd fffff80366958ff0: Unable to get Flags value from nt!KdVersionBlock 0000000000000092 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s. EXCEPTION_CODE_STR: c0000005 EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000092 EXCEPTION_STR: 0xc0000005 LOCK_ADDRESS: fffff80366982f20 -- (!locks fffff80366982f20) Cannot get _ERESOURCE type Resource @ nt!PiEngineLock (0xfffff80366982f20) Available 1 total locks PNP_TRIAGE_DATA: Lock address : 0xfffff80366982f20 Thread Count : 0 Thread address: 0x0000000000000000 Thread wait : 0x0 STACK_TEXT: ffffde00`a5c44c50 fffff80f`7dd607c1 : 00000000`00000000 ffffde00`a5c44d90 ffff8a0d`318899a6 00000000`00000000 : Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x66 [minkernel\wdf\framework\shared\targets\usb\fxusbinterface.cpp @ 835] ffffde00`a5c44c90 fffff80f`7dd62f54 : 00000000`00000000 00000000`00000000 ffff8a0d`31889930 ffff8a0d`33a01a02 : Wdf01000!FxUsbDevice::SelectConfig+0x575 [minkernel\wdf\framework\shared\targets\usb\fxusbdevice.cpp @ 1783] ffffde00`a5c44ea0 fffff80f`7dd5c0d2 : 00000000`00000020 00000000`00000000 ffff8a0d`33749b70 00000000`00000000 : Wdf01000!FxUsbDevice::SelectConfigMulti+0x298 [minkernel\wdf\framework\shared\targets\usb\km\fxusbdevicekm.cpp @ 1062] ffffde00`a5c45060 fffff80f`8039888f : ffff8a0d`33a01a50 00000000`00000020 000075f2`cc8b6488 00000000`c0000023 : Wdf01000!imp_WdfUsbTargetDeviceSelectConfig+0x352 [minkernel\wdf\framework\shared\targets\usb\fxusbdeviceapi.cpp @ 890] ffffde00`a5c450e0 fffff80f`8039651d : 00000000`00000000 000075f2`cc8b6488 ffff8a0d`33749e60 ffff8a0d`32924180 : WinUSB!WinUSB_SelectConfiguration+0x9f ffffde00`a5c45160 fffff80f`7dd09c18 : ffff8a0d`332fec18 ffff8a0d`332fe700 00000000`00000000 00000602`00000008 : WinUSB!WinUSB_PrepareHardware+0x1bd ffffde00`a5c451b0 fffff80f`7dcf619f : ffff8a0d`332fe690 fffff80f`7dcf3161 ffff8a0d`325f6ac0 ffff8a0d`332fe690 : Wdf01000!FxPnpDevicePrepareHardware::InvokeClient+0x28 [minkernel\wdf\framework\shared\irphandlers\pnp\pnpcallbacks.cpp @ 347] ffffde00`a5c45200 fffff80f`7dcfc40a : ffff8a0d`325f6ac0 ffff8a0d`332fe7e0 00000000`00000000 ffff8a0d`325f6ac0 : Wdf01000!FxPkgPnp::PnpPrepareHardware+0xff [minkernel\wdf\framework\shared\irphandlers\pnp\pnpstatemachine.cpp @ 3572] ffffde00`a5c45250 fffff80f`7dcf63c9 : ffff8a0d`332fe601 00000000`00000100 ffff8a0d`332fe690 00000000`00000108 : Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0x7a [minkernel\wdf\framework\shared\irphandlers\pnp\pnpstatemachine.cpp @ 1399] ffffde00`a5c45290 fffff80f`7dcf357f : ffff8a0d`332fe7e8 fffff80f`00000000 ffff8a0d`332fe7c0 00000000`00000000 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0x1a9 [minkernel\wdf\framework\shared\irphandlers\pnp\pnpstatemachine.cpp @ 1150] ffffde00`a5c45340 fffff80f`7dd0945a : 00000000`00000000 fffff803`666f1250 00000000`00000008 ffffde00`a5c45478 : Wdf01000!FxPkgPnp::PnpProcessEvent+0x12f [minkernel\wdf\framework\shared\irphandlers\pnp\pnpstatemachine.cpp @ 933] ffffde00`a5c453e0 fffff80f`7dcd752e : ffff8a0d`33749b70 00000000`00000000 00000000`00000000 ffff8a0d`332fe690 : Wdf01000!FxPkgPnp::_PnpStartDevice+0x4a [minkernel\wdf\framework\shared\irphandlers\pnp\fxpkgpnp.cpp @ 1862] ffffde00`a5c45440 fffff80f`7dcd6b95 : ffff8a0d`32924180 ffff8a0d`33749b70 ffff8a0d`332fe690 ffffde00`a5c45528 : Wdf01000!FxPkgPnp::Dispatch+0xee [minkernel\wdf\framework\shared\irphandlers\pnp\fxpkgpnp.cpp @ 670] ffffde00`a5c454e0 fffff803`66a8d912 : ffff8a0d`325f6ac0 ffff8a0d`30627a04 00000000`00000000 fffff803`66967230 : Wdf01000!FxDevice::DispatchWithLock+0x155 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1430] ffffde00`a5c455d0 fffff803`6664343c : ffff8a0d`325a1cc0 00000000`00000000 ffff8a0d`30627a50 fffff803`00000000 : nt!PnpAsynchronousCall+0xea ffffde00`a5c45610 fffff803`666f0cf8 : 00000000`00000000 ffff8a0d`325a1cc0 fffff803`666f1250 fffff803`666f1250 : nt!PnpSendIrp+0x54 ffffde00`a5c45680 fffff803`66b06cd7 : ffff8a0d`334809a0 ffff8a0d`30627a50 00000000`00000000 00000000`00000200 : nt!PnpStartDevice+0x88 ffffde00`a5c45710 fffff803`66b06027 : ffff8a0d`334809a0 ffffde00`a5c458e0 00000000`00000000 ffff8a0d`33480902 : nt!PnpStartDeviceNode+0xdb ffffde00`a5c457a0 fffff803`66a54944 : ffff8a0d`334809a0 00000000`00000001 00000000`00000001 ffff8a0d`334809a0 : nt!PipProcessStartPhase1+0x53 ffffde00`a5c457e0 fffff803`66cc25f2 : ffff8a0d`334809a0 fffff803`66681059 fffff803`66a16200 00000000`00000000 : nt!PipProcessDevNodeTree+0x428 ffffde00`a5c45a60 fffff803`667d3987 : ffff8a01`00000003 00000000`00000000 fffff803`00000000 ffff8a0d`33aa4aa0 : nt!PiRestartDevice+0xba ffffde00`a5c45ab0 fffff803`6665bca8 : ffff8a0d`38d71700 fffff803`669819c0 fffff803`66a16380 fffff803`66a16380 : nt!PnpDeviceActionWorker+0xe32d7 ffffde00`a5c45b80 fffff803`666faa37 : 00000000`00000000 00000000`00000080 ffff8a0d`3027a040 ffff8a0d`38d71700 : nt!ExpWorkerThread+0xd8 ffffde00`a5c45c10 fffff803`6678f876 : ffffde00`9de07180 ffff8a0d`38d71700 fffff803`666fa9f0 00000000`00000000 : nt!PspSystemThreadStartup+0x47 ffffde00`a5c45c60 00000000`00000000 : ffffde00`a5c46000 ffffde00`a5c40000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 SYMBOL_NAME: WinUSB!WinUSB_SelectConfiguration+9f MODULE_NAME: WinUSB IMAGE_NAME: WinUSB.SYS IMAGE_VERSION: 10.0.15063.413 STACK_COMMAND: .cxr 0xffffde00a5c44260 ; kb BUCKET_ID_FUNC_OFFSET: 9f FAILURE_BUCKET_ID: AV_WinUSB!WinUSB_SelectConfiguration OS_VERSION: 10.0.15063.0 BUILDLAB_STR: rs2_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {ac85bd58-6492-3f38-ae2d-47d0f754ee4a} Followup: MachineOwner --------- ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: fffff80d3e081452, The address that the exception occurred at Arg3: ffff84802c98ca68, Exception Record Address Arg4: ffff84802c98c2b0, Context Record Address Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : AV.Dereference Value: NullClassPtr Key : AV.Fault Value: Read Key : Analysis.CPU.mSec Value: 2155 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on RTX Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 27492 Key : Analysis.Memory.CommitPeak.Mb Value: 86 Key : Analysis.System Value: CreateObject Key : WER.OS.Branch Value: rs2_release Key : WER.OS.Timestamp Value: 2017-03-17T18:34:00Z Key : WER.OS.Version Value: 10.0.15063.0 ADDITIONAL_XML: 1 OS_BUILD_LAYERS: 1 BUGCHECK_CODE: 7e BUGCHECK_P1: ffffffffc0000005 BUGCHECK_P2: fffff80d3e081452 BUGCHECK_P3: ffff84802c98ca68 BUGCHECK_P4: ffff84802c98c2b0 EXCEPTION_RECORD: ffff84802c98ca68 -- (.exr 0xffff84802c98ca68) ExceptionAddress: fffff80d3e081452 (Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x0000000000000066) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000092 Attempt to read from address 0000000000000092 CONTEXT: ffff84802c98c2b0 -- (.cxr 0xffff84802c98c2b0) rax=ffffd6853714a020 rbx=0000000000000018 rcx=ffffd6853714a058 rdx=0000000000000000 rsi=0000000000000000 rdi=ffffd685371a0400 rip=fffff80d3e081452 rsp=ffff84802c98cca0 rbp=0000000000000018 r8=0000000000000000 r9=0000000000000001 r10=0000000000000000 r11=0000000000000000 r12=0000000000000002 r13=ffffd68532a11650 r14=ffffd6853714a020 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x66: fffff80d`3e081452 8a8692000000 mov al,byte ptr [rsi+92h] ds:002b:00000000`00000092=?? Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System READ_ADDRESS: fffff80283df0358: Unable to get MiVisibleState Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd fffff80283d49ff0: Unable to get Flags value from nt!KdVersionBlock 0000000000000092 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s. EXCEPTION_CODE_STR: c0000005 EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000092 EXCEPTION_STR: 0xc0000005 STACK_TEXT: ffff8480`2c98cca0 fffff80d`3e0807c1 : 00000000`00000000 ffff8480`2c98cde0 ffffd685`366a9986 00000000`00000000 : Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x66 [minkernel\wdf\framework\shared\targets\usb\fxusbinterface.cpp @ 835] ffff8480`2c98cce0 fffff80d`3e082f54 : 00000000`00000000 00000000`00000000 ffffd685`366a9910 ffffd685`371a0402 : Wdf01000!FxUsbDevice::SelectConfig+0x575 [minkernel\wdf\framework\shared\targets\usb\fxusbdevice.cpp @ 1783] ffff8480`2c98cef0 fffff80d`3e07c0d2 : 00000000`00000001 00000000`00000000 ffff8480`2c98d188 00000000`00000002 : Wdf01000!FxUsbDevice::SelectConfigMulti+0x298 [minkernel\wdf\framework\shared\targets\usb\km\fxusbdevicekm.cpp @ 1062] ffff8480`2c98d0b0 fffff802`83381b17 : ffffd685`371a0470 00000000`00000020 ffff9a0f`c9b994a0 ffffd685`35b53850 : Wdf01000!imp_WdfUsbTargetDeviceSelectConfig+0x352 [minkernel\wdf\framework\shared\targets\usb\fxusbdeviceapi.cpp @ 890] ffff8480`2c98d130 ffffd685`371a0470 : 00000000`00000020 ffff9a0f`c9b994a0 ffffd685`35b53850 00000004`00000020 : libusbK+0x1b17 ffff8480`2c98d138 00000000`00000020 : ffff9a0f`c9b994a0 ffffd685`35b53850 00000004`00000020 00000000`00000002 : 0xffffd685`371a0470 ffff8480`2c98d140 ffff9a0f`c9b994a0 : ffffd685`35b53850 00000004`00000020 00000000`00000002 ffff9a0f`c9b994a0 : 0x20 ffff8480`2c98d148 ffffd685`35b53850 : 00000004`00000020 00000000`00000002 ffff9a0f`c9b994a0 00000000`00000000 : 0xffff9a0f`c9b994a0 ffff8480`2c98d150 00000004`00000020 : 00000000`00000002 ffff9a0f`c9b994a0 00000000`00000000 fffff80d`3e098200 : 0xffffd685`35b53850 ffff8480`2c98d158 00000000`00000002 : ffff9a0f`c9b994a0 00000000`00000000 fffff80d`3e098200 fffff802`83381598 : 0x00000004`00000020 ffff8480`2c98d160 ffff9a0f`c9b994a0 : 00000000`00000000 fffff80d`3e098200 fffff802`83381598 0000297a`ca145ff8 : 0x2 ffff8480`2c98d168 00000000`00000000 : fffff80d`3e098200 fffff802`83381598 0000297a`ca145ff8 ffffd685`349caa00 : 0xffff9a0f`c9b994a0 SYMBOL_NAME: libusbK+1b17 MODULE_NAME: libusbK IMAGE_NAME: libusbK.sys STACK_COMMAND: .cxr 0xffff84802c98c2b0 ; kb BUCKET_ID_FUNC_OFFSET: 1b17 FAILURE_BUCKET_ID: AV_libusbK!unknown_function OS_VERSION: 10.0.15063.0 BUILDLAB_STR: rs2_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {29796159-6aaf-3bad-0beb-c83156b37c01} Followup: MachineOwner --------- ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: fffff807dece1452, The address that the exception occurred at Arg3: ffffce81876b8a68, Exception Record Address Arg4: ffffce81876b82b0, Context Record Address Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : AV.Dereference Value: NullClassPtr Key : AV.Fault Value: Read Key : Analysis.CPU.mSec Value: 2187 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on RTX Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 36821 Key : Analysis.Memory.CommitPeak.Mb Value: 85 Key : Analysis.System Value: CreateObject Key : WER.OS.Branch Value: rs2_release Key : WER.OS.Timestamp Value: 2017-03-17T18:34:00Z Key : WER.OS.Version Value: 10.0.15063.0 ADDITIONAL_XML: 1 OS_BUILD_LAYERS: 1 BUGCHECK_CODE: 7e BUGCHECK_P1: ffffffffc0000005 BUGCHECK_P2: fffff807dece1452 BUGCHECK_P3: ffffce81876b8a68 BUGCHECK_P4: ffffce81876b82b0 EXCEPTION_RECORD: ffffce81876b8a68 -- (.exr 0xffffce81876b8a68) ExceptionAddress: fffff807dece1452 (Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x0000000000000066) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000092 Attempt to read from address 0000000000000092 CONTEXT: ffffce81876b82b0 -- (.cxr 0xffffce81876b82b0) rax=ffffab834bb55c80 rbx=0000000000000018 rcx=ffffab834bb55cb8 rdx=0000000000000000 rsi=0000000000000000 rdi=ffffab8348eea000 rip=fffff807dece1452 rsp=ffffce81876b8ca0 rbp=0000000000000018 r8=0000000000000000 r9=0000000000000001 r10=0000000000000000 r11=0000000000000000 r12=0000000000000002 r13=ffffab834a6b9b30 r14=ffffab834bb55c80 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246 Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x66: fffff807`dece1452 8a8692000000 mov al,byte ptr [rsi+92h] ds:002b:00000000`00000092=?? Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System READ_ADDRESS: fffff8029d469358: Unable to get MiVisibleState Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd fffff8029d3c2ff0: Unable to get Flags value from nt!KdVersionBlock 0000000000000092 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s. EXCEPTION_CODE_STR: c0000005 EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000092 EXCEPTION_STR: 0xc0000005 STACK_TEXT: ffffce81`876b8ca0 fffff807`dece07c1 : 00000000`00000000 ffffce81`876b8de0 ffffab83`4b3feaf6 00000000`00000000 : Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x66 [minkernel\wdf\framework\shared\targets\usb\fxusbinterface.cpp @ 835] ffffce81`876b8ce0 fffff807`dece2f54 : 00000000`00000000 00000000`00000000 ffffab83`4b3fea80 ffffab83`48eea002 : Wdf01000!FxUsbDevice::SelectConfig+0x575 [minkernel\wdf\framework\shared\targets\usb\fxusbdevice.cpp @ 1783] ffffce81`876b8ef0 fffff807`decdc0d2 : 00000000`00000001 00000000`00000000 ffffce81`876b9188 00000000`00000002 : Wdf01000!FxUsbDevice::SelectConfigMulti+0x298 [minkernel\wdf\framework\shared\targets\usb\km\fxusbdevicekm.cpp @ 1062] ffffce81`876b90b0 fffff802`9c4c1b17 : ffffab83`48eea020 00000000`00000020 ffff950c`673086b0 ffffab83`4b4ca400 : Wdf01000!imp_WdfUsbTargetDeviceSelectConfig+0x352 [minkernel\wdf\framework\shared\targets\usb\fxusbdeviceapi.cpp @ 890] ffffce81`876b9130 ffffab83`48eea020 : 00000000`00000020 ffff950c`673086b0 ffffab83`4b4ca400 00000004`00000020 : libusbK+0x1b17 ffffce81`876b9138 00000000`00000020 : ffff950c`673086b0 ffffab83`4b4ca400 00000004`00000020 00000000`00000002 : 0xffffab83`48eea020 ffffce81`876b9140 ffff950c`673086b0 : ffffab83`4b4ca400 00000004`00000020 00000000`00000002 ffff950c`673086b0 : 0x20 ffffce81`876b9148 ffffab83`4b4ca400 : 00000004`00000020 00000000`00000002 ffff950c`673086b0 00000000`00000000 : 0xffff950c`673086b0 ffffce81`876b9150 00000004`00000020 : 00000000`00000002 ffff950c`673086b0 00000000`00000000 fffff807`decf8200 : 0xffffab83`4b4ca400 ffffce81`876b9158 00000000`00000002 : ffff950c`673086b0 00000000`00000000 fffff807`decf8200 fffff802`9c4c1598 : 0x00000004`00000020 ffffce81`876b9160 ffff950c`673086b0 : 00000000`00000000 fffff807`decf8200 fffff802`9c4c1598 0000547c`b6c04ff8 : 0x2 ffffce81`876b9168 00000000`00000000 : fffff807`decf8200 fffff802`9c4c1598 0000547c`b6c04ff8 ffffab83`4bba2900 : 0xffff950c`673086b0 SYMBOL_NAME: libusbK+1b17 MODULE_NAME: libusbK IMAGE_NAME: libusbK.sys STACK_COMMAND: .cxr 0xffffce81876b82b0 ; kb BUCKET_ID_FUNC_OFFSET: 1b17 FAILURE_BUCKET_ID: AV_libusbK!unknown_function OS_VERSION: 10.0.15063.0 BUILDLAB_STR: rs2_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {29796159-6aaf-3bad-0beb-c83156b37c01} Followup: MachineOwner --------- ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: fffff80754a91452, The address that the exception occurred at Arg3: ffffa580796e6a68, Exception Record Address Arg4: ffffa580796e62b0, Context Record Address Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : AV.Dereference Value: NullClassPtr Key : AV.Fault Value: Read Key : Analysis.CPU.mSec Value: 2358 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on RTX Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 26571 Key : Analysis.Memory.CommitPeak.Mb Value: 86 Key : Analysis.System Value: CreateObject Key : WER.OS.Branch Value: rs2_release Key : WER.OS.Timestamp Value: 2017-03-17T18:34:00Z Key : WER.OS.Version Value: 10.0.15063.0 ADDITIONAL_XML: 1 OS_BUILD_LAYERS: 1 BUGCHECK_CODE: 7e BUGCHECK_P1: ffffffffc0000005 BUGCHECK_P2: fffff80754a91452 BUGCHECK_P3: ffffa580796e6a68 BUGCHECK_P4: ffffa580796e62b0 EXCEPTION_RECORD: ffffa580796e6a68 -- (.exr 0xffffa580796e6a68) ExceptionAddress: fffff80754a91452 (Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x0000000000000066) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000092 Attempt to read from address 0000000000000092 CONTEXT: ffffa580796e62b0 -- (.cxr 0xffffa580796e62b0) rax=ffffdf0a1400ba60 rbx=0000000000000018 rcx=ffffdf0a1400ba98 rdx=0000000000000000 rsi=0000000000000000 rdi=ffffdf0a129f7600 rip=fffff80754a91452 rsp=ffffa580796e6ca0 rbp=0000000000000018 r8=0000000000000000 r9=0000000000000001 r10=0000000000000000 r11=0000000000000000 r12=0000000000000002 r13=ffffdf0a10f4c830 r14=ffffdf0a1400ba60 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246 Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x66: fffff807`54a91452 8a8692000000 mov al,byte ptr [rsi+92h] ds:002b:00000000`00000092=?? Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System READ_ADDRESS: fffff801cf65d358: Unable to get MiVisibleState Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd fffff801cf5b6ff0: Unable to get Flags value from nt!KdVersionBlock 0000000000000092 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s. EXCEPTION_CODE_STR: c0000005 EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000092 EXCEPTION_STR: 0xc0000005 STACK_TEXT: ffffa580`796e6ca0 fffff807`54a907c1 : 00000000`00000000 ffffa580`796e6de0 ffffdf0a`128b31e6 00000000`00000000 : Wdf01000!FxUsbInterface::FormatSelectSettingUrb+0x66 [minkernel\wdf\framework\shared\targets\usb\fxusbinterface.cpp @ 835] ffffa580`796e6ce0 fffff807`54a92f54 : 00000000`00000000 00000000`00000000 ffffdf0a`128b3170 ffffdf0a`129f7602 : Wdf01000!FxUsbDevice::SelectConfig+0x575 [minkernel\wdf\framework\shared\targets\usb\fxusbdevice.cpp @ 1783] ffffa580`796e6ef0 fffff807`54a8c0d2 : 00000000`00000001 00000000`00000000 ffffa580`796e7188 00000000`00000002 : Wdf01000!FxUsbDevice::SelectConfigMulti+0x298 [minkernel\wdf\framework\shared\targets\usb\km\fxusbdevicekm.cpp @ 1062] ffffa580`796e70b0 fffff801`e4281b17 : ffffdf0a`129f7620 00000000`00000020 ffff8d08`4ab779e0 ffffdf0a`12825170 : Wdf01000!imp_WdfUsbTargetDeviceSelectConfig+0x352 [minkernel\wdf\framework\shared\targets\usb\fxusbdeviceapi.cpp @ 890] ffffa580`796e7130 ffffdf0a`129f7620 : 00000000`00000020 ffff8d08`4ab779e0 ffffdf0a`12825170 00000004`00000020 : libusbK+0x1b17 ffffa580`796e7138 00000000`00000020 : ffff8d08`4ab779e0 ffffdf0a`12825170 00000004`00000020 00000000`00000002 : 0xffffdf0a`129f7620 ffffa580`796e7140 ffff8d08`4ab779e0 : ffffdf0a`12825170 00000004`00000020 00000000`00000002 ffff8d08`4ab779e0 : 0x20 ffffa580`796e7148 ffffdf0a`12825170 : 00000004`00000020 00000000`00000002 ffff8d08`4ab779e0 00000000`00000000 : 0xffff8d08`4ab779e0 ffffa580`796e7150 00000004`00000020 : 00000000`00000002 ffff8d08`4ab779e0 00000000`00000000 fffff807`54aa8200 : 0xffffdf0a`12825170 ffffa580`796e7158 00000000`00000002 : ffff8d08`4ab779e0 00000000`00000000 fffff807`54aa8200 fffff801`e4281598 : 0x00000004`00000020 ffffa580`796e7160 ffff8d08`4ab779e0 : 00000000`00000000 fffff807`54aa8200 fffff801`e4281598 000020f5`f0192ff8 : 0x2 ffffa580`796e7168 00000000`00000000 : fffff807`54aa8200 fffff801`e4281598 000020f5`f0192ff8 ffffdf0a`128fd100 : 0xffff8d08`4ab779e0 SYMBOL_NAME: libusbK+1b17 MODULE_NAME: libusbK IMAGE_NAME: libusbK.sys STACK_COMMAND: .cxr 0xffffa580796e62b0 ; kb BUCKET_ID_FUNC_OFFSET: 1b17 FAILURE_BUCKET_ID: AV_libusbK!unknown_function OS_VERSION: 10.0.15063.0 BUILDLAB_STR: rs2_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {29796159-6aaf-3bad-0beb-c83156b37c01} Followup: MachineOwner ---------
Bu sitenin çalışmasını sağlamak için gerekli çerezleri ve deneyiminizi iyileştirmek için isteğe bağlı çerezleri kullanıyoruz.