最近玩暗黑3，各种蓝屏，发现自己的内存一条是1333一条1600，已经在京东买了1600的同型号换上了，也重装的系统，结果现在还是这样啊
微软（R）Windows调试版本6.12.0002.633 X86
版权所有（c）Microsoft公司。版权所有。
加载转储文件[C：\ WINDOWS \内存转储\ 060115-11013-01.dmp]
微型核心转储文件：只有登记和堆栈跟踪可用
符号搜索路径为：*** ***无效
************************************************** **************************
*符号负荷可能是不可靠的无符号搜索路径。 *
*使用.symfix有调试器选择一个符号路径。 *
*设置你的符号路径后，使用.reload的刷新符号位置。 *
************************************************** **************************
可执行搜索路径是：
************************************************** *******************
*符号无法加载，因为符号路径未初始化。 *
* *
*符号的路径可以设置：*
*使用_NT_SYMBOL_PATH环境变量。 *
*启动调试器时使用-y <symbol_path>参数。 *
*使用.sympath和.sympath + *
************************************************** *******************
无法加载图像的Ntoskrnl.exe，Win32错误0n2
***警告：无法验证时间戳的ntoskrnl.exe
***错误：模块加载完成，但符号不能为ntoskrnl.exe中加载
Windows 7的内核版本7601（服务包1）MP（4特效）免费x64的
产品：WINNT，浴室：的TerminalServer SingleUserTS
机器名称：
内核基= 0xfffff800`04e66000 PsLoadedModuleList = 0xfffff800`050ab890
调试会话时间：周一18年6月1日：48：26.167 2015年（UTC + 8:00）
系统正常运行时间：0天1：10：03.447
************************************************** *******************
*符号无法加载，因为符号路径未初始化。 *
* *
*符号的路径可以设置：*
*使用_NT_SYMBOL_PATH环境变量。 *
*启动调试器时使用-y <symbol_path>参数。 *
*使用.sympath和.sympath + *
************************************************** *******************
无法加载图像的Ntoskrnl.exe，Win32错误0n2
***警告：无法验证时间戳的ntoskrnl.exe
***错误：模块加载完成，但符号不能为ntoskrnl.exe中加载
加载内核符号
.................................................. .............
.................................................. ..............
...........................
加载用户符号
装载卸载模块列表
......
************************************************** *****************************
* *
*检测错误分析*
* *
************************************************** *****************************
使用！分析-v来获取详细的调试信息。
检测错误1A，{41790，fffffa800116c430，FFFF，0}
*****内核符号是错误的。请修正符号做分析。
************************************************** ***********************
*** ***
*** ***
***您的调试器不使用正确的符号***
*** ***
***为了使这个命令能够正常工作，你的符号路径***
***必须指向.PDB具有完整的类型信息的文件。 ***
*** ***
***某些.pdb文件（如公共操作系统符号）不***
***包含所需要的信息。联系组***
***如果需要此命令为您提供了这些符号***
***工作。 ***
*** ***
***类型引用：NT _KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
***您的调试器不使用正确的符号***
*** ***
***为了使这个命令能够正常工作，你的符号路径***
***必须指向.PDB具有完整的类型信息的文件。 ***
*** ***
***某些.pdb文件（如公共操作系统符号）不***
***包含所需要的信息。联系组***
***如果需要此命令为您提供了这些符号***
***工作。 ***
*** ***
***类型引用：NT KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
***您的调试器不使用正确的符号***
*** ***
***为了使这个命令能够正常工作，你的符号路径***
***必须指向.PDB具有完整的类型信息的文件。 ***
*** ***
***某些.pdb文件（如公共操作系统符号）不***
***包含所需要的信息。联系组***
***如果需要此命令为您提供了这些符号***
***工作。 ***
*** ***
***类型引用：NT _KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
***您的调试器不使用正确的符号***
*** ***
***为了使这个命令能够正常工作，你的符号路径***
***必须指向.PDB具有完整的类型信息的文件。 ***
*** ***
***某些.pdb文件（如公共操作系统符号）不***
***包含所需要的信息。联系组***
***如果需要此命令为您提供了这些符号***
***工作。 ***
*** ***
***类型引用：NT KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
***您的调试器不使用正确的符号***
*** ***
***为了使这个命令能够正常工作，你的符号路径***
***必须指向.PDB具有完整的类型信息的文件。 ***
*** ***
***某些.pdb文件（如公共操作系统符号）不***
***包含所需要的信息。联系组***
***如果需要此命令为您提供了这些符号***
***工作。 ***
*** ***
***类型引用：NT _KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
***您的调试器不使用正确的符号***
*** ***
***为了使这个命令能够正常工作，你的符号路径***
***必须指向.PDB具有完整的类型信息的文件。 ***
*** ***
***某些.pdb文件（如公共操作系统符号）不***
***包含所需要的信息。联系组***
***如果需要此命令为您提供了这些符号***
***工作。 ***
*** ***
***类型引用：NT _KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
***您的调试器不使用正确的符号***
*** ***
***为了使这个命令能够正常工作，你的符号路径***
***必须指向.PDB具有完整的类型信息的文件。 ***
*** ***
***某些.pdb文件（如公共操作系统符号）不***
***包含所需要的信息。联系组***
***如果需要此命令为您提供了这些符号***
***工作。 ***
*** ***
***类型引用：NT _KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
***您的调试器不使用正确的符号***
*** ***
***为了使这个命令能够正常工作，你的符号路径***
***必须指向.PDB具有完整的类型信息的文件。 ***
*** ***
***某些.pdb文件（如公共操作系统符号）不***
***包含所需要的信息。联系组***
***如果需要此命令为您提供了这些符号***
***工作。 ***
*** ***
***类型引用：NT _KPRCB ***
*** ***
************************************************** ***********************
可能的原因如下：ntoskrnl.exe中（NT + 72a40）
跟帖：MachineOwner
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\060115-11013-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 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`04e66000 PsLoadedModuleList = 0xfffff800`050ab890
Debug session time: Mon Jun 1 18:48:26.167 2015 (UTC + 8:00)
System Uptime: 0 days 1:10:03.447
*********************************************************************
* 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
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41790, fffffa800116c430, ffff, 0}
***** 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 ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+72a40 )
Followup: MachineOwner
微软（R）Windows调试版本6.12.0002.633 X86
版权所有（c）Microsoft公司。版权所有。
加载转储文件[C：\ WINDOWS \内存转储\ 060115-11013-01.dmp]
微型核心转储文件：只有登记和堆栈跟踪可用
符号搜索路径为：*** ***无效
************************************************** **************************
*符号负荷可能是不可靠的无符号搜索路径。 *
*使用.symfix有调试器选择一个符号路径。 *
*设置你的符号路径后，使用.reload的刷新符号位置。 *
************************************************** **************************
可执行搜索路径是：
************************************************** *******************
*符号无法加载，因为符号路径未初始化。 *
* *
*符号的路径可以设置：*
*使用_NT_SYMBOL_PATH环境变量。 *
*启动调试器时使用-y <symbol_path>参数。 *
*使用.sympath和.sympath + *
************************************************** *******************
无法加载图像的Ntoskrnl.exe，Win32错误0n2
***警告：无法验证时间戳的ntoskrnl.exe
***错误：模块加载完成，但符号不能为ntoskrnl.exe中加载
Windows 7的内核版本7601（服务包1）MP（4特效）免费x64的
产品：WINNT，浴室：的TerminalServer SingleUserTS
机器名称：
内核基= 0xfffff800`04e66000 PsLoadedModuleList = 0xfffff800`050ab890
调试会话时间：周一18年6月1日：48：26.167 2015年（UTC + 8:00）
系统正常运行时间：0天1：10：03.447
************************************************** *******************
*符号无法加载，因为符号路径未初始化。 *
* *
*符号的路径可以设置：*
*使用_NT_SYMBOL_PATH环境变量。 *
*启动调试器时使用-y <symbol_path>参数。 *
*使用.sympath和.sympath + *
************************************************** *******************
无法加载图像的Ntoskrnl.exe，Win32错误0n2
***警告：无法验证时间戳的ntoskrnl.exe
***错误：模块加载完成，但符号不能为ntoskrnl.exe中加载
加载内核符号
.................................................. .............
.................................................. ..............
...........................
加载用户符号
装载卸载模块列表
......
************************************************** *****************************
* *
*检测错误分析*
* *
************************************************** *****************************
使用！分析-v来获取详细的调试信息。
检测错误1A，{41790，fffffa800116c430，FFFF，0}
*****内核符号是错误的。请修正符号做分析。
************************************************** ***********************
*** ***
*** ***
***您的调试器不使用正确的符号***
*** ***
***为了使这个命令能够正常工作，你的符号路径***
***必须指向.PDB具有完整的类型信息的文件。 ***
*** ***
***某些.pdb文件（如公共操作系统符号）不***
***包含所需要的信息。联系组***
***如果需要此命令为您提供了这些符号***
***工作。 ***
*** ***
***类型引用：NT _KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
***您的调试器不使用正确的符号***
*** ***
***为了使这个命令能够正常工作，你的符号路径***
***必须指向.PDB具有完整的类型信息的文件。 ***
*** ***
***某些.pdb文件（如公共操作系统符号）不***
***包含所需要的信息。联系组***
***如果需要此命令为您提供了这些符号***
***工作。 ***
*** ***
***类型引用：NT KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
***您的调试器不使用正确的符号***
*** ***
***为了使这个命令能够正常工作，你的符号路径***
***必须指向.PDB具有完整的类型信息的文件。 ***
*** ***
***某些.pdb文件（如公共操作系统符号）不***
***包含所需要的信息。联系组***
***如果需要此命令为您提供了这些符号***
***工作。 ***
*** ***
***类型引用：NT _KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
***您的调试器不使用正确的符号***
*** ***
***为了使这个命令能够正常工作，你的符号路径***
***必须指向.PDB具有完整的类型信息的文件。 ***
*** ***
***某些.pdb文件（如公共操作系统符号）不***
***包含所需要的信息。联系组***
***如果需要此命令为您提供了这些符号***
***工作。 ***
*** ***
***类型引用：NT KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
***您的调试器不使用正确的符号***
*** ***
***为了使这个命令能够正常工作，你的符号路径***
***必须指向.PDB具有完整的类型信息的文件。 ***
*** ***
***某些.pdb文件（如公共操作系统符号）不***
***包含所需要的信息。联系组***
***如果需要此命令为您提供了这些符号***
***工作。 ***
*** ***
***类型引用：NT _KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
***您的调试器不使用正确的符号***
*** ***
***为了使这个命令能够正常工作，你的符号路径***
***必须指向.PDB具有完整的类型信息的文件。 ***
*** ***
***某些.pdb文件（如公共操作系统符号）不***
***包含所需要的信息。联系组***
***如果需要此命令为您提供了这些符号***
***工作。 ***
*** ***
***类型引用：NT _KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
***您的调试器不使用正确的符号***
*** ***
***为了使这个命令能够正常工作，你的符号路径***
***必须指向.PDB具有完整的类型信息的文件。 ***
*** ***
***某些.pdb文件（如公共操作系统符号）不***
***包含所需要的信息。联系组***
***如果需要此命令为您提供了这些符号***
***工作。 ***
*** ***
***类型引用：NT _KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
***您的调试器不使用正确的符号***
*** ***
***为了使这个命令能够正常工作，你的符号路径***
***必须指向.PDB具有完整的类型信息的文件。 ***
*** ***
***某些.pdb文件（如公共操作系统符号）不***
***包含所需要的信息。联系组***
***如果需要此命令为您提供了这些符号***
***工作。 ***
*** ***
***类型引用：NT _KPRCB ***
*** ***
************************************************** ***********************
可能的原因如下：ntoskrnl.exe中（NT + 72a40）
跟帖：MachineOwner
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\060115-11013-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 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`04e66000 PsLoadedModuleList = 0xfffff800`050ab890
Debug session time: Mon Jun 1 18:48:26.167 2015 (UTC + 8:00)
System Uptime: 0 days 1:10:03.447
*********************************************************************
* 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
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41790, fffffa800116c430, ffff, 0}
***** 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 ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+72a40 )
Followup: MachineOwner
