윈 도 우 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 | - | - |
| 13322 | 윈 도 우| 로그인(비밀번호) 창부터 화상키보드 사용할수 있는 방법 | 이러지말아요 | 5227 | 03-18 |
| 13321 | 윈 도 우| go6600최신드라이버문의 [1] | 소어아 | 19297 | 03-18 |
| 13320 | 하드웨어| 넷북 충전을 해가며 사용시 전기세 많이 먹을까요? [1] | June.RED4™ | 3389 | 03-18 |
| 13319 | 윈 도 우| 배터리를 교체하는 것이 좋습니다. [5] | GoogleDotCom | 9341 | 03-18 |
| 13318 | 하드웨어| 아수스 바이오스 업데이트.. [11] | 비비안린 | 34547 | 03-18 |
| 13317 | 윈 도 우| 인터넷 공유 먹통인데 해결방법이 있는지.... | 이중재 | 3179 | 03-18 |
| 13316 | 윈 도 우| 절전기능이 먹통이 되요.. [1] | 비오는날 | 3142 | 03-18 |
| 13315 | 윈 도 우| 윈도우7 다중 디스플레이에 관해... [1] | 미즈키 나나 | 4554 | 03-18 |
| » | 윈 도 우| Minidump 분석 좀 부탁드리겠습니다. | 야생숫곰 | 14880 | 03-18 |
| 13313 | 윈 도 우| 윈7 자체에 모니터분할프로그램이 있는지요? [2] | 바람이불면 | 4513 | 03-18 |
| 13312 | 윈 도 우| 급합니다! 자료 다 날아가게 생겼어요! [4] | 짜바리 | 3221 | 03-18 |
| 13311 | 윈 도 우| 수정 혹시 윈도우7 정품이 아닐경우.. [3] | 하윤 | 4976 | 03-17 |
| 13310 | 하드웨어| 한글 2010 아이콘이 이상해졌어요 ㅠㅠ [6] | 콩나물국 | 5363 | 03-17 |
| 13309 | 윈 도 우| 홈프리미엄과 프로페셔널&얼티밋 속도...에 관해서 [8] | nanari | 6562 | 03-17 |
| 13308 | 하드웨어| 메인보드 e-sata 꼽는곳에 [3] | KokoroZzin | 3103 | 03-17 |
| 13307 | 윈 도 우| "짱님텐도님" 부탁 좀 드릴 수 있을까요?...^^;; [3] | Chobits0914 | 3438 | 03-17 |
| 13306 | 윈 도 우| 윈7-64b사용 윈포식구분들 급하게 부탁드립니다. [3] | SANtAFE | 3420 | 03-17 |
| 13305 | 윈 도 우| 소리없음....... | 이별은지구 | 3317 | 03-17 |
| 13304 | 윈 도 우| 문의)) \boot\bcd "bcd"파일 어떻게 열어서 편집... [1] | Chobits0914 | 5846 | 03-17 |
| 13303 | 윈 도 우| 문의)) 혹시 $OEM$ 만드는 법 아시는 분 없으신지요??? [2] | Chobits0914 | 3890 | 03-17 |