疑問 - 電腦不定時藍屏....

[t8989889o]

--------------------
閱讀本主題的最佳解答
--------------------


去年10月，
為了玩高級點的遊戲，找同學配一配
就直接把打工的錢直接砸到電腦上了~

但問題來了，
問題1.
電腦會不定時藍屏
https://docs.google.com/file/d/0B0sL...it?usp=sharing
以上是藍屏顯示的DMP檔
藍屏前徵兆:
瀏覽網頁會突然缺大部分的字、然後桌面功能開始不正常、系統有字的部分也缺字然後藍屏
問題2.
顯卡在玩遊戲時，畫面會突然當掉後變黑，然後恢復之後顯示"顯卡驅動停止，並已恢復"
尤其是在玩網頁遊戲有FLASHPLAYER的遊戲 例如.奇樂ONLINE最常發生
https://docs.google.com/file/d/0B0sL...it?usp=sharing
送修過一次，但感覺沒甚麼動過就還回來

剛買電腦就遇到這種事情，真的有夠沮喪的...
希望能找到壞的部分趁保固期間拿去送修

本人"微"懂電腦配件

電腦規格
WIN7 專業版 64位元 (學校提供授權的版本)
CPU: E3-1230
GPU: AUSU HD7770-1GD5 V2 (送修一次，毫無改善)
主板:華擎 H77Pro4
電源 :七盟ST-550PWL
硬碟: WD 330G
SSD硬碟: INTEL 60G
螢幕:LG W2261V (送修過1次，問題毫無改善)

另外，我的螢幕在玩遊戲時，每逢遊戲影片切換到遊戲，或載入到下一關時，都會黑屏，一定要把螢幕電源重開，才會看到畫面....

所以..
問題三:
這到底是不是顯卡問題，還是螢幕問題...
我試曾爬過文...但不知道是使用者太少還是直接報廢....都沒下文= =

花那麼多錢結果問題連連..好慘

感謝大大閱讀..

[crd1871]

恩,藍屏的話,有可能是記憶體的關係,試著把記憶體拔起來,然後用橡皮擦擦拭金手指看看.....

[t8989889o]

擦拭記憶體這個我有試過了 似乎不是這個問題~
而且這個藍屏在剛買組裝後就一直發生...

忘了提供記憶體品牌
UMAX DDR1333 -8G X 2

請問從藍屏有辦法得知是哪裡壞掉嗎?

[a471]

系統出現藍色畫面=大海撈針，造成的原因很多種也很廣泛，想解決得憑本事兒!
不然你以為幫人家灌系統這麼簡單啊~~~~

1.請確認主機板正確型號，H77PRO4有兩款你是哪種?
2.記憶體買錯~失敗!，DDR3-1333與1600速度的在價格上相差無幾
，應該買1600的才是...
3.請你交代W7安裝的過程..........描述得好不好涉及你的問題能否解決
4.你可以先更新顯示卡驅動程式先，看看會不會改善....
到華碩或AMD官網下載
5.你玩的遊戲名稱是?

[t8989889o]

作者: a471

系統出現藍色畫面=大海撈針，造成的原因很多種也很廣泛，想解決得憑本事兒!
不然你以為幫人家灌系統這麼簡單啊~~~~

1.請確認主機板正確型號，H77PRO4有兩款你是哪種?

ASROCK 華擎 H77Pro4 - MVP

2.記憶體買錯~失敗!，DDR3-1333與1600速度的在價格上相差無幾
，應該買1600的才是...

因為當時再原價屋特價(紅綠標)= =
3.請你交代W7安裝的過程..........描述得好不好涉及你的問題能否解決
1.進主機板按DEL
2.設定由光碟開機 灌WIN7於SSD
3.打開後灌光碟版的主板驅動和顯卡驅動
4.利用學校提供的程式進行授權
(是提供這個過程嗎?)

4.你可以先更新顯示卡驅動程式先，看看會不會改善....
到華碩或AMD官網下載

我是用裝置管理員查看是否有更新 他說是最新版~

5.你玩的遊戲名稱是?

常會當的是網頁遊戲 奇樂ONLINE~
畫面轉不過來的(螢幕反黑)的是.....幾乎每個有切換影片變成遊戲的都會
例如: BF2 COD 英雄連 甚至 馬奇英雄傳也會....

[不飛]

給您一個建議，

首先把螢幕解析度調低一點，

或是跟朋友借一台螢幕測試看看，

LG 的螢幕說實話，品質不穩。

[a471]

作者: t8989889o

常會當的是網頁遊戲 奇樂ONLINE~
畫面轉不過來的(螢幕反黑)的是.....幾乎每個有切換影片變成遊戲的都會
例如: BF2 COD 英雄連 甚至 馬奇英雄傳也會....

更新驅動程式怎麼可以靠裝置管理員?

要自己去官網下載最新的驅動程式回來用，看你要用
華碩(沒那麼新)還是AMD官網的(比較新)...

你安裝系統僅依靠主機板附的CD....難怪不穩

先更新顯示卡驅動程式先..

[米奇]

作者: t8989889o

擦拭記憶體這個我有試過了 似乎不是這個問題~
而且這個藍屏在剛買組裝後就一直發生...

忘了提供記憶體品牌
UMAX DDR1333 -8G X 2

請問從藍屏有辦法得知是哪裡壞掉嗎?

Loading Dump File [E:\Program Files\Windows Kits\8.0\Debuggers\x64\020513-15085-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\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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`04217000 PsLoadedModuleList = 0xfffff800`0445b670
Debug session time: Tue Feb 5 01:04:22.098 2013 (UTC + 8:00)
System Uptime: 0 days 0:01:07.097
*********************************************************************
* 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
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8011410b30, fffffa8011410e10, fffff80004595460}

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

----- ETW minidump data unavailable-----
unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase

*************************************************************************
*** ***
*** ***
*** 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 : wininit.exe

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

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

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8011410b30, Terminating object
Arg3: fffffa8011410e10, Process image file name
Arg4: fffff80004595460, Explanatory message (ascii)

Debugging Details:
------------------

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

----- ETW minidump data unavailable-----
unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000

DEBUG_FLR_IMAGE_TIMESTAMP: 0

PROCESS_OBJECT: fffffa8011410b30

IMAGE_NAME: wininit.exe

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xF4

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`0e24ee38 fffff800`0461d822 : 00000000`000000f4 00000000`00000003 fffffa80`11410b30

fffffa80`11410e10 : nt+0x7efc0
fffff880`0e24ee40 00000000`000000f4 : 00000000`00000003 fffffa80`11410b30 fffffa80`11410e10

fffff800`04595460 : nt+0x406822
fffff880`0e24ee48 00000000`00000003 : fffffa80`11410b30 fffffa80`11410e10 fffff800`04595460

00000000`00000086 : 0xf4
fffff880`0e24ee50 fffffa80`11410b30 : fffffa80`11410e10 fffff800`04595460 00000000`00000086

fffffa80`11410b30 : 0x3
fffff880`0e24ee58 fffffa80`11410e10 : fffff800`04595460 00000000`00000086 fffffa80`11410b30

fffff800`045c9e0b : 0xfffffa80`11410b30
fffff880`0e24ee60 fffff800`04595460 : 00000000`00000086 fffffa80`11410b30 fffff800`045c9e0b

ffffffff`ffffffff : 0xfffffa80`11410e10
fffff880`0e24ee68 00000000`00000086 : fffffa80`11410b30 fffff800`045c9e0b ffffffff`ffffffff

fffffa80`117e6b50 : nt+0x37e460
fffff880`0e24ee70 fffffa80`11410b30 : fffff800`045c9e0b ffffffff`ffffffff fffffa80`117e6b50

fffffa80`11410b30 : 0x86
fffff880`0e24ee78 fffff800`045c9e0b : ffffffff`ffffffff fffffa80`117e6b50 fffffa80`11410b30

fffffa80`11410b30 : 0xfffffa80`11410b30
fffff880`0e24ee80 ffffffff`ffffffff : fffffa80`117e6b50 fffffa80`11410b30 fffffa80`11410b30

ffffffff`ffffffff : nt+0x3b2e0b
fffff880`0e24ee88 fffffa80`117e6b50 : fffffa80`11410b30 fffffa80`11410b30 ffffffff`ffffffff

00000000`00000008 : 0xffffffff`ffffffff
fffff880`0e24ee90 fffffa80`11410b30 : fffffa80`11410b30 ffffffff`ffffffff 00000000`00000008

fffffa80`11410b30 : 0xfffffa80`117e6b50
fffff880`0e24ee98 fffffa80`11410b30 : ffffffff`ffffffff 00000000`00000008 fffffa80`11410b30

00000000`c0000005 : 0xfffffa80`11410b30
fffff880`0e24eea0 ffffffff`ffffffff : 00000000`00000008 fffffa80`11410b30 00000000`c0000005

fffffa80`117e6b50 : 0xfffffa80`11410b30
fffff880`0e24eea8 00000000`00000008 : fffffa80`11410b30 00000000`c0000005 fffffa80`117e6b50

fffff800`04548f04 : 0xffffffff`ffffffff
fffff880`0e24eeb0 fffffa80`11410b30 : 00000000`c0000005 fffffa80`117e6b50 fffff800`04548f04

ffffffff`ffffffff : 0x8
fffff880`0e24eeb8 00000000`c0000005 : fffffa80`117e6b50 fffff800`04548f04 ffffffff`ffffffff

00000000`00000001 : 0xfffffa80`11410b30
fffff880`0e24eec0 fffffa80`117e6b50 : fffff800`04548f04 ffffffff`ffffffff 00000000`00000001

fffffa80`11410b30 : 0xc0000005
fffff880`0e24eec8 fffff800`04548f04 : ffffffff`ffffffff 00000000`00000001 fffffa80`11410b30

00000000`00000008 : 0xfffffa80`117e6b50
fffff880`0e24eed0 ffffffff`ffffffff : 00000000`00000001 fffffa80`11410b30 00000000`00000008

ffffffff`746c6644 : nt+0x331f04
fffff880`0e24eed8 00000000`00000001 : fffffa80`11410b30 00000000`00000008 ffffffff`746c6644

fffff880`0e24ef50 : 0xffffffff`ffffffff
fffff880`0e24eee0 fffffa80`11410b30 : 00000000`00000008 ffffffff`746c6644 fffff880`0e24ef50

00000000`00000000 : 0x1
fffff880`0e24eee8 00000000`00000008 : ffffffff`746c6644 fffff880`0e24ef50 00000000`00000000

00000980`00000000 : 0xfffffa80`11410b30
fffff880`0e24eef0 ffffffff`746c6644 : fffff880`0e24ef50 00000000`00000000 00000980`00000000

00000000`03800aa0 : 0x8
fffff880`0e24eef8 fffff880`0e24ef50 : 00000000`00000000 00000980`00000000 00000000`03800aa0

00000000`03800380 : 0xffffffff`746c6644
fffff880`0e24ef00 00000000`00000000 : 00000980`00000000 00000000`03800aa0 00000000`03800380

00000000`0010005f : 0xfffff880`0e24ef50


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

BUCKET_ID: WRONG_SYMBOLS

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

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

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8011410b30, Terminating object
Arg3: fffffa8011410e10, Process image file name
Arg4: fffff80004595460, Explanatory message (ascii)

Debugging Details:
------------------

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

----- ETW minidump data unavailable-----
unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000

DEBUG_FLR_IMAGE_TIMESTAMP: 0

PROCESS_OBJECT: fffffa8011410b30

IMAGE_NAME: wininit.exe

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xF4

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`0e24ee38 fffff800`0461d822 : 00000000`000000f4 00000000`00000003 fffffa80`11410b30

fffffa80`11410e10 : nt+0x7efc0
fffff880`0e24ee40 00000000`000000f4 : 00000000`00000003 fffffa80`11410b30 fffffa80`11410e10

fffff800`04595460 : nt+0x406822
fffff880`0e24ee48 00000000`00000003 : fffffa80`11410b30 fffffa80`11410e10 fffff800`04595460

00000000`00000086 : 0xf4
fffff880`0e24ee50 fffffa80`11410b30 : fffffa80`11410e10 fffff800`04595460 00000000`00000086

fffffa80`11410b30 : 0x3
fffff880`0e24ee58 fffffa80`11410e10 : fffff800`04595460 00000000`00000086 fffffa80`11410b30

fffff800`045c9e0b : 0xfffffa80`11410b30
fffff880`0e24ee60 fffff800`04595460 : 00000000`00000086 fffffa80`11410b30 fffff800`045c9e0b

ffffffff`ffffffff : 0xfffffa80`11410e10
fffff880`0e24ee68 00000000`00000086 : fffffa80`11410b30 fffff800`045c9e0b ffffffff`ffffffff

fffffa80`117e6b50 : nt+0x37e460
fffff880`0e24ee70 fffffa80`11410b30 : fffff800`045c9e0b ffffffff`ffffffff fffffa80`117e6b50

fffffa80`11410b30 : 0x86
fffff880`0e24ee78 fffff800`045c9e0b : ffffffff`ffffffff fffffa80`117e6b50 fffffa80`11410b30

fffffa80`11410b30 : 0xfffffa80`11410b30
fffff880`0e24ee80 ffffffff`ffffffff : fffffa80`117e6b50 fffffa80`11410b30 fffffa80`11410b30

ffffffff`ffffffff : nt+0x3b2e0b
fffff880`0e24ee88 fffffa80`117e6b50 : fffffa80`11410b30 fffffa80`11410b30 ffffffff`ffffffff

00000000`00000008 : 0xffffffff`ffffffff
fffff880`0e24ee90 fffffa80`11410b30 : fffffa80`11410b30 ffffffff`ffffffff 00000000`00000008

fffffa80`11410b30 : 0xfffffa80`117e6b50
fffff880`0e24ee98 fffffa80`11410b30 : ffffffff`ffffffff 00000000`00000008 fffffa80`11410b30

00000000`c0000005 : 0xfffffa80`11410b30
fffff880`0e24eea0 ffffffff`ffffffff : 00000000`00000008 fffffa80`11410b30 00000000`c0000005

fffffa80`117e6b50 : 0xfffffa80`11410b30
fffff880`0e24eea8 00000000`00000008 : fffffa80`11410b30 00000000`c0000005 fffffa80`117e6b50

fffff800`04548f04 : 0xffffffff`ffffffff
fffff880`0e24eeb0 fffffa80`11410b30 : 00000000`c0000005 fffffa80`117e6b50 fffff800`04548f04

ffffffff`ffffffff : 0x8
fffff880`0e24eeb8 00000000`c0000005 : fffffa80`117e6b50 fffff800`04548f04 ffffffff`ffffffff

00000000`00000001 : 0xfffffa80`11410b30
fffff880`0e24eec0 fffffa80`117e6b50 : fffff800`04548f04 ffffffff`ffffffff 00000000`00000001

fffffa80`11410b30 : 0xc0000005
fffff880`0e24eec8 fffff800`04548f04 : ffffffff`ffffffff 00000000`00000001 fffffa80`11410b30

00000000`00000008 : 0xfffffa80`117e6b50
fffff880`0e24eed0 ffffffff`ffffffff : 00000000`00000001 fffffa80`11410b30 00000000`00000008

ffffffff`746c6644 : nt+0x331f04
fffff880`0e24eed8 00000000`00000001 : fffffa80`11410b30 00000000`00000008 ffffffff`746c6644

fffff880`0e24ef50 : 0xffffffff`ffffffff
fffff880`0e24eee0 fffffa80`11410b30 : 00000000`00000008 ffffffff`746c6644 fffff880`0e24ef50

00000000`00000000 : 0x1
fffff880`0e24eee8 00000000`00000008 : ffffffff`746c6644 fffff880`0e24ef50 00000000`00000000

00000980`00000000 : 0xfffffa80`11410b30
fffff880`0e24eef0 ffffffff`746c6644 : fffff880`0e24ef50 00000000`00000000 00000980`00000000

00000000`03800aa0 : 0x8
fffff880`0e24eef8 fffff880`0e24ef50 : 00000000`00000000 00000980`00000000 00000000`03800aa0

00000000`03800380 : 0xffffffff`746c6644
fffff880`0e24ef00 00000000`00000000 : 00000980`00000000 00000000`03800aa0 00000000`03800380

00000000`0010005f : 0xfffff880`0e24ef50


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

BUCKET_ID: WRONG_SYMBOLS

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

2: kd> !process fffffa8011410b30 3
GetPointerFromAddress: unable to read from fffff800044c5000
NT symbols are incorrect, please fix symbols
2: kd> lmvm wininit
start end module name
2: kd> g
^ No runnable debuggees error in 'g'
2: kd> gh
^ No runnable debuggees error in 'gh'


建議您做一下記憶體檢測 :Windows 內建記憶體診斷工具

[t8989889o]

作者: a471

更新驅動程式怎麼可以靠裝置管理員?

要自己去官網下載最新的驅動程式回來用，看你要用
華碩(沒那麼新)還是AMD官網的(比較新)...

你安裝系統僅依靠主機板附的CD....難怪不穩

先更新顯示卡驅動程式先..

已經從官網把主板跟顯卡的驅動全部手動更新了~
現在正在看看是否還會在藍屏
不過然需要等待就是了...

[t8989889o]

經過測試 系統提供的記憶體檢測工具

他寫"正常"


至於黑屏的部分
我這幾天去跟朋友借看看好了~

[米奇]

作者: t8989889o

經過測試 系統提供的記憶體檢測工具

他寫"正常"


至於黑屏的部分
我這幾天去跟朋友借看看好了~

8樓是您 DMP 檔解讀
請作參考

[a471]

作者: t8989889o

已經從官網把主板跟顯卡的驅動全部手動更新了~
現在正在看看是否還會在藍屏
不過然需要等待就是了...

嗯.....剩下就是看你建構系統安裝W7時掛驅動的程序對不對了...

[t8989889o]

作者: 米奇

8樓是您 DMP 檔解讀
請作參考

其實我就只看得懂最後那行中文
如何參考 我完全不會0.0

[t8989889o]

作者: a471

嗯.....剩下就是看你建構系統安裝W7時掛驅動的程序對不對了...

怎麼說? 是否有甚麼要注意的嗎?

[a471]

作者: t8989889o

怎麼說? 是否有甚麼要注意的嗎?

安裝的順序~~~就像疊積木按部就班建構系統

你目前系統穩定嗎???...