Memory_Management BSOD


  1. Posts : 6
    Windows 7
       #1

    Memory_Management BSOD


    Keep on getting random Memory_Management BSOD.
    System spec should be on my acc info.

    Attached DUMP folder to this post in a winrar file, also added extra info to it.


    I hope you guys know what the problem could be, I am depending on you.

    Edit: Ps; using 64 bit.
    Edit2: This was a clean install, and it is a new computer.
      My Computer


  2. Posts : 6,885
    Windows 7 Ultimate x64, Mint 9
       #2

    Something called KitchenBrigade is in there... Any idea what that is?

    ~Lordbob
      My Computer


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

    Baksteent said:
    Keep on getting random Memory_Management BSOD.
    System spec should be on my acc info.

    Attached DUMP folder to this post in a winrar file, also added extra info to it.


    I hope you guys know what the problem could be, I am depending on you.

    Edit: Ps; using 64 bit.
    Edit2: This was a clean install, and it is a new computer.

    Hi Baksteent and welcome


    Well this one is pretty obvious. Memory management.

    I would

    download memtestx86 and run it for several hours at least. So we cann tell if it is memory or heat

    Also run a system file check to verify and repair your system files to do that
    type cmd in search>right click and run as admin>sfc /scannow

    Also if you are overclocking stop
    if you have a raid update its driver

    Hope this helps


    Ken J+


    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\122209-16130-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*d:\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 Personal
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02809000 PsLoadedModuleList = 0xfffff800`02a46e50
    Debug session time: Tue Dec 22 15:48:56.612 2009 (GMT-5)
    System Uptime: 0 days 5:14:45.094
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................
    Loading User Symbols
    Loading unloaded module list
    ..............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1A, {3452, 1040e000, fffff700010b6200, baf0000116751856}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33ab3 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000003452, The subtype of the bugcheck.
    Arg2: 000000001040e000
    Arg3: fffff700010b6200
    Arg4: baf0000116751856
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x1a_3452
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  kitchenbrigade
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff800028ed343 to fffff8000287af00
    
    STACK_TEXT:  
    fffff880`0723a018 fffff800`028ed343 : 00000000`0000001a 00000000`00003452 00000000`1040e000 fffff700`010b6200 : nt!KeBugCheckEx
    fffff880`0723a020 fffff800`0284deee : fffffa80`04787750 fffffa80`00000004 fffff880`00004a38 fffff800`0000000b : nt! ?? ::FNODOBFM::`string'+0x33ab3
    fffff880`0723a8d0 fffff800`02b5d7af : fffff8a0`0ae1c580 fffff880`0723abe0 00000000`00000000 fffffa80`0539d060 : nt!MmCleanProcessAddressSpace+0x96
    fffff880`0723a920 fffff800`02b37b3d : 00000000`c0000005 fffff8a0`0612bd01 00000000`7ef9e000 fffffa80`06246b60 : nt!PspExitThread+0x47f
    fffff880`0723a9f0 fffff800`02857a43 : fffffa80`05dd3a10 fffffa80`062fa850 00000000`00000000 00000000`00000000 : nt!PsExitSpecialApc+0x1d
    fffff880`0723aa20 fffff800`02857e80 : 00000000`0a1bfedc fffff880`0723aaa0 fffff800`02b38710 00000000`00000001 : nt!KiDeliverApc+0x2eb
    fffff880`0723aaa0 fffff800`0287a1f7 : fffffa80`0539d060 00000000`7ef9e000 00000000`000000c0 00000000`7ef9e000 : nt!KiInitiateUserApc+0x70
    fffff880`0723abe0 00000000`771917ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
    00000000`0a0be7e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x771917ba
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+33ab3
    fffff800`028ed343 cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+33ab3
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
    
    FAILURE_BUCKET_ID:  X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+33ab3
    
    BUCKET_ID:  X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+33ab3
    
    Followup: MachineOwner
    ---------
    edit: LB kitchebrigade is a game
      My Computer


  4. Posts : 6,885
    Windows 7 Ultimate x64, Mint 9
       #4

    Thanks Ken (for the rep too),

    I thought it was, just wasnt sure if it was on there intentionally or not. Seems like that may have been a part of the problem.

    ~Lordbob
      My Computer


  5. Posts : 6
    Windows 7
    Thread Starter
       #5

    Thanks for the help so far guys,

    And yeah kitchen brigade is a game, fixing my motherŽs pc.
    IŽll try what you guys asked after Christmas, chances are it is indeed the heat (However the IDLE temp was 42 degree at startup).

    IŽll let you know how it went.


    Merry Christmas!
    Jeff
      My Computer


  6. Posts : 6
    Windows 7
    Thread Starter
       #6

    Where to get Memtestx86? I googled it and only got an iso file.

    And I am blaming the heat more and more... that would mean I'd have to get a new case + casefans, so lets hope thats not the problem.


    Greets
    Jeff
      My Computer


  7. Posts : 6,885
    Windows 7 Ultimate x64, Mint 9
       #7

    Burn the ISO to a disk, and boot into it.

    ~Lordbob
      My Computer


  8. Posts : 6
    Windows 7
    Thread Starter
       #8

    Would you like explaining what it does? I like learning from this, since I am a Junior in the IT.


    Added the "CBS" file I got from the "type cmd in search>right click and run as admin>sfc /scannow" command.

    Many thanks!

    Greets,
    Jeff
      My Computer


  9. Posts : 6,885
    Windows 7 Ultimate x64, Mint 9
       #9

    MemTest checks your memory for faults.

    ~Lordbob
      My Computer


 

  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 02:11.
Find Us