블루스크린 원인 알아볼려고 도구까지 설치했는데 중요한게

슨스드™ · 2014.12.13 20:38:27

viewimage.php?id=39bcd53fe0dd369960bac1e4&no=29bcc427b08277a16fb3dab004c86b6fbdfe40db5e1cba5dfc855cf3ad402aae389abb3b839bc163864251ff9bd92eb4f9181a552c7396b2e5dfc4379d96

viewimage.php?id=39bcd53fe0dd369960bac1e4&no=29bcc427b08277a16fb3dab004c86b6fbdfe40db5e1cba5dfc855cf3ad402aae389abb3b839bc163864251ff9bd92eb4f91842557e22c3b5e6d8c4379d96

Microsoft (R) Windows Debugger Version 6.2.8400.0 AMD64

Loading Dump File [C:\Windows\MEMORY.DMP]

Kernel Complete Dump File: Full address space is 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+ *

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

*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -

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

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7601.22736.amd64fre.win7sp1_ldr.140706-1507

Machine Name:

Kernel base = 0xfffff800`03c1f000 PsLoadedModuleList = 0xfffff800`03e62890

Debug session time: Fri Dec 12 20:08:58.700 2014 (UTC + 9:00)

System Uptime: 0 days 0:00:12.386

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

* 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+ *

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

*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -

Loading Kernel Symbols

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

Loading User Symbols

Loading unloaded module list

.

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 74, {2, fffff88004d3eae0, 2, ffffffffc000009a}

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

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

*** ***

*** Either you specified an unqualified symbol, or your debugger ***

*** doesn't have full symbol information. Unqualified symbol ***

*** resolution is turned off by default. Please either specify a ***

*** fully qualified symbol module!symbolname, or enable resolution ***

*** of unqualified symbols by typing ".symopt- 100". Note that ***

*** enabling unqualified symbol resolution with network symbol ***

*** server shares in the symbol path may cause the debugger to ***

*** appear to hang for long periods of time when an incorrect ***

*** symbol name is typed or the network symbol server is down. ***

*** ***

*** For some commands 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 ***