【水区高人多】 win8蓝屏求救! _VimIy微民网_让世界倾听微民的声音!

VimIy微民网，让世界倾听微民的声音！设为首页 | 加入收藏 | 网站地图

主页头条大杂烩图片贴吧视频音乐微博精选创意生活恶搞财经游戏体育健康男人女人购物街

当前位置：主页 > 恶搞 >

【水区高人多】 win8蓝屏求救!

整理时间:2013-02-07 00:37 来源:www.vimiy.com 作者:编辑点击:次

【楼主】(12280945)2013-02-04 22:49

» win8蓝屏求救!
    换了新电脑win8的,之后偶尔蓝屏一下,今天一下子蓝屏了3次错误信息为DRIVER_IRQL_NOT_LESS_OR_EQUAL.....
    用WinDbg看了下蓝屏记录最近两次分别是:
     Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: * Invalid *
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path. *
    * Use .symfix to have the debugger choose a symbol path. *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ********
    Executable search path is:
    *
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *******************************************************************
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    * WARNING: Unable to verify timestamp for ntoskrnl.exe
    * ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 9200 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    Machine Name:
    Kernel base = 0xfffff800`dc086000 PsLoadedModuleList = 0xfffff800`dc350a80
    Debug session time: Mon Feb 4 22:13:27.174 2013 (GMT+8)
    System Uptime: 0 days 10:06:28.049
    *******************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *******************************************************************
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    * WARNING: Unable to verify timestamp for ntoskrnl.exe
    * ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .....................................
    Loading User Symbols
    Loading unloaded module list
    ...........
    ERROR: FindPlugIns 8007007b
    *****************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *****************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {a, 2, 0, fffff880051d5074}

    Unable to load image \SystemRoot\system32\DRIVERS\raspppoe.sys, Win32 error 0n2
    * WARNING: Unable to verify timestamp for raspppoe.sys
    * ERROR: Module load completed but symbols could not be loaded for raspppoe.sys
    Unable to load image \SystemRoot\system32\DRIVERS\wfplwfs.sys, Win32 error 0n2
    * WARNING: Unable to verify timestamp for wfplwfs.sys
    * ERROR: Module load completed but symbols could not be loaded for wfplwfs.sys
    Unable to load image \SystemRoot\system32\drivers\NETIO.SYS, Win32 error 0n2
    * WARNING: Unable to verify timestamp for NETIO.SYS
    * ERROR: Module load completed but symbols could not be loaded for NETIO.SYS
    Unable to load image \SystemRoot\system32\DRIVERS\klim6.sys, Win32 error 0n2
    * WARNING: Unable to verify timestamp for klim6.sys
    * ERROR: Module load completed but symbols could not be loaded for klim6.sys
    * Kernel symbols are WRONG. Please fix symbols to do analysis.

    *********************************************************************
    * *
    * *
    * 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: nt!_KPRCB *
    * *
    *
    *
    * *
    * *
    * 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: nt!KPRCB *
    * *
    *
    *
    * *
    * *
    * 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: nt!_KPRCB *
    * *
    *
    *
    * *
    * *
    * 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: nt!KPRCB *
    * *
    *
    *
    * *
    * *
    * 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: nt!_KPRCB *
    * *
    *
    *
    * *
    * *
    * 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: nt!_KPRCB *
    * *
    *
    *
    * *
    * *
    * 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: nt!_KPRCB *
    * *
    *
    *
    * *
    * *
    * 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: nt!_KPRCB *
    * *
    ***
    *
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *
    *
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *******************************************************************
    Probably caused by : raspppoe.sys ( raspppoe+e074 )

    Followup: MachineOwner



    Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: * Invalid *
    **************************************************************************
    * Symbol loading may be unreliable without a symbol search path. *
    * Use .symfix to have the debugger choose a symbol path. *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ********
    Executable search path is:
    *
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *******************************************************************
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    * WARNING: Unable to verify timestamp for ntoskrnl.exe
    * ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 9200 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    Machine Name:
    Kernel base = 0xfffff803`03885000 PsLoadedModuleList = 0xfffff803`03b4fa80
    Debug session time: Mon Feb 4 10:52:51.496 2013 (GMT+8)
    System Uptime: 0 days 2:14:09.372
    *******************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *******************************************************************
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    * WARNING: Unable to verify timestamp for ntoskrnl.exe
    * ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .....................................
    Loading User Symbols
    Loading unloaded module list
    ........
    ERROR: FindPlugIns 8007007b
    *****************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *****************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {a, 2, 0, fffff88001dee074}

    Unable to load image \SystemRoot\system32\DRIVERS\raspppoe.sys, Win32 error 0n2
    * WARNING: Unable to verify timestamp for raspppoe.sys
    * ERROR: Module load completed but symbols could not be loaded for raspppoe.sys
    Unable to load image \SystemRoot\system32\drivers\NETIO.SYS, Win32 error 0n2
    * WARNING: Unable to verify timestamp for NETIO.SYS
    * ERROR: Module load completed but symbols could not be loaded for NETIO.SYS
    Unable to load image \SystemRoot\system32\DRIVERS\klim6.sys, Win32 error 0n2
    * WARNING: Unable to verify timestamp for klim6.sys
    * ERROR: Module load completed but symbols could not be loaded for klim6.sys
    * Kernel symbols are WRONG. Please fix symbols to do analysis.

    *********************************************************************
    * *
    * *
    * 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: nt!_KPRCB *
    * *
    *
    *
    * *
    * *
    * 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: nt!KPRCB *
    * *
    *
    *
    * *
    * *
    * 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: nt!_KPRCB *
    * *
    *
    *
    * *
    * *
    * 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: nt!KPRCB *
    * *
    *
    *
    * *
    * *
    * 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: nt!_KPRCB *
    * *
    *
    *
    * *
    * *
    * 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: nt!_KPRCB *
    * *
    *
    *
    * *
    * *
    * 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: nt!_KPRCB *
    * *
    *
    *
    * *
    * *
    * 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: nt!_KPRCB *
    * *
    ***
    *
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *
    *
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Probably caused by : raspppoe.sys ( raspppoe+e074 )

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




    新电脑感觉不是硬件问题吧,是不是软件冲突引起的? 我觉得貌似是卡巴斯基吧? 电脑盲什么都不懂,微民基友救我

网友评论(156471)2013-02-04 22:54

把卡巴斯基卸了看看

网友评论(12280945)2013-02-04 22:54

挽尊啊,快过年了 help!help!

网友评论(16158212)2013-02-04 23:00

    关键 Probably caused by : raspppoe.sys ( raspppoe+e074

    重新搞下网卡驱动什么的

网友评论(261164)2013-02-04 23:04

    我之前频繁死机，后来发现是chrome兼容性问题，换回firefox后基本不死机了。
    ----sent from my samsung GT-N7108,Android 4.1.1

网友评论(12280945)2013-02-04 23:09

    Reply to Reply Post by 歌 (2013-02-04 23:04)

    话说这几次我都是在用chrome的时候蓝屏的。。。可是chrome用了这么久，不愿意用别的啊这。。。我先试试。。

网友评论(1889573)2013-02-04 23:10

sfc /scannow

网友评论(10306552)2013-02-04 23:12

    从win7开始就没见过蓝屏了阿。。。
     发自我的 iPhone 4S, iPhone OS 6.1, NGAer 157

上一篇：老外在日本也有特权啊，(照片】童颜巨乳筱崎爱的巨乳被老外给盯上了【~转2CH】
下一篇：没有了

【精彩图集】

都说在浴霸下面拍照好看，是真的么？

都说在浴霸下面拍照好看，是真的么？

感性姐姐皮肤好白，御女中的极品。。

感性姐姐皮肤好白，御女中的极品。。

刘亦菲翻版，感觉比刘亦菲漂亮。

刘亦菲翻版，感觉比刘亦菲漂亮。

回眸一笑百媚生，屌丝心中永远的女神。

回眸一笑百媚生，屌丝心中永远的女神。

【热门视频】

女孩天生“男高音”潘倩倩《向天再借五百年》

女孩天生“男高音”潘倩倩《向天再借五百年

懒羊羊配音者：梁颖美女一枚

懒羊羊配音者：梁颖美女一枚

史上唱歌最好听的矿工——霍春宇

史上唱歌最好听的矿工——霍春宇

【魔术】魔术师刘谦春晚硬币穿玻璃魔术表演揭秘

【魔术】魔术师刘谦春晚硬币穿玻璃魔术表演

【相关文章】

关于网站 | 网站声明 | 用户反馈 | 合作伙伴 | 联系我们

Copyright © 2012年2月8日