BSOD RAM related


  1. supersport650
    Posts : 3
    Windows 7 Ultimate 64-bit
       New #1

    BSOD RAM related


    i keep getting BSOD and im not sure why. i know it has something to do with the RAM cuz i just installed another 4GB and i started getting the BSOD. i need help. ive tried playing with the timing and it helped a bit but im still getting them. i've attached the last 3 .dmp files
      My Computer
    Quote Quote

  3. zigzag3143
    Posts : 28,845
    Win 8 Release candidate 8400
       New #2

    supersport650 said:
    i keep getting BSOD and im not sure why. i know it has something to do with the RAM cuz i just installed another 4GB and i started getting the BSOD. i need help. ive tried playing with the timing and it helped a bit but im still getting them. i've attached the last 3 .dmp files
    Actually two of these three were caused by your video driver. the third by partmgr.sys. It certainly doesnt help that you have drivers from 2006.

    I would update the drivers, use ati's uninstall tool to completely remove this driver and just install the driver not all the other components.


    drivers
    Code:
    secdrv.SYS        fffff880`0638c000    fffff880`06397000    0x0000b000    0x4508052e    9/13/2006 9:18:38 AM                        
speedfan.sys        fffff880`018f9000    fffff880`01900000    0x00007000    0x45168798    9/24/2006 9:26:48 AM                        
Alpham264.sys        fffff880`06ff9000    fffff880`06ffe500    0x00005500    0x45ffae87    3/20/2007 5:51:03 AM                        
Alpham164.sys        fffff880`03fce000    fffff880`03fdaf00    0x0000cf00    0x46a45f4f    7/23/2007 3:57:03 AM                        
AtiPcie.sys        fffff880`019d5000    fffff880`019dd000    0x00008000    0x4a005486    5/5/2009 11:00:22 AM
    analysis
    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 (3)\050510-18844-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
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c0f000 PsLoadedModuleList = 0xfffff800`02e4ce50
Debug session time: Wed May  5 23:18:09.987 2010 (GMT-4)
System Uptime: 0 days 1:36:40.688
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa8052a62377, 0, fffff88004aa640f, 5}

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

Could not read faulting driver name
Probably caused by : atikmdag.sys ( atikmdag+28740f )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa8052a62377, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88004aa640f, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb70e0
 fffffa8052a62377 

FAULTING_IP: 
atikmdag+28740f
fffff880`04aa640f 488b90ff525048  mov     rdx,qword ptr [rax+485052FFh]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88005fb6d60 -- (.trap 0xfffff88005fb6d60)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800a55d078 rbx=0000000000000000 rcx=fffffa800a55d080
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004aa640f rsp=fffff88005fb6ef0 rbp=fffffa800a43bea0
 r8=0000000000000003  r9=fffffa800a73e000 r10=fffff8a001b24800
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
atikmdag+0x28740f:
fffff880`04aa640f 488b90ff525048  mov     rdx,qword ptr [rax+485052FFh] ds:fffffa80`52a62377=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cfe801 to fffff80002c7f600

STACK_TEXT:  
fffff880`05fb6bf8 fffff800`02cfe801 : 00000000`00000050 fffffa80`52a62377 00000000`00000000 fffff880`05fb6d60 : nt!KeBugCheckEx
fffff880`05fb6c00 fffff800`02c7d6ee : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40ecb
fffff880`05fb6d60 fffff880`04aa640f : fffffa80`00000001 fffffa80`00000000 fffffa80`0a43bea0 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`05fb6ef0 fffffa80`00000001 : fffffa80`00000000 fffffa80`0a43bea0 00000000`00000000 fffffa80`0a8c2030 : atikmdag+0x28740f
fffff880`05fb6ef8 fffffa80`00000000 : fffffa80`0a43bea0 00000000`00000000 fffffa80`0a8c2030 40001500`04f869a0 : 0xfffffa80`00000001
fffff880`05fb6f00 fffffa80`0a43bea0 : 00000000`00000000 fffffa80`0a8c2030 40001500`04f869a0 fffffa80`0a8c2030 : 0xfffffa80`00000000
fffff880`05fb6f08 00000000`00000000 : fffffa80`0a8c2030 40001500`04f869a0 fffffa80`0a8c2030 00000000`00000001 : 0xfffffa80`0a43bea0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atikmdag+28740f
fffff880`04aa640f 488b90ff525048  mov     rdx,qword ptr [rax+485052FFh]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  atikmdag+28740f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ab445a4

FAILURE_BUCKET_ID:  X64_0x50_atikmdag+28740f

BUCKET_ID:  X64_0x50_atikmdag+28740f

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa8052a62377, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88004aa640f, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS:  fffffa8052a62377 

FAULTING_IP: 
atikmdag+28740f
fffff880`04aa640f 488b90ff525048  mov     rdx,qword ptr [rax+485052FFh]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88005fb6d60 -- (.trap 0xfffff88005fb6d60)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800a55d078 rbx=0000000000000000 rcx=fffffa800a55d080
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004aa640f rsp=fffff88005fb6ef0 rbp=fffffa800a43bea0
 r8=0000000000000003  r9=fffffa800a73e000 r10=fffff8a001b24800
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
atikmdag+0x28740f:
fffff880`04aa640f 488b90ff525048  mov     rdx,qword ptr [rax+485052FFh] ds:fffffa80`52a62377=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cfe801 to fffff80002c7f600

STACK_TEXT:  
fffff880`05fb6bf8 fffff800`02cfe801 : 00000000`00000050 fffffa80`52a62377 00000000`00000000 fffff880`05fb6d60 : nt!KeBugCheckEx
fffff880`05fb6c00 fffff800`02c7d6ee : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40ecb
fffff880`05fb6d60 fffff880`04aa640f : fffffa80`00000001 fffffa80`00000000 fffffa80`0a43bea0 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`05fb6ef0 fffffa80`00000001 : fffffa80`00000000 fffffa80`0a43bea0 00000000`00000000 fffffa80`0a8c2030 : atikmdag+0x28740f
fffff880`05fb6ef8 fffffa80`00000000 : fffffa80`0a43bea0 00000000`00000000 fffffa80`0a8c2030 40001500`04f869a0 : 0xfffffa80`00000001
fffff880`05fb6f00 fffffa80`0a43bea0 : 00000000`00000000 fffffa80`0a8c2030 40001500`04f869a0 fffffa80`0a8c2030 : 0xfffffa80`00000000
fffff880`05fb6f08 00000000`00000000 : fffffa80`0a8c2030 40001500`04f869a0 fffffa80`0a8c2030 00000000`00000001 : 0xfffffa80`0a43bea0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atikmdag+28740f
fffff880`04aa640f 488b90ff525048  mov     rdx,qword ptr [rax+485052FFh]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  atikmdag+28740f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ab445a4

FAILURE_BUCKET_ID:  X64_0x50_atikmdag+28740f

BUCKET_ID:  X64_0x50_atikmdag+28740f

Followup: MachineOwner
---------
      My Computer
    Quote Quote

  4. supersport650
    Posts : 3
    Windows 7 Ultimate 64-bit
    Thread Starter
       New #3

    im still getting BSOD last night eveything seemed fine after replace the driver but a few mins ago my comp had 2 BSOD. add the dmp files from them. thanks for your help in advanced.

    --------------------------------------------------------------------------------------
    crashed again here is another dmp file
    Last edited by supersport650; 06 May 2010 at 17:38.
      My Computer
    Quote Quote

 

  Related Discussions
BSOD Most likely GPU-related
in BSOD Help and Support

Getting BSODs where the screen goes black, fans go crazy and computer restarts. I can only speculate on why it's happening but either it's completely random or it's got something to do with me using Google Chrome. I've tried rolling my GPU drivers back to last stable build but that did not fix the...
BSOD SSD related?
in BSOD Help and Support

Hello everyone, Recently built this computer. Had a BSOD within 24hrs of running but otherwise was fine in the first few days, even finished Crysis 3 without any problems. Had a bunch of BSODs yesterday, so I started poking around. Updated MOBO and SSD firmware. Realized the timings on my RAM...
BSOD browser related/vssc.exe related
in BSOD Help and Support

Been getting fairly regular BSOD's that only seem to happen when using a web browser. Chrome BSOD fairly regularly. Firefox less so (Only once). I've also had a vssc.exe BSOD when the pc was idle. Windows fully up to date. All drivers up to date. No conflicts. I've run a sfc scan with no errors or...
My PC has recently started erratic BSOD crashes after a year of bliss. I installed UBUNTU as second boot option and it seems to work normally. Would rather not just give up on Windows 7 - particularly as this is x64 version and UBUNTU is only x86 version; I also have some windows-only software...
BSOD perhaps GPU related
in BSOD Help and Support

I'm running x64 bit 7 Home Premium on a Alienware M11x R2. I just reformatted (they give you a real 7 DVD) and exchanged drives for an SSD but I still get the BSODs. I only use the system for WoW, email, and to edit my pictures--so I don't have a large program base to troubleshoot--but it only...
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 11:38.
Find Us