1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Windows Vista Special_pool_detected_memory_corruption

Discussion in 'Legacy Windows' started by miamiparis, 2008/02/23.

  1. 2008/02/23
    miamiparis

    miamiparis Inactive Thread Starter

    Joined:
    2008/02/23
    Messages:
    3
    Likes Received:
    0
    Since 2 weeks, I have blue screen that appear once a day inaverage with SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION. I'm beginner in debugging blue screens.
    I used windbg on the same PC and below is the result. I called Dell and they advised me to reinstall all the operating system and Dell programs. I prefer to come here and try to pinpoint the problem.
    Here is the log:

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


    Loading Dump File [C:\Windows\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available

    Symbol search path is: SRV**http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 6000.16584.x86fre.vista_gdr.071023-1545
    Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
    Debug session time: Sat Feb 23 16:28:58.285 2008 (GMT+1)
    System Uptime: 0 days 0:03:47.066
    Loading Kernel Symbols
    .......................................................................................................................................................................
    Loading User Symbols

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

    Use !analyze -v to get detailed debugging information.

    BugCheck C1, {b47e2ff8, b47e2008, 0, 23}





    Probably caused by : memory_corruption ( nt!MmFreeSpecialPool+69 )

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

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

    SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
    Special pool has detected memory corruption. Typically the current thread's
    stack backtrace will reveal the guilty party.
    Arguments:
    Arg1: b47e2ff8, address trying to free
    Arg2: b47e2008, address where bits are corrupted
    Arg3: 00000000, (reserved)
    Arg4: 00000023, caller is freeing an address where nearby bytes within the same page have been corrupted

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






    BUGCHECK_STR: 0xC1_23

    SPECIAL_POOL_CORRUPTION_TYPE: 23

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from 81ce1ca5 to 81cd8681

    STACK_TEXT:
    83463bcc 81ce1ca5 000000c1 b47e2ff8 b47e2008 nt!KeBugCheckEx+0x1e
    83463c44 81ce7c54 b47e2ff8 b69f4fe0 00000000 nt!MmFreeSpecialPool+0x69
    83463ca8 81d9830d b47e2ff8 00000000 00000000 nt!ExFreePoolWithTag+0xeb
    83463cc8 81d95173 00000000 863b3cd8 00000000 nt!IopDeleteFileObjectExtension+0x78
    83463d0c 81ded505 863b3d00 00000000 863b3d00 nt!IopDeleteFile+0x26a
    83463d28 81ded3d0 863b3d00 00000001 81cfde40 nt!ObpRemoveObjectRoutine+0x100
    83463d44 81c78fa0 00000000 00000000 85d4b470 nt!ObpProcessRemoveObjectQueue+0x39
    83463d7c 81e254e0 00000000 83468680 00000000 nt!ExpWorkerThread+0xfd
    83463dc0 81c9159e 81c78ea3 00000000 00000000 nt!PspSystemThreadStartup+0x9d
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!MmFreeSpecialPool+69
    81ce1ca5 cc int 3

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt!MmFreeSpecialPool+69

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 471ea39c

    IMAGE_NAME: memory_corruption

    FAILURE_BUCKET_ID: 0xC1_23_VRF_nt!MmFreeSpecialPool+69

    BUCKET_ID: 0xC1_23_VRF_nt!MmFreeSpecialPool+69

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

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

    SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
    Special pool has detected memory corruption. Typically the current thread's
    stack backtrace will reveal the guilty party.
    Arguments:
    Arg1: b47e2ff8, address trying to free
    Arg2: b47e2008, address where bits are corrupted
    Arg3: 00000000, (reserved)
    Arg4: 00000023, caller is freeing an address where nearby bytes within the same page have been corrupted

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






    BUGCHECK_STR: 0xC1_23

    SPECIAL_POOL_CORRUPTION_TYPE: 23

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from 81ce1ca5 to 81cd8681

    STACK_TEXT:
    83463bcc 81ce1ca5 000000c1 b47e2ff8 b47e2008 nt!KeBugCheckEx+0x1e
    83463c44 81ce7c54 b47e2ff8 b69f4fe0 00000000 nt!MmFreeSpecialPool+0x69
    83463ca8 81d9830d b47e2ff8 00000000 00000000 nt!ExFreePoolWithTag+0xeb
    83463cc8 81d95173 00000000 863b3cd8 00000000 nt!IopDeleteFileObjectExtension+0x78
    83463d0c 81ded505 863b3d00 00000000 863b3d00 nt!IopDeleteFile+0x26a
    83463d28 81ded3d0 863b3d00 00000001 81cfde40 nt!ObpRemoveObjectRoutine+0x100
    83463d44 81c78fa0 00000000 00000000 85d4b470 nt!ObpProcessRemoveObjectQueue+0x39
    83463d7c 81e254e0 00000000 83468680 00000000 nt!ExpWorkerThread+0xfd
    83463dc0 81c9159e 81c78ea3 00000000 00000000 nt!PspSystemThreadStartup+0x9d
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!MmFreeSpecialPool+69
    81ce1ca5 cc int 3

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt!MmFreeSpecialPool+69

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 471ea39c

    IMAGE_NAME: memory_corruption

    FAILURE_BUCKET_ID: 0xC1_23_VRF_nt!MmFreeSpecialPool+69

    BUCKET_ID: 0xC1_23_VRF_nt!MmFreeSpecialPool+69

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

    1: kd> lmvm nt
    start end module name
    81c00000 81fa1000 nt (pdb symbols) C:\Program Files\Debugging Tools for Windows\sym\ntkrpamp.pdb\03D7DBF252F448A484A9E17FB7734EE62\ntkrpamp.pdb
    Loaded symbol image file: ntkrpamp.exe
    Image path: ntkrpamp.exe
    Image name: ntkrpamp.exe
    Timestamp: Wed Oct 24 03:45:00 2007 (471EA39C)
    CheckSum: 00363BFB
    ImageSize: 003A1000
    File version: 6.0.6000.16584
    Product version: 6.0.6000.16584
    File flags: 0 (Mask 3F)
    File OS: 40004 NT Win32
    File type: 1.0 App
    File date: 00000000.00000000
    Translations: 0409.04b0
    CompanyName: Microsoft Corporation
    ProductName: Microsoft® Windows® Operating System
    InternalName: ntkrpamp.exe
    OriginalFilename: ntkrpamp.exe
    ProductVersion: 6.0.6000.16584
    FileVersion: 6.0.6000.16584 (vista_gdr.071023-1545)
    FileDescription: NT Kernel & System
    LegalCopyright: © Microsoft Corporation. All rights reserved.
     
    miamiparis,
    #1
  2. 2008/02/23
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    miamiparis - Welcome to the Board :)

    A caveat ....
    However, as your log states ....
    I suggest you use the built-in memory checker in Vista, again with a caveat ....
    The best way of checking RAM is to switch the sticks around the slots - if you have two sticks and 4 slots try the other two slots - run each stick on it's own switching it around in the slots and so on. I'm sure you get the general gist :)
    Typical and not unexpected - it's the simple fix all solution - maybe - not :)
     
    PeteC,
    #2


  3. to hide this advert.

  4. 2008/02/23
    miamiparis

    miamiparis Inactive Thread Starter

    Joined:
    2008/02/23
    Messages:
    3
    Likes Received:
    0
    Slots

    I had 2 sticks of 512 MB and 2 slots. I had the blue screen problem. I bought 2 sticks of 2 GB each and installed them. I had the same blue screen.
    So you would advise me to remove 1 stick and wait and see if the error comes back, and if yes, move the stick to the other slot?
    The problem could come from 1 of the slot ? not the memory sticks ?
     
    miamiparis,
    #3
  5. 2008/02/23
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Yes

    Are you sure that the memory is compatible with your mobo?
     
    PeteC,
    #4
  6. 2008/02/23
    miamiparis

    miamiparis Inactive Thread Starter

    Joined:
    2008/02/23
    Messages:
    3
    Likes Received:
    0
    memory

    Yes, it's compatible. I see the 3.5 GB displayed in the system.
    Anyway, there was the same blue screen when I used the original 1 GB that came with my Dell laptop.
     
    miamiparis,
    #5
  7. 2008/02/23
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    No, that shows it is recognised by the computer, but not necessarily fully compatible in terms of memory timings and voltage :)
     
    PeteC,
    #6

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...