• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

SSD tweaks?

F

Faethon

[H]ard|Gawd
Joined
Oct 31, 2005
Messages
1,071
Hi, i am confused after reading controversial opinions about some SSD "tweaks". Most notably, Superfetch. I have googled and found passionate opinions about that and i wonder if by now the things have settled to a more "common opinion".

Win7 is "supposed" to disable Superfetch and disk defragmenting. In my PC, the WEI gives 7.9 score to my humble Kingston VP200 120GB SATA3. Windows though didn't disable disk defragmenting (i disabled it manually) and has set Superfetch to "manual". Unfortunately, this is probably causing repeating event viewer errors about Readyboot:

The maximum file size for session "ReadyBoot" has been reached. As a result, events might be lost (not logged) to file "C:\Windows\Prefetch\ReadyBoot\ReadyBoot.etl". The maximum files size is currently set to 20971520 bytes.
Session "ReadyBoot" stopped due to the following error: 0xC0000188

So, i am wondering whether the guys saying Superfetch should be on, were right after all.


What is the consensus nowdays?

Thank you.
 
drescherjm said:
The OS is supposed to automatically enable all of the necessary tweaks. Did you reinstall or clone?
Click to expand...

I did new Windows install, but in the meantime, i have used recovery software (Macrium) to restore image. The problem is that OS doesn't seem to do the things so well. I 've never had before "readyboot" errors. Also, i noticed that if i leave the pagefile to Windows' discretion (manage for all drives), it actually creates 1 pagefile on the SSD and a 2nd pagefile on an HDD i have. That's another weird thing for me... So i set it manually to the SSD.

But i ask about this Superfetch setting, because from googling, it appears that the readyboot error, could be related to Superfetch not being active.
 
Per MS Superfetch should be off, but it's easy enough to change the setting and see what happens.

A good read as old as it is now....

http://blogs.msdn.com/b/e7/archive/2009/05/05/support-and-q-a-for-solid-state-drives-and.aspx

Not sure if this applies or not...but I figured I'd link it.

Will Superfetch be disabled on SSDs?

Yes, for most systems with SSDs.

If the system disk is an SSD, and the SSD performs adequately on random reads and doesn’t have glaring performance issues with random writes or flushes, then Superfetch, boot prefetching, application launch prefetching, ReadyBoost and ReadDrive will all be disabled.

Initially, we had configured all of these features to be off on all SSDs, but we encountered sizable performance regressions on some systems. In root causing those regressions, we found that some first generation SSDs had severe enough random write and flush problems that ultimately lead to disk reads being blocked for long periods of time. With Superfetch and other prefetching re-enabled, performance on key scenarios was markedly improved.
Click to expand...
 
Well, mine was never disabled, it was set to "manual" in services (but the service wasn't running, so i ll take that as disabled).

Anyway, thanks, i will try with Superfetch both off and on. I found various theories in google. Some say that when that error comes, you need to enable superfetch. Another suggests increasing the log file of readyboot to 60MB (from 20) and another theory yet, is that the error is normal after a new installation, because it's just a way of the OS to tell you that it has disabled readyboot...

I guess i must start and work by exclusion. MS herself, has a very useless article

http://support.microsoft.com/kb/2001347

which isn't worth a dime, because it basically says "oh, ignore it". The problem is, i like having "clean" event Viewer.


Anyway, thanks, i think now i have all possible routes to try, so i will go by trial and error.


P.S: Thanks for reminding me Limahl! http://www.youtube.com/watch?v=ZQ4HvTKYU5k
 
Well, the OS isn't trying to tell me that readyboot is disabled, because i just verified that it's enabled. So, one wrong info is out of the way.

Also, i found out that some people with SSDs and the same problem, try to solve it by... disabling readyboot too. But i am not a big fan of "disable all", so i will try the other roads.
 
If you have a intel mobo , i think you can just use intel ssd toolbox and hit optimize for the os adjustments
 
Well, i think that now i can say that enabling Superfetch, makes the readyboot error disappear. So, thank you dear Microsoft, for the "optimization", but, i will keep the superfetch on.
 
To fully disable Prefetch and Superfetch:

Open the Start Menu, type Services.msc, press Enter
Scroll down until you see the "SuperFetch" entry
Double-click on it, and choose "Disabled" from the list
Next:
Open the Start Menu, type regedit, press Enter
Go to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters
Double-click on "EnablePrefetcher" and enter "0" (default value is "3")
Double-click on "EnableSuperfetch" and enter "0" (default value is "3")

(Taken from Sean's Win7 SSD guide)

Is it possible that doing the first part without doing the regedit part would result in the readyboot errors? I don't know, but it's worth trying. Sean does say this about whether it should be on or off:

"The purpose of these is to pre-load the programs you load from slow hard drive to fast memory (cache) in case you want to run them. With your SSD, there is no need. Disable them and free up some memory and resources and stop a lot of writes to the SSD. However, this may hurt performance in older first gen SSDs and HDDs."
 
Thanks, but i 've gone mad with this error since yesterday, i 've lost count on how many times i 've restored an image trying to troubleshoot it (removing drivers etc) and now that i 've got it working, i am not touching it again.

Superfetch will remain enabled for me. If the SSD dies because of that, so be it. I don't see any performance hit, i ran CrystalDisk mark and seems right and actually i think some applications launch a little bit faster. Which makes sense, since RAM is faster than SSD.
 
Would a completely new reinstall be out of the question? I mean no upgrades, just a new format and install?
 
ob1 said:
Would a completely new reinstall be out of the question? I mean no upgrades, just a new format and install?
Click to expand...

I just did that yesterday... I may do it again, but not in this month. I am tired of re-installing and re-imaging. I had already reinstalled before Xmas in order to update drivers and some programs. But i hadn't looked at the event viewer.
 
I bit the bullet and re-installed Windows (again). And now i have no error with superfetch on manual... Beats me...
 
You must log in or register to reply here.
Back
Top