어떤 블루스크린 오류인지 도움좀 부탁드립니다
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 | - | - |
8565 | GRMCULFRER_KO_X32 (RTM7600) 인증 [2] | 민경호 | 6994 | 11-01 |
8564 | 알패스 작동이 안됩니다. [6] | 유빈아빠 | 2745 | 11-01 |
8563 | 어드민 계정 활성화 해야 하나요? [5] | slater | 2808 | 11-01 |
8562 | 한자키 없는 키보드는 어떻게 특수문자 입력하나요?? [4] | 견우 | 7578 | 11-01 |
8561 | window 7 ultimate 한글판을 영문판으로 [3] | sub | 4111 | 11-01 |
8560 | 윈도우7 프로페셔널 iso파일명 좀 알려주세요 [2] | 박찬호 | 3274 | 11-01 |
8559 | 데몬 삭제후에도 남은 드라이브..;; [2] | 사기강박증 | 2692 | 11-01 |
8558 | 하드포맷 질문 [3] | 포메 | 2195 | 11-01 |
8557 | ThinkPad Bios | 훈이 | 2753 | 11-01 |
8556 | 마지막 지푸라기라도 잡는 심정으로 문의 드립니다. [4] | 김진명 | 3225 | 11-01 |
8555 | grub4 사용해 xp 설치 가능한가요? [3] | 짐승성주 | 2209 | 11-01 |
8554 | 윈포분들은 백신 어떤거 사용하시나요?? [4] | Wide | 2409 | 11-01 |
8553 | usb로 윈7 설치시 [3] | 서태지 | 2523 | 11-01 |
8552 | ko_win7_x64_ultimate_retail_msdn_dvd.iso [3] | 서태지 | 3635 | 11-01 |
8551 | 혹시 NTDLL 에러 나시는분 있나요? | 손정섭 | 2387 | 10-31 |
8550 | 다들 음악재생프로그램 어떤거 쓰시나요~? [9] | 명후이 | 2330 | 10-31 |
8549 | 윈도우7 원래 램사용 많이하나요? [10] | 쏘갈 | 3250 | 10-31 |
8548 | [질문] 키재입력시간 및 파일이동시간 [1] | 조영식 | 1828 | 10-31 |
8547 | 여러분들의 운영체제는 무엇입니까? [3] | 서태지 | 1810 | 10-31 |
8546 | 창 닫힐떄 이상합니다... [1] | Jon.KoNeo | 1983 | 10-31 |
이같은 경우는 대부분 메모리불량 과 하드불량으로 나타나는 현상같습니다
저도 처음 이런경우을 많이접했는데요 메모리 하드디스크 교체후 아무런 증상이 안나타나더군요