- Joined
- Aug 13, 2012
- Messages
- 70 (0.02/day)
- Location
- Timmonsville, SC
System Name | L33T PC |
---|---|
Processor | (Bulldozer) AMD FX-8120 Zambezi Processor (8 CPUs), ~4.0GHz (OC'd) |
Motherboard | ASRock Fatal1ty 990FX Killer ATX AM3+ Motherboard |
Cooling | COOLER MASTER Hyper 212 EVO |
Memory | Corsair Vengeance™ 1600MHz DDR3 16GB (4 x 4) RAM |
Video Card(s) | (XFX) Ati Radeon R7770 Ultra Overclock +95Mhz Faster 1GB GDDR5 |
Display(s) | Acer H233H & Acer X203H |
Case | Thermaltake’s Black Widow V9 Black Edition |
Audio Device(s) | Sound Blaster ZX |
Power Supply | Corsair 750W |
Mouse | Logitech G600 MMO Gaming Mouse |
Keyboard | Logitech G510 Gaming Keyboard |
Software | Windows 8.1 Pro x64 |
Hi JonathanC,
That’s great news, I am glad that helped.
In order to reduce boot-up time further I would ensure that all of these optimization utilities are not loading taskbar programs/background tasks or services. Having this many programs that optimize a system can help but they also carry resource overhead.
If your Windows installation was a clean install I really don’t see how Advanced System Optimizer 3.1 corrected 8243 errors. Results from free programs like this should be taken with a large pinch of salt. Yes, it sped up boot time by 90 seconds but such residue in the registry only builds up from installing and uninstalling programs often.
Now that this program has done its job, disable it from starting with Windows to cut boot time a little further.
For example, my PC only starts my AV software and the fragmentation prevention service of PerfectDisk v12.5 Professional Build 311. That’s it, nothing else. I was even reluctant to allow PerfectDisk to start at boot up. I believe in a very minimal start-up configuration since every program that loads adds overhead, takes up a bit of RAM and has the potential to crash or cause a conflict. I believe the fewer programs that are running at start-up for speed and reliability reasons the better.
My PC boots in 35 seconds (30 seconds if you remove the time it takes for me to type my Windows password). I have an advantage of using a 600GB Western Digital VelociRaptor, SATA 6Gb/s, 10000rpm with 32 MB Cache for my Windows drive. This isn’t as fast as an SSD but it’s faster than your average HDD. My Windows installation is now 13 months old and I update every program on my PC as new updates become available, so lots of installing and occasional uninstalling. I don’t use registry optimizers; I don’t believe they can make a significant difference.
My chipset, GPU, sound card, network card and wireless network card are using the most up to date drivers.
If you have ever had any other security software installed on your computer (other than Avast and Bitdefender) I would also suggest running the appropriate removal tool for it. I have created a full of all such tools in a different forum at:
http://www.pctools.com/forum/showthread.php?69641-Bsod&p=242073#post242073
Try also booting your PC without Soluto monitoring it and see what difference it makes, monitoring a boot adds time too. One final suggestion is to disable AMD Fuel temporarily since it’s crashing; recovering from this crash during boot up is probably adding yet more time.
I hope this is of assistance to you. If I can help further, please let me know.
Thanks.
Will try some of the things you listed here and see if they help, thanks for the advice

I love how uninstalling things sped up your boot time....yet a clean install did nothing. Do you know what a clean install is?
MailMan I am beginning to question what your reason for posting even is, as it seems the last two posts you made have just been referencing back to why removing things works but a clean install doesn't. Believe or not I too am just as puzzled as you are, and I have used some of your techniques in trying to troubleshoot this, though some of them were in the past they didn't remedy the issue.
Regardless though, I do know what a clean install is... and even through a clean install with no BS added my computer still does the same thing... After a clean install I then install all the updates from microsoft, which takes the boot time down to 15 seconds, that lasts for maybe a week then it does it again, hence why i mentioned in a previous post that I am aiming more at the possibility of it being hardware related (like you had originally mentioned)
Simply because uninstalling these programs are helping, maybe because things are being erased from the HDD. Which in turn puts the HDD to work and may be remedying the problem, but how much would like to bet that a week or 2 from now, this problem will reappear? So I am aiming at the possibilities of hardware related problems, even thought this drive passed the SMART test.
So now I hope you understand why this post may have been confusing in any possible way. I will try to be more clear from here on out.
(PS: I didn't mean this in a hostile way so please do not take offense to anything stated above... I'm just really tired ATM and things are processing slow for my brain XD )
I dont know if its been said yet as im not going to pour through all these posts so i apologize in advance if it has been mentioned. (i just woke up and dont feel like it).
Have you tried a different hard drive with windows installed on it? Have you benchmarked the hard drives speed to see if youre getting accurate speeds? If the speeds are not accurate then the most likely culprit is the hard drive and it will need to be replaced.
Say for example you have your OS on your 300GB hdd and it is the one giving you the problems right now. If you can, put windows on your WD 1TB hdd (partition the drive if you have to) and boot windows. Do you still have the same problem?
I don't believe this has been brought up. I will honestly say that I haven't tested the OS on another drive since I built this rig, that may be something I'll have to try in order to figure out if it is a hardware related problem or not. Thanks for the idea

(If anyone else mentioned this I apologize for skipping over it, this has been a long frustrating issue and my nerves are quiet shot! Haha)
EDIT: Also this IS NOT a clean install. I said I have tried clean installs in the past when this issue first started, the install I am using now is only 2 months old anyways, this started about 2 days after i installed this run around.
Last edited: