Blue screeny i kilka innych problemów


(Kukulele23) #1

mianowicie mój komp to 


(falcon89) #2

Szukanie przyczyny BSOD-a za pomocą BlueScreenView

 

Logi należy umieszczać na http://www.wklej.org/


(Kukulele23) #3

Witam ciągle jak skończę grę albo od tak pojawiają się blue screeny oto kod błędu 

 

Podpis problemu:

  Nazwa zdarzenia problemu: BlueScreen

  Wersja systemu operacyjnego: 6.1.7600.2.0.0.256.1

  Identyfikator ustawień regionalnych: 1045

 

Dodatkowe informacje o problemie:

  BCCode: 3b

  BCP1: 00000000C0000005

  BCP2: FFFFF8000328E01E

  BCP3: FFFFF88009717C70

  BCP4: 0000000000000000

  OS Version: 6_1_7600

  Service Pack: 0_0

  Product: 256_1

 

 

 

a tutaj z programu odczytanie pliku dmp 

 

 

 

Microsoft ® Windows Debugger  Version 6.6.0003.5

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\Windows\Minidump\110614-60060-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 2

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

Windows Vista Kernel Version 7600 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255

Kernel base = 0xfffff80003252000 PsLoadedModuleList = 0xfffff8000348fe50

Debug session time: Thu Nov  6 19:17:21.722 2014 (GMT+1)

System Uptime: 0 days 3:58:02.705

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

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

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

Loading Kernel Symbols

Loading User Symbols

Loading unloaded module list

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

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

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

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 3B, {c0000005, fffff8000328e01e, fffff88009717c70, 0}

 

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

***                                                                   ***

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

*** WARNING: Unable to verify timestamp for hal.dll

*** ERROR: Module load completed but symbols could not be loaded for hal.dll

Probably caused by : ntoskrnl.exe ( nt+3c01e )

 

Followup: MachineOwner


 

 

Ja tego nie kumam wiec proszę o pomoc