注册 登录  
 加关注
   显示下一条  |  关闭
温馨提示!由于新浪微博认证机制调整,您的新浪微博帐号绑定已过期,请重新绑定!立即重新绑定新浪微博》  |  关闭

mie

 
 
 

日志

 
 

PAGE_FAULT_IN_NONPAGED_AREA (50)  

2011-01-10 16:21:16|  分类: 驱动 |  标签: |举报 |字号 订阅

  下载LOFTER 我的照片书  |
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: ffffffff, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: ffffffff, 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:  ffffffff

FAULTING_IP:
+ffffffffffffffff
ffffffff ??              ???

MM_INTERNAL_CODE:  0

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  services.exe

CURRENT_IRQL:  1

TRAP_FRAME:  f78b2c88 -- (.trap 0xfffffffff78b2c88)
ErrCode = 00000000
eax=00000000 ebx=0070fa58 ecx=809412b8 edx=00000000 esi=00000000 edi=f78b2d1c
eip=ffffffff esp=f78b2cfc ebp=81ddb402 iopl=0         nv up ei pl nz na po cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010203
ffffffff ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from 808253e7 to 8086c81c

FAILED_INSTRUCTION_ADDRESS:
+ffffffffffffffff
ffffffff ??              ???

STACK_TEXT:  
f78b27f8 808253e7 00000003 ffffffff 00000000 nt!RtlpBreakWithStatusInstruction
f78b2844 808262bc 00000003 c07ffff8 81ddb4a0 nt!KiBugCheckDebugBreak+0x19
f78b2bdc 80826659 00000050 ffffffff 00000000 nt!KeBugCheck2+0x5b2
f78b2bfc 8085a01b 00000050 ffffffff 00000000 nt!KeBugCheckEx+0x1b
f78b2c70 80885ed0 00000000 ffffffff 00000000 nt!MmAccessFault+0xa91
f78b2c70 ffffffff 00000000 ffffffff 00000000 nt!KiTrap0E+0xd8
WARNING: Frame IP not in any known module. Following frames may be wrong.
f78b2cf8 81d921b0 00000000 8289e3a8 f78b2d30 0xffffffff
f78b2d08 f70e4310 820e3568 00000000 f70e431e 0x81d921b0
f78b2d30 f78b2dcc 00000003 00000103 8289e3a8 NDIS!ndisMSyncQueryInformationComplete+0x15d
f78b2d58 f70e0169 820e34a0 8289e3a8 81d92150 0xf78b2dcc
f78b2d74 f70e45a2 820e34a0 81d92150 81c40b60 NDIS!ndisMRequest+0x113
f78b2d98 f70d002a 81c40b48 00000000 81c4bb50 NDIS!ndisMRundownRequests+0x32
f78b2dac 8094095c 81c40b50 00000000 00000000 NDIS!ndisWorkerThread+0x74
f78b2ddc 8088757a f70d0005 81c40b50 00000000 nt!PspSystemThreadStartup+0x2e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP:
NDIS!ndisMSyncQueryInformationComplete+15d
f70e4310 8d4e30          lea     ecx,[esi+30h]

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  NDIS!ndisMSyncQueryInformationComplete+15d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NDIS

IMAGE_NAME:  NDIS.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  42435dfa

FAILURE_BUCKET_ID:  0x50_CODE_AV_BAD_IP_NDIS!ndisMSyncQueryInformationComplete+15d

BUCKET_ID:  0x50_CODE_AV_BAD_IP_NDIS!ndisMSyncQueryInformationComplete+15d

Followup: MachineOwner
---------
  评论这张
 
阅读(2449)| 评论(1)
推荐 转载

历史上的今天

在LOFTER的更多文章

评论

<#--最新日志,群博日志--> <#--推荐日志--> <#--引用记录--> <#--博主推荐--> <#--随机阅读--> <#--首页推荐--> <#--历史上的今天--> <#--被推荐日志--> <#--上一篇,下一篇--> <#-- 热度 --> <#-- 网易新闻广告 --> <#--右边模块结构--> <#--评论模块结构--> <#--引用模块结构--> <#--博主发起的投票-->
 
 
 
 
 
 
 
 
 
 
 
 
 
 

页脚

网易公司版权所有 ©1997-2016