BugCheck 0x0000116 이 발생합니다 해결 방법은 없는지요?

Question

BugCheck 0x0000116 이 발생합니다 해결 방법은 없는지요?

익명

Bugcheck 0x0000116 이 발생합니다

BlueScreenView 의 블루스크린 분석 내용을 저장해서 복사한후 붙여넣기한 파일의 내용입니다

==================================================

Dump File : 082413-27250-01.dmp

Crash Time : 2013-08-24 오후 9:32:00

Bug Check String :

Bug Check Code : 0x00000116

Parameter 1 : fffffa80`092d7010

Parameter 2 : fffff880`07a1be30

Parameter 3 : ffffffff`c00000b5

Parameter 4 : 00000000`0000000a

Caused By Driver : dxgkrnl.sys

Caused By Address : dxgkrnl.sys+5d054

File Description : DirectX Graphics Kernel

Product Name : Microsoft® Windows® Operating System

Company : Microsoft Corporation

File Version : 6.1.7601.18126 (win7sp1_gdr.130409-1534)

Processor : x64

Crash Address : ntoskrnl.exe+75b80

Stack Address 1 :

Stack Address 2 :

Stack Address 3 :

Computer Name :

Full Path : C:\Windows\Minidump\082413-27250-01.dmp

Processors Count : 4

Major Version : 15

Minor Version : 7601

Dump File Size : 325,248

Dump File Time : 2013-08-24 오후 9:33:31

==================================================

dxgknl.sys 의 블루스크린 분석 내용을 저장해서 복사한후 붙여넣기한 파일의 내용입니다

==================================================

Filename : dxgkrnl.sys

Address In Stack : dxgkrnl.sys+5d054

From Address : fffff880`08653000

To Address : fffff880`08747000

Size : 0x000f4000

Time Stamp : 0x5164dc49

Time String : 2013-04-10 오후 12:28:09

Product Name : Microsoft® Windows® Operating System

File Description : DirectX Graphics Kernel

File Version : 6.1.7601.18126 (win7sp1_gdr.130409-1534)

Company : Microsoft Corporation

Full Path : C:\Windows\system32\drivers\dxgkrnl.sys

==================================================

Filename dxgmms1.sys 의 블루스크린 분석 내용을 저장해서 복사한후 붙여넣기한 파일의 내용입니다

==================================================

Filename : dxgmms1.sys

Address In Stack : dxgmms1.sys+ff13

From Address : fffff880`08747000

To Address : fffff880`0878d000

Size : 0x00046000

Time Stamp : 0x5164dc13

Time String : 2013-04-10 오후 12:27:15

Product Name : Microsoft® Windows® Operating System

File Description : DirectX Graphics MMS

File Version : 6.1.7601.18126 (win7sp1_gdr.130409-1534)

Company : Microsoft Corporation

Full Path : C:\Windows\system32\drivers\dxgmms1.sys

==================================================

Filename nvlddmkm.sys의 블루스크린 분석 내용을 저장해서 복사한후 붙여넣기한 파일의 내용입니다

==================================================

Filename : nvlddmkm.sys

Address In Stack : nvlddmkm.sys+13be30

From Address : fffff880`078e0000

To Address : fffff880`083c5000

Size : 0x00ae5000

Time Stamp : 0x51c41788

Time String : 2013-06-21 오후 6:06:16

Product Name : NVIDIA Windows Kernel Mode Driver, Version 320.49

File Description : NVIDIA Windows Kernel Mode Driver, Version 320.49

File Version : 9.18.13.2049

Company : NVIDIA Corporation

Full Path : C:\Windows\system32\drivers\nvlddmkm.sys

==================================================

이벤트 뷰어의 내용을 복사해서 올립니다

수준 날짜 및 시간 원본 이벤트 ID 작업 범주

오류 2013-08-24 오후 9:33:33 BugCheck 1001 없음

일반

컴퓨터가 오류 검사 후 다시 부팅되었습니다. 오류 검사: 0x00000116 (0xfffffa80092d7010, 0xfffff88007a1be30, 0xffffffffc00000b5, 0x000000000000000a). 덤프 저장 위치: C:\Windows\MEMORY.DMP. 보고서 ID: 082413-27250-01

WinDbg 로 파일 열어서 분석한 내용을 복사한거를 밑에 복사해서 붙여넣기 합니다

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

Loading Dump File [C:\Users\林採善\Desktop\bbb\082413-27250-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

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7601.18205.amd64fre.win7sp1_gdr.130708-1532

Machine Name:

Kernel base = 0xfffff8000324b000 PsLoadedModuleList = 0xfffff8000348e6d0

Debug session time: Sat Aug 24 21:32:00.200 2013 (UTC + 9:00)

System Uptime: 0 days 8:17:18.262

*********************************************************************

* 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

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Loading Kernel Symbols

...............................................................

................................................................

.............................................

Loading User Symbols

Loading unloaded module list

................

Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for dxgkrnl.sys

*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80092d7010, fffff88007a1be30, ffffffffc00000b5, a}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for nvlddmkm.sys

*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.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 ***

*** ***

*************************************************************************

Probably caused by : nvlddmkm.sys ( nvlddmkm+13be30 )

Followup: MachineOwner

CPU는 I5 760 2.80GHz

GPU는 그래픽 카드NIDIA GeForce GTX 460

GPU정보가 부족해서 사진으로 올립니다

잠긴 질문. 이 질문은 Microsoft 지원 커뮤니티에서 마이그레이션되었습니다. 질문이 도움이 되었는지 여부에 대해 응답할 수는 있지만, 메모나 회신을 추가하거나 질문을 따를 수는 없습니다.

댓글 0개

답변 1개

Answer 1

그래픽카드 부분에서 에러가 나네요..

그래픽카드 드라이버를 최신 버전으로 설치를 해보는 것이 좋겠습니다.

부팅시 해당 제조회사의 드라이버를 읽는데...

이 부분에서 오류가 나는 것 같거든요

nvida 에서 최신 드라이버의 설치된 드라이버를 비교해서

최신 것으로 바꾸어 보세요..

다음을 통해 공유

BugCheck 0x0000116 이 발생합니다 해결 방법은 없는지요?

답변 1개