Here's a copy of my message to the mailing list:

I also included an attachment of my kernel log. Unfortunately, I was given no response. Does anyone have any suggestion on what I should do moving forward? The thought of having to use an older kerenl on my workstation for the next few years is terrible. And having to make another workstation just to use Linux is equally unacceptable.

The LKML is a development list, not a support list. You should take it to a user support forum for your distribution. The kernel developers don't have the time to support the tens of millions of Linux users.

The bug you pointed to is reporting a memory failure. That is, your hardware is reporting to the Linux kernel that memory has failed. The only part that the Linux kernel has in that is properly responding to the failure (displaying the error and reboot or shutting down). If you are overclocking, stop it. If not, replace the RAM in the bank reporting failure.

I feel you read through my post too quickly, and misunderstood, or I wasn't clear enough. I was not asking for support. I was attempted to report what I believe is a bug. The other gentleman and I have almost identical errors. Furthermore, we also have almost identical hardware, and both only get the panics on versions of the kernel after 2.6.35, and we both report having normal behaviour in older kernels and in other OSes(in forum post I originally found with his info in it).I have no hardware issues, believe me I checked, so the next logical step is to assume that it's the kernel. I assumed that it was the distro's problem at first and tried another on a live cd, yet it kept happening.
In fact, since flash drives are plentiful and making bootable ones is easy, I used Mageia, Mint, and ArchBang to test the different kernels. I would much rather it be a hardware issue, as that's easily fixed, but it does not seem to be the case.

Some change between 2.6.35 and 2.6.36 and onward IS causing the panic. Or is it merely coincidence that two users with almost the exact same hardware are having the exact same problem and only after 2.6.36 and 2.6.37 in his case, though it's impossible to know which kernel he updated from, but I would bet my life on it being 2.6.35 or prior. I have no bad ram, and I'm not overclocking, so please try to be open minded instead of condescending. My system is perfectly stable in Windows, the minefield that can be OS X on non-apple purchased hardware, and with older kernels. If this were a hardware issue, or a distro specific issue, it would have already manifested itself in more ways than one. So like I said originally, if anyone has any helpful suggestions I would love to hear them.

This is not a bug reporting system, this is a volunteer support site. If you'd like to report a bug against the kernel, use the kernel bugzilla. Kernel.org is still being restored, so it may be a while until bugzilla is available again.

Keep in mind that identical hardware can have identical bugs; the problem may be in the platform (motherboard, BIOS). If the problem were that the kernel is falsely reporting fatal machine checks for bad RAM, many more people would be impacted. Older kernels interact with the hardware differently, and so the problem may only present with newer kernels.