I have been having problems with my computer randomely restarting.I installed Windbg and this is what it says:

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


Loading Dump File [C:\WINDOWS\Minidump\Mini111707-01.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 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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
Debug session time: Sat Nov 17 06:27:56.984 2007 (GMT-5)
System Uptime: 0 days 0:50:23.573
*********************************************************************
* 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 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
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {2, 7, 0, 2}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Unable to load image nv4_mini.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_mini.sys
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : nv4_mini.sys ( nv4_mini+33edf )

Followup: MachineOwner
---------Can anyone help?nv4_mini.sys is related to a graphics card. Do you use nVidia products?Nforce 2 Motherboard chipset.Even the audio is Nvidia,but it was crashing the same way when I was using a ATI graphics card.I took the ATI card out to see if that WOULD be the problem.Also it doesnt always say nv4_mini.sys.Here is a list of the other dumps.
Probably caused by : win32k.sys ( win32k+11ce )
Probably caused by : ntoskrnl.exe ( nt+1eff0 )
Probably caused by : hardware ( nt+374e )
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )



Need...more...info...gasp

Operating system / antivirus & antispyware protection / service packs installed / when did it start happening / did it ever work right / installed any new software?

Alan <>< Windows XP SP2,AVG Antivirus,been happening for a month,has gotten more frequent as of lately,yes the computer used to work right,and I have installed no new software.Perhaps you've got a virus and it's corrupted that file?

Do a virus scan.it seems that the whole boot process is screwed up completleyso how do I fix this?I perosnally havwent seen this before. Another member?well that dont sound very good.lolDo you have a Microsoft XP CD ? ?

If so go to Start / Run and type in sfc /scannow and hit Enter...
Have the CD handy as it will ask for it.
Let it run to completion and then remove the CD and re-boot.

If not post back after DLoading the 7 disk XP startup disks from Microsoft and we will have to try the Recovery Console...