|
|||||||
|
|
|
 |
|
|
Strumenti |
07-11-2010, 13:57
|
#1 |
|
Senior Member
Iscritto dal: Sep 2003
Città: Belluno-Chieti
Messaggi: 3337
|
Problemi con il pc...schermo nero e riavvio
Salve a tutti,
da tempo mi si presenta il problema in oggetto ma non ho avuto mai tempo di vedere le sue cause... in questi giorni non sopporto più questa cosa e vorrei risolverla... Il mio pc è così configurato: CPU AMD Phenom II X3 720 Ram 4*1 Gb Scheda Madre Asrock A780GXH/128M Scheda Video Gainward GTS250 Alimentatore LC-Power 6550 HD Samsung HD753LJ HD Barracuda ST3250410AS HD WD5000AAKS A volte, improvvisamente, lo schermo diventa nero e la ventola della scheda video va al massimo oppure aumenta e diminuisce i suoi giri... Ho controllato le temperature è sono nella norma... Ho tolto la scheda video (GTS250) facendo andare il pc con la Ati HD3200 integrata ma questi problemi si presentano lo stesso... Ho provato a togliere le Ram (una per volta) e il problema si verifica ugualmente... Se non ricordo male, tempo fa, quando andava in crash compariva la schermata blu (per un attimo) con l'errore Physical Memory Dump o qualcosa di simile... Per favore mi date una mano? Sono disperato ed ho urgente bisogno di sistemarlo... Ringrazio anticipatamente chi mi aiuterà... |
|
|
|
07-11-2010, 17:08
|
#2 |
|
Senior Member
Iscritto dal: May 2003
Città: venezia
Messaggi: 18854
|
Errori del genere possono essere causati anche da driver difettosi o malfunzionanti . Visto che hai gia controllato sia le ram che la scheda video , e molto probabile che il problema derivi proprio da driver difettosi .
Per risolvere potresti propvare a reistallare windows in questo modo se i problemi sono dei driver verranno sistemati . |
|
|
|
|
07-11-2010, 17:22
|
#3 | |
|
Senior Member
Iscritto dal: Sep 2003
Città: Belluno-Chieti
Messaggi: 3337
|
Quote:
prima di formattare windows 7 proverei di nuovo con linux... |
|
|
|
|
|
09-11-2010, 19:17
|
#4 |
|
Senior Member
Iscritto dal: Sep 2003
Città: Belluno-Chieti
Messaggi: 3337
|
Una delle tante volte in cui si è riavviato mi ha dato questo errore:
Codice:
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: 1 BCP1: 000000007716FEBA BCP2: 0000000000000000 BCP3: 000000000000FFFF BCP4: FFFFF8800651ACA0 OS Version: 6_1_7600 Service Pack: 0_0 Product: 256_1 File che contribuiscono alla descrizione del problema: C:\Windows\Minidump\110910-20625-01.dmp C:\Users\xxxx\AppData\Local\Temp\WER-40843-0.sysdata.xml Leggere l'informativa sulla privacy online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0410 Se l'informativa sulla privacy online non è disponibile, leggere quella offline: C:\Windows\system32\it-IT\erofflps.txt |
|
|
|
|
09-11-2010, 21:06
|
#5 |
|
Bannato
Iscritto dal: Oct 2002
Messaggi: 29264
|
Che c'è scritto nel file
C:\Windows\Minidump\110910-20625-01.dmp ? |
|
|
|
|
10-11-2010, 20:06
|
#6 | |
|
Senior Member
Iscritto dal: Sep 2003
Città: Belluno-Chieti
Messaggi: 3337
|
Quote:
Da WinDbg mi viene fuori questo: Codice:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\110910-20625-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\Users\Alve\Desktop\Symbols1
Executable search path is:
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 (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c49000 PsLoadedModuleList = 0xfffff800`02e86e50
Debug session time: Tue Nov 9 20:11:53.531 2010 (UTC + 1:00)
System Uptime: 0 days 0:05:52.000
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 1, {7716feba, 0, ffff, fffff8800651aca0}
***** 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!_KTHREAD ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+70740 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->KernelApcDisable field. A negative value indicates that a driver
has disabled APC calls without re-enabling them. A positive value indicates
that the reverse is true. This check is made on exit from a system call.
Arguments:
Arg1: 000000007716feba, address of system function (system call)
Arg2: 0000000000000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex
Arg3: 000000000000ffff, Thread->KernelApcDisable
Arg4: fffff8800651aca0, Previous KernelApcDisable
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!_KTHREAD ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
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: nt
FAULTING_MODULE: fffff80002c49000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAULTING_IP:
+3564666661343331
00000000`7716feba ?? ???
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002cb8ca9 to fffff80002cb9740
STACK_TEXT:
fffff880`0651aa68 fffff800`02cb8ca9 : 00000000`00000001 00000000`7716feba 00000000`00000000 00000000`0000ffff : nt+0x70740
fffff880`0651aa70 00000000`00000001 : 00000000`7716feba 00000000`00000000 00000000`0000ffff fffff880`0651aca0 : nt+0x6fca9
fffff880`0651aa78 00000000`7716feba : 00000000`00000000 00000000`0000ffff fffff880`0651aca0 00000000`00000004 : 0x1
fffff880`0651aa80 00000000`00000000 : 00000000`0000ffff fffff880`0651aca0 00000000`00000004 00000000`00000000 : 0x7716feba
STACK_COMMAND: kb
FOLLOWUP_IP:
nt+70740
fffff800`02cb9740 48894c2408 mov qword ptr [rsp+8],rcx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt+70740
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntoskrnl.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
  Potrebbe essere l'alimentatore? |
|
|
|
|
|
10-11-2010, 20:45
|
#7 |
|
Bannato
Iscritto dal: Oct 2002
Messaggi: 29264
|
L'unica cosa che ho capito è stata
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT  Parrebbe un problema software. Hai installato qualche periferica con driver non specifici per 7? Cerca di aggiornare tutti i driver se puoi. Usi qualche programma/tool per ottimizzare il sistema o il disco fisso? Cercando su google (apc mismatch ntoskrnl) ho trovato alcune lamentele per un certo System Mechanic Pro 9. |
|
|
|
|
10-11-2010, 20:52
|
#8 | |
|
Senior Member
Iscritto dal: Sep 2003
Città: Belluno-Chieti
Messaggi: 3337
|
Quote:
Per ottimizzare il sistema non uso nulla... |
|
|
|
|
|
10-11-2010, 21:01
|
#9 |
|
Bannato
Iscritto dal: Oct 2002
Messaggi: 29264
|
Va la va la.
Comincia con chipset e sezione audio. Cosa hai attaccato alle usb oltre mouse/tastiera/stampante? |
|
|
|
|
10-11-2010, 21:21
|
#10 |
|
Senior Member
Iscritto dal: Jul 2010
Messaggi: 9326
|
Ciao,
anche in provvisoria si riavvia?
__________________
[CASE Cooler Master Silencio 550]-[MOBO Asrock Z68 Pro3]-[CPU Intel Core i7-2600K]-[RAM 8GB G.Skill]-[HDD 1TB Samsung + 320GB Samsung + 500GB Maxtor]-[VGA Zotac Geforce GTX 560 Ti]-[MASTERIZZATORE Samsung SH-S222AB][S.O. Windows 7 64 bit] |
|
|
|
|
10-11-2010, 23:16
|
#11 | |
|
Senior Member
Iscritto dal: Sep 2003
Città: Belluno-Chieti
Messaggi: 3337
|
Quote:
|
|
|
|
|
|
16-11-2010, 10:22
|
#12 |
|
Senior Member
Iscritto dal: Sep 2003
Città: Belluno-Chieti
Messaggi: 3337
|
scusate se rispondo solo adesso....
Ho notato che anche il bios emette beep che dovrebbe corrispondere a questo: 6 Brevi - Keyboard Controller A20 Error - Errore del controller A20 della tasatiera. 7 Brevi - Virtual Mode Exception Error - Il processore ha generato un errore. Potrebbe essere un errore del processore o della scheda madre. |
|
|
|
|
16-11-2010, 11:08
|
#13 |
|
Bannato
Iscritto dal: Oct 2002
Messaggi: 29264
|
Eh non è carino. Quanti beep fa esattamente? A volte 6 a volte 7?
Prova a resettare ed aggiornare il bios. |
|
|
|
|
16-11-2010, 11:12
|
#14 | |
|
Senior Member
Iscritto dal: Sep 2003
Città: Belluno-Chieti
Messaggi: 3337
|
Quote:
Il bios l'ho già resettato ed aggiornato all'ultima versione.... |
|
|
|
|
|
16-11-2010, 15:01
|
#15 | |
|
Senior Member
Iscritto dal: Jul 2010
Messaggi: 9326
|
Quote:
__________________
[CASE Cooler Master Silencio 550]-[MOBO Asrock Z68 Pro3]-[CPU Intel Core i7-2600K]-[RAM 8GB G.Skill]-[HDD 1TB Samsung + 320GB Samsung + 500GB Maxtor]-[VGA Zotac Geforce GTX 560 Ti]-[MASTERIZZATORE Samsung SH-S222AB][S.O. Windows 7 64 bit] Ultima modifica di Blue_screen_of_death : 16-11-2010 alle 15:04. |
|
|
|
|
|
16-11-2010, 21:26
|
#16 | |
|
Senior Member
Iscritto dal: Sep 2003
Città: Belluno-Chieti
Messaggi: 3337
|
Quote:
|
|
|
|
|
|
|
| Strumenti | |
|
|
Tutti gli orari sono GMT +1. Ora sono le: 12:43.
