Solved Random crashes and freezes after installing windows to SSD

[Bujungo]

I recently bought a new laptop (HP ProBook 450 G1) and replaced the hard drive with a 250gb Samsung 840 EVO. I have been having a ton of trouble getting to work properly. First, I couldn't get Windows to install, so eventually I made a backup with Paragon Backup and Restore and imaged the original drive to the new one. The system is really unstable. It will (seemingly) randomly freeze to the point where I can move the mouse but can't click on anything or I can't even move the mouse. It also randomly restarts. I have installed all (I think) of the latest drivers from HP's website. I still think the issue might be driver related, but I'm not sure. Logs attached.

 

[derekimo]

Hi There,

Avast is what is causing them,

Unable to load image aswMonFlt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswMonFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for aswMonFlt.sys
Probably caused by : aswMonFlt.sys ( aswMonFlt+2475 )

For the time being, uninstall your Anti-Virus,

AV Uninstallers

And Install Microsoft Security Essentials which we know doesn't cause BSOD's.

 

[Bujungo]

That helped a little bit, but I'm still experiencing some instability. I've attached another log dump.

Thanks for your help, by the way.

 

[derekimo]

You're welcome,

This one is also flagging Avast, did you try the uninstaller in safe mode?

Unable to load image aswSnx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSnx.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys
 aswSnx+0x71cb

Unable to load image aswMonFlt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswMonFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for aswMonFlt.sys
Probably caused by : aswMonFlt.sys ( aswMonFlt+2475 )

avast! Uninstall Utility | Download aswClear for avast! Removal

This is another problem driver,

Unable to load image iaStorA.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iaStorA.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
 iaStorA+0x3343

That is a troublesome driver quite often, let's try this,

Remove Intel Rapid Storage Technology applications.

1. Uninstall it from Control Panel > Programs and Features.
2. Uninstall the driver from device manager:
- Right click on "my computer" icon and click "manage" on the context menu.
- In the "Computer Management" window that opens:
- Select "Device Manager" in the left pane, It will list all the existing devices.
- Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
- Select one Intel device item under it, right click, then uninstall.
- Repeat the process for all Intel items under "IDE ATA/ATAPI controllers"
3. Now restart the computer.
4. Once booted, Windows will auto configure the appropriate native system driver.

Let us know how that works out.

 

[Bujungo]

I did that. It reinstalled one of the Intel drivers (but not rapid storage) and then locked up again. New logs attached.

 

[derekimo]

Well this one doesn't like your AMD display driver,

Unable to load image atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys

Instead of updating or trying different versions see what happens if you just uninstall the driver reboot and let windows install it's WHQL version offered on reboot.

 

[Bujungo]

It looks like the AMD driver reinstalled itself, and I'm still having issues.

 

[Bujungo]

I ended up reinstalling Windows. I've had a few crashes, but after some driver updates things are a bit more stable. If it happens again I'll post another log dump.

 

[Bujungo]

Here it is. It has been pretty consistently fltmgr.sys

 

[derekimo]

Well you have just about every main driver involved in this group of crashes, not a good sign on a clean install.

Both your graphics drivers, your network driver, AV, storage.

Let's start with the known troublesome drivers,

*** WARNING: Unable to verify timestamp for avgmfx64.sys
*** ERROR: Module load completed but symbols could not be loaded for avgmfx64.sys
 avgmfx64

That is your AV, please uninstall AVG,

http://www.avg.com/us-en/utilities

And Install Microsoft Security Essentials which we know doesn't cause BSOD's.

And the IRST drivers,

*** WARNING: Unable to verify timestamp for iaStorF.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorF.sys
 iaStorF+0x1ab6

Unable to load image \SystemRoot\system32\DRIVERS\iaStorA.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iaStorA.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
Probably caused by : iaStorA.sys ( iaStorA+7be42 )

Remove Intel Rapid Storage Technology applications.

1. Uninstall it from Control Panel > Programs and Features.
2. Uninstall the driver from device manager:
- Right click on "my computer" icon and click "manage" on the context menu.
- In the "Computer Management" window that opens:
- Select "Device Manager" in the left pane, It will list all the existing devices.
- Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
- Select one Intel device item under it, right click, then uninstall.
- Repeat the process for all Intel items under "IDE ATA/ATAPI controllers"
3. Now restart the computer.
4. Once booted, Windows will auto configure the appropriate native system driver.

 

[derekimo]

Going back over your first post, since so many drivers were being blamed in that last batch of dumps.

I recently bought a new laptop (HP ProBook 450 G1) and replaced the hard drive with a 250gb Samsung 840 EVO.

Can you put the hard drive back in and see if you still get all these problems, since it seems they all started after installing the SSD it would be nice to rule that out as a culprit.

 

[Bujungo]

That's probably the issue, but I was trying to avoid removing my SSD.

 

[derekimo]

That's probably the issue, but I was trying to avoid removing my SSD.

Yeah, I can understand that. It just seems too coincidental to not try to eliminate that as a cause.

 

[Bujungo]

Assuming that is the cause, where do I go from there? Try another SSD brand? Or another PC manufacturer (I'm still in the 2 week return window)?

 

[derekimo]

Well if that is the cause, it could just be a bad SSD. Let's cross that bridge when we get there.

 

[Bujungo]

Logs for HDD. It has BSOD'd on me twice.

 

[derekimo]

There aren't any dump files in that upload.

Interesting that both drives are crashing on you, was it crashing before you changed to the SSD?

How old is this new laptop?

 

[Bujungo]

I never really gave the HDD a chance. I bought this as an open box buy from the store about a week ago. The store said it had been returned in February or March.

 

[derekimo]

So this could have been happening before the SSD swap?

At this point you may want to see if you can return that laptop, this may end up being a big lemon.

 

[Slartybart]

So this could have been happening before the SSD swap?

At this point you may want to see if you can return that laptop, this may end up being a big lemon.

I was going to suggest checking that all HW was seated properly (not too much in a laptop - memory, HD, wireless card, Optical drive, CMOS battery).

But I think Derek's plan is wiser. The machine was already returned once and while it might have been a great deal price wise, I think you'll be better off in the long run by returning while you can.

I've purchased refurbs and open box items and I have no qualms returning them after trying my best.

Don't leave your SSD in the machine if you do return it