Bluescreen BCCode:116

Oprogramowanie komputerowe Windows 7
#1

Cześć,

Dziś przy włączaniu kopmutera, nagle się zrstartował po ponownym uruchomieniu miałem komunikat o bluescreenie . Poniżej cała zawartość komunikatu:

Podpis problemu:
Nazwa zdarzenia problemu: BlueScreen
Wersja systemu operacyjnego: 6.1.7601.2.1.0.768.3
Identyfikator ustawień regionalnych: 1045

Dodatkowe informacje o problemie:
BCCode: 116
BCP1: FFFFFA800AB0D010
BCP2: FFFFF8800FB67264
BCP3: FFFFFFFFC00000B5
BCP4: 000000000000000A
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Pliki pomagające opisać problem:
C:\Windows\Minidump\091422-10998-01.dmp
C:\Users\Admin\AppData\Local\Temp\WER-17362-0.sysdata.xml

Przeczytaj w trybie online nasze zasady zachowania poufności informacji:
Oświadczenie o ochronie prywatności w systemie Windows 7

Jeśli zasady zachowania poufności informacji w trybie online nie są dostępne, przeczytaj nasze zasady zachowania poufności informacji w trybie offline:
C:\Windows\system32\pl-PL\erofflps.txt

Wyczytałem tu na forum, aby pobrać Bluescreenview ale nie potrafie tego odczytać.

Pomożecie??:slight_smile: Poniżej treść:

image
image498×699 25.8 KB

#2

Błąd na poziomie kernela. Spróbuj coś więcej wyciągnąć za pomocą WinDbg. Tutaj moja walka z niebieskim ekranem, który powstawał również na poziomie kernela Niebieski ekran **INTERNAL_POWER_ERROR** (czyli jak dowiedzieć się więcej z pliku dump z bluescreen'a) - #14 przez Bradlee spróbuj przeprowadzić podobną analizę.

#3

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\091422-10998-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.24511.amd64fre.win7sp1_ldr_escrow.190729-1700
Machine Name:
Kernel base = 0xfffff80002e4f000 PsLoadedModuleList = 0xfffff80003088c90
Debug session time: Wed Sep 14 12:13:40.196 2022 (GMT+2)
System Uptime: 0 days 0:00:24.960

  • 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, {fffffa800ab0d010, fffff8800fb67264, 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 ***

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

Probably caused by : nvlddmkm.sys ( nvlddmkm+d4a264 )

Followup: MachineOwner

Taką analize dał mi program… za cholere nie potrafie tego ogarnąć

#4

Niestety nie wiem o co chodzi :thinking:

#5

Sterownik NVIDII. Może przeinstaluj obecny sterownik? Lub zainstaluj nowszy?