|
|
|
![]() |
|
Strumenti |
![]() |
#1 |
Member
Iscritto dal: Dec 2007
Messaggi: 91
|
Schermata blu!
Gia due volte in 2 giorni mi ha dato schermata blu.
Ho un pc fisso con win 7. Dopo uno scan con Whocrashed mi ha dato questo risultato: System Information (local) -------------------------------------------------------------------------------- computer name: DARIO-PC windows version: Windows 7 Service Pack 1, 6.1, build: 7601 windows dir: C:\Windows CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU E4600 @ 2.40GHz Intel586, level: 6 2 logical processors, active mask: 3 RAM: 3220758528 total VM: 2147352576, free: 1936519168 -------------------------------------------------------------------------------- Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Sun 18/08/2013 14:30:29 GMT your computer crashed crash dump file: C:\Windows\Minidump\081813-20794-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80) Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x602B, 0x60290000C0D6) Error: MEMORY_MANAGEMENT file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a severe memory management error occurred. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Sun 18/08/2013 14:30:29 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x602B, 0x60290000C0D6) Error: MEMORY_MANAGEMENT Bug check description: This indicates that a severe memory management error occurred. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Sun 18/08/2013 07:22:58 GMT your computer crashed crash dump file: C:\Windows\Minidump\081813-18002-01.dmp This was probably caused by the following module: win32k.sys (win32k+0x6BF8E) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600012BF8E, 0xFFFFF880025EAD80, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\win32k.sys product: Sistema operativo Microsoft® Windows® company: Microsoft Corporation description: Driver Win32 multiutente Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. On Sat 17/08/2013 13:41:49 GMT your computer crashed crash dump file: C:\Windows\Minidump\081713-21106-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80) Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000D17C60, 0xFFFF, 0x0) Error: MEMORY_MANAGEMENT file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a severe memory management error occurred. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Sat 10/08/2013 08:38:53 GMT your computer crashed crash dump file: C:\Windows\Minidump\081013-21294-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00) Bugcheck code: 0x1A (0x5100, 0xFFFFF6FD4002D5D8, 0x145, 0x80) Error: MEMORY_MANAGEMENT file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a severe memory management error occurred. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. A cosa è dovuto? Che devo fare per risolverlo? |
![]() |
![]() |
![]() |
#2 |
Senior Member
Iscritto dal: Jan 2010
Messaggi: 37089
|
Per iniziare controlla la ram, meglio sarebbe utilizzando il pc con un solo banco di ram alla volta.
|
![]() |
![]() |
![]() |
#3 |
Senior Member
Iscritto dal: Aug 2013
Messaggi: 385
|
Dal report dovrebbe proprio essere un errore della RAM
__________________
|
![]() |
![]() |
![]() |
#4 |
Senior Member
Iscritto dal: Feb 2009
Messaggi: 50674
|
Ciaoo visto che hai un pc fisso, oltre a provare la ram un banco alla volta, dai anche una pulita dalla polvere all'interno del case .
Poi anche staccando la ram dagli alloggiamenti, la pulisci e pulisci anche gli alloggiamenti stessi con un pennellino . Da quanto tempo non apri il case ![]() Controlla anche le ventole che girino bene, che non facciano un rumore strano e che non ci sia polvere su di esse . Quanta ram hai ? 4 gb ?
__________________
Aomei in Prog. & Utility - Lic OEM - Q di Merc Ott '22 - W10 Spot Images Seasons from '20 to Summer 2022 - DailyPic dalle Eccezioni alle Unique Images + Rec > DailyPic Unique Images Novembre 2022 |
![]() |
![]() |
![]() |
#5 |
Member
Iscritto dal: Dec 2007
Messaggi: 91
|
Ultimamente lo sento più rumoroso del solito e di polvere c'è nè di sicuro.. saranno 6 mesi che non lo apro.
Non ho mai staccato un banco ram però.. come si fa? Li stacco uno alla volta e poi? |
![]() |
![]() |
![]() |
#6 |
Senior Member
Iscritto dal: Jan 2010
Messaggi: 37089
|
No, li stacchi tutti meno uno, poi provi gli altri, ma sempre uno per volta, così alla fine dovresti identificare rapidamente quello eventualmente difettoso. Dai anche una pulita approfondita all'interno del pc.
|
![]() |
![]() |
![]() |
#7 | ||
Senior Member
Iscritto dal: Feb 2009
Messaggi: 50674
|
Quote:
![]() Io ormai l'ho tengo aperto, cosi è più arieggiato . Quote:
Per togliere la ram, devi tirare, piano ![]() Per tornare a ri-posizionarla, la inserisci finche i due ganci bianchi non scattano in modo tale da bloccare il modulo della ram stesso . Ho trovato questo articolo che mostra i ganci chiusi e aperti degli alloggiamenti o detti anche socket della ram e parla anche di aria compressa per la pulizia . Se ce l'hai perchè no ![]() http://www.gratisdivx.com/public/new...pc_desktop.asp
__________________
Aomei in Prog. & Utility - Lic OEM - Q di Merc Ott '22 - W10 Spot Images Seasons from '20 to Summer 2022 - DailyPic dalle Eccezioni alle Unique Images + Rec > DailyPic Unique Images Novembre 2022 |
||
![]() |
![]() |
![]() |
Strumenti | |
|
|
Tutti gli orari sono GMT +1. Ora sono le: 22:18.