0x00000019 0x0000000000000021 when using readyboost

Anonymous
2014-08-19T06:04:32+00:00

I use readyboost on my pc because it improves the speed of some the games I play (Battlefield 4, in particular). I have been using a 16 Gb. USB Flash drive since 2010 without any problem. But I recently added a 32 Gb. XD (SD) card to use for readyboost. I can access the card fine, and chkdsk says there are no errors, but since I have started using the card, I keep getting random 0x19 BSOD stop errors. the parameter is 0x21. I do not know what to do next or why readyboost is causing this error. it goes away when I stop using the 32Gb card. the full error is:

The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000019 (0x0000000000000021, 0xfffffa8010f19000, 0x0000000000001030, 0xb03c3740a81a7de7). A dump was saved in: C:\windows\Minidump\081814-32292-01.dmp. Report Id: 081814-32292-01.

I suspect readyboost is the cause of the issue, because the only difference in conditions between when it does and it does not happen is, is the use of the 32Gb card. I know that there is a 32Gb limit to the size of the memory card I can use. but using the max size should not be causing any issues

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

109 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2014-10-28T14:04:04+00:00

    I can't really say.

    All I know is your issue is likely stemming from your card reader causing problems with your new USB device, or you have bad RAM.

    Regards,

    Patrick

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-10-28T13:33:09+00:00

    the thought just occurred to me, while I was reading up on SD card terminology. I read that unless a reader specifically states it supports sdhc, it will does not support sdhc.

    If my card reader did not support sdhc, I would not be able to read much less format the card, correct?

    I can not find anywhere on or in my system that states SDHC, but yet I'm able to access, format, read and write to an SDHC card

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-10-28T12:54:34+00:00

    the SD (SDHC) card is a brand new one and there are no defective sectors detected. I have the latest O2 drivers available for my laptop. I would have thought that more effort would be put into card reader drivers than what you are indicating

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-10-28T08:30:39+00:00

    Thanks, Patrick. I am Working on reinstalling my OS.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2014-10-28T04:32:14+00:00

    Hi,

    SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)

    This indicates that the driver wrote to an invalid section of the special pool.

    BugCheck C1, {fffff900ca9acf80, 1873, 80, 21}

    Usage:                  

    Base Address:           fffff900`00000000

    End Address:            fffff960`00020000

    Region Size:            00000060`00020000

    VA Type:                SessionSpace

    VAD Address:            0x0

    Commit Charge:          0x100000001

    Protection:             0x7ff8d45dff88 []

    Memory Usage:           Private

    No Change:              yes

    6: kd> k

    Child-SP          RetAddr           Call Site

    fffff88009b306b8 fffff80003be4416 nt!KeBugCheckEx

    fffff88009b306c0 fffff80003c0f956 nt!MmFreeSpecialPool+0x196

    fffff88009b30800 fffff960000ab195 nt!ExDeferredFreePool+0xf4e

    fffff88009b308b0 fffff960000ac5f3 win32k!EXLATEOBJ::vAddToCache+0x75

    fffff88009b308f0 fffff960002227d4 win32k!EXLATEOBJ::bInitXlateObj+0x1d7

    fffff88009b30970 fffff960000ab807 win32k!NtGdiBitBltInternal+0x994

    fffff88009b30b50 fffff80003ad9e53 win32k!NtGdiBitBlt+0x5b

    fffff88009b30bc0 000007fefe5425ba nt!KiSystemServiceCopyEnd+0x13

    00000000020de768 fffff80003ad2210 0x000007fe`fe5425ba

    fffff88009b30e10 0000000000000000 nt!KiCallUserMode

    nt!MmFreeSpecialPool+0x196 is trying to free an incorrect special pool memory block that's located in session space.

    6: kd> !pte fffff900ca9acf80

                                               VA fffff900ca9acf80

    PXE at FFFFF6FB7DBEDF90    PPE at FFFFF6FB7DBF2018    PDE at FFFFF6FB7E4032A0    PTE at FFFFF6FC80654D60

    contains 00000001C5E87863  contains 00000001C7094863  contains 000000009EC96863  contains 0000000069E53863

    pfn 1c5e87    ---DA--KWEV  pfn 1c7094    ---DA--KWEV  pfn 9ec96     ---DA--KWEV  pfn 69e53     ---DA--KWEV

        [X] (0x00000000) Automatic Checks

        [X] (0x00000001) Special pool

        [ ] (0x00000002) Force IRQL checking

        [X] (0x00000008) Pool tracking

        [ ] (0x00000010) I/O verification

        [ ] (0x00000020) Deadlock detection

        [ ] (0x00000080) DMA checking

        [ ] (0x00000100) Security checks

        [ ] (0x00000800) Miscellaneous checks

    Verifier is checking for special pool corruption and tracking pool, so the fact that a driver was behind the bad call tells me you have probably bad SD card or some complication. If there is a complication, it's in my opinion being caused by your card read drivers:

    6: kd> lmvm o2sdgx64

    start             end                 module name

    fffff8800f494000 fffff8800f49e780   o2sdgx64   (deferred)             

        Image path: \SystemRoot\system32\DRIVERS\o2sdgx64.sys

        Image name: o2sdgx64.sys

        Timestamp:        Tue Aug 18 05:00:36 2009

    Most card reader drivers are **** regardless of their date. Check for an update on Toshiba's site - http://support.toshiba.com/drivers

    If no update available, uninstall the drivers and give it a try without them. If no avail, not much you can do I am afraid.

    Regards,

    Patrick

    Was this answer helpful?

    0 comments