bsod help

hi heres my new build setup:
Asus P5Q Pro Turbo motherboard
Windows 7 professional 64 bit operating system
Intel Core 2 Duo E7500 2.93GHz Socket 775 1066FSB 3MB L2 Cache Retail Boxed Processor
OCZ 4GB Kit (2x2GB) DDR2 1066MHz/PC2-8500 Reaper Memory HPC Edition Dual Channel
XFX HD 4890 XXX Edition 1GB DDR5 Dual DVI HDTV Out PCI-E Graphics
850w NorthQ Black Magic Flex Power Supplie
2 x 1TB Seagate ST310005N1D1AS-RK Barracuda 7200.11, SATA 3Gb/s, 7200rpm, 32MB Cache, 8.5 ms set up in raid
i keep getting the blue screen of death with random error codes memory has been tested lots of times with no errors also the graphis card and cpu seems to be no problems
downloaded lastet drivers from asus
heres some of the many error codes:
Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.256.48 Locale
ID: 2057 Additional information about the problem:
BCCode: 1e BCP1: FFFFFFFFC0000005 BCP2: FFFFF80002AFC35F BCP3: 0000000000000000 BCP4: FFFFFFFFFFFFFFFF OS Version: 6_1_7600 Service Pack: 0_0 Product: 256_1
Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.256.48 Locale
ID: 2057 Additional information about the problem:
BCCode: 3b BCP1: 00000000C0000005 BCP2: FFFFF80002BF40F3 BCP3: FFFFF88006F2CB40 BCP4: 0000000000000000 OS Version: 6_1_7600 Service Pack: 0_0 Product: 256_1 plus many many more also installed windows 7 32 bit everything seems to work fine no crashes but i do not want to run a 32 bit operating system so please can anybody help...........

will do where do i find it

here you go thanx for help ...Attachment 27088

attached dumps above

pearcie said:

here you go thanx for help ...Attachment 27088

Pearcie

After a quick look at the latest dump file it seems to have been caused by the atikmdag.sys. If I were you I would download the ati driver again and install it. You can check to see what version you have by going into device manager (type device manager in search) and look for the appropriate drivers


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


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

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a4d000 PsLoadedModuleList = 0xfffff800`02c8ae50
Debug session time: Sun Sep 6 19:33:54.732 2009 (GMT-4)
System Uptime: 0 days 0:05:33.339
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff880042b23a6, fffff880026cb800, 0}

Probably caused by : atikmdag.sys ( atikmdag+2843a6 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880042b23a6, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880026cb800, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
atikmdag+2843a6
fffff880`042b23a6 66398a8c000000 cmp word ptr [rdx+8Ch],cx

CONTEXT: fffff880026cb800 -- (.cxr 0xfffff880026cb800)
rax=0000000019740800 rbx=fffff8a008180420 rcx=0000000000001974
rdx=0000003180000004 rsi=fffffa8003a91948 rdi=fffffa8006678940
rip=fffff880042b23a6 rsp=fffff880026cc1e8 rbp=000000000000022c
r8=fffffa8003a91948 r9=000000000001f6a0 r10=fffff8a008180420
r11=fffff8a0081803f0 r12=fffffa80039f8bc0 r13=00000000000009af
r14=00000000000000ac r15=fffff88000be0000
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
atikmdag+0x2843a6:
fffff880`042b23a6 66398a8c000000 cmp word ptr [rdx+8Ch],cx ds:002b:00000031`80000090=????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: CoDWaW.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff880042b23a6

STACK_TEXT:
fffff880`026cc1e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x2843a6


FOLLOWUP_IP:
atikmdag+2843a6
fffff880`042b23a6 66398a8c000000 cmp word ptr [rdx+8Ch],cx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: atikmdag+2843a6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME: atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5d41c3

STACK_COMMAND: .cxr 0xfffff880026cb800 ; kb

FAILURE_BUCKET_ID: X64_0x3B_atikmdag+2843a6

BUCKET_ID: X64_0x3B_atikmdag+2843a6

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

I dont have a true debugger so Im sugesting you re-install the driver while waiting for one of our debugging guru's to give you a more comprehensive analysis

KEn

thanx zigzag3143 will give it ago im not that hopeful as i have already tried different drivers but will try again..............

pearcie said:

thanx zigzag3143 will give it ago im not that hopeful as i have already tried different drivers but will try again..............

pearcie

If that doesn't cure it upload the other bsods and we will have aa look at them all

Ken

zigzag3143 said:

pearcie said:

thanx zigzag3143 will give it ago im not that hopeful as i have already tried different drivers but will try again..............

pearcie

If that doesn't cure it upload the other bsods and we will have aa look at them all

Ken

Ken

This seems to be another good reason for me not to RUN X64.


Snuffy