阅读:5296回复:2
PAGE_FAULT_IN_NONPAGED_AREA (50)
各位大牛们!看看小弟的调试信息!这个错到底该怎么改?有什么想法说一说!!谢谢!!
*** Fatal System Error: 0x00000050 (0x81CD98B8,0x00000000,0x804EF0D2,0x00000000) Break instruction exception - code 80000003 (first chance) A fatal system error has occurred. Debugger entered on first try; Bugcheck callbacks have not been invoked. A fatal system error has occurred. Connected to Windows XP 2600 x86 compatible target at (Tue Jan 19 21:51:26.359 2010 (GMT+8)), ptr64 FALSE Loading Kernel Symbols ............................................................... ................................................... Loading User Symbols ............................. Loading unloaded module list ............ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {81cd98b8, 0, 804ef0d2, 0} ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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: kernel32!pNlsUserInfo *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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: kernel32!pNlsUserInfo *** *** *** ************************************************************************* Probably caused by : crypt_file.sys ( crypt_file!SfWrite+2d5 ) Followup: MachineOwner --------- nt!RtlpBreakWithStatusInstruction: 80528bdc cc int 3 kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: 81cd98b8, memory referenced. Arg2: 00000000, value 0 = read operation, 1 = write operation. Arg3: 804ef0d2, If non-zero, the instruction address which referenced the bad memory address. Arg4: 00000000, (reserved) Debugging Details: ------------------ ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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: kernel32!pNlsUserInfo *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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: kernel32!pNlsUserInfo *** *** *** ************************************************************************* READ_ADDRESS: 81cd98b8 FAULTING_IP: nt!IoBuildPartialMdl+a6 804ef0d2 8b11 mov edx,dword ptr [ecx] MM_INTERNAL_CODE: 0 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: notepad.exe TRAP_FRAME: f75e0d00 -- (.trap 0xfffffffff75e0d00) ErrCode = 00000000 eax=ffc3824c ebx=81a5bee0 ecx=81cd98b8 edx=0007ec61 esi=00000007 edi=7ec61000 eip=804ef0d2 esp=f75e0d74 ebp=f75e0d7c iopl=0 nv up ei ng nz ac po cy cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010293 nt!IoBuildPartialMdl+0xa6: 804ef0d2 8b11 mov edx,dword ptr [ecx] ds:0023:81cd98b8=???????? Resetting default scope LAST_CONTROL_TRANSFER: from 804f8b9d to 80528bdc STACK_TEXT: f75e083c 804f8b9d 00000003 81cd98b8 00000000 nt!RtlpBreakWithStatusInstruction f75e0888 804f978a 00000003 00000000 c040e6c8 nt!KiBugCheckDebugBreak+0x19 f75e0c68 804f9cb5 00000050 81cd98b8 00000000 nt!KeBugCheck2+0x574 f75e0c88 8051dc4f 00000050 81cd98b8 00000000 nt!KeBugCheckEx+0x1b f75e0ce8 8054151c 00000000 81cd98b8 00000000 nt!MmAccessFault+0x8e7 f75e0ce8 804ef0d2 00000000 81cd98b8 00000000 nt!KiTrap0E+0xcc f75e0d7c f7f58e4c 0007ec61 81911ae8 00000000 nt!IoBuildPartialMdl+0xa6 f75e0dd4 f7f62748 81a5bee0 81a3fd28 819f7008 Fastfat!FatMultipleAsync+0xda f75e0ed0 f7f59e7e 81a5bee0 819f7008 e1241ba8 Fastfat!FatNonCachedIo+0x320 f75e1070 f7f4db9a 81a5bee0 819f7008 819f7008 Fastfat!FatCommonWrite+0xeca f75e10b4 804ef119 81a3fc30 819f7008 81bcabf0 Fastfat!FatFsdWrite+0xad f75e10c4 f97b53ca 819f7100 8190a688 f75e1140 nt!IopfCallDriver+0x31 f75e10d4 804ef119 81955020 819f7008 819f7124 sr!SrWrite+0xaa f75e10e4 f7573bf5 81993940 81a045a8 804ed43e nt!IopfCallDriver+0x31 f75e1140 804ef119 8190a688 819f7008 00000000 crypt_file!SfWrite+0x2d5 [e:\work\sfilter\sfilter.c @ 2606] f75e1150 804f0411 f75e118c f75e1324 00000000 nt!IopfCallDriver+0x31 f75e1164 8050d497 81993905 f75e118c f75e1220 nt!IoSynchronousPageWrite+0xaf f75e1248 8050de68 e144f000 e144f080 e144f080 nt!MiFlushSectionInternal+0x3bf f75e1284 804e48a2 00000000 e144f000 00000000 nt!MmFlushSection+0x1e0 f75e130c f7571580 00010000 00000000 00000000 nt!CcFlushCache+0x386 f75e1358 f7573223 81909310 f75e1394 f7571dca crypt_file!cfFileCacheClear_noif+0x1f0 [e:\work\crypt_file_2010-1-14\cf_file_irp.c @ 525] f75e13ec f7570503 8190a688 819db008 819db108 crypt_file!cfIrpCreatePre+0x363 [e:\work\crypt_file_2010-1-14\cf_create.c @ 393] f75e1418 f757a9bc 8190a688 81955020 8190a81c crypt_file!OnSfilterIrpPre+0x73 [e:\work\crypt_file_2010-1-14\cf_sfilter.c @ 76] f75e1484 804ef119 8190a688 819db008 819db008 crypt_file!SfCreate+0x1ec [e:\work\sfilter\sfilter.c @ 2330] f75e1494 80579616 81a92c38 819bc0ac f75e163c nt!IopfCallDriver+0x31 f75e1574 805b5cbc 81a92c50 00000000 819bc008 nt!IopParseDevice+0xa12 f75e15fc 805b2065 00000000 f75e163c 00000040 nt!ObpLookupObjectName+0x56a f75e1650 8056d1bf 00000000 00000000 f75e1701 nt!ObOpenObjectByName+0xeb f75e17d4 8053e638 0007eec8 0007eea0 0007eef4 nt!NtQueryAttributesFile+0xf1 f75e17d4 7c92e4f4 0007eec8 0007eea0 0007eef4 nt!KiFastCallEntry+0xf8 0007ee80 7c92d6fc 7c80b843 0007eec8 0007eea0 ntdll!KiFastSystemCallRet 0007ee84 7c80b843 0007eec8 0007eea0 0007f6cc ntdll!NtQueryAttributesFile+0xc 0007eef4 01002ab5 0100a900 00000001 00000000 kernel32!GetFileAttributesW+0x79 0007f6d0 01005134 0100a900 0100a900 00000000 NOTEPAD!SetTitle+0x60 0007f6fc 01002802 00160134 0100a900 001051b8 NOTEPAD!SaveFile+0x286 0007f92c 01003599 00000000 0007f9b0 01003429 NOTEPAD!CheckSave+0xf3 0007f948 77d18734 00160134 00000010 00000000 NOTEPAD!NPWndProc+0x170 0007f974 77d18816 01003429 00160134 00000010 USER32!InternalCallWinProc+0x28 0007f9dc 77d28ea0 00000000 01003429 00160134 USER32!UserCallWinProcCheckWow+0x150 0007fa30 77d28eec 005b4158 00000010 00000000 USER32!DispatchClientMessage+0xa3 0007fa58 7c92e453 0007fa68 00000018 005b4158 USER32!__fnDWORD+0x24 0007fa58 80500690 0007fa68 00000018 005b4158 ntdll!KiUserCallbackDispatcher+0x13 f75e1aa0 8059806d f75e1b5c f75e1b60 f75e1b30 nt!KiCallUserMode+0x4 f75e1afc bf813d96 00000002 f75e1b40 00000018 nt!KeUserModeCallback+0x87 f75e1b80 bf813f2c bc684158 00000010 00000000 win32k!SfnDWORD+0xa8 f75e1bc8 bf81411e 02684158 00000010 00000000 win32k!xxxSendMessageToClient+0x176 f75e1c14 bf80ecc1 bc684158 00000010 00000000 win32k!xxxSendMessageTimeout+0x1a6 f75e1c38 bf8542ec bc684158 00000010 00000000 win32k!xxxSendMessage+0x1b f75e1c74 bf80bb30 bc684158 0000f060 00f9038f win32k!xxxSysCommand+0x16e f75e1cd4 bf80ec87 bc684158 00000112 0000f060 win32k!xxxRealDefWindowProc+0xc97 f75e1cec bf820a6f bc684158 00000112 0000f060 win32k!xxxWrapRealDefWindowProc+0x16 f75e1d08 bf80eece bc684158 00000112 0000f060 win32k!NtUserfnNCDESTROY+0x27 f75e1d40 8053e638 00160134 00000112 0000f060 win32k!NtUserMessageCall+0xae f75e1d40 7c92e4f4 00160134 00000112 0000f060 nt!KiFastCallEntry+0xf8 0007fa58 7c92e453 0007fa68 00000018 005b4158 ntdll!KiFastSystemCallRet 0007fa7c 77d194be 77d28e0d 00160134 00000112 ntdll!KiUserCallbackDispatcher+0x13 0007fad0 77d28dd9 00160134 00000112 0000f060 USER32!NtUserMessageCall+0xc 0007faec 5adc3bc2 00160134 00000112 0000f060 USER32!RealDefWindowProcW+0x47 0007fb04 5addc7f6 0007fb30 00034800 0007fb64 UxTheme!DoMsgDefault+0x2d 0007fb14 5adc1ac7 00034800 0007fb30 00f9038f UxTheme!OnDwpSysCommand+0x3d 0007fb64 5adc1b3d 5addc7cb 00000000 0000f060 UxTheme!_ThemeDefWindowProc+0x13a 0007fb80 77d294ed 00160134 00000112 0000f060 UxTheme!ThemeDefWindowProcW+0x18 0007fbc8 010038c2 00160134 00000112 0000f060 USER32!DefWindowProcW+0x6b 0007fbf0 77d18734 00160134 00000112 0000f060 NOTEPAD!NPWndProc+0x499 0007fc1c 77d2bdf1 01003429 00160134 00000112 USER32!InternalCallWinProc+0x28 0007fc84 77d2927b 00000000 01003429 00160134 USER32!UserCallWinProcCheckWow+0xea 0007fcc0 77d292e3 005b4158 005b40d8 0000f060 USER32!SendMessageWorker+0x4a5 0007fce0 5ade8895 00160134 00000112 0000f060 USER32!SendMessageW+0x7f 0007fd04 5adc1ac7 00034800 0007fd20 00f9038f UxTheme!OnDwpNcLButtonDown+0xa8 0007fd54 5adc1b3d 5ade87ed 00000000 00000014 UxTheme!_ThemeDefWindowProc+0x13a 0007fd70 77d294ed 00160134 000000a1 00000014 UxTheme!ThemeDefWindowProcW+0x18 0007fdb8 010037dc 00160134 000000a1 00000014 USER32!DefWindowProcW+0x6b 0007fde0 77d18734 00160134 000000a1 00000014 NOTEPAD!NPWndProc+0x3b3 0007fe0c 77d18816 01003429 00160134 000000a1 USER32!InternalCallWinProc+0x28 0007fe74 77d189cd 00000000 01003429 00160134 USER32!UserCallWinProcCheckWow+0x150 STACK_COMMAND: kb FOLLOWUP_IP: crypt_file!SfWrite+2d5 [e:\work\sfilter\sfilter.c @ 2606] f7573bf5 8945f0 mov dword ptr [ebp-10h],eax FAULTING_SOURCE_CODE: 2602: if (NULL != (PSFILTER_DEVICE_EXTENSION) DeviceObject->DeviceExtension && 2603: NULL !=((PSFILTER_DEVICE_EXTENSION) DeviceObject->DeviceExtension)->AttachedToDeviceObject && 2604: NULL != Irp) 2605: { > 2606: status = IoCallDriver( ((PSFILTER_DEVICE_EXTENSION) DeviceObject->DeviceExtension)->AttachedToDeviceObject, Irp ); 2607: 2608: } 2609: else 2610: { 2611: ASSERT(FALSE); SYMBOL_STACK_INDEX: e SYMBOL_NAME: crypt_file!SfWrite+2d5 FOLLOWUP_NAME: MachineOwner MODULE_NAME: crypt_file IMAGE_NAME: crypt_file.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4b558e43 FAILURE_BUCKET_ID: 0x50_crypt_file!SfWrite+2d5 BUCKET_ID: 0x50_crypt_file!SfWrite+2d5 Followup: MachineOwner --------- |
|
沙发#
发布于:2010-01-20 15:32
大家说说我该怎么分析,或者从什么地方入手解决这个蓝屏的问题?
|
|
板凳#
发布于:2010-03-12 13:32
偶 也遇到了,猜想是代码中对内存操作不规范,。。。
|
|