어떤 블루스크린 오류인지 도움좀 부탁드립니다
2009.10.30 09:00
오류내용
컴퓨터가 오류 검사 후 다시 부팅되었습니다. 오류 검사: 0x0000003b (0x00000000c0000005, 0xfffff88000c0a41f, 0xfffff880097b1d20, 0x0000000000000000). 덤프 저장 위치: C:\Windows\MEMORY.DMP. 보고서 ID: 103009-26488-01
아래는 .dump파일 복사했습니다
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Brave\Desktop\103009-26488-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
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03064000 PsLoadedModuleList = 0xfffff800`032a1e50
Debug session time: Fri Oct 30 06:00:00.910 2009 (GMT+9)
System Uptime: 0 days 0:28:41.611
*********************************************************************
* 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
*** 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 3B, {c0000005, fffff88000c0a41f, fffff880097b1d20, 0}
Unable to load image \SystemRoot\system32\DRIVERS\ataport.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ataport.SYS
*** ERROR: Module load completed but symbols could not be loaded for ataport.SYS
***** 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 : ataport.SYS ( ataport+a41f )
Followup: MachineOwner
---------
윈도우 7 64비트 사용중입니다
어디가 이상있는지 도움좀 부탁드립니다
감사합니다
댓글 [1]
-
행복한별 2009.10.30 09:27
| 번호 | 제목 | 글쓴이 | 조회 | 등록일 |
|---|---|---|---|---|
| [공지] | 질문과 답변 게시판 이용간 유의사항 | gooddew | - | - |
| 8606 | 이유가 뭘까요...? [2] | OI가 | 1958 | 11-02 |
| 8605 | 멀티부팅 질문입니다... [4] | lphyxsius | 2319 | 11-02 |
| 8604 | 업데이트 기록 검토에 중복으로 작성된 목록을 제거 하고 ... [3] | 패닉 | 3518 | 11-02 |
| 8603 | 윈7 칩셋패치 할때 질문좀 드립니다.. | 이보형 | 2562 | 11-02 |
| 8602 | win7 x64 ulti 설치 후 이상없다가 mbr error3 [1] | 최흥현 | 2747 | 11-02 |
| 8601 | ROM BIOS 에러 ㅠㅠ [1] | 포메 | 2417 | 11-02 |
| 8600 | 지난 대학생 프로모션에서 결제오류로 환불 받기로 하신분... [1] | 작은천사 | 2266 | 11-02 |
| 8599 | 시작메뉴에서 문서 삭제문제입니다. [3] | 야사단 | 2576 | 11-02 |
| 8598 | xp 7 멀티부팅중인데 xp에서만 특정하드가 버벅거립니다 [1] | 유령의노래 | 2452 | 11-01 |
| 8597 | 지문인식이 사라졌습니다.. | 드와이트 | 2260 | 11-01 |
| 8596 | 인터넷 익스플로러 64비트 에서 어도비 플래쉬 플레이어 [3] | chanchan | 4074 | 11-01 |
| 8595 | 프로모션 인증에 대해서 궁금합니다 [2] | 마왕 | 2110 | 11-01 |
| 8594 | 질문좀!! 윈도우7 업그레이드!! [3] | dariel | 2344 | 11-01 |
| 8593 | 인증방법에 따라 윈7 속도가 틀리나요?? [2] | minkyu85 | 2990 | 11-01 |
| 8592 | 지포스 쓰시는 분들 화면재생빈도 해결 되었나요? [5] | 블루리즈 | 3020 | 11-01 |
| 8591 | 윈7 과 XP간 네트워크 공유 연결방법 질문 [4] | 하늘하늘이 | 5178 | 11-01 |
| 8590 | 윈도우7 얼티밋 32비트 쓰는데 The KMPlayer 에러 [6] | 김처사 | 3431 | 11-01 |
| 8589 | 확장자 프로그램 연결 푸는방법없나요? [2] | CloudStrife | 2715 | 11-01 |
| 8588 | 익스8 삭제방법 없나요? [2] | 정태진 | 2391 | 11-01 |
| 8587 | 윈도우7 테마팩 사용하기 [3] | KcEAbFR9 | 4325 | 11-01 |
이같은 경우는 대부분 메모리불량 과 하드불량으로 나타나는 현상같습니다
저도 처음 이런경우을 많이접했는데요 메모리 하드디스크 교체후 아무런 증상이 안나타나더군요