Sapphire Vapor-x HD 5770: Blocco/errato funzionamento dei driver.

[frakka]

Lillo prova a dare un pelo di volt in più alle ram, probabilmente il problema è lì e la vga non c'entra nulla.

[Lillo]

Lillo prova a dare un pelo di volt in più alle ram, probabilmente il problema è lì e la vga non c'entra nulla.

grazie frakka...quale voltaggio aumento?? ne ho 4:

DRAM data REF (CHA)
DRAM ctrl REF (CHA)
DRAM data REF (CHB)
DRAM ctrl REF (CHB)

[frakka]

Ehm... Boh!

Quei parametri dovrebbero riferirsi al ChannelA e ChannelB quindi una volta individuato il parametro lo setti uguale su ChannelA e ChannelB.
Il parametro cui mi riferivo è la tensione di alimentazione e dovrebbe aggirarsi nell'intorno di 1,8V-1,9V

Aspè... Dal manuale della tua mobo nessuno dei due! Nel menù "Extreme Tweaker Menù" dovresti avere anche una voce "DRAM Voltage" impostata su [Auto] e che permette diversi valori.
Riferisciti al capitolo 3.3.23 del manuale della tua mobo.

Se controlli l'hardware monitor alla voce "Voltage Monitor" dovresti poter vedere il valore impostato attualmente per le tue RAM.

Voltage Monitor
CPU Voltage; CPU PLL Voltage; PCH Voltage; IMC Voltage; DRAM Voltage;
DRAM Termination Voltage; 3.3V Voltage; 5V Voltage; 12V Voltage
The onboard hardware monitor automatically detects the voltage output
through the onboard voltage regulators.

Da quel valore ci regoliamo. Però le tue ram dovrebbero lavorare @1,5V... Strano che non ce la facciano.

[blizzard]

Riporto anche qua quanto si evince dal file dmp relativo all'ultimo crash di oggi 19/04/2010

dopo circa 5-6 giorni, dove tutto ha funzionato senza prob, oggi si è ripresentato il problema di freez -blackscreen e successivo recupero di win e quindi blue scree.
Questi i dati del mess di errore:

Firma problema:
Nome evento problema: BlueScreen
Versione SO: 6.1.7600.2.0.0.256.1
ID impostazioni locali: 1040

Ulteriori informazioni sul problema:
BCCode: 116
BCP1: FFFFFA80048104E0
BCP2: FFFFF880044F802C
BCP3: 0000000000000000
BCP4: 0000000000000002
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

questo quanto riportato nel file di errore salvato in C:\windows\ minidump

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


Loading Dump File [C:\Windows\Minidump\041910-19734-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 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a09000 PsLoadedModuleList = 0xfffff800`02c46e50
Debug session time: Mon Apr 19 15:25:00.310 2010 (GMT+2)
System Uptime: 0 days 5:16:52.402
*********************************************************************
* 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, {fffffa80048104e0, fffff880044f802c, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.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 : atikmpag.sys ( atikmpag+602c )

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

attendo notizie
grazie

[Lillo]

Riporto anche qua quanto si evince dal file dmp relativo all'ultimo crash di oggi 19/04/2010

dopo circa 5-6 giorni, dove tutto ha funzionato senza prob, oggi si è ripresentato il problema di freez -blackscreen e successivo recupero di win e quindi blue scree.
Questi i dati del mess di errore:



questo quanto riportato nel file di errore salvato in C:\windows\ minidump




attendo notizie
grazie

blizzard abbiamo lo stesso identico problema!!! Io sto provando la soluzione di frakka che mi sembra piu logica...
...non ho chipset nvidia

[blizzard]

Sto aspettando la risposta,
sebbene i problemi siano simili lillo, non è detto che anche la causa lo sia, difatti non mi capitano frequentemente come con la precedente scheda.
c'è ancora il prob temp che non riesco a capire fra le varie cose....

[blizzard]

Sto ancora aspettando una risposta.
Giusto per riassumere:
oggi ho riportato la scheda indietro per l'RMA, loro iniziano ad essere restii ed ipotizzano sia difetto del mio sistema operativo (al solito ma è anche la 3 scheda che cambio)

Oltre alle schermate blu (di cui ho riportato ampiamente i resoconti relativi all'errore anche tramite il debugger di win) gli altri problemi riscontrati sono stati i seguenti:
- Temperature alte: a full load si sfiorano i 60-65°
- Ventola che al max aumenta la frequenza al 46% in full load
(sono stato costretto a settarla manualmente al 60% fisso con temp in full load di poco vicine ai 60°)

- Driver video che smette di funzionare e win7 ripristina
- Blocco del PC se avvio il programma Hardware monitor (ultima versione)

Attendo una vostra risposta
Grazie