Random BSODs on New Computer

Hi,

I've posted on these forums before, but I was never able to solve my blue screen problem. I've been struggling with these blue screens since I built my computer about 5 months ago. I'm currently running windows 7 64 bit. I've ran multiple memory tests with 7 passes and they have all come up clean. Like I said, the blue screen are normally random, but lately, I've been getting something like atikmdag.sys. This has something to do with the video card doesn't it? Any help would be greatly appreciated.

Mzimzim said:

Hi,

I've posted on these forums before, but I was never able to solve my blue screen problem. I've been struggling with these blue screens since I built my computer about 5 months ago. I'm currently running windows 7 64 bit. I've ran multiple memory tests with 7 passes and they have all come up clean. Like I said, the blue screen are normally random, but lately, I've been getting something like atikmdag.sys. This has something to do with the video card doesn't it? Any help would be greatly appreciated.

You uploaded the app instead of the results. Please try this method.




To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.



To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

Minidumps

Mzimzim said:

Minidumps

The crashes have many different caused but most of them point to your video driver.

I would re-install it using this.
When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

Or Phyxion.net - Driver Sweeper

When it is removed then download and install the fresh copy.

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\New folder\051511-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02c15000 PsLoadedModuleList = 0xfffff800`02e5a650
Debug session time: Sun May 15 21:36:32.916 2011 (GMT-4)
System Uptime: 0 days 9:26:23.227
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff8802cd9f2e8, a, 0, fffff88004cc6a28}

Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+3d9a28 )

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

2: 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: fffff8802cd9f2e8, memory referenced
Arg2: 000000000000000a, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88004cc6a28, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec4100
 fffff8802cd9f2e8 

CURRENT_IRQL:  a

FAULTING_IP: 
atikmdag+3d9a28
fffff880`04cc6a28 8b1482          mov     edx,dword ptr [rdx+rax*4]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xD1

PROCESS_NAME:  SC2.exe

TRAP_FRAME:  fffff88009fe3520 -- (.trap 0xfffff88009fe3520)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000009fe3800 rbx=0000000000000000 rcx=fffff9800a34afd8
rdx=fffff88004e112e8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004cc6a28 rsp=fffff88009fe36b0 rbp=fffffa8008f39000
 r8=fffff88004e11318  r9=0000000000000000 r10=fffff98001548f90
r11=fffff88009fe3798 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
atikmdag+0x3d9a28:
fffff880`04cc6a28 8b1482          mov     edx,dword ptr [rdx+rax*4] ds:76a0:fffff880`2cd9f2e8=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c942a9 to fffff80002c94d00

STACK_TEXT:  
fffff880`09fe33d8 fffff800`02c942a9 : 00000000`0000000a fffff880`2cd9f2e8 00000000`0000000a 00000000`00000000 : nt!KeBugCheckEx
fffff880`09fe33e0 fffff800`02c92f20 : 000000ba`00000000 00000000`00000000 00000000`000001f1 fffffa80`08fd6020 : nt!KiBugCheckDispatch+0x69
fffff880`09fe3520 fffff880`04cc6a28 : 00000000`00000000 fffff880`09fe3780 7ff00000`00000000 fffff880`0449a38c : nt!KiPageFault+0x260
fffff880`09fe36b0 00000000`00000000 : fffff880`09fe3780 7ff00000`00000000 fffff880`0449a38c fffffa80`05913000 : atikmdag+0x3d9a28


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atikmdag+3d9a28
fffff880`04cc6a28 8b1482          mov     edx,dword ptr [rdx+rax*4]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  atikmdag+3d9a28

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d40a4bc

FAILURE_BUCKET_ID:  X64_0xD1_VRF_atikmdag+3d9a28

BUCKET_ID:  X64_0xD1_VRF_atikmdag+3d9a28

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

I actually just used this program about a week ago to update my video driver. It didn't work. Is there any chance this could could be hardware related?

Mzimzim said:

I actually just used this program about a week ago to update my video driver. It didn't work. Is there any chance this could could be hardware related?

sure there is. It could be driver, video card, vram, power, heat, etc.