BSOD memory management

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by lostinspace, Feb 4, 2010.

  1. lostinspace

    lostinspace New Member

    Joined:
    Feb 4, 2010
    Messages:
    4
    Likes Received:
    0
    Hi, I built a pc late last year.
    (not sure which specs you need)
    core i5 proc
    motherboard ASUS P6T DELUXE V2 1366 X58 RT
    VGA PNY VCGGTX260CXPB GTX 260 (nvidia video card)
    6GB OCZ memory

    I went ahead and put windows 7 (64 bit) on the box, I'm mostly playing games with it. I've been plagued with BSOD (memory management) everything I'm seeing on the boards says I need to look at my DMP file, but when I open it with the WinDbg all I see are hieroglyphs. My suspicion is that I have bad memory, it looks like there is a way for me to test them to tell which are good and which are bad, I'm not sure what to do, for that matter I'm not entirely sure it is bad memory. I've downloaded the latest drivers for everything I could think of, could use some help if you have any ideas. I tried to upload the dmp file but it isn't a valid file type to upload.
     
  2. reghakr

    reghakr Excellent Member

    Joined:
    Jan 26, 2009
    Messages:
    14,220
    Likes Received:
    180
    Try right-clicking on the executable file itself,choose the Compatibility tab and run it in XP mode.

    There are also other adjustments you can make here.

    Good luck.
     
  3. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    There is a lot of different things you can try, but I would first recommend investigating (googling) XMP mode it seems that with some memory it's better left off and with some memory in needs to be on. Maybe experiment, if it's on turn it off or vice versa. See if that helps
     
  4. lostinspace

    lostinspace New Member

    Joined:
    Feb 4, 2010
    Messages:
    4
    Likes Received:
    0
    I got the dmp to finally open up. Here is what I am seeing. I hit the !analyze to get the second set of data. I'm not sure what to make of the (Probably caused by : ntkrnlmp.exe) and the (DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT) in the second set of data.

    1st set
    ------------------------------------
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\020410-17628-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\symbols*Symbol information
    Executable search path is:
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02a60000 PsLoadedModuleList = 0xfffff800`02c9de50
    Debug session time: Thu Feb 4 18:04:35.509 2010 (GMT-8)
    System Uptime: 0 days 0:33:47.397
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1A, {41201, fffff680001cf040, 8200001e43491867, fffffa8006a4a0b0}

    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13bf2 )

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

    1st set
    ------------------------------------
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000041201, The subtype of the bugcheck.
    Arg2: fffff680001cf040
    Arg3: 8200001e43491867
    Arg4: fffffa8006a4a0b0

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


    BUGCHECK_STR: 0x1a_41201

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    PROCESS_NAME: League of Lege

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from fffff80002b321ee to fffff80002ad1f00

    STACK_TEXT:


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt! ?? ::FNODOBFM::`string'+13bf2
    fffff800`02b321ee cc int 3

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+13bf2

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

    FAILURE_BUCKET_ID: X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13bf2

    BUCKET_ID: X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13bf2

    Followup: MachineOwner
    ---------
     
  5. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833

Share This Page

Loading...