Dator reboot och bluescreen hjälp plz

Halloj har sökt runt på internet och hittade en tråd med liknande fel här som jag har men den kunde jag i skriva i så gör en ny istället.

Mitt problem är att Datorn rebootar till och från vilket den gjort under en lång tid nu på sistone får jag även en bluescreen som säger något om atkdisp varje gång den omstartart ofrivilligt.

Gfx : Asus 7600 GT ( nyaste drivisar från nvidia.com installerade)

Startar om datorn igen och får att windows återställts efter ett allvarligt fel
samt
Felsignatur
BCCode : 100000ea BCP1 : 88280DA8 BCP2 : 89A02A50 BCP3 : BACE3CB4
BCP4 : 00000001 OSVer : 5_1_2600 SP : 2_0 Product : 256_1

Och att 3 loggfiler skapats
Mini040708-01.dmp
Sysdata.xml
Manifest.txt

Detta är vad som står i .dmp filen

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

Loading Dump File [C:\Documents and Settings\Mattias.SILKE\Skrivbord\Mini040708-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805533a0
Debug session time: Mon Apr 7 12:20:13.953 2008 (GMT+2)
System Uptime: 0 days 0:39:38.557
Loading Kernel Symbols
.....................................................................................................................................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000EA, {88280da8, 89a02a50, bace3cb4, 1}

*** WARNING: Unable to verify timestamp for nv4_mini.sys
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys

Probably caused by : nv4_mini.sys ( nv4_mini+7182b )

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

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

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 88280da8, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 89a02a50, Pointer to a DEFERRED_WATCHDOG object.
Arg3: bace3cb4, Pointer to offending driver name.
Arg4: 00000001, Number of times "intercepted" bugcheck 0xEA was hit (see notes).

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

FAULTING_THREAD: 88280da8

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0xEA

PROCESS_NAME: Wow.exe

LAST_CONTROL_TRANSFER: from 804f8e6e to 80540b9f

STACK_TEXT:
b5efc0f4 804f8e6e bace3b40 bace3b70 00000000 nt!KiUnlockDispatcherDatabase+0x77
b5efc108 bac78a67 bace3b94 00000000 00000000 nt!KeSetEvent+0x74
b5efc3fc 804fd18b bace3b40 b5efc448 b5efc43c watchdog!WatchdogKernelApc+0x13b
b5efc44c 806d0c35 00000000 00000000 b5efc464 nt!KiDeliverApc+0xb3
b5efc44c 805272d6 00000000 00000000 b5efc464 hal!HalpApcInterrupt+0xc5
b5efc4d4 b957482b b8152410 b95973ce 89aa8cf0 nt!READ_REGISTER_ULONG+0x6
WARNING: Stack unwind information not available. Following frames may be wrong.
b5efc4dc b95973ce 89aa8cf0 8986d958 00009410 nv4_mini+0x7182b
b5efc4e0 89aa8cf0 8986d958 00009410 89865640 nv4_mini+0x943ce
b5efc4e4 8986d958 00009410 89865640 8986d958 0x89aa8cf0
b5efc4e8 00000000 89865640 8986d958 00000000 0x8986d958

STACK_COMMAND: .thread 0xffffffff88280da8 ; kb

FOLLOWUP_IP:
nv4_mini+7182b
b957482b ?? ???

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: nv4_mini+7182b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_mini

IMAGE_NAME: nv4_mini.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47567b8b

FAILURE_BUCKET_ID: 0xEA_IMAGE_nv4_mini.sys_DATE_2007_12_05

BUCKET_ID: 0xEA_IMAGE_nv4_mini.sys_DATE_2007_12_05

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

kd> lmvm nv4_mini
start end module name
b9503000 b9c1a480 nv4_mini T (no symbols)
Loaded symbol image file: nv4_mini.sys
Image path: nv4_mini.sys
Image name: nv4_mini.sys
Timestamp: Wed Dec 05 11:20:59 2007 (47567B8B)
CheckSum: 0071A480
ImageSize: 00717480
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0

Tacksam om något kunde hjälpa till . Säg till bara om ja behöver posta något mer info men .dmp filen beskriver väl problemet?