어떤 블루스크린 오류인지 도움좀 부탁드립니다
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 | - | - |
| 99252 | drivermax 3.4 | nukko | 12414 | 03-25 |
| 99251 | 기 타| LDH 이라는 확장자명 질문드려요 | 흉턱 | 12405 | 04-18 |
| 99250 | W7에서 네이트온 설치 [4] | 나그네 | 12396 | 12-13 |
| 99249 | 윈 도 우| 오토캐드 2006 설치와 ..실행 어떻게해야하나요? [5] | nanari | 12386 | 03-13 |
| 99248 | 폴더속성에서 읽기전용 해제가 안되네요 [1] | 1 | 12376 | 03-21 |
| » | 어떤 블루스크린 오류인지 도움좀 부탁드립니다 [1] | POONG3 | 12364 | 10-30 |
| 99246 | 하드웨어| 삼성 데스크탑 바이오스를 응급복구할 수 있는 방법이 없을... [1] | 감사맨 | 12350 | 02-20 |
| 99245 | 하드웨어| PRTG Network Monitor 사용법 문의 드립니다. [1] | 율짱 | 12341 | 07-31 |
| 99244 | 기 타| 혹시 크롬확장프로그램중 Proxy SwitchySharp 사용방법 아... | soosoo | 12340 | 11-25 |
| 99243 | 윈 도 우| ThinkPad T61에 win7이나,Server2008r2설치? [4] | alejandro | 12338 | 12-24 |
| 99242 | 기 타| 휴대폰에 있는 dcf파일 컴퓨터에서 재생 할수는 없는가? [1] | 거산 | 12310 | 01-26 |
| 99241 | 윈 도 우| 국민은행 공인인증 로그인 무한 반복?? [4] | 냥냥222 | 12310 | 02-26 |
| 99240 | 하드웨어| 플래쉬max에서 gif 이어 붙이는 방법..^.^ [2] | 비비안린 | 12310 | 02-24 |
| 99239 | 윈 도 우| 한글 2010 사용 시 응답없음 현상 [1] | goldshot | 12254 | 06-17 |
| 99238 | HP 노트북 윈도우 7 OEM 인증 안되구 있습니다 HP 노트북 ... [7] | 깡다구 | 12254 | 08-09 |
| 99237 | 윈 도 우| xp만능고스트.gho파일을 iso로 변환... [4] | 제비날다 | 12246 | 12-01 |
| 99236 | 윈 도 우| 운영체제가 현재 이 응용프로그램을 실행하도록 구성되지 ... [1] | 봄을그리다 | 12240 | 11-18 |
| 99235 | 윈 도 우| windows7 + 포토샵 CS3 조합으로 인터넷 연결 끊김 [4] | biosbios | 12228 | 11-22 |
| 99234 | 윈 도 우| 윈도우7 파일 아이콘 변경은 어떻게? [2] | GoogleDotCom | 12208 | 04-10 |
| 99233 | 소프트웨어| Easy DriverPacks v5.23 으로 만능고스트 만들어보신분? | 꼬오꼬 | 12207 | 03-01 |
이같은 경우는 대부분 메모리불량 과 하드불량으로 나타나는 현상같습니다
저도 처음 이런경우을 많이접했는데요 메모리 하드디스크 교체후 아무런 증상이 안나타나더군요