BSOD when going out of sleep

[Daniol71]

If I put my computer to sleep (to make the BSOD appear) while running DV, will the faulty driver be flagged or does it only work when you're logged in to the computer?

 

[Arc]

Hi Daniol71.

Make it sure that the SSD is running with the latest firmware.
Download V300_525fw_Win, for sv300s3 | Kingston Technology

It is important to know that whether the BSOD is appearing even with the latest SSD firmware applied or not.

 

[Daniol71]

Hi Arc,

Thanks for the suggestion, the SSD was indeed in need of a firmware update. Sadly that didn't fix the BSOD problem :/

 

[Arc]

Hi Arc,

Thanks for the suggestion, the SSD was indeed in need of a firmware update. Sadly that didn't fix the BSOD problem :/

OK, do another thing.

Follow http://www.sevenforums.com/tutorials/778-power-plan-settings-change.html. When you are in Step 5, apply this settings:

View attachment 320184

Also, post a screenshot of the SSD using CrystalDiskInfo - Software - Crystal Dew World

 

[Daniol71]

Alright, done that, it would be annoying if the SSD is faulty since it's brand new

 

[Arc]

The smart data looks good.

Does teh BSOD still happens at wake-up, after changing the power management setting for the SSD?

The SSD is brand new ... that is a good info. Was the situation the same before applying the SSD?

 

[Daniol71]

I set the hard disk to never turn off like you said but the BSOD still happens like it used to.

Here's the thing though, before I had Win8 installed on an exact same model SSD and never had any of these issues. So my guess is either it's Win7 drivers that aren't installed or not working properly. But since my system for some reason can't make dump files, there's no way to find out.

When I first bought the laptop it had Win7 installed on a HDD. I didn't have this problem, but that's because it came straight from the factory. My guess is a fresh install would have caused the same thing back then

 

[Arc]

A dump file is not needed to debug a stop 0xF4. A dump file will not give any more information other than the bugcheck code plus "probably caused by either wininit or csrss".

A stop 0xF4 is storage failure.

The only thing is uneven here that the storage failure occurs only when you are waking the computer up. That means, the disc goes to sleep, but fails to get the power back within the stipulated time. It is even interesting that the BSOD occurs even after you changed the power management policy.

I set the hard disk to never turn off like you said but the BSOD still happens like it used to.

An exact same model worked good, that is not any guarantee that this one will also work good.

Here's the thing though, before I had Win8 installed on an exact same model SSD and never had any of these issues.

Can you test the SSD in another computer? Or can you test another disk in this computer?

One more thing ..... as you installed the SSD yourself, make it sure that there is no loose connection. Open it and then re-seat it.

A stop 0xF4 is a storage related issue. Windows installation and drivers has nothing to do with it.

 

[Thedoctor44]

Try these

1. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

3. Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

 

[Daniol71]

A dump file is not needed to debug a stop 0xF4. A dump file will not give any more information other than the bugcheck code plus "probably caused by either wininit or csrss".

A stop 0xF4 is storage failure.

The only thing is uneven here that the storage failure occurs only when you are waking the computer up. That means, the disc goes to sleep, but fails to get the power back within the stipulated time. It is even interesting that the BSOD occurs even after you changed the power management policy.

I set the hard disk to never turn off like you said but the BSOD still happens like it used to.

An exact same model worked good, that is not any guarantee that this one will also work good.

Here's the thing though, before I had Win8 installed on an exact same model SSD and never had any of these issues.

Can you test the SSD in another computer? Or can you test another disk in this computer?

One more thing ..... as you installed the SSD yourself, make it sure that there is no loose connection. Open it and then re-seat it.

A stop 0xF4 is a storage related issue. Windows installation and drivers has nothing to do with it.

I'll check if the SSD is connected correctly and I'll also try with the original HDD that came with the laptop.

NOTE: The BSOD happens when I try to log in after sleep. Most of the time the login screen will show up, and when I click to login it will load for a couple of minutes and then the BSOD appears. Also, hibernation works fine so it sounds weird that it's hard disk related.

 

[Daniol71]

Try these

1. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

3. Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

Alright, settings 1 and 2 were already set the way you suggested, but Windows Error Reporting wasn't, so I fixed that.

Now I just made the BSOD appear and got a STOP: c000021a [Fatal System Error]

Hopefully there will be a dump when I restart the laptop, if yes I'll post it asap.

 

[Daniol71]

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"

 

[Arc]

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]

Alright, sorry for the late reply. Arc was right, the problem came from the SSD. Everything is working fine with the original HDD. 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.

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.

 

[Arc]

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.

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.

 

[Daniol71]

Thanks, I got a very generic answer from Kingston support but hopefully I can get it replaced.

"Dear Lecoq

Thank you for your reply.

We are not aware of such issues, although sleep mode is not really necessary as the SSD has quick bootup and shut down times.

If you haven't applied any changes after Windows 7 installation and you running the SSD in AHCI Modes, then it should work without any issues.

Have you already updated the Firmware of the SSD, which can be found on the following Link:
Download V300_525fw_Win, for sv300s3 | Kingston Technology

I would also recommend to ensure your win 7 system has latest BIOS, Chipset Drivers, AHCI Driver and windows updates installed.

Should you continue to have any issues, please do not hesitate to contact us again,

Warm Regards
Bala"

 

[Daniol71]

I got a BSOD (probably caused by driver verifier) while using the laptop. It seems to have been caused by ATK0100 ACPI UTILITY driver which is an ASUS driver that seems to auto-install with the pc, I never installed it myself.

Anyway, for the first time my pc made a memory dump, so I'll attach it, it's only a minidump though.

 

[Arc]

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

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
[COLOR=Red]Probably caused by : ATK64AMD.sys[/COLOR] ( ATK64AMD+18ac )

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

Which is very old.

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 http://www.sevenforums.com/tutorials/219576-clean-up-factory-bloatware.html, 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.

 

[Daniol71]

That's the weird part right, this is a clean version of Windows 7 Home Premium (not from Asus or anything), I'm just using the license that's on the sticker of my laptop. It seems like it automatically uses that driver, and on top of that it uses the 2006 version although the latest one available for my laptop is from 2009 (the 2009 version doesn't solve the original problem of this thread however). Is there any way to replace it by a generic Microsoft driver? Or does it have to be the Asus one?

 

[Arc]

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.