서버 / 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 | - | - |
| 45559 | 윈 도 우| usb 이미지 기록 실패! | 천상기린아 | 2170 | 01-19 |
| 45558 | 윈 도 우| 윈도우즈 7과 8 을 명령으로 절전모드 안되게 하려면 어떻... [5] | 마져 | 2192 | 01-19 |
| 45557 | 윈 도 우| cmd, reg 파일이 노트패드로 열립니다. [3] | 야옹이언니 | 1427 | 01-19 |
| 45556 | 윈 도 우| 최대절전모드 파티션 질문 [3] | Zason | 4047 | 01-19 |
| 45555 | 기 타| aimp url열기는 어덯게 여나요?? [1] | ㄷㄱ | 1196 | 01-19 |
| 45554 | 기 타| 크롬 업데이트 이후 피그툴.. [2] | A/S | 1793 | 01-19 |
| 45553 | 윈 도 우| 노트북에서 사용중인 윈도우8 다른 컴에 설치 [6] | 금빛어둠 | 1883 | 01-18 |
| 45552 | 윈 도 우| windows 8 media center 인증된 것를 8.1 media center로 ... [1] | 소주 | 1527 | 01-18 |
| 45551 | 기 타| virtualbox에 ubuntu를 설치해보려하는데 에러가 납니다 [1] | bliss | 1260 | 01-18 |
| 45550 | 윈 도 우| 보드를 바꿔서 bios 개조를 했는데 인증이 자꾸 풀립니다 ㅠㅠ | 멀티링크 | 1958 | 01-18 |
| 45549 | 윈 도 우| 윈7에서는 사운드 볼륨 조절할때 8처럼 나오게 할 수 없나요?? [2] | TheOscar | 1193 | 01-18 |
| 45548 | 기 타| 트루이미지 2014 최신 버젼? [2] | DaBin | 2103 | 01-18 |
| 45547 | 소프트웨어| 로보폼(Ai Roboform)사용법 [2] | 소슬곡 | 2012 | 01-18 |
| 45546 | 윈 도 우| 패러럴 윈도우8.1 궁금한게 있는데요. [2] | 크로터 | 1175 | 01-18 |
| 45545 | 소프트웨어| 아크로니스 트루이미지 2014 프리미엄 세가지 문의 [8] | wuser2k | 1951 | 01-18 |
| 45544 | 윈 도 우| 긴급 - 인터넷이 안열려요 [12] | 낭만주의 | 2233 | 01-18 |
| 45543 | 하드웨어| 노트북 하드 맛탱이 좀 봐 주셔요....ㅎ [4] | 벗나무 | 1232 | 01-18 |
| 45542 | 기 타| sysprep CEO 에서... [1] | namurang | 3691 | 01-18 |
| 45541 | 소프트웨어| Sandboxie로 뱅킹은 이용못하나요? [2] | 원이85 | 1314 | 01-18 |
| 45540 | 윈 도 우| 윈도우 7 지원종료가... [19] | 흐흐흐 | 3878 | 01-18 |
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. 원하는 계정 유형을 선택한 다음 계정 유형 변경을 클릭합니다.