Problema BlueScreen :(

[mister bo]

salve a tutti, ragazzi... Vi vorrei chiedere un piccolo consiglio riguardo delle schermate blu abbastanza frequenti (diaciamo 1-2 volte al giorno). Qui vi riporto il dump:

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


Loading Dump File [C:\Users\mister bo\Desktop\113010-15007-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\Windows\Symbols
Executable search path is: 
Unable to load image 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 (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x82c18000 PsLoadedModuleList = 0x82d60810
Debug session time: Tue Nov 30 21:11:17.995 2010 (UTC + 1:00)
System Uptime: 0 days 0:29:57.696
Unable to load image 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
.....
Unable to load image win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {ffff4495, 1, 97917205, 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                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : hardware ( win32k+a7205 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffff4495, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 97917205, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 00000000, (reserved)

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

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: 82c18000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  0

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 ffff4495 

FAULTING_IP: 
win32k+a7205
97917205 20899544ffff    and     byte ptr [ecx-0BB6Bh],cl

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

CURRENT_IRQL:  0

MISALIGNED_IP: 
win32k+a7205
97917205 20899544ffff    and     byte ptr [ecx-0BB6Bh],cl

LAST_CONTROL_TRANSFER:  from 9794ce5f to 97917205

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
9637fbe4 9794ce5f fe95ab90 fd324b38 00000000 win32k+0xa7205
9637fccc 9793503e fe0d72b0 fe8ee3f8 fe732720 win32k+0xdce5f
9637fd00 82c5b44a 0a010277 00000000 00000000 win32k+0xc503e
9637fd34 77f064f4 badb0d00 0213ba00 00000000 nt+0x4344a
9637fd38 badb0d00 0213ba00 00000000 00000000 0x77f064f4
9637fd3c 0213ba00 00000000 00000000 00000000 0xbadb0d00
9637fd40 00000000 00000000 00000000 00000000 0x213ba00


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k+a7205
97917205 20899544ffff    and     byte ptr [ecx-0BB6Bh],cl

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k+a7205

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  IP_MISALIGNED

BUCKET_ID:  IP_MISALIGNED

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

1: kd> lmvm hardware
start    end        module name

che ne dite? mi pare un po' generico quel "Probably caused by: hardware" ...
Ho provato a cercare la sigla dell'errore su internet ma nulla... che mi consigliate? il pc è quello in firma...
Grazie
Ciao

[mister bo]

up

[Blue_screen_of_death]

testa le ram

dalla firma vedo che nel pc sono installati 2 banchi di ram

quindi smontane uno e testa il pc con memtest (da boot) e vedi se crasha ancora...

poi prova anche l'altro

se le ram sono ok direi che la causa è da ricercare tra qualche componente o driver difettoso

[mister bo]

guarda, la scheda madre ha un bottoncino apposito per testarle all'avvio e dice che è tutto ok... piuttosto sto guardando ora da Everest che il clock della vram e della gpu sono stati downclockati entrambi dell'8/9% come mai??? cosa posso fare?
ecco i valori:
Clock GPU (Geometric Domain): 50 MHz (originale: 763 MHz)
Clock GPU (Shader Domain): 101 MHz (originale: 1526 MHz)
Clock memoria: 67 MHz (originale: 950 MHz)
grazie
Fabio

[Lioank]

è normale che sono clokkate... il bios fa ciò per stabilizzare il sistema... ho letto : MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

molto prob un errore nei driver reinstalla tutti i driver, se hai cambiato qualcosa di recente rimetti solo quelli... senò cambiali tutti dal pirmo all'ultimo... un'altro consiglio metti win7... cmq metti un driver alla volta e testalo uno alla volta... una volta ho avuto un prob simile è la causa erano i driver di nero per il lettore cd XD

[mister bo]

ho windows 7 E c'è una novità: ho levato un banco di ram e ora va tutto alla grande! Che stupido che sono.... comunque ora sto dando un'occhiata ai driver... anche se questo downclock mi preoccupa non poco... adesso dovrebbe essere stabile il sistema, no?
grazie per l'aiuto
Fabio

[Blue_screen_of_death]

allora sostituisci il banco di ram difettoso...

per i timings dei componenti, prova a resettare il bios togliendo la batteria per 10 minuti...così le frequenze di clock dovrebbero tornare normali