If you are encountering the issue we know about - you do not have to disable cookie scanning.
You only need to upgrade to the 5400 engine. Since this update is only available at the moment if you grab it manually, be sure to retrieve the ePO version of the update package - the SuperDAT will only work for 32-bit systems (it does not contain the necessary binaries to update 64-bit), ePO version will update 32-bit and 64-bit.
If you have already used the SuperDAT on a 64-bit system, then only the 32 bit engine gets updated. You'll still need to use the ePO version, to either let the Agent run the update or to extract the files yourself for manually updating the 64-bit engine.
If this does not resolve the issue of McShield crashing when scanning cookies, then you are experiencing a different problem which we are not aware of (or something described above was missed). Working with Support at that time to investigate the cause would be prudent.
If this is a known issue why was I never told by support to upgrade to engine 5400? I was told to re-install VSE 8.7i, install new sticks of RAM (this blew my mind), exclude PUPs, and disable On-Access protection. If tech support has a case with a Mcshield.exe crash on OAS, they should first check the engine version, correct? This must have just become a known issue because a month ago there was no answer to this problem from Gold Support.
>install new sticks of RAM (this blew my mind)
I know you're being serious but I do get a chuckle out of what support people recommend to customers, and I say that with reference to any organization with a support offering - I've had to be on the line to various support personnel too and have to shake my head sometimes at what I get asked to do. My advice: don't be afraid to challenge a course of action if it doesn't make sense; our hope is that a reasonable effort can be made in the course of troubleshooting to obtain information about the reported issue/behavior, and ideally to find a solution. I'm sure the technician's methods would've eventually lead to this being the issue - granted, it's nice when things can be recognized, and solved quickly.
I've only recently joined these forums (if that wasn't obvious to everyone), other colleagues have too, and our goal is to add value and to help encourage this online community to thrive. It looks like that's working so far...
Finding the right information can be a frustrating task - a sore point we're quite familiar with ourselves. This particular issue, for example, was documented in the online version of the Patch release notes when the Patch released. But it was either not read, or not understood, even by internal technicians - so we have to assume it always takes a bit of time for knowledge to disseminate when it's available. These forums should help with that in future, and reduce that frustration.