Win 7 64bit blue screening and rebooting

sorry, here´s the minidump

RobertTo said:

sorry, here´s the minidump

This one was caused by your video driver. I would un-install completely and reinstall a fresh copy.

I would also run a system file check
(type cmd in search>right click and run as admin>sfc /scannow ( note the space between sfc and "/")

Let us know the results

Ken

Code:

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


Loading Dump File [C:\Users\K\Desktop\040710-16848-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a55000 PsLoadedModuleList = 0xfffff800`02c92e50
Debug session time: Wed Apr  7 01:25:46.130 2010 (GMT-4)
System Uptime: 0 days 0:00:41.176
Loading Kernel Symbols
...............................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8009b584e0, fffff88003f4202c, 0, d}

*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+602c )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8009b584e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003f4202c, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000d, Optional internal context dependent data.

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


FAULTING_IP: 
atikmpag+602c
fffff880`03f4202c 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`057a1898 fffff880`04f11cbc : 00000000`00000116 fffffa80`09b584e0 fffff880`03f4202c 00000000`00000000 : nt!KeBugCheckEx
fffff880`057a18a0 fffff880`04f11a43 : fffff880`03f4202c fffffa80`09b584e0 00000000`00000000 fffffa80`09166410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`057a18e0 fffff880`04fb8f07 : fffffa80`09b584e0 00000000`00000000 00000000`00000000 fffffa80`09166410 : dxgkrnl!TdrIsRecoveryRequired+0x21f
fffff880`057a1910 fffff880`04fe6d7e : 00000000`00000000 00000000`000009bf fffff880`057a1a70 fffffa80`09166410 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`057a19f0 fffff880`04fe279e : fffffa80`09166410 ffffffff`feced300 00000000`00000002 fffff880`04fb52f2 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`057a1a30 fffff880`04fe1034 : fffffa80`09166410 00000000`00000002 fffff880`04fe0dc0 00000000`00000000 : dxgmms1!VidSchiWaitForDrainFlipQueue+0x92
fffff880`057a1b20 fffff880`04fe12fe : 00000000`00000000 00000000`00000002 00000000`00000002 00000000`00000000 : dxgmms1!VidSchiHandleControlEvent+0x4c
fffff880`057a1b50 fffff880`04fb42c6 : ffffffff`ff676980 fffffa80`09166410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x23e
fffff880`057a1bf0 fffff880`04fe0e7a : 00000000`00000000 fffffa80`09b7d010 00000000`00000080 fffffa80`09166410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`057a1d00 fffff800`02d6a166 : 00000000`fffffc32 fffffa80`09191b60 fffffa80`06ce4890 fffffa80`09191b60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`057a1d40 fffff800`02aa5486 : fffff800`02c3fe80 fffffa80`09191b60 fffff800`02c4dc40 fffff880`01221a90 : nt!PspSystemThreadStartup+0x5a
fffff880`057a1d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+602c
fffff880`03f4202c 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+602c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b8dd275

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

Thanks.

I´ll try it. My sfc /scannow resulted in "win resource protection could not perform requested operation". Tried chkdsk /f /r...no errors found. After restart, tried scannow again...same error. Yesterday, I tried to run memtest....no errors. Today after 7 minutes, it foun 2432 errors. I don´t know what´s happening to my PC. I have installed nothig last 5 days and I´m having such a contradictory test results. Please, could you tell me, what was the problem in my previous minidump files? Cause my system didn´t change, so I´m curious.

Thanks a lot

I tried a repair install but it didn´t let me do it. Some files were corrupted. Here´s another minidump, please, tell me what´s written there. After, I´ll send my PC for a RMA.

Thanks.

Suggest you look in bios for the XMP profile for your memory and use those settings. It's unlikely the problem will fix itself unless you get those memory settings correct.