Sapphire Radeon HD5700 Aggiornamento BIOS - [FOCUS]

[blizzard]

E' necessario analizzare il file minidump che viene prodotto durante il crash del sistema. Le informazioni così come fornite non sono purtroppo significative.
Avete già provato a testare le ram di sistema?

c'è un modo per recuperare questo file?
le Ram sono apposto

[betaxp86]

E' dentro la cartella indicata nel log di errore C:\Windows\Minidump

[blizzard]

E' dentro la cartella indicata nel log di errore C:\Windows\Minidump

Purtroppo la cartella è vuota, probabile che win7 abbia cancellato le segnalazio errore durante una qualche procedura di manutenzione?
appena si ripresenterà il problema vedro di prendere tal file
(stranamente da quando ho settato la ventola al 60% non mi da piu alcun problema, circa 4 giorni)

[rubber24]

ciao ragazzi io ho una ati sapphire hd 5770 ma non è vapor x e vi spiego il mio problema oggi ho formattato il mio pc e ho istallato windows 7 64 bit e fin qui nessun problema
inizio a istallare i driver necessari ma quando vado ad istallare il driver video succede ke nel pannello della risoluzione video mi risluta ke le mie impostazioni consigliate sono 1920x1080 come giusto ke sia per mio schermo lg da 23 pollici w2361v ma la cosa strana è ke si vede male e ke il desktop non è grande quanto tutto lo schermo ma in torno vi è un bordo nero cosa ke con windows 7 32 bit non succedeva come mai qualkuno mi può aiutare?
vi comunico ke inoltre ke guardando sullo scatolo scopro ke i numeri della mia skeda
pn 288-1e147-001sa
sku 11163-02-21r
corrispondo a quelle delle skede con problemi bios come mai?

[Lillo]

Ma con Xp si presentano tutti sti BUG ?

[Lillo]

Come si leggono questi file? ne ho un po:
041210-25006-01.dmp 141 kB 12/04/10 13.35.23
041310-31137-01.dmp 412.3 kB 13/04/10 14.14.05
041310-31621-01.dmp 137 kB 13/04/10 13.24.43
041510-29437-01.dmp 134.3 kB 15/04/10 14.06.54

[betaxp86]

Qui puoi scaricare il tool per aprire questi file
http://www.microsoft.com/whdc/Devtoo...g/default.mspx

Scarica Install Debugging Tools for Windows 32-bit Version

Poi apri Windbg e fai open crash dump, alla fine dell'analisi sarà riportato il nome del file incriminato per il crash.

[blizzard]

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]

Qui puoi scaricare il tool per aprire questi file
Driver Developer Resources: Debugging Tools for Windows

Scarica Install Debugging Tools for Windows 32-bit Version

Poi apri Windbg e fai open crash dump, alla fine dell'analisi sarà riportato il nome del file incriminato per il crash.

Nulla...
...accesso negato...
...ma con XP ci sono gli stesi problemi?

[betaxp86]

Per l'analisi del DUMP è evidente che il problema è causato dai driver della VGA.
Prima di procedere con l'RMA dovresti:
Reinstallare l'OS con i driver 10.4 e riprovare.