Niebieski ekran


(Lexjakub) #1

Mam problem z moim pc, mianowicie jak gram w coś albo robie coś na kompie co wymaga więcej "mocy" komp gaśnie i pojawia się niebieski ekran śmierci. Tutaj wrzucam to co było w pliku .dmp

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86

Copyright (c) Microsoft Corporation. All rights reserved.



Loading Dump File [C]

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 argument when starting the debugger. *

* using .sympath and .sympath+ *

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

Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2

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

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

Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7601.17944.x86fre.win7sp1_gdr.120830-0333

Machine Name:

Kernel base = 0x82c3a000 PsLoadedModuleList = 0x82d844d0

Debug session time: Sat Jan 5 16:46:03.929 2013 (GMT+2)

System Uptime: 0 days 2:18:24.693

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

* 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 argument when starting the debugger. *

* using .sympath and .sympath+ *

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

Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2

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

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

Loading Kernel Symbols

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

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

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

Loading User Symbols

Loading unloaded module list

......

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

* *

* Bugcheck Analysis *

* *

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


Use !analyze -v to get detailed debugging information.


BugCheck D1, {d3c5ddc1, a, 8, d3c5ddc1}


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

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

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

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

******

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

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

* 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 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 argument when starting the debugger. *

* using .sympath and .sympath+ *

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

Probably caused by : dxgkrnl.sys ( dxgkrnl+1b14 )


Followup: MachineOwner

---------


1: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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


DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high. This is usually

caused by drivers using improper addresses.

If kernel debugger is available get stack backtrace.

Arguments:

Arg1: d3c5ddc1, memory referenced

Arg2: 0000000a, IRQL

Arg3: 00000008, value 0 = read operation, 1 = write operation

Arg4: d3c5ddc1, address which referenced memory


Debugging Details:

------------------


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

******

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

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

* 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 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 argument when starting the debugger. *

* using .sympath and .sympath+ *

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


ADDITIONAL_DEBUG_TEXT:  

Use '!findthebuild' command to search for the target build information.

If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.


MODULE_NAME: dxgkrnl


FAULTING_MODULE: 82c3a000 nt


DEBUG_FLR_IMAGE_TIMESTAMP: 4ce78ffe


READ_ADDRESS: unable to get nt!MmSpecialPoolStart

unable to get nt!MmSpecialPoolEnd

unable to get nt!MmPoolCodeStart

unable to get nt!MmPoolCodeEnd

 d3c5ddc1 


CURRENT_IRQL: 0


FAULTING_IP: 

+57e2952f0169def0

d3c5ddc1 ?? ???


CUSTOMER_CRASH_COUNT: 1


DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT


BUGCHECK_STR: 0xD1


LAST_CONTROL_TRANSFER: from d3c5ddc1 to 82c7acdb


FAILED_INSTRUCTION_ADDRESS: 

+57e2952f0169def0

d3c5ddc1 ?? ???


STACK_TEXT:  

WARNING: Stack unwind information not available. Following frames may be wrong.

807e3b5c d3c5ddc1 badb0d00 00000000 00000000 nt+0x40cdb

807e3bd8 93ca5b14 86a552c0 00000000 807e3bfc 0xd3c5ddc1

807e3be8 82cc4250 872dea00 869c34f0 00000000 dxgkrnl+0x1b14

807e3bfc 82c73e9d 872dea00 869c34f0 807e3c28 nt+0x8a250

807e3c28 9090dbb6 badb0d00 00000000 807e3c48 nt+0x39e9d

807e3d20 82cb158d 00000000 0000000e 7ecfbfcf amdk8+0x1bb6

807e3d24 00000000 0000000e 7ecfbfcf bfff775f nt+0x7758d

(rgabrysiak) #2

Cześć

Spróbuj zainstalować starsze bądź nowsze sterowniki do karty graficznej.

Sprawdź temperatury, być może komputer się przegrzewa i trzeba go wyczyścić.


(Lexjakub) #3

instalowałem, i cały czas jest to samo.. komp wyczyszczony.. może złe stery mam? karta to hd4850, masz może jakieś zarzucić? bo te z strony amd to lipa jest..


(rgabrysiak) #4

Cześć

Instalowałeś zarówno starsze jak i nowsze? Jeżeli tak spróbuj jeszcze zaktualizować DirectX.

Jeżeli masz możliwość przetestuj kartę graficzną na innym komputerze.


(Lexjakub) #5

Instalacja sterów po raz x10, dalej bez zmian


(rgabrysiak) #6

Masz zainstalowane wszystkie niezbędne aktualizacje do systemu?


(Lexjakub) #7

tak


(Agatonster) #8

Kunorator ,

Proszę zapoznaj się z tematem i popraw tytuł tematu na konkretny, mówiący o problemie. W celu dokonania zaleconej korekty proszę użyć przycisku Edytuj przy poście otwierającym ten temat.

Zignorowanie zalecenia będzie skutkowało przeniesieniem tematu do Kosza.