阅读:1161回复:3
为什么2003会引起这个问题呢?
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: f9ab4ef0 Arg3: 00000000 Arg4: 00000000 Debugging Details: ------------------ BUGCHECK_STR: 0x7f_8 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP PROCESS_NAME: svchost.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from f9614e8b to f961333a STACK_TEXT: f79e30ac f9614e8b f79e3668 e14761e0 00000002 Ntfs!_SEH_prolog+0x1a f79e3278 f9614894 f79e3668 81335af0 e14761e0 Ntfs!NtfsPrepareBuffers+0x25c f79e3454 f9615a2a f79e3668 81335af0 e14761e0 Ntfs!NtfsNonCachedIo+0x1ee f79e3658 f9615c84 f79e3668 81335af0 0108070a Ntfs!NtfsCommonWrite+0x18a0 f79e37d4 f9b29431 817c3020 81335af0 812799f8 Ntfs!NtfsFsdWrite+0x16a f79e47b8 804f24f3 817c3020 81335af0 00002000 file!HookWriteDispatch+0x191 [i:\file\hookfilesystem.c @ 290] f79e47c8 804facaa f79e4804 f79e4924 8173f518 nt!IofCallDriver+0x3f f79e47dc 804feb24 81279907 f79e4804 f79e4880 nt!IoSynchronousPageWrite+0xad f79e48b0 804fe308 e1506088 e150608c e150608c nt!MiFlushSectionInternal+0x3c4 f79e48f8 805253eb 8173f518 00000000 00000050 nt!MmFlushSection+0x22d f79e4990 805082e0 8120b680 000a9c7a f79e49cc nt!CcMapAndCopy+0x44f f79e4990 805082e0 8120b680 000a9c7a f79e49cc nt!CcCopyWrite+0x1c2 f79e4a1c f961a3a8 812799f8 f79e4bf4 00000050 nt!CcCopyWrite+0x1c2 f79e4c18 f9615c84 812703b8 81267008 f79e4cfe Ntfs!NtfsCommonWrite+0x1c8d f79e4c8c f9b29431 817c3020 81267008 81267008 Ntfs!NtfsFsdWrite+0x16a f79e5c70 804f24f3 817c3020 81267008 00000000 file!HookWriteDispatch+0x191 [i:\file\hookfilesystem.c @ 290] f79e5c80 80587208 81267150 00000000 81267008 nt!IofCallDriver+0x3f f79e5c94 8058c4a6 817c3020 81267008 812799f8 nt!IopSynchronousServiceTail+0x6f f79e5d38 804e1d24 00000304 00000000 00000000 nt!NtWriteFile+0x5e0 f79e5d38 7ffe0304 00000304 00000000 00000000 nt!KiSystemService+0xd0 00f0ff04 00000000 00000000 00000000 00000000 SharedUserData!SystemCallStub+0x4 STACK_COMMAND: kb FOLLOWUP_IP: file!HookWriteDispatch+191 [i:\file\hookfilesystem.c @ 290] f9b29431 898538f0ffff mov dword ptr [ebp-0FC8h],eax FAULTING_SOURCE_CODE: 286: IoCompleteRequest( Irp, IO_NO_INCREMENT ); 287: return STATUS_INVALID_DEVICE_REQUEST; 288: } 289: > 290: status=RealWriteDispatch(DeviceObject,Irp); 291: 292: return status; 293: } 294: 295: /* |
|
沙发#
发布于:2008-03-31 14:17
RealWriteDispatch 是 磁盘驱动 IRP_MJ_WRITE 的地址
|
|
板凳#
发布于:2008-03-31 14:31
HookWriteDispatch占用的栈太多了。
|
|
地板#
发布于:2008-03-31 14:37
那他允许 占用栈多少字节?
|
|