전체를 복사해왔어요
블루스크린 때문에 미쳐버릴것만 같습니다.. 대체 무슨이유에서 블루스크린이 뜨는건지 알려주세요 ㅠㅠ
Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:WindowsMEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17763 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff800`4ae0f000 PsLoadedModuleList = 0xfffff800`4b22aad0
Debug session time: Mon Feb 18 06:19:58.071 2019 (UTC + 9:00)
System Uptime: 0 days 6:44:03.219
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000e7`9a8d7018). Type ".hh dbgerr001" for details
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {0, 501, 500, fffff8004b351380}
*************************************************************************
*** ***
*** ***
*** 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: TickPeriods ***
*** ***
*************************************************************************
Probably caused by : USBXHCI.SYS ( USBXHCI!TR_ReleaseDoubleBuffer+20 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff8004b351380, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: TickPeriods ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 401
BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434
SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.
SYSTEM_PRODUCT_NAME: B360M-DS3H
SYSTEM_SKU: Default string
SYSTEM_VERSION: Default string
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: F11
BIOS_DATE: 09/17/2018
BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.
BASEBOARD_PRODUCT: B360M DS3H
BASEBOARD_VERSION: Default string
DUMP_TYPE: 1
BUGCHECK_P1: 0
BUGCHECK_P2: 501
BUGCHECK_P3: 500
BUGCHECK_P4: fffff8004b351380
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
CPU_COUNT: c
CPU_MHZ: c78
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 9e
CPU_STEPPING: a
CPU_MICROCODE: 6,9e,a,0 (F,M,S,R) SIG: 96'00000000 (cache) 96'00000000 (init)
BLACKBOXBSD: 1 (!blackboxbsd)
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x133
PROCESS_NAME: NVIDIA Share.exe
CURRENT_IRQL: d
ANALYSIS_SESSION_HOST: DESKTOP-TRQ43IB
ANALYSIS_SESSION_TIME: 02-18-2019 07:06:25.0038
ANALYSIS_VERSION: 10.0.17763.132 amd64fre
LAST_CONTROL_TRANSFER: from fffff8004b065145 to fffff8004afc2440
STACK_TEXT:
fffff800`4d283ba8 fffff800`4b065145 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff800`4d283bb0 fffff800`4af332e4 : 0000466a`2a1d4435 00000000`00000000 00000000`0017acce fffff800`49d1f180 : nt!KeAccumulateTicks+0x12ed25
fffff800`4d283c10 fffff800`4b880332 : 00000000`00000000 fffff800`4b8e4bf0 fffff800`4d27c650 00000000`00000002 : nt!KeClockInterruptNotify+0x604
fffff800`4d283f30 fffff800`4ae518b5 : 00000038`722c97cb fffff800`4b8e77e0 fffff800`4b8e7890 fffff800`4d27c650 : hal!HalpTimerClockInterrupt+0xf2
fffff800`4d283f60 fffff800`4afc3e3a : fffff800`4d27c650 fffff800`4b8e77e0 00000000`00000000 ffffb30e`4d08b510 : nt!KiCallInterruptServiceRoutine+0xa5
fffff800`4d283fb0 fffff800`4afc4387 : ffffb30e`57ace010 fffff800`4d27c5d8 fffff800`4d27c5d8 00000000`00000001 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff800`4d27c5d0 fffff800`4ae3b770 : ffffb30e`4be5d400 fffff800`4d27c7f1 ffffb30e`4be90010 fffff800`61c33fb8 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff800`4d27c760 fffff800`4ae3b737 : ffffb30e`4d08b510 fffff800`49d1f180 fffff800`4d270028 fffff800`4d27c848 : nt!KxWaitForSpinLockAndAcquire+0x30
fffff800`4d27c790 fffff800`61c24f70 : ffffb30e`4be5d400 ffffb30e`4b06d4a8 00000000`00000004 fffff800`4d27c860 : nt!KeAcquireSpinLockRaiseToDpc+0x87
fffff800`4d27c7c0 fffff800`61c32aaf : ffffb30e`4be5d400 ffffb30e`4be5d400 00000000`00000004 00000000`00000000 : USBXHCI!TR_ReleaseDoubleBuffer+0x20
fffff800`4d27c7f0 fffff800`61c33055 : ffffb30e`4be5d400 ffffb30e`4d08b4b0 fffff800`4d27cb68 fffff800`4d27c8c1 : USBXHCI!Bulk_TransferData_Free+0x1b
fffff800`4d27c820 fffff800`61c32eb5 : 00000000`ffffffff fffff800`4d27c902 ffffb30e`4be5d260 ffffb30e`4d08b4b0 : USBXHCI!Bulk_Transfer_PrepareForCompletion+0x139
fffff800`4d27c890 fffff800`61c30ed7 : ffffb30e`4be5d400 00000000`00000001 ffffb30e`4be5d490 fffff800`4d27cb68 : USBXHCI!Bulk_Transfer_CompleteCancelable+0x159
fffff800`4d27c8f0 fffff800`61c2f770 : fffff800`49d1f180 fffff800`4aed6f9d ffffb30e`47ad2000 fffff806`c5fe2053 : USBXHCI!Bulk_ProcessTransferEventWithED1+0x41f
fffff800`4d27c9b0 fffff800`61c25183 : 00000000`00000002 ffffb30e`47acf268 fffff800`02000240 fffff800`4d27cae0 : USBXHCI!Bulk_EP_TransferEventHandler+0x10
fffff800`4d27c9e0 fffff800`61c188d7 : 00000000`0000002b fffff800`4d27cad1 ffffb30e`4b1c3460 fffff800`61c02ff4 : USBXHCI!TR_TransferEventHandler+0x17
fffff800`4d27ca10 fffff800`61c37042 : fffff800`4d27cb68 fffff800`4d27cb38 00000000`00000000 fffff800`4d27cb40 : USBXHCI!Endpoint_TransferEventHandler+0x13f
fffff800`4d27ca90 fffff800`61c1b5b0 : ffffb30e`4b0b5260 fffff800`4d27cb89 ffffb30e`4b0b5330 ffffb30e`4bd5d668 : USBXHCI!UsbDevice_TransferEventHandler+0x92
fffff800`4d27caf0 fffff800`61c1bffc : 00400a02`00000010 0000465b`4a5e89e8 ffffb30e`513fc470 ffffb30e`4b0b5060 : USBXHCI!Interrupter_DeferredWorkProcessor+0x500
fffff800`4d27cbf0 fffff806`c5ee381d : ffffb30e`46c3e310 fffff800`00000460 00000000`00400a02 00000000`00000000 : USBXHCI!Interrupter_WdfEvtInterruptDpc+0xc
fffff800`4d27cc20 fffff800`4aec7c67 : fffff800`4d27ccb8 ffffb30e`46c0f000 00000000`00000f44 fffff800`49d21f80 : Wdf01000!FxInterrupt::_InterruptDpcThunk+0x9d [minkernelwdfframeworksharedirphandlerspnpkminterruptobjectkm.cpp @ 410]
fffff800`4d27cc60 fffff800`4aec72ae : 00000000`0000001e 00000000`00989680 ffffb30e`55edb080 00000000`00000019 : nt!KiExecuteAllDpcs+0x2e7
fffff800`4d27cda0 fffff800`4afc92a5 : 00000000`00000000 fffff800`49d1f180 ffffc301`ba70fa80 ffffd900`6ac4fa00 : nt!KiRetireDpcList+0x1ae
fffff800`4d27cfb0 fffff800`4afc9090 : 00000000`00000036 fffff800`4b881ae6 00000000`00000000 ffffc301`ba70fa80 : nt!KxRetireDpcList+0x5
ffffc301`ba70f9c0 fffff800`4afc8955 : 00007ff9`202bf560 fffff800`4afc3f01 00000000`9ccff700 ffffc301`ba70fa80 : nt!KiDispatchInterruptContinue
ffffc301`ba70f9f0 fffff800`4afc3f01 : 00000000`9ccff700 ffffc301`ba70fa80 ffffd900`6ac4fa00 ffffc301`ba70fa80 : nt!KiDpcInterruptBypass+0x25
ffffc301`ba70fa00 00007ff9`1d233ca7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatch+0xb1
000000e7`9ccff210 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`1d233ca7
THREAD_SHA1_HASH_MOD_FUNC: cf9ce88cefa0522d9b5ade4cbedbdfe2f99feb0f
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 241eba022c095886c2ed47474311f83fedf48946
THREAD_SHA1_HASH_MOD: a65fb7b37df7972fa6df8833a3770d80de27f9c3
FOLLOWUP_IP:
USBXHCI!TR_ReleaseDoubleBuffer+20
fffff800`61c24f70 0f1f440000 nop dword ptr [rax+rax]
FAULT_INSTR_CODE: 441f0f
SYMBOL_STACK_INDEX: 9
SYMBOL_NAME: USBXHCI!TR_ReleaseDoubleBuffer+20
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: USBXHCI
IMAGE_NAME: USBXHCI.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION: 10.0.17763.1
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 20
FAILURE_BUCKET_ID: 0x133_DPC_USBXHCI!TR_ReleaseDoubleBuffer
BUCKET_ID: 0x133_DPC_USBXHCI!TR_ReleaseDoubleBuffer
PRIMARY_PROBLEM_CLASS: 0x133_DPC_USBXHCI!TR_ReleaseDoubleBuffer
TARGET_TIME: 2019-02-17T21:19:58.000Z
OSBUILD: 17763
OSSERVICEPACK: 0
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: unknown_date
BUILDDATESTAMP_STR: 180914-1434
BUILDLAB_STR: rs5_release
BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434
ANALYSIS_SESSION_ELAPSED_TIME: 508
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x133_dpc_usbxhci!tr_releasedoublebuffer
FAILURE_ID_HASH: {ba32ec60-4a1b-6996-56c5-504fe8672609}
Followup: MachineOwner
---------
마나오리
마나오리 
