GTX 680, trasigt? Drivrutin slutade fungera, blåskärm

Trädvy Permalänk
Medlem
Plats
Kalmar
Registrerad
Jul 2011

GTX 680, trasigt? Drivrutin slutade fungera, blåskärm

Hej!

Jag köpte förra veckan ett Gainward GeForce GTX 680 4GB Phantom
http://www.komplett.se/k/ki.aspx?sku=749601

Efter en dag fick jag första felet, skärmen svartnade och datorn hängde sig några sekunder, och sen kom det en ruta som talade om att nVidias drivrutin hade slutat att fungera.
Startade om datorn och donade lite så fungerade det igen,

Efter ett par dagar till så kom det igen, men mycket värre, datorn hängde sig i 30 sekunder och sen kom det blåskärm
Har dumpfilen, men fattar inte ett smack av den.

Jag har läst lite att det kan bero på fel i registret, eller att den får för lite ström om det är fabriksöverklockat.
Jag funderar på om det är värt att prova lite olika saker (tips på vad man kan testa?)
Eller om jag helt enkelt bara ska skicka tillbaka det RMA?

* Fractal Design R5 * ASUS Swift PG278QR * MSI Z170A GAMING M7 * Intel Core i7 6700K / NZXT Kraken x61 * ASUS GTX 1080 Ti Strix OC* Corsair Vengeance LPX Black DDR4 2x8GB 3000MHz * EVGA SuperNova 850W G2 * Samsung SSD PRO 850-Series 250GB * Samsung SSD EVO 850-Series 1TB * Windows 10 Pro -64bit * Objetive Designs O2+ODAC * Philips Fidelio X2 + AntLion MicMod V4

Trädvy Permalänk
Medlem
Plats
Kalmar
Registrerad
Jul 2011

Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\081512-10108-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`03262000 PsLoadedModuleList = 0xfffff800`034a6670
Debug session time: Wed Aug 15 21:49:20.383 2012 (UTC + 2:00)
System Uptime: 0 days 12:42:07.554
*********************************************************************
* 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
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff88102b7aae0, 2, 1, fffff8800171faf2}

*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : tcpip.sys ( tcpip+63af2 )

Followup: MachineOwner
---------

* Fractal Design R5 * ASUS Swift PG278QR * MSI Z170A GAMING M7 * Intel Core i7 6700K / NZXT Kraken x61 * ASUS GTX 1080 Ti Strix OC* Corsair Vengeance LPX Black DDR4 2x8GB 3000MHz * EVGA SuperNova 850W G2 * Samsung SSD PRO 850-Series 250GB * Samsung SSD EVO 850-Series 1TB * Windows 10 Pro -64bit * Objetive Designs O2+ODAC * Philips Fidelio X2 + AntLion MicMod V4

Trädvy Permalänk
Medlem
Plats
Tungelsta
Registrerad
Okt 2004

testa äldre drivrutin kanske, eller nyare..
Det är nog inte grafikkortet det är fel på.

[Nanoxia Deep Silence 1][Intel i5 2550K] [ASUS P8Z77-V [16Gb DDR3 G.Skill Ripjaws X] [OCZ Agillity 3 90GB] [WD Black 1.0TB] [XFX HD7970 DD GHZ-Edition] [LG 27" IPS] [BOSE 2.1 system] [BeQuiet Straight Power 680W 80+ Gold Modular] [Qpad QH-90 Headset]

Trädvy Permalänk
Medlem
Plats
Kalmar
Registrerad
Jul 2011
Skrivet av prOZac:

testa äldre drivrutin kanske, eller nyare..
Det är nog inte grafikkortet det är fel på.

Jag har de senaste WHQL drivarna. Ska man testa senaste BETA kanske? Känns ju inte så stabilt ?

* Fractal Design R5 * ASUS Swift PG278QR * MSI Z170A GAMING M7 * Intel Core i7 6700K / NZXT Kraken x61 * ASUS GTX 1080 Ti Strix OC* Corsair Vengeance LPX Black DDR4 2x8GB 3000MHz * EVGA SuperNova 850W G2 * Samsung SSD PRO 850-Series 250GB * Samsung SSD EVO 850-Series 1TB * Windows 10 Pro -64bit * Objetive Designs O2+ODAC * Philips Fidelio X2 + AntLion MicMod V4

Trädvy Permalänk
Medlem
Plats
Scandinavium
Registrerad
Sep 2002

AMD FX53 939 | MSI nForce4 939 | Ati Radeon x1800XT OC PE | 2*1024mb G-Skill 1-2-3-2-5 | Comhem 10/1 | Frölunda Indians SM GULD!!!
In Hoc Signo Vinces!

Trädvy Permalänk
Medlem
Plats
Kalmar
Registrerad
Jul 2011

Testar nu med Beta 304.79, har installerat om kortet igen, och även kört Registry cleaner. Om detta inte fungerar så är väl nästa steg att installera om Windows, men det vete fasen om man pallar, har redan fått godkänd RMA retur, men testar några dagar till i alla fall.

* Fractal Design R5 * ASUS Swift PG278QR * MSI Z170A GAMING M7 * Intel Core i7 6700K / NZXT Kraken x61 * ASUS GTX 1080 Ti Strix OC* Corsair Vengeance LPX Black DDR4 2x8GB 3000MHz * EVGA SuperNova 850W G2 * Samsung SSD PRO 850-Series 250GB * Samsung SSD EVO 850-Series 1TB * Windows 10 Pro -64bit * Objetive Designs O2+ODAC * Philips Fidelio X2 + AntLion MicMod V4

Trädvy Permalänk
Medlem
Plats
Helsingborg
Registrerad
Dec 2008

Testat kortet i en annan dator?

Stationär " Annihilator" : i7 930 @ 4Ghz | EVGA GTX 1070 FTW
LAPTOP "Skyline" i7 6700HQ | GTX 950
Kamera : Canon 70D, Canon 550D och DJI Phantom 2 vision +

Bilen: V50 Classic
Lek bilen: SKYLINE R33

Trädvy Permalänk
Medlem
Plats
Jkpg
Registrerad
Jun 2011
Skrivet av DeFeCT79:

Hej!

Jag köpte förra veckan ett Gainward GeForce GTX 680 4GB Phantom
http://www.komplett.se/k/ki.aspx?sku=749601

Efter en dag fick jag första felet, skärmen svartnade och datorn hängde sig några sekunder, och sen kom det en ruta som talade om att nVidias drivrutin hade slutat att fungera.
Startade om datorn och donade lite så fungerade det igen,

Efter ett par dagar till så kom det igen, men mycket värre, datorn hängde sig i 30 sekunder och sen kom det blåskärm
Har dumpfilen, men fattar inte ett smack av den.

Jag har läst lite att det kan bero på fel i registret, eller att den får för lite ström om det är fabriksöverklockat.
Jag funderar på om det är värt att prova lite olika saker (tips på vad man kan testa?)
Eller om jag helt enkelt bara ska skicka tillbaka det RMA?

Har du senaste bios till ditt moderkort? Vet många som har haft problem med detta. Dock mest de med z77 moderkort och PCIE 3.0 men det skadar ju inte att prova.

ASUS Maximus VIII Hero | i7 6700K @ stock | ASUS GTX 1080 Strix | 32 GB Corsair Vengeance LPX 2666MHz | Samsung 850 Pro 256GB | Intel 520 240GB SSD | Seagate Barracuda Green 2TB | EVGA Supernova G2 750W | Corsair 400Q |

Trädvy Permalänk
Medlem
Plats
Kalmar
Registrerad
Jul 2011

Japp, nyaste BIOS installerat

Den fungerat klanderfritt i typ 6-8 månader, inte en enda gång har den hängt sig innan jag satte i det nya 680-kortet
Och lite svårt tyvärr att testa med annan dator, då det tog 2 dagar mellan de gånger den hängde sig och fick blåskärm

* Fractal Design R5 * ASUS Swift PG278QR * MSI Z170A GAMING M7 * Intel Core i7 6700K / NZXT Kraken x61 * ASUS GTX 1080 Ti Strix OC* Corsair Vengeance LPX Black DDR4 2x8GB 3000MHz * EVGA SuperNova 850W G2 * Samsung SSD PRO 850-Series 250GB * Samsung SSD EVO 850-Series 1TB * Windows 10 Pro -64bit * Objetive Designs O2+ODAC * Philips Fidelio X2 + AntLion MicMod V4

Trädvy Permalänk
Medlem
Plats
Umeå
Registrerad
Apr 2005

Jag lider av ungefär samma problem mitt Asus GTX 680 DC2 Top 2gb.
Någon blåskärm har jag inte lyckats åstakomma, men däremot att skärmen svartnar i några sekunder och hoppar ut till Windows.
Klockar man ner kortet med hjälp utav Asus GPU Tweak (Gainward har väl något liknande program?) så händer problemet inte lika ofta.
Men det är ganska irriterande att man inte kan använda kortet fullt ut. Tanken är väl att man ska överklocka med hjälp utav GPU Tweak. Klockar jag upp mitt kort så tar det inte många sekunder i krävande spel innan skärmen svartnar, drivrutinerna startar om, spelet hänger sig och man blir utslängd till Windows.
Ska göra några tester i 3Dmark med både underklockat kort, stock och OC. Fungerar 3dmark i OC läge så är det knappast kortet det är fel på.
Återkommer med resultat.