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

mie

 
 
 

日志

 
 

蓝屏: PAGE_FAULT_IN_NONPAGED_AREA  

2011-01-09 16:55:59|  分类: 驱动 |  标签: |举报 |字号 订阅

  下载LOFTER 我的照片书  |
*******************************************************************************
*                                                                             *
*                        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: 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:
------------------

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


*************************************************************************
***                                                                   ***
***                                                                   ***
***    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:  CODE_CORRUPTION

BUGCHECK_STR:  0x50

LAST_CONTROL_TRANSFER:  from 80a4aa8a to 80a4b1f7

FAILED_INSTRUCTION_ADDRESS:
+ffffffffffffffff
ffffffff ??              ???

STACK_TEXT:  
f6e1594c 80a4aa8a badb0d00 80010031 00000000 hal!HalpDispatchInterrupt+0xcf
f6e15a08 bf85154a 00000003 81e3fc28 00000001 hal!KfLowerIrql+0x12
f6e159d4 80827b42 80827822 e1a23008 00000000 win32k!xxxMsgWaitForMultipleObjects+0xc5
WARNING: Frame IP not in any known module. Following frames may be wrong.
f6e15a08 bf85154a 00000003 81e3fc28 00000001 0x80827b42
f6e15a5c bf82604f 00000002 81e3fc28 bf811313 win32k!xxxMsgWaitForMultipleObjects+0xc5
f6e15d30 bf829254 bf9b30e0 00000001 f6e15d54 win32k!xxxDesktopThread+0x346
f6e15d40 bf87f76c bf9b30e0 f6e15d64 0071fff4 win32k!xxxCreateSystemThreads+0x6a
f6e15d54 80882fa8 00000000 00000022 00000000 win32k!NtUserCallOneParam+0x23
f6e15d64 7c95ed53 badb0d00 0071ffec 00000000 0x80882fa8
f6e15d68 badb0d00 0071ffec 00000000 00000000 ntdll!KiFastSystemCall+0x3
00000000 f000ff53 f000e2c3 f000ff53 f000ff53 0xbadb0d00
00000000 00000000 f000e2c3 f000ff53 f000ff53 0xf000ff53


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !hal


    80a4b1eb-80a4b1f2  8 bytes - hal!HalpDispatchInterrupt+c3
    [ fa 89 35 80 00 fe ff 8b:54 02 00 00 f0 05 00 00 ]
8 errors : !hal (80a4b1eb-80a4b1f2)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

Followup: memory_corruption
---------
//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

HAL(硬件抽象层)都出问题了。悲惨,

//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
进程信息:
PROCESS 81e36020  SessionId: 0  Cid: 01ec    Peb: 7ffd7000  ParentCid: 018c
    DirBase: 16065040  ObjectTable: e16b0458  HandleCount: 397.
    Image: csrss.exe
    VadRoot 81d1d120 Vads 105 Clone 0 Private 331. Modified 754. Locked 0.
    DeviceMap e1000058
    Token                             e155fab0
    ElapsedTime                       00:10:05.244
    UserTime                          00:00:00.000
    KernelTime                        00:00:00.437
    QuotaPoolUsage[PagedPool]         91940
    QuotaPoolUsage[NonPagedPool]      6616
    Working Set Sizes (now,min,max)  (1613, 50, 345) (6452KB, 200KB, 1380KB)
    PeakWorkingSetSize                1625
    VirtualSize                       41 Mb
    PeakVirtualSize                   41 Mb
    PageFaultCount                    3368
    MemoryPriority                    BACKGROUND
    BasePriority                      13
    CommitCharge                      412

        THREAD 81e325e8  Cid 01ec.01fc  Teb: 7ffde000 Win32Thread: e1b87c10 WAIT: (Unknown) UserMode Alertable
            81e392d0  SynchronizationEvent
            81e39330  SynchronizationEvent
            81e39300  SynchronizationEvent

        THREAD 81e2b900  Cid 01ec.0208  Teb: 7ffdd000 Win32Thread: e179fcd8 WAIT: (Unknown) UserMode Non-Alertable
            81e34ac8  Semaphore Limit 0x7fffffff

        THREAD 81e29db0  Cid 01ec.020c  Teb: 7ffdc000 Win32Thread: 00000000 WAIT: (Unknown) UserMode Non-Alertable
            81e2b8c8  Semaphore Limit 0x7fffffff

        THREAD 81e3c880  Cid 01ec.0218  Teb: 7ffdb000 Win32Thread: e1762008 WAIT: (Unknown) UserMode Non-Alertable
            81e34ac8  Semaphore Limit 0x7fffffff

        THREAD 81e245c0  Cid 01ec.022c  Teb: 7ffda000 Win32Thread: e1a1cad8 READY
        THREAD 81e25a60  Cid 01ec.0230  Teb: 7ffd9000 Win32Thread: e1a23008 RUNNING on processor 0
        THREAD 81e0e020  Cid 01ec.0278  Teb: 7ffd8000 Win32Thread: e1b3c9a8 WAIT: (Unknown) UserMode Non-Alertable
            81e25dd8  SynchronizationEvent
            81e0efb0  SynchronizationEvent

        THREAD 81e0bb40  Cid 01ec.02a0  Teb: 7ffd6000 Win32Thread: e1bcab78 WAIT: (Unknown) UserMode Non-Alertable
            81e34ac8  Semaphore Limit 0x7fffffff

        THREAD 81d13260  Cid 01ec.00e4  Teb: 7ffd5000 Win32Thread: e1feb628 WAIT: (Unknown) UserMode Non-Alertable
            81e34ac8  Semaphore Limit 0x7fffffff

        THREAD 822e6db0  Cid 01ec.011c  Teb: 7ffd4000 Win32Thread: e20667d0 WAIT: (Unknown) UserMode Non-Alertable
            81c3c910  SynchronizationEvent

//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
  评论这张
 
阅读(2300)| 评论(0)
推荐 转载

历史上的今天

在LOFTER的更多文章

评论

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

页脚

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