Random Restarts

Hi
Ive tried to avoid posting my problem but it has finally baked my head. Ive been experiencing random restart. It is very random too, It could be fine for a few days then it could restart 1 - 5 times a day. Ive checked the memory and that tests fine, I even replaced the memory to be double sure. I am getting fedup now. Here is the most recent dump. I do hope someone can help.

TIA
Paul

Code:

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


Loading Dump File [C:\WINDOWS\Minidump\Mini021410-02.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: 
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 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Sun Feb 14 18:28:25.218 2010 (GMT+0)
System Uptime: 0 days 3:06:14.773
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 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
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {b3d780c0, 5, 0, b9679db5}

***** 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                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : nv4_mini.sys ( nv4_mini+78db5 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: b3d780c0, memory referenced
Arg2: 00000005, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: b9679db5, address which referenced memory

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

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: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  453bddb2

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 b3d780c0 

CURRENT_IRQL:  5

FAULTING_IP: 
nv4_mini+78db5
b9679db5 8b861c040000    mov     eax,dword ptr [esi+41Ch]

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xD1

LAST_CONTROL_TRANSFER:  from b95eecd5 to b9679db5

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
b3d77d24 b95eecd5 00000000 00000000 804da779 nv4_mini+0x78db5
b3d77d28 00000000 00000000 804da779 8298a340 VIDEOPRT!pVideoPortInterrupt+0x1d


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nv4_mini+78db5
b9679db5 8b861c040000    mov     eax,dword ptr [esi+41Ch]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nv4_mini+78db5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nv4_mini

IMAGE_NAME:  nv4_mini.sys

BUCKET_ID:  WRONG_SYMBOLS

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

 

What is OS, security software? Any specs you give can only help.

Same problem in safe mode? Course, that would be hard to tell in this case perhaps.

The fact it is so intermittent points to a possible hardware problem, faulty keyboards can cause this. Can you try another?

 

Sorry, Its XP SP3. Please don't laught at the spec, Its pretty old now, If I could afford a new one, I would get one without hesitation.

MSI KM4M-L, AMD XP2700, 2GB Ram. 250GB, 300GB 1TB and 80GB hard drives. Ti4400 graphics. Kaspersky Internet security. Logitech MX3000 Wireless KB and mouse.

Ive not tried it in safe mode for testing as I am using it most of the time. I have a feeling it may be something to do with the graphics card, Ive just fitted a ye old MX440 I found in the loft to see how it goes

 

Well, Its not restarted once since I started this topic. Strange. Anyway, Im junking the Mobo, CPU and graphics card and replacing them with new ones. They are all about 6 years old now so are a bit long in the tooth to say the least