BSOD 0x00000133

https://support.microsoft.com/en-us/help/3029348/

BSOD分析

08-26

Windows XP下的USB设备,使用我自己写的驱动后设备不停的Reset,该设备是透过一个USB Hub与电脑相连,rn重启后得到如下的信息,请各位帮忙分析下原因:rnrn*******************************************************************************rn* *rn* Bugcheck Analysis *rn* *rn*******************************************************************************rnrnDRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)rnAn attempt was made to access a pageable (or completely invalid) address at anrninterrupt request level (IRQL) that is too high. This is usuallyrncaused by drivers using improper addresses.rnIf kernel debugger is available get stack backtrace.rnArguments:rnArg1: 00000107, memory referencedrnArg2: 00000002, IRQLrnArg3: 00000000, value 0 = read operation, 1 = write operationrnArg4: f75489f0, address which referenced memoryrnrnDebugging Details:rn------------------rnrn*** WARNING: Unable to verify timestamp for bhound5.sysrn*** ERROR: Module load completed but symbols could not be loaded for bhound5.sysrn*** WARNING: Unable to verify timestamp for hcmon.sysrn*** ERROR: Module load completed but symbols could not be loaded for hcmon.sysrnrnREAD_ADDRESS: 00000107 rnrnCURRENT_IRQL: 2rnrnFAULTING_IP: rnusbhub!USBH_FdoQueryBusRelations+472rnf75489f0 8b10 mov edx,dword ptr [eax]rnrnCUSTOMER_CRASH_COUNT: 5rnrnDEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULTrnrnBUGCHECK_STR: 0xD1rnrnPROCESS_NAME: SystemrnrnLOCK_ADDRESS: 805523e0 -- (!locks 805523e0)rnrnResource @ nt!PiEngineLock (0x805523e0) AvailablernrnWARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.rnrnrnWARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.rnrn1 total locksrnrnPNP_TRIAGE: rn Lock address : 0x805523e0rn Thread Count : 0rn Thread address: 0x00000000rn Thread wait : 0x0rnrnLAST_CONTROL_TRANSFER: from f7548f9f to f75489f0rnrnSTACK_TEXT: rnf78d2994 f7548f9f 84b26d50 846d8008 846d8008 usbhub!USBH_FdoQueryBusRelations+0x472rnf78d29b4 f7549039 84b26d50 846d8008 00000007 usbhub!USBH_FdoPnP+0x143rnf78d29dc f75491ee 84b26d50 846d8008 f78d2a08 usbhub!USBH_FdoDispatch+0x63rnf78d29ec f7710435 84b26c98 846d8008 846d8008 usbhub!USBH_HubDispatch+0x5ernWARNING: Stack unwind information not available. Following frames may be wrong.rnf78d2a08 b56f67dd 84b26c98 00000000 846d8008 bhound5+0x1435rnf78d2a24 804ef003 84b26c98 846d8008 f78d2aa4 hcmon+0x27ddrnf78d2a34 805880a9 00000000 84713ee8 84713fc8 nt!IopfCallDriver+0x31rnf78d2a60 804f6ba9 84b26c98 f78d2a80 84713fc8 nt!IopSynchronousCall+0xb7rnf78d2aa8 805843b5 00000000 84784530 00000001 nt!IopQueryDeviceRelations+0x45rnf78d2ac0 80587817 84713ee8 00000001 84a8d208 nt!PipEnumerateDevice+0x23rnf78d2d18 80587c56 84713ee8 00000001 00000000 nt!PipProcessDevNodeTree+0x21brnf78d2d4c 804f675d 00000003 805524c0 8055b47c nt!PiProcessReenumeration+0x60rnf78d2d74 8053500e 00000000 00000000 86fba8b8 nt!PipDeviceActionWorker+0x141rnf78d2dac 805c5d5e 00000000 00000000 00000000 nt!ExpWorkerThread+0x100rnf78d2ddc 805421f2 80534f0e 00000001 00000000 nt!PspSystemThreadStartup+0x34rn00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16rnrnrnSTACK_COMMAND: kbrnrnFOLLOWUP_IP: rnbhound5+1435rnf7710435 ?? ???rnrnSYMBOL_STACK_INDEX: 4rnrnSYMBOL_NAME: bhound5+1435rnrnFOLLOWUP_NAME: MachineOwnerrnrnMODULE_NAME: bhound5rnrnIMAGE_NAME: bhound5.sysrnrnDEBUG_FLR_IMAGE_TIMESTAMP: 3f8bbffdrnrnFAILURE_BUCKET_ID: 0xD1_bhound5+1435rnrnBUCKET_ID: 0xD1_bhound5+1435rnrnFollowup: MachineOwnerrn---------rnrn

高手进来帮帮忙,XPSP3 BSOD 8E Dump File analysis

11-04

新学windbg,分析Dump File,遇到了问题。请求帮忙rnLoading Dump File [F:\WDBG\Dmp\Mini103009-01.dmp]rnMini Kernel Dump File: Only registers and stack trace are availablernrnSymbol search path is: srv*d:\Symbols\XPSP3*http://msdl.microsoft.com/download/symbols;d:\Symbols\XPSP3rnExecutable search path is: rnWindows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatiblernProduct: WinNt, suite: TerminalServer SingleUserTSrnBuilt by: 2600.xpsp.080413-2111rnMachine Name:rnKernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720rnDebug session time: Fri Oct 30 19:20:37.718 2009 (GMT+8)rnSystem Uptime: 0 days 0:00:28.421rnLoading Kernel Symbolsrn...............................................................rn.........................rnLoading User SymbolsrnLoading unloaded module listrn.........rn*******************************************************************************rn* *rn* Bugcheck Analysis *rn* *rn*******************************************************************************rnrnUse !analyze -v to get detailed debugging information.rnrnBugCheck 1000008E, c0000047, 804fcf34, f723a8d8, 0rnrnProbably caused by : ntkrpamp.exe ( nt!KeReleaseSemaphore+3a )rnrnFollowup: MachineOwnerrn---------rnrn1: kd> !analyze -vrn*******************************************************************************rn* *rn* Bugcheck Analysis *rn* *rn*******************************************************************************rnrnKERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)rnThis is a very common bugcheck. Usually the exception address pinpointsrnthe driver/function that caused the problem. Always note this addressrnas well as the link date of the driver/image that contains this address.rnSome common problems are exception code 0x80000003. This means a hardrncoded breakpoint or assertion was hit, but this system was bootedrn/NODEBUG. This is not supposed to happen as developers should never havernhardcoded breakpoints in retail code, but ...rnIf this happens, make sure a debugger gets connected, and thernsystem is booted /DEBUG. This will let us see why this breakpoint isrnhappening.rnArguments:rnArg1: c0000047, The exception code that was not handledrnArg2: 804fcf34, The address that the exception occurred atrnArg3: f723a8d8, Trap FramernArg4: 00000000rnrnDebugging Details:rn------------------rnrnrnEXCEPTION_CODE: (NTSTATUS) 0xc0000047 - rnrnFAULTING_IP: rnnt!KeReleaseSemaphore+3arn804fcf34 85db test ebx,ebxrnrnTRAP_FRAME: f723a8d8 -- (.trap 0xfffffffff723a8d8)rnESP EDITED! New esp=f723ac88rnErrCode = 00000000rneax=00000000 ebx=00000001 ecx=00000000 edx=00000000 esi=85a1c994 edi=00000002rneip=804fcf34 esp=f723a94c ebp=f723ac9c iopl=0 nv up ei pl zr na pe ncrncs=0000 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000246rnnt!KeReleaseSemaphore+0x3a:rn804fcf34 85db test ebx,ebxrnResetting default scopernrnCUSTOMER_CRASH_COUNT: 1rnrnDEFAULT_BUCKET_ID: DRIVER_FAULTrnrnBUGCHECK_STR: 0x8ErnrnPROCESS_NAME: svchost.exernrnLAST_CONTROL_TRANSFER: from 805a625f to 804fcf34rnrnSTACK_TEXT: rnf723ac9c 805a625f 85a1c994 00000001 00000001 nt!KeReleaseSemaphore+0x3arnf723ad48 8054161c 00000108 00a7ff74 00a7fe38 nt!NtReplyWaitReceivePortEx+0x3bfrnf723ad48 7c90e4f4 00000108 00a7ff74 00a7fe38 nt!KiFastCallEntry+0xfcrnWARNING: Frame IP not in any known module. Following frames may be wrong.rn00a7ff80 00000000 00000000 00000000 00000000 0x7c90e4f4rnrnrnSTACK_COMMAND: kbrnrnFOLLOWUP_IP: rnnt!KeReleaseSemaphore+3arn804fcf34 85db test ebx,ebxrnrnSYMBOL_STACK_INDEX: 0rnrnSYMBOL_NAME: nt!KeReleaseSemaphore+3arnrnFOLLOWUP_NAME: MachineOwnerrnrnMODULE_NAME: ntrnrnIMAGE_NAME: ntkrpamp.exernrnDEBUG_FLR_IMAGE_TIMESTAMP: 4802516arnrnFAILURE_BUCKET_ID: 0x8E_nt!KeReleaseSemaphore+3arnrnBUCKET_ID: 0x8E_nt!KeReleaseSemaphore+3arnrnFollowup: MachineOwnerrn---------rnrn1: kd> uf nt!KeReleaseSemaphorernnt!KeReleaseSemaphore:rn804fcefa 8bff mov edi,edirn804fcefc 55 push ebprn804fcefd 8bec mov ebp,esprn804fceff 51 push ecxrn804fcf00 53 push ebxrn804fcf01 56 push esirn804fcf02 57 push edirn804fcf03 33c9 xor ecx,ecxrn804fcf05 ff1588804d80 call dword ptr [nt!_imp_KeAcquireQueuedSpinLockRaiseToSynch (804d8088)]rn804fcf0b 8b7508 mov esi,dword ptr [ebp+8]rn804fcf0e 8b5e04 mov ebx,dword ptr [esi+4]rn804fcf11 8ac8 mov cl,alrn804fcf13 8b4510 mov eax,dword ptr [ebp+10h]rn804fcf16 8d3c03 lea edi,[ebx+eax]rn804fcf19 3b7e10 cmp edi,dword ptr [esi+10h]rn804fcf1c 884dff mov byte ptr [ebp-1],clrn804fcf1f 7f04 jg nt!KeReleaseSemaphore+0x2b (804fcf25)rnrnnt!KeReleaseSemaphore+0x27:rn804fcf21 3bfb cmp edi,ebxrn804fcf23 7d0f jge nt!KeReleaseSemaphore+0x3a (804fcf34)rnrnnt!KeReleaseSemaphore+0x2b:rn[color=#FF0000]804fcf25 e86e890400 call nt!KiUnlockDispatcherDatabase (80545898)rn804fcf2a 68470000c0 push 0C0000047hrn804fcf2f e8d8a00400 call nt!ExRaiseStatus (8054700c)[/color]nt!KeReleaseSemaphore+0x3a:rn804fcf34 85db test ebx,ebxrn804fcf36 897e04 mov dword ptr [esi+4],edirn804fcf39 7511 jne nt!KeReleaseSemaphore+0x52 (804fcf4c)rn......rn1: kd> uf nt!ExRaiseStatusrnFlow analysis was incomplete, some code may be missingrnnt!ExRaiseStatus:rn8054700c 55 push ebprn8054700d 8bec mov ebp,esprn8054700f 9c pushfdrn80547010 81ec20030000 sub esp,320hrn80547016 8985dcfdffff mov dword ptr [ebp-224h],eaxrn8054701c 898dd8fdffff mov dword ptr [ebp-228h],ecxrn80547022 8d852cfdffff lea eax,[ebp-2D4h]rn80547028 8b4d04 mov ecx,dword ptr [ebp+4]rn8054702b 8988b8000000 mov dword ptr [eax+0B8h],ecxrn80547031 8998a4000000 mov dword ptr [eax+0A4h],ebxrn80547037 8990a8000000 mov dword ptr [eax+0A8h],edxrn8054703d 89b0a0000000 mov dword ptr [eax+0A0h],esirn80547043 89b89c000000 mov dword ptr [eax+9Ch],edirn80547049 8d4d08 lea ecx,[ebp+8]rn8054704c 8988c4000000 mov dword ptr [eax+0C4h],ecxrn80547052 8b4d00 mov ecx,dword ptr [ebp]rn80547055 8988b4000000 mov dword ptr [eax+0B4h],ecxrn8054705b 8b4dfc mov ecx,dword ptr [ebp-4]rn8054705e 8988c0000000 mov dword ptr [eax+0C0h],ecxrn80547064 8c88bc000000 mov word ptr [eax+0BCh],csrn8054706a 8c9898000000 mov word ptr [eax+98h],dsrn80547070 8c8094000000 mov word ptr [eax+94h],esrn80547076 8ca090000000 mov word ptr [eax+90h],fsrn8054707c 8ca88c000000 mov word ptr [eax+8Ch],gsrn80547082 8c90c8000000 mov word ptr [eax+0C8h],ssrn80547088 c70007000100 mov dword ptr [eax],10007hrn8054708e 8d85dcfcffff lea eax,[ebp-324h]rn80547094 8b4d04 mov ecx,dword ptr [ebp+4]rn80547097 89480c mov dword ptr [eax+0Ch],ecxrn8054709a 8b4d08 mov ecx,dword ptr [ebp+8]rn8054709d 8908 mov dword ptr [eax],ecxrn8054709f c7401000000000 mov dword ptr [eax+10h],0rn805470a6 c7400800000000 mov dword ptr [eax+8],0rn805470ad c7400401000000 mov dword ptr [eax+4],1rn805470b4 8d8d2cfdffff lea ecx,[ebp-2D4h]rn805470ba 51 push ecxrn805470bb 50 push eaxrn805470bc e8bd9efeff call nt!RtlDispatchException (80530f7e)rn805470c1 8d8d2cfdffff lea ecx,[ebp-2D4h]rn805470c7 8d85dcfcffff lea eax,[ebp-324h]rn805470cd 6a01 push 1rn805470cf 51 push ecxrn805470d0 50 push eaxrn805470d1 e87a9afbff call nt!ZwRaiseException (80500b50)rn805470d6 50 push eaxrn805470d7 e830ffffff call nt!ExRaiseStatus (8054700c)rn805470dc 0000 add byte ptr [eax],alrn805470de 0000 add byte ptr [eax],alrn805470e0 0000 add byte ptr [eax],alrn1.我查了DDK文档,发现C0000047是STATUS_SEMAPHORE_EXCEEDED,不理解是这个数值怎么来的,在nt!KiUnlockDispatcherDatabase 之后怎么就出来了这个值rn2.nt!ExRaiseStatus 是处理这个C0000047 exception的吗?是不是出错就在这个函数?rn3.新手学习Windbg,应该需要些什么背景知识呢?需要学习操作系统原理,驱动开发原理吗?rnrnrn

没有更多推荐了,返回首页

私密
私密原因:
请选择设置私密原因
  • 广告
  • 抄袭
  • 版权
  • 政治
  • 色情
  • 无意义
  • 其他
其他原因:
120
出错啦
系统繁忙,请稍后再试