BSOD every month

[Caketaker]

Hello

Since i got a new computer near end of last year with new cpu, memory etc. I've been getting BSOD nearly every month and latest one was a few days ago.

I've got this memory.dmp file and tried zipping it up to attach it to the forums but it's still too big to attach to the forums.

 

[Jonathan_King]

Welcome CareTaker!

Try uploading it to RapidShare.

 

[Caketaker]

Thanks but it's caketaker not caretaker

I've uploaded file via rapidshare....

RapidShare: 1-CLICK Web hosting - Easy Filehosting

 

[Jonathan_King]

That dmp file looks corrupted. Try setting your computer to generate a minidump, then follow these instruction for uploading it: http://www.sevenforums.com/tutorials/83172-dump-files-upload-seven-forums-analysis.html

Instructions for changing to Minidump are contained in the link.

 

[Tews]

Your .dmp file is 80mb!! Follow these steps to enable a small memory dump..


Click Start, point to Settings, and then click Control Panel.
Double-click System.
Click the Advanced tab, and then click Settings under Startup and Recovery.
In the Write debugging information list, click Small memory dump (64k).

This will help us in analyzing your .dmp file...

 

[Caketaker]

Ah right...

here is the minidump file...

 

[Jonathan_King]

Looks like bad RAM. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and run at least 5 passes.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {188, 2, 0, fffff880014c981c}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

 

[Caketaker]

Thanks for your help.

I'll give this memtest a try to see if anything comes up.

 

[Caketaker]

Well i did the memtest and it reported no errors. Just wondering if you could take a look at last months minidump to see what that says....

 

[zigzag3143]

Well i did the memtest and it reported no errors. Just wondering if you could take a look at last months minidump to see what that says....

This one was caused by your video driver. I would use the Mfr uninstall tool to completley remove this driver then install a fresh copy.


Let us know if you need help with this

Ken

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


Loading Dump File [C:\Users\K\Desktop\041110-17050-01.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;srv*e:\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 Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c54000 PsLoadedModuleList = 0xfffff800`02e91e50
Debug session time: Sun Apr 11 03:06:05.254 2010 (GMT-4)
System Uptime: 0 days 0:09:35.987
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80043e44e0, fffff88003ed802c, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** 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
---------

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

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

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


FAULTING_IP: 
atikmpag+602c
fffff880`03ed802c 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`05f729c8 fffff880`04f1eef8 : 00000000`00000116 fffffa80`043e44e0 fffff880`03ed802c 00000000`00000000 : nt!KeBugCheckEx
fffff880`05f729d0 00000000`00000116 : fffffa80`043e44e0 fffff880`03ed802c 00000000`00000000 00000000`00000002 : dxgkrnl+0x5cef8
fffff880`05f729d8 fffffa80`043e44e0 : fffff880`03ed802c 00000000`00000000 00000000`00000002 00000000`00000000 : 0x116
fffff880`05f729e0 fffff880`03ed802c : 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000 : 0xfffffa80`043e44e0
fffff880`05f729e8 00000000`00000000 : 00000000`00000002 00000000`00000000 00000000`00000000 fffff880`04f1ec02 : atikmpag+0x602c


STACK_COMMAND:  kb

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

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  atikmpag+602c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bab0dbd

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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