BSOD when going out of sleep

Alright, the problem seems to have evolved. Not sure if it's because I've been running driver verifier for 24h+ or because I started the Windows Error Reporting service. As I stated above, I got the BSOD STOP: c000021a [Fatal System Error] when returning from sleep. Now, when returning from sleep I get nothing at all, the screen is turned off. This error seems to be much more common, so hopefully we can find a solution.

Edit: I also refitted the SSD like Arc proposed, and made sure that it was properly connected, didn't solve the problem.

Second Edit: After installing Intel Matrix Storage Manager from the Asus driver page (originally installed with the laptop) I got a new BSOD STOP:0x00000019 and the mention that "crash dump failed"

Daniol71 said:

Edit: I also refitted the SSD like Arc proposed, and made sure that it was properly connected, didn't solve the problem.

Second Edit: After installing Intel Matrix Storage Manager from the Asus driver page (originally installed with the laptop) I got a new BSOD STOP:0x00000019 and the mention that "crash dump failed"

A stop 0x19 is a Bad pool header, usually caused by a device driver. As it appeared after installing a new device driver, that may be blamed for it.

A winlogon fatal error may occur due to various reasons.

But now it is the time to use another disc in the computer on a test basis.

Daniol71 said:

Is this due to a fault on my SSD or does Win7 need to be configured in a special way to run on a SSD? I'd really prefer using the SSD and any help would be appreciated.

Windows does not need a special way to run a SSD, the AHCI mode activated is enough for it to run smoothly. In this case it appears to be a faulty disk only. And there are plenty of it, the post flood period products .... as the experts say.

Daniol71 said:

Note: I bought the SSD from Amazon UK (like I did with the previous one) but I won't be in the UK until August, so I can't send it back. If you know any way for me to fix the problem myself it would be great.

I'll drop an email to Kingston support too, to check if there are any known errors with Windows 7.

I will see if anyone of us have an idea about it.

Driver Verifier catches weak and old drivers on purpose.
This time it caught ATK Hotkey ATK0101 ACPI UTILITY Driver.

Code:

BugCheck C9, {22f, fffff8800415c8ac, fffff9800ceeae10, 0}

*** WARNING: Unable to verify timestamp for ATK64AMD.sys
*** ERROR: Module load completed but symbols could not be loaded for ATK64AMD.sys
Probably caused by : ATK64AMD.sys ( ATK64AMD+18ac )

Followup: MachineOwner
---------

Which is very old.

Code:

fffff880`0415b000 fffff880`04163000   ATK64AMD T (no symbols)           
    Loaded symbol image file: ATK64AMD.sys
    Image path: ATK64AMD.sys
    Image name: ATK64AMD.sys
    Timestamp:        Fri Oct 27 18:15:25 2006 (4541FF65)
    CheckSum:         0000F651
    ImageSize:        00008000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

If you want to get rid of it, I'd recommend you to Clean Up Factory Bloatware, with a special reference to Point #13

13. Consider a Clean Reinstall - Factory OEM Windows 7 which is often better than getting a new computer considering how pre-installed bloatware can corrupt Windows 7 even if it's completely cleaned up.

Microsoft does not have any replacement for this driver. It is just a bloatware by ASUS. And as it is failing, it should be removed.