虚拟切片在病理实验教学中的运用,病理切片,病理学切片,病理切片制作过程,病理学组..
扫扫二维码，随身浏览文档
手机或平板扫扫即可继续访问
虚拟切片在病理实验教学中的运用
举报该文档为侵权文档。
举报该文档含有违规或不良信息。
反馈该文档无法正常浏览。
举报该文档为重复文档。
推荐理由：
将文档分享至：
分享完整地址
文档地址：
粘贴到BBS或博客
flash地址：
支持嵌入FLASH地址的网站使用
html代码：
&embed src='/DocinViewer--144.swf' width='100%' height='600' type=application/x-shockwave-flash ALLOWFULLSCREEN='true' ALLOWSCRIPTACCESS='always'&&/embed&
450px*300px480px*400px650px*490px
支持嵌入HTML代码的网站使用
您的内容已经提交成功
您所提交的内容需要审核后才能发布，请您等待！
3秒自动关闭窗口天极传媒：天极网全国分站
您现在的位置：
& &&现实转换为虚拟场景的装备
真实还是中二病？现实转换为虚拟场景的装备天极网游戏频道 11:01
　　天极游戏讯 无论是高端玩家也好，普通玩家也罢，大家肯定都设想过自己进入游戏中身临其境的场景。随着人类的进步，社会的发展，一款游戏仅仅是华丽的效果已经不足以满足玩家的需求了!要做到真实逼真才是王道。
　　近日，一支来自国外的技术小组就开发出了一种名为“Atlas”的仿真游戏系统，除了我们上面所提到的两款周边产品之外，系统中还包括一部iPhone。
　　工作时，三款设备通过无线方式彼此连接而又各司其职。其中，Oculus Rift眼镜负责视野控制，Razer Hydra电子枪则对应游戏中的枪支实施射击，而iPhone则主要是利用摄像头拍摄事先放在地上的坐标参照物和陀螺仪、加速计来判断玩家的行进状态。
　　目前，Atlas系统正在众筹平台Kickstarter网站中募集后续的研发资金，因此那些想要获得这么一套装备的玩家还需要耐心等待一段时间了。看到这些画面，你是否心动了呢？
　　　　　　　　　　扫描二维码 手游攻略随身带
（作者：王媛责任编辑：王媛）
欢迎在新浪微博上关注我们扫一扫!奖品周周抽
* 网友发言均非本站立场，本站不在评论栏推荐任何网店、经销商，谨防上当受骗！
数码整机手机软件
document.write(""); 上传我的文档
 下载
 收藏
该文档贡献者很忙，什么也没留下。
 下载此文档
正在努力加载中...
复杂网络上病毒传播的元胞自动机模拟
下载积分：50
内容提示：复杂网络上病毒传播的元胞自动机模拟.pdf
文档格式：PDF|
浏览次数：2|
上传日期： 10:42:34|
文档星级：
该用户还上传了这些文档
复杂网络上病毒传播的元胞自动机模拟.PDF
官方公共微信您的位置：>>>正文
3D的灾难：易致人身体不适产生“模拟疾病”
环球网科技
　　【环球网科技综合报道】据《每日邮报》9月29日报道，3D画面立体逼真，令人宛如置身现场，已经成为一股风潮。然而，有专家称iPhone、3D影片和电脑游戏的3D效果造成的不适现象，恐将成为21世纪最严重的&职业病&。
　　据报道，科技专家已分辨出传统动晕症(晕车、晕船、晕机)与这种称作&模拟疾病&(simulation&sickness)不适症状的差异，长时间盯着荧幕，与搭乘船只、汽车或飞机产生的不适并不相同。
　　专家还说，随着这些装置模仿我们周围环境的能力愈来愈强，这种情况只会日益恶化。
　　一般的动晕症是因为内耳感觉人体移动，但视觉并未产生相同反应所导致。
　　而观看3D影像造成的不适却恰好相反，我们看见物体移动，并告诉大脑身体应该处于移动状态，但事实上我们却是站着或坐着不动。
　　报道说，刚刚下载IOS7新版本的iPhone用户，就已体会到这种不适。
　　苹果公司(Apple)搭载的操作系统在数位显示器上，使用了一种视差效果，这种设计是为了让手机画面看起来更加立体。
　　报道说，长期以来，众所周知能让画面&真实呈现&在使用者眼前的3D技术会导致头痛，原因是我们视线会自然聚焦在往前靠近的物体，但实际上，我们只是盯着一种平滑、不会移动的表面，眼睛被视觉效果愚弄而逐渐感到疲惫。
　　对科技迷来说，不幸的是这种问题并不会随着科技进步而有所改善。
　　事实上，科学家预期，3D显示器和模拟现实装置，模仿真实世界的能力只会愈来愈强。
　　这意味着我们的大脑可能更容易受骗，出现模拟疾病的不适将变得加频繁。(实习编辑：黄珊&审核：谭利娅)
责任编辑：李文瑶
请选择您浏览此新闻时的心情
24小时点击排行
12345678910
24小时跟帖排行
环球今日推荐安装VS2013后，Hyper -v 虚拟器 导致 上网就蓝屏，不是个案，是丑陋的遗传病，你何时能治好？何谈WP8开发？
故障现像：
主板：技喜 H77M
CPU：E3 1230 V2
显卡：华硕 560Ti
硬盘：三星 128G 830 Pro
注意：以套系统共20台，公司统一配置的，已经在Win 7, win 8 系统中好好的工作一年多没有任何问题
==========================
Win 8.1 Pro +update 1 (正版 刚出时优惠买的)
Visual studio 2013 (Update 1 更新与否与蓝屏没关系，因为我们试过，更新它与否照样蓝屏)
全新的系统，没有安装任何其它软件
----------------------------------------------------
首先安装 win 8.1 pro，安装完，打所有驱动，一切OK，然后，安装Visual studio 2013,安装完，重启，一切OK（Hyper -v这就自动安装完了）。
好了，问题来了，重启后进入系统，使用VS 2013 建立 windows phone 8.0的项目，并调试一切正常没有任何问题（Hyper -v也正常，无蓝屏无死机现象）。但是...........，这时使用IE浏览器（什么Firefox,Chrome,Safair等等浏览器都试了，不分什么浏览器的，蓝屏是硬道理，永远的蓝屏），使用不超过1分钟或左右，突然就蓝屏重启。（不管你是打开着VS2013还是关闭着VS2013，不管是你停止没停止 Hyper -V）,就是蓝屏，蓝屏，蓝屏，蓝屏...........
什么样，才能不蓝屏呢，只有
控制面板 --程序和功能--启动或关闭 Windows功能-------卸载 Hyper -V
这样彻底把 Hyper -v 卸载掉，重启，然后一切正常了，你怎么用都不蓝屏了，你用任何浏览器，用一天都不会有一次死机。
以上结果是三天内，安装不下20次win 8.1 及 update 1，折腾无数遍的结果
下面上 刚才 蓝屏时 的 Bump文件
下载地址如下：&&
想看的，这有一个Bump文件的内容
===================================
Microsoft (R) Windows Debugger Version 6.3. AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\JoingressOctverve\Desktop\0-01.dmp]
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 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 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff803` PsLoadedModuleList = 0xfffff803`
Debug session time: Sun Apr 13 18:13:14.781 2014 (UTC + 8:00)
System Uptime: 0 days 0:07:26.596
*********************************************************************
* 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 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
..........
************* Symbol Loading Error Summary **************
Module name
The system cannot find the file specified
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*** WARNING: Unable to verify timestamp for NETIO.SYS
*** ERROR: Module load completed but symbols could not be loaded for NETIO.SYS
*******************************************************************************
Bugcheck Analysis
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007F, {8, fffff8, fffff8, fffffd9}
***** 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
Type referenced: nt!_KPRCB
*************************************************************************
*************************************************************************
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
Type referenced: nt!KPRCB
*************************************************************************
*************************************************************************
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
Type referenced: nt!_KPRCB
*************************************************************************
*************************************************************************
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
Type referenced: nt!KPRCB
*************************************************************************
*************************************************************************
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
Type referenced: nt!_KPRCB
*************************************************************************
*************************************************************************
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
Type referenced: nt!_KPRCB
*************************************************************************
*************************************************************************
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
Type referenced: nt!_KPRCB
*************************************************************************
*************************************************************************
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
Type referenced: nt!_KPRCB
*************************************************************************
Probably caused by : NETIO.SYS ( NETIO+d5d9 )
Followup: MachineOwner
0: kd& Probably caused byProbably caused by!analyze -v
^ No runnable debuggees error in 'Probably caused byProbably caused by!analyze -v'
0: kd& !analyze -v
*******************************************************************************
Bugcheck Analysis
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).
The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
kb will then show the corrected stack.
Arguments:
Arg1: 0008, EXCEPTION_DOUBLE_FAULT
Arg2: fffff8
Arg3: fffff8
Arg4: fffffd9
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
Type referenced: nt!_KPRCB
*************************************************************************
*************************************************************************
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
Type referenced: nt!KPRCB
*************************************************************************
*************************************************************************
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
Type referenced: nt!_KPRCB
*************************************************************************
*************************************************************************
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
Type referenced: nt!KPRCB
*************************************************************************
*************************************************************************
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
Type referenced: nt!_KPRCB
*************************************************************************
*************************************************************************
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
Type referenced: nt!_KPRCB
*************************************************************************
*************************************************************************
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
Type referenced: nt!_KPRCB
*************************************************************************
*************************************************************************
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
Type referenced: nt!_KPRCB
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
You can run '. .reload' to try to fix the symbol path and load symbols.
MODULE_NAME: NETIO
FAULTING_MODULE: fffff nt
DEBUG_FLR_IMAGE_TIMESTAMP:
DUMP_FILE_ATTRIBUTES: 0xc
Insufficient Dumpfile Size
Kernel Generated Triage Dump
BUGCHECK_STR:
CUSTOMER_CRASH_COUNT:
DEFAULT_BUCKET_ID:
WIN8_DRIVER_FAULT
CURRENT_IRQL:
ANALYSIS_VERSION: 6.3. (debuggers(dbg).2) amd64fre
LAST_CONTROL_TRANSFER:
from 0000 to fffffd9
STACK_TEXT:
fffff803`42ed3fe0 00000 : 00`00 00000 : NETIO+0xd5d9
STACK_COMMAND:
FOLLOWUP_IP:
NETIO+d5d9
fffff801`02c0d5d9 ff15d9ae0400
qword ptr [NETIO+0x584b8 (fffff801`02c584b8)]
SYMBOL_STACK_INDEX:
SYMBOL_NAME:
NETIO+d5d9
FOLLOWUP_NAME:
MachineOwner
IMAGE_NAME:
BUCKET_ID:
WRONG_SYMBOLS
FAILURE_BUCKET_ID:
WRONG_SYMBOLS
ANALYSIS_SOURCE:
FAILURE_ID_HASH_STRING:
km:wrong_symbols
FAILURE_ID_HASH:
{70b057e8-e7-ac72d4d365f8}
Followup: MachineOwner
而且我们在网上查了一些同样的问题，为什么微软的 Hyper - v 有如此 BUG,为什么经历了，6，7年了，还不解决？什么时候解决？
还有，只有在不安装Hyper 的情况下电脑才能上网，而要上网就不能用Hyper ??? 这让我们如何解决，有没有不用Hyper虚拟器来开发 WP 8.0/WP 8.1的方法，有其它虚拟器能与VS联手开发 WP 8吗，请高手指点，希望微软快正视问题吧
试了许多办法，也尝试过加一块虚拟网卡，然后就有两块网卡了，结果照样是蓝屏。
说明，Hyper -v 与
Qualcomm Atheros AR8151 PCI-E Gigabit Ethernet Controller (NDIS 6.30) 网卡（也就是技嘉主板上的网卡）冲突，希望微软尽快解决
请问在 删除 外部 虚拟交换机 之后打再打开IE 是不是就不会蓝屏呢？
我也有这个问题，解决不了，也不知道别的开发者怎么可以的
我在九月下旬装完vs2013 update2后也碰到了同样的问题，当时就搜到了楼主的这个贴子，也是没有办法妥善解决。不过经多次试验后发现每当我在Hyper-V已开启的前提下进行宽带连接后过几分钟就会蓝屏，如果电脑进行无线连接则不会，当时已经安装了所有驱动，设备管理器中也无显示警告的现象，所以驱动应该是安装的没问题的。后来为了方便上网就把Hyper-V功能关掉使用着，一直到现在。最近两天又不死心想看看wp8模拟器能不能起来，于是开了Hyper-V重启电脑，进行宽带连接，打开vs2013跑了下demo结果可以正常使用了，不会蓝屏！wp8模拟器先开始不能上网，因为我装过virtualbox的缘故于是就把virtualbox的虚拟网卡禁用了一下过会再恢复，wp8模拟器成功上网！一
说实话我不知道为什么到现在Hyper-V打开同时我使用了宽带连接它也能正常工作，我只能把我电脑目前的情况给大家说一下，看看能否帮助到大家。
系统: win8.1 pro, 64位
软件: vs2013 update2, virtualbox4.3.6 r91406
没法发图片，里面是几张网络连接相关的图片
/redir?resid=59645AFF12DAF0F7!198&authkey=!ANhCwi9ToquHhXo&ithint=folder%2cpng
Microsoft 正在进行一项网上调查，以了解您对 Technet 网站的意见。如果您选择参加，我们将会在您离开 Technet 网站时向您显示该网上调查。是否要参加？
<input type="hidden" id="hdnTrackerText" value="请不要关闭此窗口。谢谢！完成访问时，调查将显示在此处，所以请不要关闭此窗口。" />
不是 IT 专业人员？}