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-27T17:32:51+00:00

    Cybot, I've asked Patrick to take a look at the file. Hopefully he will, when he logs back on.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-10-25T23:15:47+00:00

    it is 188 Mb. here is the link:

    http://1drv.ms/1tapWZr

    I may have misstated the natue of the dump... it was a normal dump like the others. I said what I did, because I have seen my pc freeze up during the creation of the stop error dump. in this case no freeze occurred, so a"full" dump was created. this is not a full memory dump as this option is disabled for PC's with more that 2Gb of RAM in windows 7.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-10-25T03:50:25+00:00

    I turned on verifier and setup the pool and  special pool options. I then went about my business and waited for the inevitable stop error. this time the stop error was "SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION"

    the computer was able to record a full dump, would you like to look at it?

    what little analysis I can do seems to indicate win32k.sys, which does not seem like the cause.

    I was using the dos prompt when the stop occurred so I doubt win32k.sys is the cause, but I could be wrong

    one thing I have noticed with the dumps, is what ever the computer is doing when it stops, is being indicated as the reason for the error. this is obviously not the cause. is there any thing I can do that will generate a more detailed analysis?

    Yes, if it is not too large.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-10-25T02:21:38+00:00

    I turned on verifier and setup the pool and  special pool options. I then went about my business and waited for the inevitable stop error. this time the stop error was "SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION"

     the computer was able to record a full dump, would you like to look at it?

    what little analysis I can do seems to indicate win32k.sys, which does not seem like the cause.

    I was using the dos prompt when the stop occurred so I doubt win32k.sys is the cause, but I could be wrong

    one thing I have noticed with the dumps, is what ever the computer is doing when it stops, is being indicated as the reason for the error. this is obviously not the cause. is there any thing I can do that will generate a more detailed analysis?

    Was this answer helpful?

    0 comments
  5. Anonymous
    2014-10-24T04:59:28+00:00

    although I am seeing the error message talked about for the hotfix, the hotfix says it is not applicable am assuming this is because the hotfix is not for win7 SP1. I did use the memory dump diagnostic  link at the top of the hotfix page though, so maybe, just maybe, something will come of that

    Was this answer helpful?

    0 comments