BlueScreen

[erfix]

Siema

Mam problem

brat zainstalował WOW'a i do tego sterowniki nividy dla grafiki

zaraz po tym pojawil się bulescreen ;/

próbowałem zrobić formata ale to nic nie daje, system sie isntaluje Win7 ale po restarcie pojawaia sie bluescreen i za 4 może 5 restartem system się włącza z takim bledem :

 

Podpis problemu:

Nazwa zdarzenia problemu: BlueScreen

Wersja systemu operacyjnego: 6.1.7601.2.1.0.256.1

Identyfikator ustawień regionalnych: 1045

Dodatkowe informacje o problemie:

BCCode: 1000007e

BCP1: FFFFFFFFC0000005

BCP2: 0000000000000000

BCP3: FFFFF88002FB98E8

BCP4: FFFFF88002FB9140

OS Version: 6_1_7601

Service Pack: 1_0

Product: 256_1

Pliki pomagające opisać problem:

C:\Windows\Minidump\021212-16536-01.dmp

C:\Users\bien\AppData\Local\Temp\WER-113490-0.sysdata.xml

Przeczytaj w trybie online nasze zasady zachowania poufności informacji:

http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0415

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

 

Próbowałem załadaować jakiegoś linuxa ale za każdym razezm wystakiwal mi Error że brak tam czegoś gdzie na innych kompac smigało normalnie

 

próbowałem tez wymienić dysk ale dzieje się tak z każdym (bylo ich 8 i wszystkie sata)

 

o co moze biegac z tym?

 

Sory za błedy ale pisze z tel;/

 

z góry dzięki za pomoc

 

 

 

EDIT

 

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64

Copyright © Microsoft Corporation. All rights reserved.

 

Loading Dump File [C:\Windows\Minidump\021212-16536-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 (2 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850

Machine Name:

Kernel base = 0xfffff800`0264c000 PsLoadedModuleList = 0xfffff800`02891e90

Debug session time: Sun Feb 12 00:44:43.385 2012 (UTC + 1:00)

System Uptime: 0 days 0:00:14.289

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

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

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, 0, fffff88002fb98e8, fffff88002fb9140}

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

*** ***

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

Probably caused by : nvlddmkm.sys ( nvlddmkm+5a0b7e )

Followup: MachineOwner

---------

 

z tego co wyczytałem to jest coś nie tak grafka ale nic wiecej nie wiem

[Flavius]

C:\Windows\Minidump\021212-16536-01.dmp

 

Spakuj pliki z tego folderu,shostuj gdzieś i daj tutaj linka do nich

 

Co do kodu 0x1000007e to jest on równoznaczny z kodem 0x7e a przyczyny różne karta grafiki,BIOS,pamięć...

 

http://www.carrona.org/bsodindx.html#0x1000007E

http://www.carrona.org/bsodindx.html#0x0000007E