Problema schermate blu win xp

[ninosting]

Salve a tutti.

Vi chiedo aiuto perchè non riesco a capire cosa abbia il pc.
Da qualche giorno all'improvviso il pc si blocca e parte la schermata blu che segnala un errore. Le prime volte riavviando è andato tutto a posto ma ieri dopo aver riavviato, il pc caricava il bios, poi schermata nera con un cursore lampeggiante in alto a sinistra e nulla più. Ho riavviato e addirittura non mi dava più segnale a video. Poi ho spento e riacceso e stessa cosa, cioè caricava bios e schermata nera...riavviavo e dinuovo niente segnale video. Finchè all'ennesima volta che ho spento e riacceso è partito senza problemi. Oggi poco dopo che l'ho acceso, schermata blu ma si è riavviato senza problemi.
Ho usato il programma per leggere i minidump e ho salvato i rapporti, se volete li posto!

Il mio pc è un amd 3800 dual core con due banchi di mem da 1 gb ciascuno e scheda madre asrock 785G. Sistema operativo windows xp sp3.
Per favore aiutatemi.

Grazie.

[MdE2005]

Non conoscendo i dettagli della questione, ti posso solo dire che può essere un preludio alla "bruciatura" della scheda video.


Ciao

[ninosting]

Grazie dell'aiuto inanzitutto.
Dimmi posso mandarti qualche dettaglio o qualcosa per poter capire che cos'è? Io ho una ati radeon 3870 x2 usata manco 2 mesi...possibile si stia bruciando? non ho overcloccato nulla e il case è ultra raffreddato...l'unica cosa...è che 1 mese fa abbiamo avuto un calo pauroso di tensione nel palazzo...tanto che l'illuminazione dello schermo si è affievolita fino a causare lo spegnimento del pc.
Se esiste qualche programma di diagnostica o qualcosa che posso postare per farti capire il problema sono a disposizione. Per ora ho solo come dicevo i log dei file minidump.

Grazie e buona giornata.

[darkkik]

Dovresti dire cosa segnalava la schermata blu...è sintomatico del problema che la causa.

[ninosting]

Allora copio e incollo gli ultimi due minidump che sono usciti dalle schermate blu.
Il primo:


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


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

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.100427-1636
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sat Oct 30 12:06:30.781 2010 (GMT+1)
System Uptime: 0 days 0:06:03.398
Loading Kernel Symbols
.................................................. .................................................. .......................
Loading User Symbols
Loading unloaded module list
............
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf813dd6, 991a41a8, 0}

Probably caused by : win32k.sys ( win32k!SfnDWORD+b5 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: bf813dd6, The address that the exception occurred at
Arg3: 991a41a8, Trap Frame
Arg4: 00000000

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a "0x%08lx" ha fatto riferimento alla memoria a "0x%08lx". La memoria non poteva essere "%s".

FAULTING_IP:
win32k!SfnDWORD+b5
bf813dd6 a5 movs dword ptr es:[edi],dword ptr [esi]

TRAP_FRAME: 991a41a8 -- (.trap 0xffffffff991a41a8)
ErrCode = 00000002
eax=e2ff8a20 ebx=00000000 ecx=00000000 edx=00000000 esi=991a4228 edi=7f80f6f4
eip=bf813dd6 esp=991a421c ebp=991a4284 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
win32k!SfnDWORD+0xb5:
bf813dd6 a5 movs dword ptr es:[edi],dword ptr [esi] es:0023:7f80f6f4=???????? ds:0023:991a4228=000103de
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: nero.exe

LAST_CONTROL_TRANSFER: from bf813f5f to bf813dd6

STACK_TEXT:
991a4284 bf813f5f bbe80310 0000000f 00000000 win32k!SfnDWORD+0xb5
991a42cc bf814151 48e80310 0000000f 00000000 win32k!xxxSendMessageToClient+0x176
991a4318 bf80ecf4 bbe80310 0000000f 00000000 win32k!xxxSendMessageTimeout+0x1a6
991a433c bf81f75b bbe80310 0000000f 00000000 win32k!xxxSendMessage+0x1b
991a4368 bf81f62b bbe80310 00000001 0013e140 win32k!xxxUpdateWindow2+0x79
991a4388 bf836881 bbe80310 00000001 991a43b4 win32k!xxxInternalUpdateWindow+0x6f
991a4398 bf8368d8 bbe80310 0013e140 991a470c win32k!xxxUpdateWindow+0xf
991a43b4 8054164c 000103de 0000005e 0013e140 win32k!NtUserCallHwndLock+0x4b
991a43b4 7c91e514 000103de 0000005e 0013e140 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0013e140 00000000 00000000 00000000 00000000 0x7c91e514


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!SfnDWORD+b5
bf813dd6 a5 movs dword ptr es:[edi],dword ptr [esi]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!SfnDWORD+b5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4c7d06ce

FAILURE_BUCKET_ID: 0x8E_win32k!SfnDWORD+b5

BUCKET_ID: 0x8E_win32k!SfnDWORD+b5

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

[ninosting]

Il secondo è:

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


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

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.100427-1636
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Nov 2 17:55:22.625 2010 (GMT+1)
System Uptime: 0 days 0:04:28.359
Loading Kernel Symbols
.................................................. .................................................. .................................
Loading User Symbols
Loading unloaded module list
.......
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {800012d8, 2, 1, 804f478e}

Probably caused by : ntkrpamp.exe ( nt!IopTimerDispatch+4e )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 800012d8, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 804f478e, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: 800012d8

CURRENT_IRQL: 2

FAULTING_IP:
nt!IopTimerDispatch+4e
804f478e ff4df8 dec dword ptr [ebp-8]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from 8050220f to 804f478e

STACK_TEXT:
805512e0 8050220f 8055adc0 00000000 bd229710 nt!IopTimerDispatch+0x4e
805513fc 8050232b 8055c0c0 ffdff9c0 ffdff000 nt!KiTimerListExpire+0x14b
80551428 80545ebf 8055c4c0 00000000 00004316 nt!KiTimerExpiration+0xb1
80551440 8055be60 ffdffc50 00000000 8055be60 nt!KiRetireDpcList+0x61
80551450 80545da4 00000000 0000000e 00000000 nt!KiIdleThread0
80551454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!IopTimerDispatch+4e
804f478e ff4df8 dec dword ptr [ebp-8]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!IopTimerDispatch+4e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4bd6e0e8

FAILURE_BUCKET_ID: 0xA_W_nt!IopTimerDispatch+4e

BUCKET_ID: 0xA_W_nt!IopTimerDispatch+4e

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


Grazie mille!!!