Windows 7: Sporadic Blinking Cursor on Resume from Hibernate - Latitude E6510

This error has finally gotten to me and I'm seeking some help. From the time I purchased my Dell Latitude E6510, I've had random failures to resume from hibernation. It happens about once every 5 tries, and it never happens back-to-back (meaning if I power down and reboot using the same hibernation file the resume will work fine). Once the system boots, it is always rock solid.

The blinking cursor freeze happens after the Starting Windows screen, right as the video mode changes. The timing is different each time, because in some instances the system will sit there and do nothing, in other instances the Intel BT/WIFI driver will load, and in other instances the hard drive will work for about 2-3 minutes (not solid, normal resume load) as if the computer was resuming fine but the video driver never changed modes. Note that in the last situation when I eventually reboot (I wait for the HD to stop spinning to try to avoid FS corruption, though it doesn't always work) the system doesn't think it resumed properly even though it goes through most of the motions.

Everything within my power has been updated. NVidia drivers to their latest, Intel chipset and WIFI/BT drivers to their latest, Windows Updates, BIOS, you name it. I've seen other posts in the forums about E6510s failing on resume, but they all involved UEFI which I do not use.



I've tried to run traces to catch the hanging driver, but the traces don't complete until the system boots successfully, and looking at the traces I can't find any indication of where the computer failed to resume then tried again and successfully resumed. There is nothing in the event log from the time of the failed boot either. I tried increasing my swap file from automatic to the recommended size (a +3-4gb difference) to no avail. I'm at a loss. Is there something the equivalent of the old XP "boot with logging enabled" that would dump to a file so I could see the point in the resume where the system hangs or what fails to fully initialize?

Any help or ideas would be greatly appreciated. Thanks.

(P.S. On a most likely unrelated note I also get sporadic BSODs on boot once in a while, but only on a full boot, never on a hibernate. The issue is hard to chase down though, because the driver that BSODs is always a different one. I've tried chasing those down to no avail as well by updating/downgrading drivers. I do have minidumps for them. But again, likely unrelated.)