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

mie

 
 
 

日志

 
 

BSOD蓝屏:DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)  

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

  下载LOFTER 我的照片书  |
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 00000000, address which referenced memory

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:  00000000

CURRENT_IRQL:  2

FAULTING_IP:
+0
00000000 ??              ???

PROCESS_NAME:  lsass.exe

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xD1

TRAP_FRAME:  f69e5c10 -- (.trap 0xfffffffff69e5c10)
ErrCode = 00000000
eax=00000000 ebx=ffdff000 ecx=00000010 edx=80010031 esi=81e11db0 edi=81e12830
eip=00000000 esp=f69e5c84 ebp=81e1d020 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
00000000 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from 808253e7 to 8086c81c

FAILED_INSTRUCTION_ADDRESS:
+0
00000000 ??              ???

STACK_TEXT:  
f69e580c 808253e7 00000003 00000000 00000000 nt!RtlpBreakWithStatusInstruction
f69e5858 808262bc 00000003 00000000 00000000 nt!KiBugCheckDebugBreak+0x19
f69e5bf0 80886099 0000000a 00000000 00000002 nt!KeBugCheck2+0x5b2
f69e5bf0 00000000 0000000a 00000000 00000002 nt!KiTrap0E+0x2a1
WARNING: Frame IP not in any known module. Following frames may be wrong.
f69e5c80 00000000 8089f470 0000023e 829e0660 0x0


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!KiTrap0E+2a1
80886099 833d80f3898000  cmp     dword ptr [nt!KiFreezeFlag (8089f380)],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiTrap0E+2a1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlpa.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  42435b14

FAILURE_BUCKET_ID:  0xD1_CODE_AV_NULL_IP_nt!KiTrap0E+2a1

BUCKET_ID:  0xD1_CODE_AV_NULL_IP_nt!KiTrap0E+2a1

Followup: MachineOwner
---------

怎么会读写了地址0x00000000?!
  评论这张
 
阅读(2130)| 评论(0)
推荐 转载

历史上的今天

在LOFTER的更多文章

评论

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

页脚

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