윈 도 우 Minidump 분석 좀 부탁드리겠습니다.
2010.03.18 04:16
win7 깔고 6개월간 잘 쓰던 컴터가 갑자기 블루스크린이 뜨네요.
열흘전에 ssd를 구입해서 달아 놓고 썼었는데 그동안 문제가 없다가 어제부터 첫부팅할때나 재부팅 할때 가끔
부팅화면에서 바탕화면으로 넘어오자마자 다운이 되었는데 다시 한번 재부팅하면
부팅이 되긴 하는데 이런 메세지가 뜨더군요.
------------------------------------------------------------------------------------------------
문제 서명:
문제 이벤트 이름: BlueScreen
OS 버전: 6.1.7600.2.0.0.256.1
로캘 ID: 1042
문제에 대한 추가 정보:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8007BFF8F8
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
문제 설명에 도움이 되는 파일:
C:\Windows\Minidump\031810-18969-01.dmp
------------------------------------------------------------------------------------------------
인터넷 검색을 좀 해봤는데 메모리 덤프를 분석하면 된다고 해서
Debugging Tools for windows를 다운 받아서 파일을 열어봤는데
-------------------------------------------------------------------------------------------------
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\031810-18969-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`02e1a000 PsLoadedModuleList = 0xfffff800`03057e50
Debug session time: Thu Mar 18 03:29:30.504 2010 (GMT+9)
System Uptime: 0 days 0:00:09.143
*********************************************************************
* 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
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8007bff8f8, 0, 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!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
Unable to load image PSHED.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PSHED.dll
*** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : hardware
Followup: MachineOwner
-------------------------------------------------------------------------------------------------
위와 같이 뜹니다. 어떻게 해결해야 할지 조언 좀 부탁드리겠습니다.
댓글 [0]
| 번호 | 제목 | 글쓴이 | 조회 | 등록일 |
|---|---|---|---|---|
| [공지] | 질문과 답변 게시판 이용간 유의사항 | gooddew | - | - |
| 13336 | 윈 도 우| 작업표시줄이 사라지는 문제 [2] | 하늘나무 | 4320 | 03-19 |
| 13335 | 하드웨어| 문의)) PC 2대 연결하는 법 좀 알려주셔요~~~^^;; [5] | Chobits0914 | 4642 | 03-19 |
| 13334 | 하드웨어| 엑셀 함수 검증좀 해주세요 [2] | 눈비 | 2837 | 03-19 |
| 13333 | 윈 도 우| Memory Runs at Dual Channel Inter leaved | 이별은지구 | 3770 | 03-19 |
| 13332 | 윈 도 우| 영문 윈도우7 엔터프라이즈 해시값 좀 가르쳐 주세요 [1] | 오마르 | 3384 | 03-19 |
| 13331 | 하드웨어| 도와주세요.! 네트워크 공격을 받습니다. 화면 캡쳐했습니다. [2] | 박제신 | 3096 | 03-19 |
| 13330 | 윈 도 우| ip 구성이 옳바르지 않습니다. 이거 해결방법좀 알려주세요 [3] | 눈팅다껌 | 3406 | 03-19 |
| 13329 | 윈 도 우| power dvd10 오류.... [1] | 푸이잇 | 2904 | 03-19 |
| 13328 | 윈 도 우| 토렌트에 대하여 질문드립니다 [4] | Bguy | 2947 | 03-19 |
| 13327 | 하드웨어| ati 5770 hydraVision 이라는 플이 무엇인가요 ? [1] | 운수 대통 | 3489 | 03-19 |
| 13326 | 하드웨어| 마더보드 조립에 들어가는 부품 질문 [4] | kdksj | 3062 | 03-18 |
| 13325 | 하드웨어| 한컴오피스2010 이랑 한글2010 가격차이 질문입니다 [7] | 오마르 | 9753 | 03-18 |
| 13324 | 윈 도 우| 짱님텐도님께 질문 있습니다!!! [5] | Chobits0914 | 2381 | 03-18 |
| 13323 | 윈 도 우| 홈버전을...... [4] | 현이아비 | 3174 | 03-18 |
| 13322 | 윈 도 우| 로그인(비밀번호) 창부터 화상키보드 사용할수 있는 방법 | 이러지말아요 | 5217 | 03-18 |
| 13321 | 윈 도 우| go6600최신드라이버문의 [1] | 소어아 | 19288 | 03-18 |
| 13320 | 하드웨어| 넷북 충전을 해가며 사용시 전기세 많이 먹을까요? [1] | June.RED4™ | 3376 | 03-18 |
| 13319 | 윈 도 우| 배터리를 교체하는 것이 좋습니다. [5] | GoogleDotCom | 9331 | 03-18 |
| 13318 | 하드웨어| 아수스 바이오스 업데이트.. [11] | 비비안린 | 34534 | 03-18 |
| 13317 | 윈 도 우| 인터넷 공유 먹통인데 해결방법이 있는지.... | 이중재 | 3166 | 03-18 |