서버 / IT 윈도우2008 R2 블루스크린 후 자동 종료가 안되요...(덤프분석 좀 해주세요.)
2014.01.09 18:36
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa802ca3d060, Physical Device Object of the stack
Arg3: fffff8800237f518, Functional Device Object of the stack
Arg4: fffffa8063b19700, The blocked IRP
Debugging Details:
------------------
***** 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!_IRP ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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!TRIAGE_9F_POWER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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!_IRP ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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!_IO_STACK_LOCATION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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!_IRP ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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!_IRP ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: nt
FAULTING_MODULE: fffff8000264d000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd5b
DRVPOWERSTATE_SUBCODE: 3
IRP_ADDRESS: fffffa8063b19700
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`0237f4c8 fffff800`027399c2 : 00000000`0000009f 00000000`00000003 fffffa80`2ca3d060 fffff880`0237f518 : nt!KeBugCheckEx
fffff880`0237f4d0 fffff800`026d8652 : fffff880`0237f600 fffff880`0237f600 00000000`00000001 00000000`00000000 : nt!wcsncat_s+0x1b57a
fffff880`0237f570 fffff800`026d84f6 : fffff800`02874f00 00000000`04bb3560 00000000`00000000 00000000`00000000 : nt!KeReleaseMutant+0xb22
fffff880`0237f5e0 fffff800`026d83de : 00000b43`24e91540 fffff880`0237fc58 00000000`04bb3560 fffff880`02359188 : nt!KeReleaseMutant+0x9c6
fffff880`0237fc30 fffff800`026d81c7 : 00000231`b5e509c1 00000231`04bb3560 00000231`b5e509f9 00000000`00000060 : nt!KeReleaseMutant+0x8ae
fffff880`0237fcd0 fffff800`026c4a2a : fffff880`02356180 fffff880`02361ec0 00000000`00000000 fffff800`027e4b90 : nt!KeReleaseMutant+0x697
fffff880`0237fd80 00000000`00000000 : fffff880`02380000 fffff880`0237a000 fffff880`0237fd40 00000000`00000000 : nt!KiCpuId+0x79a
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntkrnlmp.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
고수님들의 답변 기다리겠습니다.
댓글 [2]
| 번호 | 제목 | 글쓴이 | 조회 | 등록일 |
|---|---|---|---|---|
| [공지] | 질문과 답변 게시판 이용간 유의사항 | gooddew | - | - |
| 45306 | 윈 도 우| Gadget [2] | 겨울나그네 | 1012 | 01-10 |
| 45305 | 윈 도 우| vmware 윈도우설치후 백업하여 실컴설치가능한가요 [3] | 호산 | 1435 | 01-10 |
| 45304 | 윈 도 우| 마우스 드래그 색상 변경이 가능한가요?? [1] | 강태공져니 | 2245 | 01-10 |
| 45303 | 윈 도 우| 작업표시줄에 시작메뉴같은거 추가하고 싶은데요. [8] | 닭그네 | 1470 | 01-10 |
| 45302 | 소프트웨어| wim 파일을 마운트 해서 편집할수 있는 프로그램이 있나요? [5] | 한스 | 1723 | 01-10 |
| 45301 | 소프트웨어| Visual Studio 2013 [8] | 일자무식 | 1510 | 01-10 |
| 45300 | 윈 도 우| 윈도우7 64비트 IE11에서 한글명 파일 다운로드시 깨짐현상 [4] | 토발즈 | 28680 | 01-10 |
| 45299 | 윈 도 우| 크롬 업데이트후 마우스 제스츄어 작동 | 까막 | 1064 | 01-09 |
| 45298 | 윈 도 우| 순정 윈도우7 익스플로러 9 즐겨찾기에 대한민국 웹 사이트... [5] | 원이85 | 1628 | 01-09 |
| 45297 | 하드웨어| usb 쓰기 방지? [5] | 인빠 | 21892 | 01-09 |
| 45296 | 윈 도 우| 외장하드에 winpe 4 in 1 넣고 윈도우7 설치시... | 탑심 | 2408 | 01-09 |
| 45295 | 윈 도 우| 윈81에서 공인 인증서 갱신이 안됨니다. [5] | 좋은데이 | 2412 | 01-09 |
| 45294 | 기 타| avast 모바일 오진 문의 드립니다. [3] | Sapphire | 1251 | 01-09 |
| 45293 | 하드웨어| 메모리 오버클럭은 어떻게 하나요??? [4] | 대박상한가 | 1608 | 01-09 |
| 45292 | 윈 도 우| 윈도우디펜더 오류현상 [5] | eight7 | 1798 | 01-09 |
| » | 서버 / IT| 윈도우2008 R2 블루스크린 후 자동 종료가 안되요...(덤프... [2] | 희재아빠 | 2076 | 01-09 |
| 45290 | 하드웨어| 13인치 노트북 추천 부탁드립니다.. [2] | 보이져125 | 1380 | 01-09 |
| 45289 | 윈 도 우| MPEG4인가 이건 DXVA 가속이 안되나보죠. [4] | 닭그네 | 1268 | 01-09 |
| 45288 | 윈 도 우| 윈도우7 블루스크린 질문(동영상 유) [4] | 졸려요 | 1913 | 01-09 |
| 45287 | 하드웨어| p4 3.0 / 램 1기가인데, 질문이요. [11] | 꿈꾼사람 | 1546 | 01-09 |
run '!findthebuild -s 이게 뭘 리로드 하느건지.??
일단 알아보구요...
칩셋 드라이버 설치.. 네이버 검색 전원관련.. 윈도우 종료 문제..검색..
============================================
종료가 되지 않는문제와, 부팅후 실행속도가 느린점
===================================================================
작업방법 1. 타사 시작 프로그램 해제
작업방법 2. 업데이트 / 드라이버 업데이트
또한 필터 드라이버를 사용하는 프로그램 (예: 바이러스 백신, 원격 제어 및 백업 소프트웨어) 또한 최신으로 업데이트 하시기 바랍니다.
작업방법 3. 새 계정 만들기
Windows 7 및 기타 하위 버전에서 사용자 지정 설치를 통해서 Windows 8 을 설치한 경우라면 아래와 같이 새 계정을 만들어 보신 후 동일증상이 나타나는지 확인해보시기 바랍니다.
https://windows.microsoft.com/ko-KR/windows-8/create-user-account
1. 윈도우 로고키 + X키를 누른 후 제어판을 클릭합니다.
2. 사용자 계정 및 가족 보호 - 사용자 계정을 차례로 클릭하고 사용자 계정을 다시 클릭합니다.
3. 변경할 사용자 선택에서 변경할 계정을 선택 후 계정유형 변경을 클릭합니다.
4. 원하는 계정 유형을 선택한 다음 계정 유형 변경을 클릭합니다.