|
|||||||
|
|
|
 |
|
|
Strumenti |
26-11-2014, 18:28
|
#1 |
|
Senior Member
Iscritto dal: Oct 2005
Città: Terronia
Messaggi: 1731
|
Nuovo pc. Riavvii e Bsod con Win7 e Win8.1. Aiuto
Salve a tutti. Ho problemi con il mio nuovo pc. I problemi che riscontro sono i seguenti:
1)random, si verificano dei riavvii e/o schermate blu. Ho provato Win7, Win8.1 e Win10 technical preview; 2)lo scrolling delle pagine web (verticale) non è sempre fluido, se è attivo lo scrolling continuo; 3) qualche volta ho freeze con artefatti (si blocca tutto). Queste cose si verificano in meniera del tutto casuale e spesso durante la navigazione. Mai durante il gaming. Ho provato anche prime95 e lo stress test di Aida e non succede nulla. La ram è stata controllata con memtest 86+ per circa 5 ore. Zero errori. I dischi (SSD+HD) sono stati controllati con check disk. Zero errori. Questo è il contenuto degli ultimi tre file dump: 1)Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\112614-8140-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Symbol Path validation summary ************** Response Time (ms) Location Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 8 Kernel Version 9600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 9600.17415.amd64fre.winblue_r4.141028-1500 Machine Name: Kernel base = 0xfffff800`6d674000 PsLoadedModuleList = 0xfffff800`6d94d250 Debug session time: Wed Nov 26 09:38:18.055 2014 (UTC + 1:00) System Uptime: 0 days 18:38:39.750 Loading Kernel Symbols . Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long. Run !sym noisy before .reload to track down problems loading symbols. .............................................................. ................................................................ .......................... Loading User Symbols Loading unloaded module list .................... *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A0000001, {5, 0, 0, 0} Probably caused by : atikmdag.sys ( atikmdag+2824e ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Unknown bugcheck code (a0000001) Unknown bugcheck description Arguments: Arg1: 0000000000000005 Arg2: 0000000000000000 Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0xA0000001 PROCESS_NAME: System CURRENT_IRQL: b ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre LAST_CONTROL_TRANSFER: from fffff8005b91324e to fffff8006d7c49a0 STACK_TEXT: ffffd000`fa853b58 fffff800`5b91324e : 00000000`a0000001 00000000`00000005 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx ffffd000`fa853b60 00000000`a0000001 : 00000000`00000005 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x2824e ffffd000`fa853b68 00000000`00000005 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffd000`fa853c70 : 0xa0000001 ffffd000`fa853b70 00000000`00000000 : 00000000`00000000 00000000`00000000 ffffd000`fa853c70 00000000`00000000 : 0x5 STACK_COMMAND: kb FOLLOWUP_IP: atikmdag+2824e fffff800`5b91324e ?? ??? SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: atikmdag+2824e FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmdag IMAGE_NAME: atikmdag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 530abc59 FAILURE_BUCKET_ID: 0xA0000001_atikmdag+2824e BUCKET_ID: 0xA0000001_atikmdag+2824e ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0xa0000001_atikmdag+2824e FAILURE_ID_HASH: {f1c6bffd-901a-7f99-9a93-9a0eacc9ad03} Followup: MachineOwner --------- 2)Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\112214-7828-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Symbol Path validation summary ************** Response Time (ms) Location Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 8 Kernel Version 9600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 9600.17415.amd64fre.winblue_r4.141028-1500 Machine Name: Kernel base = 0xfffff803`93607000 PsLoadedModuleList = 0xfffff803`938e0250 Debug session time: Sat Nov 22 08:58:18.457 2014 (UTC + 1:00) System Uptime: 0 days 0:00:02.151 Loading Kernel Symbols . Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long. Run !sym noisy before .reload to track down problems loading symbols. ......................................................... Loading User Symbols Mini Kernel Dump does not contain unloaded driver list ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, ffffe001f1a79038, 0, 0} Probably caused by : AuthenticAMD Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: ffffe001f1a79038, Address of the WHEA_ERROR_RECORD structure. Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ BUGCHECK_STR: 0x124_AuthenticAMD CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre STACK_TEXT: ffffd000`bd9cf500 fffff803`9398dee8 : ffffd000`bd5c0180 ffffe001`f1a79010 ffffe001`f03d8800 fffff803`936387f9 : nt!WheapCreateLiveTriageDump+0x81 ffffd000`bd9cfa30 fffff803`937ce0f8 : ffffe001`f1a79010 fffff803`938ef7a0 ffffe001`f03d8880 fffff803`938b9300 : nt!WheapCreateTriageDumpFromPreviousSession+0x44 ffffd000`bd9cfa60 fffff803`937cef15 : fffff803`938ef740 fffff803`938ef7a0 ffffe001`f03d8880 00000000`00000000 : nt!WheapProcessWorkQueueItem+0x48 ffffd000`bd9cfaa0 fffff803`936a338c : fffff803`93b1c040 fffff803`937ceef0 ffffe001`f03d8880 fffff803`938b9300 : nt!WheapWorkQueueWorkerRoutine+0x25 ffffd000`bd9cfad0 fffff803`93708c70 : 3302ebc3`8bfe434c ffffe001`f03d8880 00000000`00000080 ffffe001`f03d8880 : nt!ExpWorkerThread+0x28c ffffd000`bd9cfb80 fffff803`9375dfc6 : fffff803`9390a180 ffffe001`f03d8880 ffffe001`f012d040 c3c0940f`c985c033 : nt!PspSystemThreadStartup+0x58 ffffd000`bd9cfbe0 00000000`00000000 : ffffd000`bd9d0000 ffffd000`bd9c9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: AuthenticAMD IMAGE_NAME: AuthenticAMD DEBUG_FLR_IMAGE_TIMESTAMP: 0 IMAGE_VERSION: FAILURE_BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_CACHE_PRV BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_CACHE_PRV ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x124_authenticamd_processor_cache_prv FAILURE_ID_HASH: {cedb04af-9437-ee8e-2e67-54d858b5dbbc} Followup: MachineOwner --------- 3)Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Minidump\112014-13640-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Symbol Path validation summary ************** Response Time (ms) Location Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 8 Kernel Version 9600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 9600.17328.amd64fre.winblue_r3.140827-1500 Machine Name: Kernel base = 0xfffff803`9c213000 PsLoadedModuleList = 0xfffff803`9c4e9370 Debug session time: Thu Nov 20 13:59:19.065 2014 (UTC + 1:00) System Uptime: 0 days 0:00:01.761 Loading Kernel Symbols . Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long. Run !sym noisy before .reload to track down problems loading symbols. ............................................................. Loading User Symbols Mini Kernel Dump does not contain unloaded driver list ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, ffffe001f3095038, 0, 0} Probably caused by : AuthenticAMD Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: ffffe001f3095038, Address of the WHEA_ERROR_RECORD structure. Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ BUGCHECK_STR: 0x124_AuthenticAMD CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre STACK_TEXT: ffffd001`b73a3500 fffff803`9c598fd0 : ffffd001`b6fe5180 ffffe001`f3095010 fffff803`9c4f8800 fffff803`9c293339 : nt!WheapCreateLiveTriageDump+0x81 ffffd001`b73a3a30 fffff803`9c3d7454 : ffffe001`f3095010 ffffd001`b73a3b50 fffff803`9c4f88e0 ffffe001`f213a040 : nt!WheapCreateTriageDumpFromPreviousSession+0x44 ffffd001`b73a3a60 fffff803`9c3d8271 : fffff803`9c4f88e0 ffffd001`b73a3b50 fffff803`9c4f88e0 ffffd001`b73a3b50 : nt!WheapProcessWorkQueueItem+0x48 ffffd001`b73a3aa0 fffff803`9c2825e3 : fffff803`9c4c2300 fffff803`9c3d824c 00000000`00000000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25 ffffd001`b73a3ad0 fffff803`9c311e70 : 4101b70f`02b70f44 ffffe001`f213a040 ffffe001`f213a040 ffffe001`f2075040 : nt!ExpWorkerThread+0x293 ffffd001`b73a3b80 fffff803`9c3687c6 : ffffd001`b6de9180 ffffe001`f213a040 ffffe001`f2125880 06800d48`e0200f19 : nt!PspSystemThreadStartup+0x58 ffffd001`b73a3be0 00000000`00000000 : ffffd001`b73a4000 ffffd001`b739d000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: AuthenticAMD IMAGE_NAME: AuthenticAMD DEBUG_FLR_IMAGE_TIMESTAMP: 0 IMAGE_VERSION: FAILURE_BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x124_authenticamd_processor_bus_prv FAILURE_ID_HASH: {6fd7875b-9a1b-9e09-d6d6-816026a875c8} Followup: MachineOwner --------- Ho provato già 5/6 versioni di Catalyst, senza risolvere. La configurazione e basata su AMD A8-7600, Gigabyte F2a88XN-wifi e 4x2GB di ram Kington DDR3 1866. Ringrazio in anticipo chi volesse aiutarmi.
__________________
Concluso affari positivamente con: Piccolospazio,erysed,En3rGiE,Gandalf72,catpresent,Manuelcese20,cirano76,garfles,Fabrizio Giammarco,Mister D,thekubrik |
|
|
|
26-11-2014, 20:53
|
#2 |
|
Senior Member
Iscritto dal: Jan 2010
Messaggi: 37088
|
Se ti capita esclusivamente durante la navigazione, inizia disattivando l'accelerazione HW, nelle opzioni avanzate di IE. Se usi un altro browser la puoi disattivare direttamente dalle opzioni del click destro sul video.
|
|
|
|
|
26-11-2014, 21:47
|
#3 | |
|
Senior Member
Iscritto dal: Oct 2005
Città: Terronia
Messaggi: 1731
|
Quote:
purtroppo non è solo durante la navigazione. Una volta è capitato anche con Vlc.
__________________
Concluso affari positivamente con: Piccolospazio,erysed,En3rGiE,Gandalf72,catpresent,Manuelcese20,cirano76,garfles,Fabrizio Giammarco,Mister D,thekubrik |
|
|
|
|
|
26-11-2014, 22:04
|
#4 |
|
Senior Member
Iscritto dal: Jan 2007
Città: quel ramo del lago di como, che volge a mezzogiorno... ^^
Messaggi: 19625
|
hai parlato di 40 sistemi diversi.
ma i driver video sono sempre diversi o sono sempre gli stessi? perchè il problema sta li.
__________________
|
|
|
|
|
26-11-2014, 22:43
|
#5 | |
|
Senior Member
Iscritto dal: Oct 2005
Città: Terronia
Messaggi: 1731
|
Quote:
Ho scritto che ho testato varie review di drivers catalyst (compresi gli ultimi WHQL di Settembre) ma le schermate blu e i riavvii non si risolvono. Ho formattato già 5 volte.
__________________
Concluso affari positivamente con: Piccolospazio,erysed,En3rGiE,Gandalf72,catpresent,Manuelcese20,cirano76,garfles,Fabrizio Giammarco,Mister D,thekubrik |
|
|
|
|
|
|
| Strumenti | |
|
|
Tutti gli orari sono GMT +1. Ora sono le: 05:50.
