0x00000019 0x0000000000000021 when using readyboost

Anonymous

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

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

Anonymous

2014-09-07T05:09:36+00:00

malwarebytes free and malwarebytes premium, is the same software, the only difference is the adding of a license key to enable various premium features. version 2.0.2 fixes the bsod issues here. I will turn off the the realtime function for now, making it the same as the free version.

eset update function say 7.0.317.4 is up to date. and the virus definitions are the latest available.

earlier I reenabled readyboost for the SD card, and about 30 mins. later the system had another 0x19 BSOD.

as long as I don't use the card for readyboost the system is as stable as can be. but enabling the card for readyboost, seems to destabilize the system.

as for norton when ever I uninstall it after a factory reset, I am persistant at removing all traces of that software. I probably do a better job than the Norton renmoval tool does
Was this answer helpful?

0 comments No comments
Anonymous

2014-09-08T00:58:41+00:00

Have you had a BSOD since disabling Malwarebytes real time protection?
Was this answer helpful?

0 comments No comments
Anonymous

2014-09-08T04:12:00+00:00

let me re enable readyboost on the sd card and ill get back to you on that
Was this answer helpful?

0 comments No comments
Anonymous

2014-09-08T22:33:43+00:00

OK looking back at what I have already posted, I have come up with the following:

the problem was originally two fold. one half of my problems stemmed from the fact that for what ever reason, the SD card did not like the NTFS formatting. I have since switched the card over to ExFat and the problems related to that have disappeared.

the other half has been the Bad_Pool_Header BSOD error that keeps occurring.

after not running into the bsod with readyboost enabled for 4+ hours, decided to turn on verifier with the pool tracking and special pool option selected. although my PC was slowed down to a snails pace. it did another BSOD. I use WhoCrashed Home, to analyze the dumps, but instead of the usual (sic) you crashed but we cant determine the driver that cauesd it message, it gave this output:

System Information (local)

computer name: CHRISSOLOMON-PC

windows version: Windows 7 Service Pack 1, 6.1, build: 7601

windows dir: C:\windows

Hardware: Satellite P500, TOSHIBA

CPU: GenuineIntel Intel(R) Core(TM) i7 CPU Q 720 @ 1.60GHz Intel586, level: 6

8 logical processors, active mask: 255

RAM: 8452026368 total

*** * Crash Dump Analysis*

Crash dump directory: C:\windows\Minidump

Crash dumps are enabled on your computer.

On Mon 9/8/2014 10:07:54 PM GMT your computer crashed

crash dump file: C:\windows\Minidump\090814-27456-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x74540)

Bugcheck code: 0xC1 (0xFFFFF980DC756EA0, 0xB68, 0x160, 0x21)

Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION

file path: C:\windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that the driver wrote to an invalid section of the special pool.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Mon 9/8/2014 10:07:54 PM GMT your computer crashed

crash dump file: C:\windows\memory.dmp

This was probably caused by the following module: mbamchameleon.sys (mbamchameleon+0x65EB)

Bugcheck code: 0xC1 (0xFFFFF980DC756EA0, 0xB68, 0x160, 0x21)

Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION

file path: C:\windows\system32\drivers\mbamchameleon.sys

product: Malwarebytes Chameleon

company: Malwarebytes Corporation

description: Malwarebytes Chameleon Protection Driver

Bug check description: This indicates that the driver wrote to an invalid section of the special pool.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mbamchameleon.sys (Malwarebytes Chameleon Protection Driver, Malwarebytes Corporation).

Google query: Malwarebytes Corporation SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION

so for now, I am keeping MBAM's realtime functions disabled. I will also open up a case over on the malwarebytes site
Was this answer helpful?

0 comments No comments
Anonymous

2014-09-08T22:51:12+00:00

OK, thanks for the follow-up.
Was this answer helpful?

0 comments No comments