Updated hardware; now Windows 7 crashes when waking from sleep

I've been searching around online for the past few hours trying to find a solution from this, to no avail.

Problem:
I recently upgraded my old computer's motherboard/cpu to an Asus Z87-PRO and i7-4770K respectively.
At first I didn't bother doing a fresh install; I just uninstalled the old Mobo drivers and installed the new ones, which I thought worked at first. That is, until my computer first went to sleep.

Every time it wakes up, whether put to sleep on a timer or manually, it lets me log in with my password and then freezes at the welcome screen.

But here's where it gets weird.
Sometimes, but not all the time, I will get an error stating:

The instruction referenced at 0xXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX referenced memory at 0xYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY. The required data was not placed into memory because an I/O error status of 0x0000000e.

Click on OK to terminate the program.

The weirder thing is that when it shows, it isn't always the same process that is named (which is why I didn't include it).

Regardless of whether this happens, it always shuts down after a little bit of waiting, but never reaches the desktop. This issue has *only* happened when waking up from sleep mode, and otherwise the entire system has worked fine (Side note: It also died when it woke up to do automatic updates in the middle of the night).

It does not, however, yield a BSOD, meaning I don't have a memory dump to go from.

My attempted solutions:

At first I attempted reinstalling Windows 7, because I figured it's possible that one of the old drivers could have caused an interference of some kind.
This, however, had no beneficial effect. All it did was require a few hours of updates -.-

After this, I attempted finding all the updated firmware for the Motherboard's chipset/sata drivers, just in case that was the issue. Still nothing.

Then I found an article with a similar problem on Tom's Hardware, and so i tried setting the disk to never turn off (I also followed a series of SSD optimizations from an article there as well). Still no luck.

Finally, in desperation, I updated my BIOS firmware. Of course, no luck.

I really have no idea what this could be. I have used this same SSD for Windows for the past 2 years, and I've been through 2 other motherboards with no problem.
For those wondering, this is my current setup:

Setup:
CPU: Intel i7-4770K
Mobo: Asus Z87-PRO
Graphics: 2GB VRAM GDDR5 XFX AMD Radion 6870X
Memory: 4x8GB Corsair Vengeance
OS Drive: 60GB Corsair Force 3 SSD
OS: Windows 7 Professional

Does anyone here have any suggestions for trouble shooting to hopefully make this work? I don't know what else to do!

Hello Bitwize. Welcome to the forum.

You say you upgraded the motherboard and CPU. Did you upgrade the RAM as well, or are you re-using the old RAM?

If so, do you know if that old RAM is compatible with the motherboard and CPU?

You say you upgraded the motherboard and CPU. Did you upgrade the RAM as well, or are you re-using the old RAM?

If so, do you know if that old RAM is compatible with the motherboard and CPU?

The ram is still DRR3 running at 1600MHz, and is listed as compatible in the Motherboard's manual, so it should be.

its definutly a ram issue. data cant be written to or read from the ram causing windows to hang.

check out crucials website to see if your ram is compatible like stated above.

the other option is to take out one stick at a time and see if its a dodgy stick causing the issue, you do have 32gb so loosing a stick or 2 wont really effect much unless youre a hardcore video/picture editor ^_^

I actually tried the one-stick-at-a-time thing and found that it didn't solve anything (sadly).
Also, as stated above, the motherboard manual says that the Corsair model I have should be compatible. I hope that's not the issue because that would be a pain-in-the-ass.

To be sure you could run Memtest on it. Run it overnight at least 3 passes.
Memtest86+ - Advanced Memory Diagnostic Tool

Once you have completed the test and can rule out RAM then we can look at other potential hardware problems.