我们

  • 博客介绍

易也博客是一个“合众博客”站点,所谓合众,是经过管理员批准的一众技术爱好者,在这个站点上用各自的账号发表博客。合众博客有别于传统的博客,一个人管理和统御站点的所有事务和内容——它的问题是,很少有人有这样旺盛的经历,把博客站点推向兴盛。

张佩是这个站点的首要管理员,所有新帐号都由他批准和建立。现在我们有四位作者,希望有越来越多的朋友参与。请主动找我。

在这个站点上发表文章,我们只有一个要求:技术干货!

  • 作者们
  1.  张佩,1982年生人,十数年经验的资深Windows内核程序员,《竹林蹊径》一书作者,喜爱编程和文章。现在Intel上海亚太研发中心的开源技术中心(OTC)工作。

myHead_ok个人简历LinkedIn
博客镜像CSDN

除了内核和调试,我也做过很多UI开发,擅长使用Win32和MFC,最近常使用第三方界面库JUCE。最近在学习DirectX 3D和OpenCL编程。

欢迎网友来小站访问,也希望、喜欢和网友互动。你们可以给我留言,也可以给我发送邮件:zhang.xiaopei在outlook.com (’在’=’@’)

  2.  罗冰,喜欢侦探小说、历史小说、漫画、足球….爱好太多,博而不精。误入编程领域,十数年未有明显建树,仍不改初衷,纯粹喜欢。现居南京,做嵌入式无线通讯相关产品。

Robin_Head_ok个人简历LinkedIn

       十多年编程经历,前5年主要开发语言是x86汇编和C,开发各类OptionRom。后5年涉及一些驱动开发和MFC以及UEFI编程,从此更多的精力用在了团队和公司管理上。然不忘初心,仍不停于在各技术领域钻研,其乐无穷。
近一年开始,对物联网相关产业极有兴趣,立志并着手进行中。
       有缘相识佩兄,邀我在此开博。诠才末学,不值方家一笑。希望和技术同好多多交流:luobing4365@163.com

384 total views, 3 views today

《我们》有16个想法

    1. 谢谢问起。板子没货了,打板对我而言是个负担。下半年起,很多人通过各种途径问CY001的情况,所以已决定再打一次板,再生产50片。12月下旬应可以看到。

  1. 无法完成签名,提示的是
    XXX.inf is failed to be signed, refer to log file.
    不过我也没有找到这个log文件在哪,大侠帮助一下小弟我否?

  2. >>> [Device Install (DiInstallDevice) – ROOT\UNKNOWN000]
    >>> Section start 2016/09/22 21:46:49.273
    cmd: “C:\Windows\system32\mmc.exe” /s C:\Windows\system32\devmgmt.msc
    dvi: {Plug and Play Service: Device Install for ROOT\UNKNOWN000}
    ump: Creating Install Process: DrvInst.exe 21:46:49.278
    ! ndv: Installing NULL driver!
    dvi: Set selected driver complete.
    dvi: {DIF_ALLOW_INSTALL} 21:46:49.322
    dvi: No class installer for ‘未知驱动程序软件程序包’
    dvi: No CoInstallers found
    dvi: Default installer: Enter 21:46:49.333
    dvi: Default installer: Exit
    dvi: {DIF_ALLOW_INSTALL – exit(0xe000020e)} 21:46:49.337
    dvi: {DIF_INSTALLDEVICE} 21:46:49.339
    dvi: No class installer for ‘未知驱动程序软件程序包’
    dvi: Default installer: Enter 21:46:49.350
    ! dvi: Installing NULL driver!
    ! dvi: A NULL driver installation is not allowed for this type of device!
    !!! dvi: Cleaning up failed installation (e0000219)
    !!! dvi: Default installer: failed!
    !!! dvi: Error 0xe0000219: The installation failed because a function driver was not specified for this device instance.
    dvi: {DIF_INSTALLDEVICE – exit(0xe0000219)} 21:46:49.366
    ump: Server install process exited with code 0xe0000219 21:46:49.377
    ump: {Plug and Play Service: Device Install exit(e0000219)}
    <<< Section end 2016/09/22 21:46:49.381
    <<< [Exit status: FAILURE(0xe0000219)]

    我是驱动初学者能不能帮我看看这是什么问题

    1. 这是因为找不到合适的驱动包。你的设备ID是ROOT\UNKNOWN000(奇怪),然后系统尝试寻找能应用的驱动时失败。

  3. Probably caused by : ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!5801A4BE820000 )

    Followup: MachineOwner
    ———

    1: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    KERNEL_SECURITY_CHECK_FAILURE (139)
    A kernel component has corrupted a critical data structure. The corruption
    could potentially allow a malicious user to gain control of this machine.
    Arguments:
    Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
    Arg2: ffffe1809a005f70, Address of the trap frame for the exception that caused the bugcheck
    Arg3: ffffe1809a005ec8, Address of the exception record for the exception that caused the bugcheck
    Arg4: 0000000000000000, Reserved

    Debugging Details:
    ——————

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    *** ***
    *** ***
    *** Either you specified an unqualified symbol, or your debugger ***
    *** doesn’t have full symbol information. Unqualified symbol ***
    *** resolution is turned off by default. Please either specify a ***
    *** fully qualified symbol module!symbolname, or enable resolution ***
    *** of unqualified symbols by typing “.symopt- 100”. Note that ***
    *** enabling unqualified symbol resolution with network symbol ***
    *** server shares in the symbol path may cause the debugger to ***
    *** appear to hang for long periods of time when an incorrect ***
    *** symbol name is typed or the network symbol server is down. ***
    *** ***
    *** For some commands 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: nt!_KPRCB ***
    *** ***
    *************************************************************************
    请问张老师这个问题怎么解决,我没法往下继续了,怎么提示symbols是错误的呢
    另外已将dmp文件上传,如有时间帮忙分析下吧,多谢了http://pan.baidu.com/s/1nvRPb3z

发表评论

电子邮件地址不会被公开。 必填项已用*标注