Vista/7 - Schermate blu (bsod):individuazione cause dell'errore e possibili soluzioni

[n3o999]

Originariamente inviato da Eress

Vedi qui

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

ho visto il primo post...

ma non ho capito molto. il file minidump per postarlo completo non c'è. inoltre qualè il codice errore da mettere sul sito microsoft??

non si può sapere come risolvere?

[Eress]

Se imposti correttamente i valori nelle opzioni avanzante>avvio e ripristino come spiegato nella guida, alla fine dopo l'eventuale schermata blu dovresti trovare il file dmp in C/Windows/Minidump lo zippi e lo posti come allegato

[AmoN89]

ragazzi non so se bastano come info però per ora sono risucito a racimolare queste con bluescreenview

 ==================================================
Dump File         : MEMORY.DMP
Crash Time        : 15/01/2011 21:56:48
Bug Check String  : 
Bug Check Code    : 0x00000101
Parameter 1       : 00000000`00000019
Parameter 2       : 00000000`00000000
Parameter 3       : fffff880`009b2180
Parameter 4       : 00000000`00000004
Caused By Driver  : 
Caused By Address : 
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Computer Name     : 
Full Path         : C:\Windows\Minidump\MEMORY.DMP
Processors Count  : 8
Major Version     : 15
Minor Version     : 7600
Dump File Size    : 482.271.160
==================================================

qualche soluzione? il bsod è relativo al pc in firma e sorge sporadicamente...

[Eress]

Sono informazioni incomplete ed inutilizabili

[AmoN89]

Originariamente inviato da Eress

Sono informazioni incomplete ed inutilizabili

è riapparso il bsod e dice questo
"a clock interrupt was not recieved on a secondary processor within the allocated interval", il bug check code e i parametri sono quelli che ho postato precedentemente...

[Eress]

Dovresti dare una controllata all'HW, hai fatto overclock, qualche intervento/modifica hw ultimamente?

vedi anche qui

http://www.evga.com/forumsarchive/tm...09&mpage=1&key

[LaToX]

Ciao a tutti...avrei bisogno di un vostro aiuto in merito a questo problema. Il pc è un Dell 1564 con windows 7 64bit.

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000094, The exception code that was not handled
Arg2: fffff88004e1d8f2, The address that the exception occurred at
Arg3: fffff88002f4eda8, Exception Record Address
Arg4: fffff88002f4e610, Context Record Address

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!_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 ***
*** ***
*************************************************************************

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.

FAULTING_MODULE: fffff80002e11000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 49cc26b1

EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {ERRORE DI EXCEPTION} Divisione intera per zero.

FAULTING_IP:
bcmwl664+58f2
fffff880`04e1d8f2 41f7f9 idiv eax,r9d

EXCEPTION_RECORD: fffff88002f4eda8 -- (.exr 0xfffff88002f4eda8)
ExceptionAddress: fffff88004e1d8f2 (bcmwl664+0x00000000000058f2)
ExceptionCode: c0000094 (Integer divide-by-zero)
ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT: fffff88002f4e610 -- (.cxr 0xfffff88002f4e610)
rax=000000000000000c rbx=fffffa80038ef000 rcx=0000000000001770
rdx=0000000000000000 rsi=0000000000000000 rdi=fffffa80038ef000
rip=fffff88004e1d8f2 rsp=fffff88002f4efe8 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=00000000000007d0
r11=0000000000000064 r12=0000000000000001 r13=0000000000000002
r14=fffffa80038efe88 r15=0000000000000056
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
bcmwl664+0x58f2:
fffff880`04e1d8f2 41f7f9 idiv eax,r9d
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x7E

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff88004e261aa to fffff88004e1d8f2

STACK_TEXT:


FOLLOWUP_IP:
bcmwl664+58f2
fffff880`04e1d8f2 41f7f9 idiv eax,r9d

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: bcmwl664+58f2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: bcmwl664

IMAGE_NAME: bcmwl664.sys

STACK_COMMAND: .cxr 0xfffff88002f4e610 ; kb

BUCKET_ID: WRONG_SYMBOLS

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

[Eress]

Ê la scheda di rete wireless Broadcom 802.11 Network Adapter wireless driver

[LaToX]

Sì è vero, è il driver della periferica wireless ma come posso fare per sistemarlo??
Ho notato che il problema si presenta quando stacco l'alimentazione ed il portatile lavora con la sua batteria. O quando lo avvio senza alimentazione.

[Eress]

Cerca se ci sono driver aggiornati e dai anche una controllata nel risparmio energia>opzioni avanzate>wireless

[LaToX]

Originariamente inviato da Eress

Cerca se ci sono driver aggiornati e dai anche una controllata nel risparmio energia>opzioni avanzate>wireless

Ok grazie al tuo consiglio forse ho risolto. Ora il pc era stabile. Ho settato la scheda wireless con lo stesso profilo di risparmio energetico, ovvero tutto al max delle prestazioni.

Così per curiosità, come ti è venuto di consigliami di guardare questo particolare??

[Eress]

Originariamente inviato da LaToX

Così per curiosità, come ti è venuto di consigliami di guardare questo particolare??

Perché essendo coinvolta la scheda di rete, ci poteva anche stare un problema nelle impostazioni del risparmio energia e poi mi avevi dato l'indizio della batteria...

[libano]

mi spiegate che significa??ho provato ad eseguire la procedura descritta in prima pagina ma non ci capisco molto,qualcuno mi dà una mano???



Uploaded with ImageShack.us

[Eress]

Inizia a etstare la ram, magari scollegando un banco alla volta. Seguendo la guida dovresti riuscire ad estrarre il file dmp, alla fine serve quello per risalire alla causa

[libano]

Originariamente inviato da Eress

Inizia a etstare la ram, magari scollegando un banco alla volta. Seguendo la guida dovresti riuscire ad estrarre il file dmp, alla fine serve quello per risalire alla causa

dicevi a me??
mi puoi spiegare un po meglio,come faccio a testare la ram??è dovuto alla ram il problema???
non ci capisco nulla!!

[|| Luca ||]

Ragazzi, la versione dei symbols da scaricare è la retail o la checked?

[Eress]

No non devi scaricare nulla, ma solo indicare al programma il percorso ai symbols sul server MS, nella guida c'è scritto mi pare

[Egolo]

una schermata blu recitante tipo:

A problem has been detected and Windows has been shut down to prevent damage to your computer.

If this is the first time you’ve seen this stop error screen, restart your computer. If this screen appears again, follow these steps:

Check to be sure you have adequate disk space. If a driver is identified in the Stop message, disable the driver or check with the manufacturer for driver updates. Try changing video adapters.

Check with your hardware vendor for any BIOS updates. Disable BIOS memory options such as caching or shadowing. If you need to use Safe Mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and then select Safe Mode.

che appare la prima volta che si accende un notebook nuovo, ancor prima di installare e configurare tutto, che cosa può significare?

[Mgz]

Salve a tutti, provo anche io a chiedervi aiuto perchè non so più dove sbattere la testa

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


Loading Dump File [C:\Windows\Minidump\011911-22453-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\Symbols
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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02810000 PsLoadedModuleList = 0xfffff800`02a4de50
Debug session time: Wed Jan 19 09:20:30.256 2011 (UTC + 1:00)
System Uptime: 0 days 0:04:45.913
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 1E, {ffffffffc000001d, fffff88006eb7ec0, 0, 0}

***** 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                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+70740 )

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

avete qualche idea? Da quando ho installato Win7 ho continuamente bluscreen, con esattamente lo stesso hardware che avevo usando xp che non mi ha mai dato problemi...

[Eress]

Originariamente inviato da Egolo

una schermata blu recitante tipo:


che appare la prima volta che si accende un notebook nuovo, ancor prima di installare e configurare tutto, che cosa può significare?

Che ti hanno appena venduto un pc difettoso

Originariamente inviato da Mgz

Salve a tutti, provo anche io a chiedervi aiuto perchè non so più dove sbattere la testa

C'è un errore nei symbols e da quel log non si ricava nulla. Riprova seguendo bene la guida per il bugcheck puntando per i simboli al server di MS oppure posta qui il file dmp zippato