BSOD unsure if it's memory

Page 1 of 4 123 ... LastLast

  1. Posts : 39
    Windows 7 Home Premium 32bit
       #1

    BSOD unsure if it's memory


    Hello,

    My computer arrived on April 30th 2011, so it's new and I'm getting the BSOD.

    I think it is bad memory, but Cyberpower wants me to be sure. They'll take the computer in for service, but that means I'm out a PC for a long time.

    I have attached the latest dump file and am curious if anyone can diagnose it.


    I have Windows 7 Home Premium.

    AMD Dragon...something

    AMD Phenom II
    x6 109T Processor
    3.20 GHZ

    8 Gig of Ram
    64 Bit Operating System

    AMD Radeon 6800 Series Video Card

    I have run Memtest86 on each memory stick individually. All of them in all slots report an error 31% into the test.

    Thanks for your help!
      My Computer


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

    Rmarsden said:
    Hello,

    My computer arrived on April 30th 2011, so it's new and I'm getting the BSOD.

    I think it is bad memory, but Cyberpower wants me to be sure. They'll take the computer in for service, but that means I'm out a PC for a long time.

    I have attached the latest dump file and am curious if anyone can diagnose it.


    I have Windows 7 Home Premium.

    AMD Dragon...something

    AMD Phenom II
    x6 109T Processor
    3.20 GHZ

    8 Gig of Ram
    64 Bit Operating System

    AMD Radeon 6800 Series Video Card

    I have run Memtest86 on each memory stick individually. All of them in all slots report an error 31% into the test.

    Thanks for your help!
    Indeed was memory corruption but I suspect from a driver.

    What error and on what pass did memtest error?

    Also please run driver verifier to find the problem driver

    I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
      My Computer


  3. Posts : 39
    Windows 7 Home Premium 32bit
    Thread Starter
       #3

    Will do.

    I don't make it a single pass before the memtest86 shows errors around 30% into the test. The screen starts to turn red and numbers pass by and don't seem to want to stop. I'm a novice at memtest86 and may not be understanding it correctly.

    If it helps, it normally seems to crash when playing video on the internet using Chrome or Explorer. Occasionally, when I'm using Word. I've not had it crash during any games.

    I'll work on figuring out driver verifier!
      My Computer


  4. Posts : 28,845
    Win 8 Release candidate 8400
       #4

    Rmarsden said:
    Will do.

    I don't make it a single pass before the memtest86 shows errors around 30% into the test. The screen starts to turn red and numbers pass by and don't seem to want to stop. I'm a novice at memtest86 and may not be understanding it correctly.

    If it helps, it normally seems to crash when playing video on the internet using Chrome or Explorer. Occasionally, when I'm using Word. I've not had it crash during any games.

    I'll work on figuring out driver verifier!
    If memtest errors on a single pass outside of the windows environment there is a memory problem. You can narrow it to single stick by testing them one at a time. ALso test them with a known good stick in each slot
      My Computer


  5. Posts : 39
    Windows 7 Home Premium 32bit
    Thread Starter
       #5

    Maybe this will make sense to you.

    I have 4 sticks. I tested each alone and each had an error at 31% into the first test. So I don't think it even gets passed the first pass.

    I tried the sticks in different slots and had the same issue.

    Every stick fails at 31%. when tested alone no matter the slot.

    The computer is just over a month old and only recently acted this way.

    I'll get on the driver testing soon as I can and give you more information. While I can get the computer back to Cyberpower for repairs, if I do so, I doubt I'll see it again anytime soon.
      My Computer


  6. Posts : 39
    Windows 7 Home Premium 32bit
    Thread Starter
       #6

    A few more dumpfiles, might be of use finding out what is crashing my computer.
      My Computer


  7. Posts : 39
    Windows 7 Home Premium 32bit
    Thread Starter
       #7

    It's getting worse. Crashes on startup. Crashes during games.

    Some more dmp files!

    I haven't gone through driver verify yet. I need to back up files and get a second computer ready in case this one won't start back up.
      My Computer


  8. Posts : 28,845
    Win 8 Release candidate 8400
       #8

    Rmarsden said:
    It's getting worse. Crashes on startup. Crashes during games.

    Some more dmp files!

    I haven't gone through driver verify yet. I need to back up files and get a second computer ready in case this one won't start back up.
    These were related to your video driver. I would re-install newest using this method


    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


    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\061611-21606-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 (6 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Machine Name:
    Kernel base = 0xfffff800`03058000 PsLoadedModuleList = 0xfffff800`0329d650
    Debug session time: Thu Jun 16 13:18:24.852 2011 (GMT-4)
    System Uptime: 0 days 0:03:29.991
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ............................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {fffff80004cd60cb, 1, fffff88004cd60b5, 2}
    
    Unable to load image 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+4810b5 )
    
    Followup: MachineOwner
    ---------
    
    3: 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: fffff80004cd60cb, memory referenced.
    Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
    Arg3: fffff88004cd60b5, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000002, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003307100
     fffff80004cd60cb 
    
    FAULTING_IP: 
    atikmdag+4810b5
    fffff880`04cd60b5 66413100        xor     word ptr [r8],ax
    
    MM_INTERNAL_CODE:  2
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff88003ee5a90 -- (.trap 0xfffff88003ee5a90)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=000000000000f13c rbx=0000000000000000 rcx=0000000000000038
    rdx=fffff88003ee5c70 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88004cd60b5 rsp=fffff88003ee5c28 rbp=cccccccccccccccd
     r8=fffff80004cd60cb  r9=fffff88003ee5c70 r10=0000000000024184
    r11=fffff88002fd5101 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up di pl nz na po nc
    atikmdag+0x4810b5:
    fffff880`04cd60b5 66413100        xor     word ptr [r8],ax ds:5ca8:fffff800`04cd60cb=????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80003082400 to fffff800030d7d00
    
    STACK_TEXT:  
    fffff880`03ee5928 fffff800`03082400 : 00000000`00000050 fffff800`04cd60cb 00000000`00000001 fffff880`03ee5a90 : nt!KeBugCheckEx
    fffff880`03ee5930 fffff800`030d5e2e : 00000000`00000001 fffff800`04cd60cb 2483da56`d36c8d00 00000000`00000004 : nt! ?? ::FNODOBFM::`string'+0x448c6
    fffff880`03ee5a90 fffff880`04cd60b5 : fffff880`04c96714 fffff880`04ed7600 cccccccc`00000000 00000000`00000000 : nt!KiPageFault+0x16e
    fffff880`03ee5c28 fffff880`04c96714 : fffff880`04ed7600 cccccccc`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x4810b5
    fffff880`03ee5c30 fffff880`04ed7600 : cccccccc`00000000 00000000`00000000 00000000`00000000 fffff880`030a4180 : atikmdag+0x441714
    fffff880`03ee5c38 cccccccc`00000000 : 00000000`00000000 00000000`00000000 fffff880`030a4180 fffff8a0`0001d085 : atikmdag+0x682600
    fffff880`03ee5c40 00000000`00000000 : 00000000`00000000 fffff880`030a4180 fffff8a0`0001d085 00000003`00000285 : 0xcccccccc`00000000
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    atikmdag+4810b5
    fffff880`04cd60b5 66413100        xor     word ptr [r8],ax
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  atikmdag+4810b5
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmdag
    
    IMAGE_NAME:  atikmdag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4dae3c99
    
    FAILURE_BUCKET_ID:  X64_0x50_atikmdag+4810b5
    
    BUCKET_ID:  X64_0x50_atikmdag+4810b5
    
    Followup: MachineOwner
    ---------
      My Computer


  9. Posts : 39
    Windows 7 Home Premium 32bit
    Thread Starter
       #9

    Ok I downloaded Driver Sweeper

    I deleted the video card driver

    I used Driver Sweeper

    When I restarted the computer a new driver automatically installed.

    I used Driver Updater and it says all drivers are up to date.

    I'll post any other crashes if they occur.
      My Computer


  10. Posts : 39
    Windows 7 Home Premium 32bit
    Thread Starter
       #10

    Crashed on facebook, screen turned into a bunch of lines first, then bsod said it was making a dump file but did not.

    Will keep you posted.

    My 'gut' tells me something with the video card! Will keep you posted. When I use driver-verifier what does it do 'different'? Are the dump files more informative?
      My Computer


 
Page 1 of 4 123 ... LastLast

  Related Discussions
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 06:43.
Find Us