Ge Chickswimsuit %D1%C7%D6%DE%B3%C9%C8%CB%CE%DE%C2%EB%D7%AA%CC%FB%C7%F8 Solo%20mature It 1 Chick Swimsuit Timmy's Blog » win7下0×124蓝屏的一种解决办法

十分感谢，我按照你的办法，问题暂时没有再出现，是否已经解决有待观察。一开始我还以为处理器有问题呢。你的cpu是什么型号的，蓝屏是不是因为运行暴风影音，火狐浏览器，浏览器等软件造成的？我每次运行这些软件不出两分钟，就蓝屏，代码就是0×124,查看事件管理器，一般报两个错误，一个是缓存层级架构错误，一个是总线错误。。。。

为什么我的WIN7搜索ntkrnlpa，会有好多个呢，而且差不多有4 5个不同的版本

楼主你好，我最近因为加了一根内存条之后出现0×00000124蓝屏，之后我把内存条拔掉之后蓝屏还有，今天分析内存转储文件发现有可能为athr.sys,hal.dll,ntoskrnl.exe的问题。楼主你说的ntkrnlpa版本有三个不同，且现在用的是win7 SP1。求楼主帮忙分析下

楼主您好，我也是碰到了和你一样的问题，我用的是华硕本本F8sr，自己升级了CPU，T8300加针版的，也升级了显卡9650m gt，经常在浏览网页时出现蓝屏，代码也是124，但是我玩魔兽的时候不会出现！不知道楼主的问题现在还出现了没有？这个问题整整困扰了我3个多月了~重装了系统还是一样出现，网上找了些帖子，说是可能和CPU关系比较大~有种说法是CPU在轻载的时候待机电压过低导致的~和淘宝卖家联系，卖家坚决说CPU是没问题的，让我从别的地方入手~郁闷啊~到底是不是CPU的问题哦，楼主你觉得呢~

@rainzhu
貌似也是这个吗？ntoskrnl.exe？？？
Microsoft (R) Windows Debugger Version 6.7.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Rain\Desktop81511-16130-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 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 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0×84014000 PsLoadedModuleList = 0x8415c830
Debug session time: Mon Aug 15 14:35:50.975 2011 (GMT+8)
System Uptime: 0 days 0:00:06.817
*********************************************************************
* 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 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
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {}

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

*********************************************************************
* 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : hardware

Followup: MachineOwner

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, MCA_ASSERT
Arg2: 895de79c, Address of WHEA_ERROR_RECORD structure
Arg3: 00000000, High 32 bits of MCi_STATUS MSR for the MCA bank that had
the error
Arg4: 00000000, Low 32 bits of MCi_STATUS MSR for the MCA bank that had
the error

Debugging Details:
——————

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

*********************************************************************
* 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************

FAULTING_MODULE: 8403c000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 0

WHEA_ERROR_RECORD: !errrec ffffffff895de79c

BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8dd13cc4 8410b0c5 895de780 841a3c28 841a3c20 nt+0×322493
8dd13ce4 8410beef 841a3c20 895de780 841a3c50 nt+0xcf0c5
8dd13d00 840aa03b 841a3c20 00000000 868e5640 nt+0xcfeef
8dd13d50 8424a9df 00000001 afb6bb65 00000000 nt+0x6e03b
8dd13d90 840fc1d9 840a9f2e 00000001 00000000 nt+0x20e9df
00000000 00000000 00000000 00000000 00000000 nt+0xc01d9

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
———