Niespodziewany reset.

[Karhu15]

Witam. Mam problem gdyż podczas grania mój komputer się restartuje.Oto informacje z "WinDbg".

 

1.

Microsoft ® Windows Debugger Version 6.3.9600.16384 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:WindowsMinidump040713-34538-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 SystemRootsystem32ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`03018000 PsLoadedModuleList = 0xfffff800`0325c670
Debug session time: Sun Apr  7 12:36:33.374 2013 (UTC + 1:00)
System Uptime: 0 days 5:00:32.665
*********************************************************************
* 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 SystemRootsystem32ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.....

************* Symbol Loading Error Summary **************
Module name   Error
ntoskrnl The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*******************************************************************************
* *
*   Bugcheck Analysis   *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c000001d, fffffa800540b88e, fffff88002bd6e10, 0}

***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
***   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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
***   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 ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+75c40 )

Followup: MachineOwner

 

2.

Microsoft ® Windows Debugger Version 6.3.9600.16384 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:WindowsMinidump101013-32385-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 SystemRootsystem32ntoskrnl.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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Machine Name:
Kernel base = 0xfffff800`03255000 PsLoadedModuleList = 0xfffff800`034986d0
Debug session time: Thu Oct 10 17:04:59.997 2013 (UTC + 1:00)
System Uptime: 0 days 0:17:24.542
*********************************************************************
* 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 SystemRootsystem32ntoskrnl.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
.....

************* Symbol Loading Error Summary **************
Module name   Error
ntoskrnl The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*** 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, {fffffa80062294e0, fffff88007431378, 0, d}

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

*************************************************************************
*** ***
*** ***
***   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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
***   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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
***   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 ***
*** ***
*************************************************************************
Probably caused by : nvlddmkm.sys ( nvlddmkm+135378 )

Followup: MachineOwner

 

 

Proszę o pomoc.

Edytowane 4 Kwietnia 2014 przez Klaus
log dałem w spoiler

[Klaus]

Proszę: Zanim cokolwiek napiszesz..

[Dijkstra]

Brak jakichkolwiek informacji - konfiguracja komputera, kiedy się restartuje etc.

Błąd powoduje prawdopodobnie sterownik ekranu (nvidia), ale dlaczego tak się dzieje? Hmmm...

 

[Karhu15]

Parametry:
Płyta główna: Urtla Durable 3 classic   MA785GT-UD3H

Karta graficzna: GIGABYTE GTX 260

Zasilacz: OCZ MOD X STREAM-PRO POWER SUPPLY M009

Zainstalowana pamięć ram : 4 GB

Procesor: Amd Phenom™ II X4 955 prosessor 3.62 GHz

 

Podczas grania następuje reset.

Edytowane 29 Marca 2014 przez Karhu15

[Karhu15]

Witam. Mam problem gdyż podczas grania mój komputer się restartuje.Oto informacje z "WinDbg".

 

 

1.

Microsoft ® Windows Debugger Version 6.3.9600.16384 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:WindowsMinidump040713-34538-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 SystemRootsystem32ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`03018000 PsLoadedModuleList = 0xfffff800`0325c670
Debug session time: Sun Apr  7 12:36:33.374 2013 (UTC + 1:00)
System Uptime: 0 days 5:00:32.665
*********************************************************************
* 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 SystemRootsystem32ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.....

************* Symbol Loading Error Summary **************
Module name   Error
ntoskrnl The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*******************************************************************************
* *
*   Bugcheck Analysis   *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c000001d, fffffa800540b88e, fffff88002bd6e10, 0}

***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
***   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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
***   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 ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+75c40 )

Followup: MachineOwner

 

2.

Microsoft ® Windows Debugger Version 6.3.9600.16384 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:WindowsMinidump101013-32385-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 SystemRootsystem32ntoskrnl.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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Machine Name:
Kernel base = 0xfffff800`03255000 PsLoadedModuleList = 0xfffff800`034986d0
Debug session time: Thu Oct 10 17:04:59.997 2013 (UTC + 1:00)
System Uptime: 0 days 0:17:24.542
*********************************************************************
* 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 SystemRootsystem32ntoskrnl.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
.....

************* Symbol Loading Error Summary **************
Module name   Error
ntoskrnl The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*** 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, {fffffa80062294e0, fffff88007431378, 0, d}

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

*************************************************************************
*** ***
*** ***
***   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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
***   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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
***   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 ***
*** ***
*************************************************************************
Probably caused by : nvlddmkm.sys ( nvlddmkm+135378 )

Followup: MachineOwner

 

 

 

Parametry komputera:
Płyta główna: Urtla Durable 3 classic   MA785GT-UD3H

Karta graficzna: GIGABYTE GTX 260

Zasilacz: OCZ MOD X STREAM-PRO POWER SUPPLY M009

Zainstalowana pamięć ram : 4 GB

Procesor: Amd Phenom™ II X4 955 prosessor 3.62 GHz

 

Podczas grania następuje reset.

Call

Send SMS

Add to Skype

You'll need Skype CreditFree via Skype

Edytowane 4 Kwietnia 2014 przez Klaus
logi w spoiler

[reyden]

Z tego co widzę problemem może być karta albo jej sterowniki .

 

Wrzuć najnowsze sterowniki , a jak masz najnowsze to spróbuj starszych .

 

Jaka jest temperatura karty - ściągnij GPU-Z i pokaż screena zakładki sensors .

 

Możesz też włączyć zapisywanie pliku log i zawartość loga wstawić na forum , tylko tym razem użyj tagów spoiler .

[ajayeti]

Czy to czasem nie ta karta, której nie możesz rozebrać w innym temacie?

[Karhu15]

Tak to ta karta "problemowa". Ojj są z nią przeboja w końcu staruszek ma z 5-7 lat.

Instalowałem sterowniki z płyty w zestawe z kartą i nadal występował problem a co to ten "plik log"

[MiG29]

Zasilacz też ma 5-7 lat?

[Karhu15]

Nie.Tylko karta taka stara a takto wszystko ma po 3-4 lata.

[szpachla2]

Jakie temperatury masz?

[Karhu15]

Karta po resecie wynosiła okoo 60*C.

[Klaus]

Na dzień dobry to odkręć procesor na domyślne takty. Najlepiej zrób clear cmos lub "Load Optimized Defaults" w biosie. 

[Karhu15]

Panowie jest jeszcze problem. Gdy karta graficzna jest podlaczona do komputera ten nie włączya się czyli:

 

Włączają się 2 wentylatory (bez głównego na chłodzeniu oraz bez tego na karcie graficznej).Komputer wydaje bardziej ciche dźwięki niż wcześniej. A na zintegrowanej grafice smiga piękinie.

[reyden]

Ten problem występował od początku czy pojawił się dopiero nie dawno .

 

Komp z tym GTX260 w ogóle nie startuje teraz ?

 

To może być oznaka tego że karta jednak dogorywa i niedługo pewno trafi do krainy wiecznych marków , jak już nie trafiła .

[Karhu15]

Tak z GTX'em nie startuje. A oroblem BYł już jakiś czas lecz jednak komputer czasami się włączał.

[reyden]

Jak jeszcze nie zrobiłeś tego to rozbierz kartę , przeczyść radiatory i nałóż nową pastę na rdzeń , choć wg. mnie to nie wiele pomoże.

 

Możesz spróbować też piekarnika , przy odrobinie szczęścia karta powinna podziałać jeszcze kilka m-cy po piekarniku jak wszystko zrobisz prawidłowo .

[Karhu15]

Jakiego "piekarnika"?

[reyden]

Karta może mieć tzw. zimne luty , z powodu zmniejszonej wytrzymałości stopu lutowniczego ( podziękuj ekologom za to ) często się zdarza że po jakimś czasie połączenia lutowane zawodzą i sprzęt przestaje pracować .

 

Popularnym , domowym sposobem na zimne luty jest wygrzanie karty w piekarniku , może to choć na jakiś czas "naprawić " kartę i sprawdzić że jeszcze trochę podziała .

 

Niestety jak to zrobić dokładnie i jak przygotować kartę to ci za bardzo nie powiem , poza tym że musisz zdemontować cały plastik z karty oraz chłodzenie .

[Dijkstra]

Oraz kondensatory - na pewno wszystkie nie solid state, a co do solid state, też nie wiem, jakie temperatury zniosą pasywnie.

[Karhu15]

Wszystko w pożądku. Rozumiem. Tylko że nie mogę zdjąć tej obudowy. BO prawdopodownie Pasta trzyma.

[Karhu15]

Teraz gdy nawet mam monitor podlaczony do zintegrowanej karty graf. to wystepuje problem z wlaczeniem sie komputera czyli:
Gdy włączam komputer włącza sie wsztstki nie licząc głównego wentylatora oraz nie ma sygnału do monitora.