[SOLVED] Sporadic boot delays after system migration to another SSD

[Toppa]

Hello,

I'm stumped on this issue and I hope that someone could help me out.

My system:
Windows 7 64bit SP1
AMD Phenom II X4 955
Gigabyte GA-870A-UD3 (Award BIOS F5)
2x4GB Team Group PC3-10700 DDR3 RAM CL9-9-9-24
NVIDIA GeForce GTX 460 1GB (350.12)

Previous SSD: G.Skill Phoenix Pro 120GB
New SSD: Transcend 512GB

One fact that could lead to the solution is the following:
- The problem occured first after I transferred my whole system from my old to my new SSD. Before the migration the problem never occured.

I migrated the complete SSD via Acronis True Image to the bigger one.
Everything works fine, but since the migration I face sporadic delays in the post boot phase.
The delays occur right after I log in to Windows with my password.
When I hover the mouse over the taskbar, I see the Windows 7 hourglass (loop) for about 2 minutes.
In this time I cannot load or start anything. The loop is cycling, the mouse is moveable. But the rest seems freezed.
After that time the remaining systray applications start up and the system works completely fine.
Sometimes I can boot Windows without that problem. But the most time the problem persists.

I traced the boot process via the performance tools (etl-file) many times and saw the following everytime:
At the graph "Disk Usage - Utilization by Process, IO Type" the process "chrome.exe" is displayed as the originator.
I reinstalled Chrome completely and disabled all extensions. No improvements.
But perhaps chrome isn't the cause of the problem.

Furthermore I rebuild the MBR and Boot Sector (bootrec /fixmbr, /fixboot and /rebuildbcd).
First I thought the problem was solved. But a minute ago it happened again. :huh:

Can some help me? What should I provide you with?
Systemeventlogs? etl-files? With which options should I generate them?

Regards,
Toppa

 

[Toppa]

Here is a screenshot I made while investigating the issue:

(Click)



/Edit:
Forget what I said in the first posting. It's not chrome.exe everytime!
I made some more traces and it's a random process utilizing the disk at that boot stage.
Here another screenshot:

(click)

 

[Digerati]

I don't have a clue what is happening so just thinking out loud.

Does it boot into Safe Mode okay?

What if you temporarily put back in the old SSD? Any problems? If it works perfectly with the old SSD back in, then you know the rest of your hardware is working fine and the problem is something with the migration, the new SSD or some change that happened after the migration.

 

[Tekno Venus]

Can you upload the ETL file(s) you collected?

What flags/options did you have set?

Thanks.

 

[Toppa]

Thank you for your answers.

My old SSD was plugged and formatted in my notebook. I can't test in that direction.

I tried several things:
- Boot in safe mode with network -> 4 smooth boots, 2 faulty boots
- Boot in safe mode without network -> 5 smooth boots so far!
- Boot normally -> 1 faulty boot immediately, disabled network adapter, next boot was faulty too

I looked in my system event log and noticed the following:
- When the boot is flawed, the system event log showed two warnings everytime -> amd_sata event id 129 "Reset to device, \Device\RaidPort0, was issued."
- When the boot is fine, none of these event ids show up



The etl-tracefile is sized about 1,6gb. Should I upload this one?
I can only provide you with a screenshot in german, but I think you figure out what it means.
Or should I create a new file with your preferred settings? I can reproduce the problem at all times.


(boot, verbose, file)


Is it possible, that the new drive can't work correctly with the ADM Sata driver?
But why only sometimes when booting. The rest of the system works fine.

 

[Tekno Venus]

Is the BIOS set to AHCI? If not, don't change it yet - just let me know. It will either be AHCI or IDE

The event viewer is a good idea:

- open Event Viewer (eventvwr.msc)
- expand the Custom Views category (left click on the > next to the words "Custom Views")
- right click on Administrative Events
- select "Save all Events in Custom View as..."
- save the file as Admin.evtx
- zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
- upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).

Regarding the ETL, that is a bit large. I'll have a think about what flags I want and let you know. Just send the event viewer logs for now.

Stephen

 

[Tekno Venus]

Hi,

For the ETL, check the following:

• First level triage (if you have that option)
• CPU
• Disk I/O

This should be enough and will reduce the file size.

Stephen

 

[Toppa]

Everything in BIOS is set to AHCI. I've checked it just now.
Before and after the problem occured the first time, right after the migration, I changed no settings anywhere.
The old SSD didn't had that problem with the same settings.

Attached the event viewer files.
ETL will follow.

 

[Toppa]

Here it is:

https://www.dropbox.com/s/iemadtwmx5bozuo/TOPPA-PC.05-15-2015.19-30-23.Boot_1.etl?dl=0

 

[Toppa]

I looked into the file by myself and tried the following:
- Disabled the evernotewebclipper.exe from autostart and evernote web clipper extension in chrome. Didn't solve the problem.

 

[Tekno Venus]

Thanks.

Whilst you're waiting for me to look at it, there are a few things I want to check.

Go to device manager, check for any warning symbols. Also make sure that the storage/chipset drivers are installed and up to date.

Try following the steps here: Event ID 129 – storachi - Reset to device, \Device\RaidPort0, was issued. - Kevin Holman's System Center Blog - Site Home - TechNet Blogs

Can you also run the BSOD Collection app for me. I know you're not having any BSODs, but it collects a lot of useful information. BSOD Posting Instructions

Stephen

 

[Toppa]

1.)
I'm trying to keep all drivers up to date.
Therefore I had installed the latest chipset drivers from the AMD homepage (Ver. 14.12) as soon as they were released.
But the included storage driver didn't work with my old SSD -> "AMD SATA Controller Version 1.2.1.376 [23.09.2014]".
With this storage driver installed, the problem described in this thread happened every 10-20 seconds.
An interval like this: 20 seconds ok - 2 min freeze - 20 seconds ok - 2 minutes freeze... and so on.

Because of this I reverted the storage driver back to version "AMD SATA Controller Version 1.2.1.349 [27.06.2013]"
With this driver everything was fine on my old SSD. Even the boot was smooth at all times.

Today I retried the recent "amd-catalyst-omega-14.12-sb-sata-ahci-win8.1-win7" chipset drivers, which again include the storage driver "AMD SATA Controller Version 1.2.1.376 [23.09.2014], but the problem as stated above stays the same.
20s - 2m - 20s -2m ...
I downloaded some older amd sata drivers just now and tried them too (1.2.0.164 [07.01.2009]) -> 20-2-20-2...
The same happens when i revert to the "Standard AHCI1.0 serial-ATA-controller".

The only driver which functions (besides the sporadic boot delay) on the new SSD is version 1.2.1.349 - the same I used on my old SSD. As mentioned above, I didn't changed anything before and after the migration, because my system ran fine with the old SSD.

Device manager: No warning signals
Current storage driver: AMD SATA Controller Version 1.2.1.349 [27.06.2013]

2.)
I'm running the balanced power management options since ever.
As mentioned in your link, I'm too running the "PCI Express - Link State Power Management" setting at "Medium Energy Saving" (don't know the english expression).
I changed the settings as proposed in your link to "Off". No improvements.

3.)
I ran the BSODCollectionApp. It ran through everything but it failed to create a zip file by itself.
I zipped the content of the "SysnativeFileCollectionApp". Hope this is correct.

-> Attached the SysnativeFileCollectionApp.zip and perfmon.zip

 

[Toppa]

The problem occures more often when I make a cold start.
The longer the system is shut down, the more likely it happens.

When I warm-restart the system, the more likely the problem doesn't happen.

 

[Toppa]

But it could be my subjective opinion.
Just now I booted for the first time of the new day and it worked like charm.

 

[Tekno Venus]

Well that's interesting!

I've been digging through that ETL log and it's really not much help. It seems this is related to the SSD itself, the motherboard, BIOS settings or the way Acronis migrated the SSD.

I note you've moved from a large SSD to a small one - how did you go about doing this in Acronics? Did you re-size the partition and move the MFT?

The reason I ask is that the MFT seems to show up a lot in the logs. Note how chrome.exe's disk service time in the stack is only 19.573.

Have you checked trim is enabled? Run this command and tell me the output: fsutil behavior query DisableDeleteNotify

 

[Toppa]

Hi,

I moved from a small 120GB to a large 512GB SSD! Don't remember exact settings from Acronis, but it was quite easy and nothing special to configure.

"fsutil behavior query DisableDeleteNotify" -> "DisableDeleteNotify = 0"

TRIM is activated

 

[Tekno Venus]

Sorry, I read your initial post wrong

Let's see what Chkdsk has to say

chkdsk /f

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
Warning: In very rare scenarios, chkdsk can cause data loss. Make sure you have a backup of your data before continuing.

1. Click on the Start
   
   button and in the search box, type Command Prompt
2. When you see Command Prompt on the list, right-click on it and select Run as administrator
3. When command prompt opens, copy and paste the following commands into it, press enter after each
   
   chkdsk /f
   
   
4. Reboot
5. Download ListChkdskResult.exe (by SleepyDude) from the link below:
   
   https://dl.dropboxusercontent.com/u/12354842/My Tools/ListChkdskResult.exe
6. Double click on it to run it. It will take a few seconds to scan, then it will open a Notepad window with the log. Copy and paste the contents of this into your next post please!

 

[Toppa]

ListChkdskResult by SleepyDude v0.1.7 Beta | 21-09-2013


------< Log generate on 16.05.2015 14:31:06 >------
Category: 0
Computer Name: Toppa-PC
Event Code: 1001
Record Number: 2394828
Source Name: Microsoft-Windows-Wininit
Time Written: 05-14-2015 @ 14:16:28
Event Type: Informationen
User:
Message:


Dateisystem auf C: wird überprüft.
Der Typ des Dateisystems ist NTFS.
Die Volumebezeichnung lautet Windows.




Eine Datenträgerüberprüfung ist geplant.
Die Datenträgerüberprüfung wird jetzt ausgeführt.


CHKDSK überprüft Dateien (Phase 1 von 3)...
372224 Datensätze verarbeitet.


Dateiüberprüfung beendet.
1958 große Datensätze verarbeitet.


0 ungültige Datensätze verarbeitet.


2 E/A-Datensätze verarbeitet.


88 Analysedatensätze verarbeitet.


CHKDSK überprüft Indizes (Phase 2 von 3)...
454876 Indexeinträge verarbeitet.


Indexüberprüfung beendet.
0 nicht indizierte Dateien überprüft.


0 nicht indizierte Dateien wiederhergestellt.


CHKDSK überprüft Sicherheitsbeschreibungen (Phase 3 von 3)...
372224 SDs/SIDs verarbeitet.


562 nicht verwendete Indexeinträge aus Index $SII der Datei 0x9 werden aufgeräumt.
562 nicht verwendete Indexeinträge aus Index $SDH der Datei 0x9 werden aufgeräumt.
562 nicht verwendete Sicherheitsbeschreibungen werden aufgeräumt.
CHKDSK komprimiert den Datenstrom für die Sicherheitsbeschreibung
41327 Datendateien verarbeitet.


CHKDSK überprüft USN-Journal...
35385528 USN-Bytes verarbeitet.


Die Überprüfung von USN-Journal ist abgeschlossen.
CHKDSK hat freien Speicher gefunden, der in der MFT-Bitmap (Master
File Table) als zugeordnet gekennzeichnet ist.
Fehler in Volumebitmap werden berichtigt.
Windows hat Probleme im Dateisystem behoben.


500003836 KB Speicherplatz auf dem Datenträger insgesamt
218760664 KB in 306821 Dateien
163276 KB in 41330 Indizes
0 KB in fehlerhaften Sektoren
490088 KB vom System benutzt
65536 KB von der Protokolldatei belegt
280589808 KB auf dem Datenträger verfügbar


4096 Bytes in jeder Zuordnungseinheit
125000959 Zuordnungseinheiten auf dem Datenträger insgesamt
70147452 Zuordnungseinheiten auf dem Datenträger verfügbar


Interne Informationen:
00 ae 05 00 ff 4f 05 00 5a a1 09 00 00 00 00 00 .....O..Z.......
be 4e 00 00 58 00 00 00 00 00 00 00 00 00 00 00 .N..X...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................


Die Überprüfung des Datenträgers wurde abgeschlossen.
Bitte warten Sie bis der Computer neu gestartet wurde.


-----------------------------------------------------------------------
Category: 0
Computer Name: Toppa-PC
Event Code: 26214
Record Number: 2393141
Source Name: Chkdsk
Time Written: 05-12-2015 @ 16:10:13
Event Type: Informationen
User:
Message: Chkdsk wurde im Lesen-/Schreibenmodus ausgeführt.


Dateisystem auf D: wird überprüft.
Bereitstellung des Volumes aufgehoben. Alle offenen Bezüge auf dieses
Volume sind ungültig.
Die Volumebezeichnung lautet Daten.


CHKDSK überprüft Dateien (Phase 1 von 5)...
185344 Datensätze verarbeitet.


Dateiüberprüfung beendet.
1 große Datensätze verarbeitet.


0 ungültige Datensätze verarbeitet.


0 E/A-Datensätze verarbeitet.


0 Analysedatensätze verarbeitet.


CHKDSK überprüft Indizes (Phase 2 von 5)...
185390 Indexeinträge verarbeitet.


Indexüberprüfung beendet.




CHKDSK überprüft Sicherheitsbeschreibungen (Phase 3 von 5)...
185344 SDs/SIDs verarbeitet.


232 nicht verwendete Indexeinträge aus Index $SII der Datei 0x9 werden aufgeräumt.
232 nicht verwendete Indexeinträge aus Index $SDH der Datei 0x9 werden aufgeräumt.
232 nicht verwendete Sicherheitsbeschreibungen werden aufgeräumt.
Überprüfung der Sicherheitsbeschreibungen beendet.
24 Datendateien verarbeitet.


CHKDSK überprüft USN-Journal...
35247008 USN-Bytes verarbeitet.


Die Überprüfung von USN-Journal ist abgeschlossen.
CHKDSK überprüft Dateidaten (Phase 4 von 5)...
185328 Dateien wurden verarbeitet.


Dateidatenüberprüfung beendet.
CHKDSK überprüft freien Speicherplatz (Phase 5 von 5)...
56565318 freie Cluster verarbeitet.


Verifizierung freien Speicherplatzes ist beendet.
CHKDSK hat freien Speicher gefunden, der in der Volumebitmap als
zugeordnet gekennzeichnet ist.
Windows hat Probleme im Dateisystem behoben.


244196351 KB Speicherplatz auf dem Datenträger insgesamt
17639836 KB in 39 Dateien
1608 KB in 25 Indizes
293631 KB vom System benutzt
65536 KB von der Protokolldatei belegt
226261276 KB auf dem Datenträger verfügbar


4096 Bytes in jeder Zuordnungseinheit
61049087 Zuordnungseinheiten auf dem Datenträger insgesamt
56565319 Zuordnungseinheiten auf dem Datenträger verfügbar


-----------------------------------------------------------------------

 

[Toppa]

Tell me if this attachement is better to read for you.

 

[Toppa]

Solved.

I plugged my system disk to the second storage controller on the mainboard (JMicron, Sata II) and everything is fine.

I won't go into further investigation for whatever reason there is this problem, because this topic has cost me a week already.
My hardware is about six years old and I anyways planned to exchange the mainboard and cpu etc.
The SSD shouldn't be defective and the downgrade from Sata III to II should be something I can deal with in the meantime.

Thank you for your help.

Things I additionaly tested were:
- Reinstalled Windows
- Exchanged Sata cables
- Switched Sata ports (on the same controller)
- Installed a bunch of amd sata and chipset drivers
- Deactivated HPIM/DPIM in power management settings
- Disconnected DVDROM and other HDDs