求助~M800一直出現藍色畫面,不知哪裡出問題(補圖(藍色畫面))

dadow313170

dadow313170
個人積分：0分
文章編號：9507418

0分

樓主

2008-12-20 17:23

自己使用M800使用VISTA 家用進階版，
每次工作到一半都會出現藍色畫面後立刻消失。

重新開機後出現

求助~M800一直出現藍色畫面,不知哪裡出問題(補圖(藍色畫面))

錯誤訊息每次都一樣，內容如下

問題簽章:
問題事件名稱: BlueScreen
作業系統版本: 6.0.6001.2.1.0.768.3
地區設定: 1028

與問題相關的其他資訊:
BCCode:1000008e
BCP1: C0000005
BCP2: 92F1336C
BCP3: B15596EC
BCP4: 00000000
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1

路進:
C:\Windows\Minidump\Mini122008-01.dmp
C:\Users\xxx\AppData\Local\Temp\WER-124566-0.sysdata.xml
C:\Users\xxx\AppData\Local\Temp\WER63F0.tmp.version.txt

参考:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0c04

======================================================

求助~M800一直出現藍色畫面,不知哪裡出問題(補圖(藍色畫面))

這張圖是原廠記憶體

這張圖是廠商贈送記憶體

是不是計時表所有資訊數據不同，導致系統不穩呢

2008-12-20 17:23 發佈

文章關鍵字 M800 藍色畫面補圖問題

newluke

newluke
個人積分：0分
文章編號：9535897

0分

2樓

2008-12-22 21:18

你要不要把你的 *.dmp (例如 Mini122008-01.dmp) 放上來,
這樣應該可以看看是那個 driver 造成的 BlueScreen.

bqm969.

bqm969.
個人積分：2分
文章編號：9536665

2分

3樓

2008-12-22 22:04

有找到 Mini122008-01.dmp檔案
使用筆記本開起出現亂碼，不知如何開啟這檔案。
張貼給大家看
ps:原廠dirver完全沒有更新更改過

dx8053

dx8053
個人積分：0分
文章編號：9536958

0分

4樓

2008-12-22 22:21

請下載Win debuger來檢視這個DMP檔案吧~

jalen22001

jalen22001
個人積分：17分
文章編號：9544229

17分

5樓

2008-12-23 11:49

我之前也有過類似的問題
後來發現是BIOS的版本問題
送回原廠調整過後到現在到現在就沒有問題了

bqm969.

bqm969.
個人積分：2分
文章編號：9549659

2分

6樓

2008-12-23 17:58

剛好我也遇到這問題，把錯誤訊息貼出來

=============================================

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

Loading Dump File [D:\Windows\Minidump\Mini122008-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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x81e10000 PsLoadedModuleList = 0x81f27c70
Debug session time: Sat Dec 20 00:17:58.219 2008 (GMT+8)
System Uptime: 0 days 0:53:28.117
*********************************************************************
* 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\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
....
Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 92f1336c, b15596ec, 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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 : dxgkrnl.sys ( dxgkrnl+2436c )

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

newluke

newluke
個人積分：0分
文章編號：9551181

0分

7樓

2008-12-23 20:24

http://www.rzhome.net/blog/article.asp?id=663

dadow313170

dadow313170
個人積分：0分
文章編號：9568838

0分

樓主

2008-12-24 20:42

補上藍色畫面圖片，請大家再幫我看看

hcytcl

hcytcl
個人積分：0分
文章編號：9578977

0分

9樓

2008-12-25 12:12

dadow313170 wrote:
自己使用M800使用...(恕刪)

小弟我最近也買m800...
剛剛看了一下版大的圖...
您的記憶體插到4G...M800不是最大只有支援到3G而已嗎?
會不會是.....
如有錯也歡迎指正.... 0o0

dadow313170

dadow313170
個人積分：0分
文章編號：9582360

0分

樓主

2008-12-25 15:37

個人使用M800 P8400 ，沒有更新BISO前，RAM可以抓到4G