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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2014-09-23T01:13:20+00:00

    had two more 0x19's in one of the dumps, mbamchameleon.sys was clearly indicated, which was odd as the program was not loaded, and it's services were disabled. so, for the time being I have uninstalled MBAM. the other 0x19 said a component of diskkeeper was responsible. I can find no other posts relating the file that whocrashed found and 0x19. I think that only reason it was listed as the cause, is that was in the middle of something when the 0x19 occurred, this happened after I uninstalled mbam. if I get another 0x19 and it lists  diskkeeper component again, I will try uninstalling diskkeeper too. I am considering going into msconfig and disabling everything but the things that were on the computer when  it came to me fresh from the factory (M$ related stuff and Toshiba installed stuff). if it still bsod's then, I don't know what i'll do. I am still convinced that the crashes are related to readyboost.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-09-21T17:14:30+00:00

    I don't know if you have the ability to or not, but my other thread that PA BEAR mentioned in an earlier post seems to have gone dead. if at all possible, maybe you could notify him that that I'm still having issues over there? I have kinda hit a brick wall over there and really need someone with more knowledge than I have.        

    "the other post"  https://answers.microsoft.com/en-us/windows/forum/windows_7-windows_update/cbs-mum-package-naming-issue-causing-false/9cd9b2e0-0377-46dc-9d2b-5b9d7fedac4a

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-09-21T14:19:20+00:00

    yes I  can. let me generate a link for you. let me warn you though, even though the zip file did reduce the file size down from 800Mb, the compressed file is still almost 200 mb in size

    Link:

    http://1drv.ms/XG7Y3S

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-09-20T13:18:22+00:00

    Can you provide the most recent minidump and memory.dmp files ?

    Was this answer helpful?

    0 comments
  5. Anonymous
    2014-09-20T01:24:16+00:00

    I sent in a request for support to malwarebytes,  but have yet to hear from them. in the mean time MBAM has ben set not to load with windows.

    I am still getting 0x19 BAD_POOL_HEADER bsod's, just not as often as before. RDYBOOST.SYS is  the module hat is causing the crashes according to WhoCrashed.

    I am using the home version of WhoCrashed, so I can not view the dump details.

    Was this answer helpful?

    0 comments