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