Olas me gustaria saber por que es que sucede esto, algunas veces me sucede al iniciar mi pc (Es una Portatil VAIO Windows Vista Home Basic Memoria RAM de 502 de 1.73 GHz), pro tmb me sucede mientras estoy jugando, GunBound, Y me sale el problema del BlueScreen.

Los archivos que causan este problema sgun mi "Informes de problemas y soluciones" son:
Mini092107.dmp
sysdata.xml
Version.txt

Algunos de estos archivos estan en la carpeta MiniDump, eh leido en algunos foros que debo de actualizar mis tarjeta grafica y de sonido, por lo que ia lo ic

Tmb me han recomendado que vaya a SISTEMAS, "Configuracion Avanzada del Sistema", apartado "Inicio y recuperación", clic en "Configuracion", Poner "Ninguno" en ESCRIBIR INFORMACION DE DEPURACION (Antes de eso estaba en Volcado de memoria del Kernel)

Me gustaria saber que es lo que tengo que hacer para solucionar esto ya que me reinicia la pc cada una hora.

Gracias de Antemano

Descarga el Debugging
Una vez que lo tengas instalado lo ejecutas vas a File->Open crash dump, navega a C:Windows y busca la carpeta llamada Minidump, ábrela encontraras un archivo ejemplo: Mini050907-01.dmp le das abrir y esperas a que lo analice.
Una vez que termine de analizarlo copias y pegas su contenido aquí, para analizarlo.
Nota: En la linea del análisis:

Tienes un link para hacer clic hazlo para que te de toda la información completa.
Un saludo, jbex

Olas hice lo que me recomendaste y esto es lo que aparece :

Microsoft ® Windows Debugger Version 6.7.0005.1
Copyright © Microsoft Corporation. All rights reserved.


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

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
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 Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x81800000 PsLoadedModuleList = 0x81911db0
Debug session time: Sat Sep 22 10:02:31.405 2007 (GMT-5)
System Uptime: 0 days 0:00:54.107
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
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 TimerStop.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for TimerStop.sys
*** ERROR: Module load completed but symbols could not be loaded for TimerStop.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {204038f3, 2, 0, 876930ad}

***** 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 ***
*** ***
*************************************************************************
Probably caused by : TimerStop.sys ( TimerStop+10ad )

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

Y despues de acrle clic al link me sale esto:

FAULTING_MODULE: 81800000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4586fb6c

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
204038f3

CURRENT_IRQL: 2

FAULTING_IP:
TimerStop+10ad
876930ad 8b400c mov eax,dword ptr [eax+0Ch]

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from 87693210 to 876930ad

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8226fb00 87693210 a46b2000 a4740000 0008e000 TimerStop+0x10ad
8226fb14 87693228 819871e0 8cd37c00 8ca55000 TimerStop+0x1210
8226fcfc 8198766f 00000001 00000000 8226fd24 TimerStop+0x1228
8226fd44 81878e18 89cd9d00 00000000 839eb020 nt+0x18766f
8226fd7c 81a254a8 89cd9d00 82264680 00000000 nt+0x78e18
8226fdc0 8189145e 81878d1b 00000001 00000000 nt+0x2254a8
00000000 00000000 00000000 00000000 00000000 nt+0x9145e


STACK_COMMAND: kb

FOLLOWUP_IP:
TimerStop+10ad
876930ad 8b400c mov eax,dword ptr [eax+0Ch]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: TimerStop+10ad

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: TimerStop

IMAGE_NAME: TimerStop.sys

BUCKET_ID: WRONG_SYMBOLS

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

Por lo que veo te indica que el problema puede deberse a TimerStop.sys .

Y si no estoy equivocado dicho archivo se sobrescribe y usa para evitar la activación de Windows Vista.
Ese crack no suele dar problemas en versiones de 32 bits, pero si en las de 64 bits.
¿Es tu caso?
Un saludo, jbex

No el mio es de 32 bits
La verdad es desesperante, crees que sea favorable reformatear mi pc?

Yo antes de volver a formatear probaría a recuperar el archivo original sobrescrito y vería si solucionaba el error.
Un saludo, jbex