서버 / 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 | - | - |
| 45293 | 윈 도 우| 윈도우디펜더 오류현상 [5] | eight7 | 1797 | 01-09 |
| » | 서버 / IT| 윈도우2008 R2 블루스크린 후 자동 종료가 안되요...(덤프... [2] | 희재아빠 | 2076 | 01-09 |
| 45291 | 하드웨어| 13인치 노트북 추천 부탁드립니다.. [2] | 보이져125 | 1379 | 01-09 |
| 45290 | 윈 도 우| MPEG4인가 이건 DXVA 가속이 안되나보죠. [4] | 닭그네 | 1267 | 01-09 |
| 45289 | 윈 도 우| 윈도우7 블루스크린 질문(동영상 유) [4] | 졸려요 | 1912 | 01-09 |
| 45288 | 하드웨어| p4 3.0 / 램 1기가인데, 질문이요. [11] | 꿈꾼사람 | 1545 | 01-09 |
| 45287 | 하드웨어| SSD문제인지 파워 문제인지 헷갈립니다..ㅜㅜ [2] | 풍운의별 | 1208 | 01-09 |
| 45286 | 소프트웨어| Buffer overrun detected! (acdsee 7) 도와주세요 [2] | 항상같음 | 2467 | 01-09 |
| 45285 | 기 타| 다음 문자열을 환경변수로 저장하는 배치구문좀 가르쳐주세... [5] | .NET | 989 | 01-09 |
| 45284 | 윈 도 우| 인증이 된건가요? 안된건가요? [5] | Darcy | 1651 | 01-09 |
| 45283 | 기 타| 천사박스 비밀번호 변경후 로그인 불가.. [2] | joyfuI | 1783 | 01-09 |
| 45282 | 소프트웨어| 울트라iso에서 용량큰 usb하드 인식방법이 궁금합니다. [12] | 루팅걸 | 2466 | 01-09 |
| 45281 | 소프트웨어| 동영상 잘라내는 프로그램 중에... [6] | 해피그라 | 2843 | 01-09 |
| 45280 | 기 타| dll로 묶여있는 아이콘들은 어떻게 수정하나요? [3] | 클라크 | 1104 | 01-09 |
| 45279 | 윈 도 우| 프로그램이 실행이 안돼서 질문드려요... [5] | 바보에이스 | 1851 | 01-09 |
| 45278 | 윈 도 우| 바탕화면 폴더 관련 오류수정 방법 좀.... [5] | 땡땡이 | 1645 | 01-09 |
| 45277 | 윈 도 우| 제발요!! 인증문제 [8] | 나잘난 | 1914 | 01-09 |
| 45276 | 윈 도 우| 윈도우 8.1 일부 앱 실행 및 설치 불가 어떻게 해결하나요? | 은주리사나 | 2077 | 01-09 |
| 45275 | 소프트웨어| 오피스 2010설치할때 다음 항목을 설치전에 미리 설정할수 ... [2] | .NET | 1420 | 01-09 |
| 45274 | 윈 도 우| 프리모캐시 0.92베타버전 | 푸른푸른 | 1437 | 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. 원하는 계정 유형을 선택한 다음 계정 유형 변경을 클릭합니다.