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

mie

 
 
 

日志

 
 

蓝屏BSOD: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)  

2011-01-09 17:47:02|  分类: 驱动 |  标签: |举报 |字号 订阅

  下载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: 01dfd3d1, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: e22818f0, 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                         ***
***                                                                   ***
*************************************************************************

WRITE_ADDRESS:  01dfd3d1

CURRENT_IRQL:  2

FAULTING_IP:
+ffffffffe22818f0
e22818f0 010417          add     dword ptr [edi+edx],eax

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  lsass.exe

TRAP_FRAME:  f797ab78 -- (.trap 0xfffffffff797ab78)
ErrCode = 00000002
eax=00000000 ebx=ffdff000 ecx=00000017 edx=80010031 esi=81e07ae0 edi=81ded3a0
eip=e22818f0 esp=f797abec ebp=81e1e020 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
e22818f0 010417          add     dword ptr [edi+edx],eax ds:0023:01dfd3d1=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 80969a30 to e22818f0

POSSIBLE_INVALID_CONTROL_TRANSFER:  from 80969a2b to 80876f98

STACK_TEXT:  
WARNING: Frame IP not in any known module. Following frames may be wrong.
f797abe8 80969a30 f797ac14 80930355 00000001 0xe22818f0
81e1e020 00000000 81e12e90 81e12e90 81e1e030 nt!SepPrivilegeCheck+0x8e


STACK_COMMAND:  .trap 0xfffffffff797ab78 ; kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  CPU_CALL_ERROR

Followup: MachineOwner
---------
 *** Possible invalid call from 80969a2b ( nt!SepPrivilegeCheck+0x89 )
 *** Expected target 80876f98 ( nt!ExReleaseResourceLite+0x0 )

///////////////////////////////////////////////////////////////////////////////////////////////////
进程信息:
kd> !process
PROCESS 81e1e020  SessionId: 0  Cid: 0268    Peb: 7ffd7000  ParentCid: 0210
    DirBase: 15da30a0  ObjectTable: e1b29a48  HandleCount: 339.
    Image: lsass.exe
    VadRoot 81e1d248 Vads 139 Clone 0 Private 636. Modified 25. Locked 1.
    DeviceMap e1000058
    Token                             e1b29ac0
    ElapsedTime                       00:44:00.956
    UserTime                          00:00:00.093
    KernelTime                        00:00:00.296
    QuotaPoolUsage[PagedPool]         76516
    QuotaPoolUsage[NonPagedPool]      11528
    Working Set Sizes (now,min,max)  (1740, 50, 345) (6960KB, 200KB, 1380KB)
    PeakWorkingSetSize                1746
    VirtualSize                       46 Mb
    PeakVirtualSize                   52 Mb
    PageFaultCount                    2098
    MemoryPriority                    BACKGROUND
    BasePriority                      9
    CommitCharge                      1364

        THREAD 81e4d518  Cid 0268.0280  Teb: 7ffde000 Win32Thread: 00000000 WAIT: (Unknown) UserMode Non-Alertable
            81e4d3c8  NotificationEvent

        THREAD 81e4c5a8  Cid 0268.0284  Teb: 7ffdd000 Win32Thread: 00000000 WAIT: (Unknown) UserMode Alertable
            81e4c620  NotificationTimer

        THREAD 81e4c2d8  Cid 0268.0288  Teb: 7ffdc000 Win32Thread: 00000000 WAIT: (Unknown) UserMode Non-Alertable
            81e24f60  QueueObject
            81e4c350  NotificationTimer

        THREAD 81e0a020  Cid 0268.028c  Teb: 7ffdb000 Win32Thread: 00000000 WAIT: (Unknown) UserMode Alertable
            81e4c1e0  NotificationTimer
            81e44020  Thread
            81e073f8  SynchronizationEvent
            81e055a0  SynchronizationEvent
            81e4a5e8  SynchronizationEvent
            81e4acd0  SynchronizationEvent
            81e482d0  SynchronizationEvent
            81e4c110  SynchronizationEvent
            81e4b910  SynchronizationEvent
            81e4b858  SynchronizationTimer
            81e45ea0  SynchronizationEvent
            81e473b8  SynchronizationEvent
            81e4cff0  SynchronizationEvent
            82952928  SynchronizationEvent
            8224de10  SynchronizationEvent
            81f1ce48  SynchronizationEvent
            81dc71e8  SynchronizationEvent

        THREAD 81e0ac28  Cid 0268.0290  Teb: 7ffda000 Win32Thread: 00000000 WAIT: (Unknown) UserMode Non-Alertable
            81e4c038  Semaphore Limit 0x7fffffff

        THREAD 81e4bdb0  Cid 0268.0294  Teb: 7ffd9000 Win32Thread: 00000000 WAIT: (Unknown) UserMode Non-Alertable
            81e0a6e8  SynchronizationEvent

        THREAD 81e08020  Cid 0268.02ac  Teb: 7ffd8000 Win32Thread: 00000000 WAIT: (Unknown) UserMode Alertable
            81e08098  NotificationTimer

        THREAD 81e45898  Cid 0268.02c0  Teb: 7ffd5000 Win32Thread: 00000000 WAIT: (Unknown) UserMode Non-Alertable
            81e4b640  QueueObject
            81e45910  NotificationTimer

        THREAD 81e44020  Cid 0268.02cc  Teb: 7ff9f000 Win32Thread: 00000000 WAIT: (Unknown) UserMode Non-Alertable
            81e45140  Semaphore Limit 0x7fffffff

        THREAD 81e07ae0  Cid 0268.02e4  Teb: 7ff99000 Win32Thread: e208ed98 RUNNING on processor 0
        THREAD 81e07168  Cid 0268.02ec  Teb: 7ff97000 Win32Thread: 00000000 WAIT: (Unknown) UserMode Non-Alertable
            81e07428  Semaphore Limit 0x7fffffff

        THREAD 81e06c88  Cid 0268.02f0  Teb: 7ff96000 Win32Thread: 00000000 WAIT: (Unknown) UserMode Non-Alertable
            81e07060  Semaphore Limit 0x7fffffff

        THREAD 81e059a0  Cid 0268.02f4  Teb: 7ff95000 Win32Thread: 00000000 WAIT: (Unknown) UserMode Non-Alertable
            81e4b640  QueueObject
            81e05a18  NotificationTimer

        THREAD 81e064a0  Cid 0268.02fc  Teb: 7ff93000 Win32Thread: 00000000 WAIT: (Unknown) UserMode Non-Alertable
            81e06ee8  Semaphore Limit 0x7fffffff

        THREAD 81e04d00  Cid 0268.0304  Teb: 7ff92000 Win32Thread: 00000000 WAIT: (Unknown) UserMode Non-Alertable
            81e058a0  Semaphore Limit 0x7fffffff

        THREAD 81e46db0  Cid 0268.0320  Teb: 7ff90000 Win32Thread: 00000000 WAIT: (Unknown) UserMode Non-Alertable
            81e45860  Semaphore Limit 0x7fffffff

        THREAD 81db37a0  Cid 0268.0574  Teb: 7ff94000 Win32Thread: 00000000 WAIT: (Unknown) UserMode Non-Alertable
            81e45540  Semaphore Limit 0x7fffffff

        THREAD 81d43770  Cid 0268.01f0  Teb: 7ffd6000 Win32Thread: 00000000 WAIT: (Unknown) UserMode Non-Alertable
            821629f8  NotificationEvent
            81e35560  NotificationEvent

        THREAD 81ded3a0  Cid 0268.0318  Teb: 7ffd4000 Win32Thread: 00000000 READY
  评论这张
 
阅读(2620)| 评论(0)
推荐 转载

历史上的今天

在LOFTER的更多文章

评论

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

页脚

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