Uso Wifi e ottengo schermata blu

[gnaogab]

Ciao!
Sto impazzendo con un portatile di un amico:
Acer Aspire 5742G, 4Gb ram e S.O. win7 originale.
I primi BSOD li ho persi perchè era spuntato "riavvia pc dopo errore" e sovrascrivi file dump.

Per non sbagliare formatto e reinstallo il S.O da zero, tutto pulito. Driver aggiornati. Windows Update fatti.
HD tune nessun errore
MemTest nessun errore
Mi collego in internet con chiave usb della 3 e tutto fila liscio per una settimana. Il WiFi è sempre acceso che continua a cercare reti, ma non lo faccio collegare.
Collegato via LAN tutto OK.
A casa sua mi collego via WIFi a Fasweb.
Dopo 4 minuti ventola a palla, HD 100% in uso, si muove solo il mouse e scermata blu
Quattro volte di seguito.

Dump:
"
Nome evento problema: BlueScreen
Versione SO: 6.1.7600.2.0.0.768.3
ID impostazioni locali: 1040

Ulteriori informazioni sul problema:
BCCode: f4
BCP1: 0000000000000003
BCP2: FFFFFA80088FB060
BCP3: FFFFFA80088FB340
BCP4: FFFFF80002FE35D0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
""


Datemi una dritta perchè sto impazzendo....

Grazie a tutti
Gabriele

[Eress]

Serve il file dmp da analzzare

http://www.hwupgrade.it/forum/showthread.php?t=1955371

puoi usare anche BlueScreenView.

[gnaogab]

Ciao!
meno male che avevo salvato il codice come txt, non trovo più il file dump (cartella vuota).
per il momento sto intallando SDK 7 più i symbol.....
Il codice:
Firma problema:
Nome evento problema: BlueScreen
Versione SO: 6.1.7600.2.0.0.768.3
ID impostazioni locali: 1040

Ulteriori informazioni sul problema:
BCCode: f4
BCP1: 0000000000000003
BCP2: FFFFFA80088FB060
BCP3: FFFFFA80088FB340
BCP4: FFFFF80002FE35D0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

File che contribuiscono alla descrizione del problema:
C:\Windows\Minidump\101913-133817-01.dmp
C:\Users\luigi\AppData\Local\Temp\WER-157093-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

Salgatto, qui funziona con la chiavetta. il WiFi è sempre acceso e trova tutte le reti.... non so che pesci pigliare..

Grazie a tutti.
Gabriele

[gnaogab]

Ecco, manco ho finito di parlare che eccone altre due!



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

Ulteriori informazioni sul problema:
BCCode: f4
BCP1: 0000000000000003
BCP2: FFFFFA8008899910
BCP3: FFFFFA8008899BF0
BCP4: FFFFF8000317B7B0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

File che contribuiscono alla descrizione del problema:
C:\Windows\Minidump\102813-49389-01.dmp
C:\Users\luigi\AppData\Local\Temp\WER-60887-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


Con win debug trovo il file dmp ma mi dice che non posso aprirlo.... adesso cerco di capire l'inghippo..
gab

[Eress]

Devi seguire le istruzioni del post che ti ho linkato, in modo da salvare il file dmp ed evitare anche il riavvio automatico sulla bsod. Senza file dmp non si può capire la causa, il solo codice f4 è troppo generico.

[gnaogab]

Ciao.

problema risolto del file dmp, bastava leggere:doh:

Ieri dopo qualche crash ho desisto, ma ho visto che non sempre mi salva un dump... cercherò spiegazioni più avanti.
Qui sotto c'è il file dump


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


Loading Dump File [C:\Windows\Minidump\102813-49389-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 Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02e01000 PsLoadedModuleList = 0xfffff800`030446d0
Debug session time: Mon Oct 28 22:36:11.120 2013 (UTC + 1:00)
System Uptime: 0 days 0:02:50.197
*********************************************************************
* 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 F4, {3, fffffa8008899910, fffffa8008899bf0, fffff8000317b7b0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Probably caused by : csrss.exe

Followup: MachineOwner



Sul disco C: lo trovo in windows\system32 e in windows\winsxs\amd64_microsoft-windows-csrss_........

Ora, per non sbagliare riformatto tutto, ma so già che la bsod tornerà afar capolino..... quindi secondo voi cosa devo controllare?
Aspetto a formattare?

Grazie ancora
Gabriele

[Eress]

Solitamente bsod collegati a quel file sono causati da malware. Comunque sia, ci sono anche problemi di simboli col debugger di windows, per quello consigliavo di usare BlueScreenView.