Windows 8/8.1 painfully slow to Boot .Take 10-15 min

[sasha007]

Hi ,


I've had certain problem with my Windows 8 installation .
Let me summarize the entire scenario but before that below are my System Details .


System :- Dell Inspiron 17R SE 7720 Laptop .
O/S :- Windows 8.1 .


I formatted my system yesterday and installed Windows 8.1 via MSDN ISO . Installed Dell Drivers and a few programs like Norton 360 etc , after which i shutdown my system yesterday .


When i opened my system today , i was shocked to see Preparing automatic repair message on the Dell boot screen . It tried Automatic repair because it said that Windows was unable to boot properly . However , Automatic repair was unable to do anything .


After that i shutdown my system again and then again powered it on. This time it booted to Windows but took about 5 min to get to the password screen . After booting to Desktop mode , i tried to open chrome , task manager etc , but nothing opened , and the system was painfully slow up until 10 min . After which everything was normal .


Tried to open Event log and it also crashed .


I again restarted my system and this time it was lightening fast . Tried to shutdown and restart 2-3 times more , and it was fast all these times .


Can someone please help me understand what is causing this issue ? I've attached a dump of all my logs using SF Diagnostic tool .


Please help .

 

[Simba]

Could be bad sectors on the hard drive, run chkdsk to eliminate or fix that issue.

 

[usasma]

1) Start with the free diagnostics located at Initial Hardware Diagnostics At work we start all repairs with a set of diagnostics. Often they find problems that weren't even expected. It's a waste of time to try to fix software on a system that has hardware problems. You may also want to try the rest of the diagnostics here: Additional Hardware Diagnostics
2) Ensure that you have ALL Windows Updates This fixes the majority of Windows problems.

Just FYI:

In most cases I look for errors in this order (although when scanning reports it can be in any order):
- 3rd party drivers (usually the cause of over 90% of BSOD's)
- hardware problems (usually the cause of less than 10% of BSOD's)
- Windows problems (usually the cause of less than 1% of BSOD's - but I think this number is significantly affected by asking to have Windows fully updated)

Please do the following (keep trying as I think we need this logfile):
- open Event Viewer (run eventvwr.msc from the "Run" dialog))
- 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).

No memory dumps in the uploaded files. Please do this:

Upload Dump Files:
NOTE: If using a disk cleaning utility, please stop using it while we are troubleshooting your issues.
Please go to C:\Windows\Minidump and zip up the contents of the folder. Then upload/attach the .zip file with your next post.
Left click on the first minidump file.
Hold down the "Shift" key and left click on the last minidump file.
Right click on the blue highlighted area and select "Send to"
Select "Compressed (zipped) folder" and note where the folder is saved.
Upload that .zip file with your next post.

If you have issues with "Access Denied" errors, try copying the files to your desktop and zipping them up from there. If it still won't let you zip them up, post back for further advice.

If you don't have anything in that folder, please check in C:\Windows for a file named MEMORY.DMP. If you find it, zip it up and upload it to a free file hosting service. Then post the link to it in your topic so that we can download it.

Also, search your entire hard drive for files ending in .dmp, .mdmp, and .hdmp. Zip up any that you find and upload them with your next post.

Then, follow the directions here to set your system for Minidumps (much smaller than the MEMORY.DMP file): Set MiniDumpMore info on dump file options here: Overview of memory dump file options for Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2

Please install the drivers for this device:

USB2.0-CRW USB\VID_0BDA&PID_0129\20100201396000000 The drivers for this device are not installed.

 

[TeknoBug]

15 minutes to boot? Wow Windows 3.1 nostalgia. My laptop boots win 8.1 in 3ish seconds.

 

[sasha007]

1) Start with the free diagnostics located at Initial Hardware Diagnostics At work we start all repairs with a set of diagnostics. Often they find problems that weren't even expected. It's a waste of time to try to fix software on a system that has hardware problems. You may also want to try the rest of the diagnostics here: Additional Hardware Diagnostics 2) Ensure that you have ALL Windows Updates This fixes the majority of Windows problems. Just FYI:

In most cases I look for errors in this order (although when scanning reports it can be in any order): - 3rd party drivers (usually the cause of over 90% of BSOD's) - hardware problems (usually the cause of less than 10% of BSOD's) - Windows problems (usually the cause of less than 1% of BSOD's - but I think this number is significantly affected by asking to have Windows fully updated)

Please do the following (keep trying as I think we need this logfile): - open Event Viewer (run eventvwr.msc from the "Run" dialog)) - 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). No memory dumps in the uploaded files. Please do this:

Upload Dump Files: NOTE: If using a disk cleaning utility, please stop using it while we are troubleshooting your issues. Please go to C:\Windows\Minidump and zip up the contents of the folder. Then upload/attach the .zip file with your next post. Left click on the first minidump file. Hold down the "Shift" key and left click on the last minidump file. Right click on the blue highlighted area and select "Send to" Select "Compressed (zipped) folder" and note where the folder is saved. Upload that .zip file with your next post. If you have issues with "Access Denied" errors, try copying the files to your desktop and zipping them up from there. If it still won't let you zip them up, post back for further advice. If you don't have anything in that folder, please check in C:\Windows for a file named MEMORY.DMP. If you find it, zip it up and upload it to a free file hosting service. Then post the link to it in your topic so that we can download it. Also, search your entire hard drive for files ending in .dmp, .mdmp, and .hdmp. Zip up any that you find and upload them with your next post. Then, follow the directions here to set your system for Minidumps (much smaller than the MEMORY.DMP file): Set MiniDumpMore info on dump file options here: Overview of memory dump file options for Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2

Please install the drivers for this device:

USB2.0-CRW USB\VID_0BDA&PID_0129\20100201396000000 The drivers for this device are not installed.

Which Diagnostics to run from the many in the link to posted ?


Also , Aren't there any log reports in the zip file i posted ?

 

[sasha007]

1) Start with the free diagnostics located at

Initial Hardware Diagnostics At work we start all repairs with a set of diagnostics. Often they find problems that weren't even expected. It's a waste of time to try to fix software on a system that has hardware problems. You may also want to try the rest of the diagnostics here: Additional Hardware Diagnostics
2) Ensure that you have ALL Windows Updates This fixes the majority of Windows problems.

Just FYI:

In most cases I look for errors in this order (although when scanning reports it can be in any order):

- 3rd party drivers (usually the cause of over 90% of BSOD's)
- hardware problems (usually the cause of less than 10% of BSOD's)
- Windows problems (usually the cause of less than 1% of BSOD's - but I think this number is significantly affected by asking to have Windows fully updated)

Please do the following (keep trying as I think we need this logfile):
- open Event Viewer (run eventvwr.msc from the "Run" dialog))
- 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).

No memory dumps in the uploaded files. Please do this:

Upload Dump Files:
NOTE: If using a disk cleaning utility, please stop using it while we are troubleshooting your issues.
Please go to C:\Windows\Minidump and zip up the contents of the folder. Then upload/attach the .zip file with your next post.
Left click on the first minidump file.
Hold down the "Shift" key and left click on the last minidump file.
Right click on the blue highlighted area and select "Send to"
Select "Compressed (zipped) folder" and note where the folder is saved.
Upload that .zip file with your next post.

If you have issues with "Access Denied" errors, try copying the files to your desktop and zipping them up from there. If it still won't let you zip them up, post back for further advice.

If you don't have anything in that folder, please check in C:\Windows for a file named MEMORY.DMP. If you find it, zip it up and upload it to a free file hosting service. Then post the link to it in your topic so that we can download it.

Also, search your entire hard drive for files ending in .dmp, .mdmp, and .hdmp. Zip up any that you find and upload them with your next post.

Then, follow the directions here to set your system for Minidumps (much smaller than the MEMORY.DMP file): Set MiniDumpMore info on dump file options here: Overview of memory dump file options for Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2

Please install the drivers for this device:

USB2.0-CRW USB\VID_0BDA&PID_0129\20100201396000000 The drivers for this device are not installed.

Hi ,

My system ran file all of yesterday after that one long startup .

Again i did a clean shutdown yesterday and started up my system today . Again it took about 12 minutes to boot .

Even after booting to Desktop System was not responsive for 5-6 more min . Noticed one odd thing in the task manager that Disk usage stayed at 100% all that time .

Below is the Link for the dumps created by SF Diagnostic Tool :

https://mega.co.nz/#fmtRdjyIxK

Now Regarding the steps you asked usasma .

1. Which all Diagnostics to run from Initial Hardware Diagnostics?

2. Have installed All Windows updates . Installed Driver for USB2.0-CRW USB\VID_0BDA&PID_0129\20100201396000000 as you asked.

3. Event Viewer as you asked :

https://mega.co.nz/#fmtRdjyIxK

4. Did not find anything in C:\Windows\Minidump

Checked Advanced System Settings and here is the screenshot :



What do you want me to change these settings to ?

5 . Searched the Hard drive and found some dumps . Zipped and uploaded .

Link :-https://mega.co.nz/#fmtRdjyIxK

6. No Bad sectors on drive . Its clean !

But Ran SeaTools For Windows and it says :-

Short DST FAIL

Its log file :-

--------------- SeaTools for Windows v1.2.0.8 ---------------
27-10-2013 20:03:09
Model: ST1000LM024
Serial Number: S2WZJ90C
Firmware Revision: A22R
Short DST - Started 27-10-2013 20:03:09
Short DST - FAIL 27-10-2013 20:03:12
Sense Key: 0x05 Sense Code: 0x20 Sense Qual: 0x00 FRU: 0x00
SeaTools Test Code: D662B0E1
Short DST - Started 27-10-2013 20:03:39
Short DST - FAIL 27-10-2013 20:03:42
Sense Key: 0x05 Sense Code: 0x20 Sense Qual: 0x00 FRU: 0x00
SeaTools Test Code: D662B0E1
Short DST - Started 27-10-2013 20:17:41
Short DST - FAIL 27-10-2013 20:17:43
Sense Key: 0x05 Sense Code: 0x20 Sense Qual: 0x00 FRU: 0x00
SeaTools Test Code: D662B0E1
Inquiry - Started 27-10-2013 20:19:04
Short Generic - Started 27-10-2013 20:19:11
Short Generic - Pass 27-10-2013 20:28:34
Short DST - Started 27-10-2013 20:28:45
Short DST - FAIL 27-10-2013 20:28:47
Sense Key: 0x05 Sense Code: 0x20 Sense Qual: 0x00 FRU: 0x00
SeaTools Test Code: D662B0E1
Short DST - Started 27-10-2013 20:39:19
Short DST - FAIL 27-10-2013 20:39:22
Sense Key: 0x05 Sense Code: 0x20 Sense Qual: 0x00 FRU: 0x00
SeaTools Test Code: D662B0E1




Kindly tell what to do now ?

 

[OldMX]

You have a bad disk, time to RMA if under warranty.

 

[sasha007]

You have a bad disk, time to RMA if under warranty.

You sure ?

HDD passed Short Generic Test.




Now Running Long generic test now and it is taking quite some time .

 

[usasma]

Run long/extended test. If it fails - drive is likely dead/dying.

Sent from my phone - will be online in the AM

 

[sasha007]

Hi Usasma ,

Just now completed the Long generic test in SeaTools for Windows and it passed .




Also to be sure i ran the Dell diagnostics at boot time of my laptop and it passed everything .

Kindly Suggest what to do ?

 

[OldMX]

Can you post a screenshot of Crystal Diskinfo showing decimal values?

Should look something like this:
View attachment 30500

 

[sasha007]

Here you go :-

Crystal Disk Info Screenshot for my Hard disk :-



Crystal Disk Info Screenshot for my SSD :-

 

[usasma]

Although the hard drive is still a suspect, it's not as likely as it was before you ran the Dell and Seagate diagnostics.
Please run all of the diagnostics at this link: Hardware Diagnostics
This is designed to test those parts that have easily available diagnostic tests.

Just FYI - there aren't any Pass/Fail tests for SSD's. So problems with SSD's will have to be inferred through tests like CrystalDiskInfo. I'd suggest posting a screen shot of the SSD in CrystalDiskInfo so that OldMX can have a look at it (they seem more familiar with that test than I am). I'm leaning towards blaming the SSD here - but that's just a hunch/guess on my part.

The other report that I asked for is a combination of error reports from throughout the system. The generic reports that you've already submitted don't contain all of that info. Additionally, it's a great tool for looking for patterns when an error in one log is related to an error in another log.

I cannot access the download for the Admin report. I suspect that it's because I am not registered at their site. Try zipping it up and uploading it here.

Did you check in C:\Windows for a file named MEMORY.dmp? If you found one, what was the date on it? If it was recent, please upload it. If it's in the dumps that you found and uploaded at MegaUpload, please upload them to a free service that doesn't require registration to download (such as DropBox or SkyDrive).

Right now we are looking for problems in the storage sub-system, so we have to do things that relate to the hard drive/SSD and it's controllers. We also have to look lower in case something else is causing these issues. A problem with one device in the storage sub-system (such as the SSD) can cause problems with other devices (such as the Seagate hard drive). So can bad cabling/connectors; problems with storage controllers (on the motherboard) - either hardware or software, and even with the other components/software on the motherboard.

If you have an nVidia or SiS storage controller - those drivers are very outdated (a Google search suggests that your storage controllers are from Intel). The memory dumps will help to tell us if the nVidia/SiS drivers are involved or not.

Another thing to do is to have Task Manager open to the Processes tab when the system boots - and then keep an eye on what's hogging all the disk activity. You can also check the RAM and memory usage there - and the Performance tab may give you some more info. That may give clues as to what's causing the problem.

Please run this test on all hard drives. It will test the file structure on the hard drives (if you've already run it, please disregard):

CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
FWIW - I know that the /F is supposed to be redundant, but I prefer to have it run anyway.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Please let us know what the results said when it's done.

Finally, we have to keep compatibility issues in mind. Although Win8.1 is a very stable OS, I have seen more problems with it than I did with Win8.

 

[jimbo45]

Hi there

Obviously "Houston ---- We have a problem ........!".

Right before doing anything else we need to see if your HDD is defective.

Two suggestions here -- my favourite would be to boot a LINUX Live CD and then see if you can access the files on the computers HDD -- there's loads of Linux live CD's that you can download.

The other one would be to restore the Factory partition again and see if the machine boots OK.

Either of these options should tell you quickly if your HDD is defective --if it is then get it changed --warranty if the PC is under warranty - or if not you can do it yourself really simply on most desktop PC's - and most laptops -- CAREFUL though when you remove the HDD in a laptop as the cable can be fairly flimsy -- you won't need any tools other than a screwdriver.

If the HDD is NOT defective - backup what you need from it and then totally wipe it (format etc) then do a complete Windows install from scratch. Keep the recovery partition though.

For partition creation etc -- bootable copy of GPARTED can be downloaded from almost anywhere or Partition Wizard etc - I use GPARTED but any are OK.

Note also remove external USB devices during boot - sometimes - especially on desktop PC's having these connected at boot makes the BIOS go into all sorts of testing / diagnostic routines --but even here it still shouldn't take THAT long to boot.

Cheers
jimbo

 

[sasha007]

Although the hard drive is still a suspect, it's not as likely as it was before you ran the Dell and Seagate diagnostics.
Please run all of the diagnostics at this link: Hardware Diagnostics
This is designed to test those parts that have easily available diagnostic tests.

Just FYI - there aren't any Pass/Fail tests for SSD's. So problems with SSD's will have to be inferred through tests like CrystalDiskInfo. I'd suggest posting a screen shot of the SSD in CrystalDiskInfo so that OldMX can have a look at it (they seem more familiar with that test than I am). I'm leaning towards blaming the SSD here - but that's just a hunch/guess on my part.

The other report that I asked for is a combination of error reports from throughout the system. The generic reports that you've already submitted don't contain all of that info. Additionally, it's a great tool for looking for patterns when an error in one log is related to an error in another log.

I cannot access the download for the Admin report. I suspect that it's because I am not registered at their site. Try zipping it up and uploading it here.

Did you check in C:\Windows for a file named MEMORY.dmp? If you found one, what was the date on it? If it was recent, please upload it. If it's in the dumps that you found and uploaded at MegaUpload, please upload them to a free service that doesn't require registration to download (such as DropBox or SkyDrive).

Right now we are looking for problems in the storage sub-system, so we have to do things that relate to the hard drive/SSD and it's controllers. We also have to look lower in case something else is causing these issues. A problem with one device in the storage sub-system (such as the SSD) can cause problems with other devices (such as the Seagate hard drive). So can bad cabling/connectors; problems with storage controllers (on the motherboard) - either hardware or software, and even with the other components/software on the motherboard.

If you have an nVidia or SiS storage controller - those drivers are very outdated (a Google search suggests that your storage controllers are from Intel). The memory dumps will help to tell us if the nVidia/SiS drivers are involved or not.

Another thing to do is to have Task Manager open to the Processes tab when the system boots - and then keep an eye on what's hogging all the disk activity. You can also check the RAM and memory usage there - and the Performance tab may give you some more info. That may give clues as to what's causing the problem.

Please run this test on all hard drives. It will test the file structure on the hard drives (if you've already run it, please disregard):

CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
FWIW - I know that the /F is supposed to be redundant, but I prefer to have it run anyway.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Please let us know what the results said when it's done.

Finally, we have to keep compatibility issues in mind. Although Win8.1 is a very stable OS, I have seen more problems with it than I did with Win8.

Hi usasma ,

Please interpret my reply point by point (points are in the same chronology of information that you asked for) so that it is easy for you to go through the information :-

1. As advised , I will run all of the diagnostics at this link: Hardware Diagnostics . But is it fine if i dont run the stress tests for GPU as i'm afraid of them , since on my last system running Furmark test fried my Nvidia GPU .

So Kindly advise if not running GPU related tests is fine or not ?

2. Posted a CrystalDisk Info screenshot for my SSD as well in the same post above for OldMx to have a look .

3. I checked in C:\Windows and did not find any MEMORY.dmp file . This may be because i don't have small memory dump set in my advanced settings , but a Complete memory dump set .

Here is a screenshot of my system advanced settings :



3.1 Please advise on why are there no dumps ?
3.2 What should Write Debugging information be set to ?
3.3 Also , should Automatic restart be checked ?


4. Here is the dropbox link for the reports that i uploaded previously on Mega .

Seven Forum Diagnostic Tool Report for 26th October (which i included in my previous post when the slow boot was encountered -

https://www.dropbox.com/s/cjbaiip2o4wn6j0/SF_27-10-2013.zip

Seven Forum Diagnostic Tool Report for today 29th October (again created just in case any new info ) -

https://www.dropbox.com/s/0jkhejpzu2jjlv5/SF_29-10-2013.zip

Event Viewer Administrative events dump for 26-10-2013 (as in previous post )-

https://www.dropbox.com/s/xmlyu0w1jdy7cps/Event Log 26-10-2013.zip

Event Viewer Administrative events dump for today 29-10-2013 -

https://www.dropbox.com/s/zc28v2uji1hlah3/Event Log 29-10-2013.zip

Dumps whatever found in the entire drive -

https://www.dropbox.com/s/z6i5h9ryodh0ljx/Dumps.zip


5. Regarding the task manager monitoring , is there any tool that can dump all the activities including the resource usage during boot into some text file so that we can have a look ?

One odd thing i noticed , is that the Disk is 100% usage during boot . The disk even goes to 100% usage when i do some cut/copy/paste operation .

6. Will Run Chkdsk and post the results in the next post .

7. Just for your information , the slow boot does occur once every 5-10 boots . Rest of the boots are lightening fast . Why should it be like this ?

If possible , Please kindly revert on a point by point basis so that it would be easy for me to take care of each and everything .
And i don't miss anything .

Awaiting your revert . Thanks

 

[usasma]

I am presuming that by "revert" you actually mean "reply" - that is, you want me to answer your questions, or reply about the information that you've provided.

Here are the points that you asked about:
1. Skip what you want - but each test that you skip is a potential problem that you're skipping. With Furmark (as with any stress test) - damage is a real possibility. You must watch the system closely and be prepared to stop the tests immediately if problems occur. As for frying your GPU previously - this tells me that the cooling solution for the GPU was broken - so the GPU may have already been damaged, or it would have shortly been damaged by excessive temps.

2. The CrystalDisk screenshot for the SSD doesn't look good to me (I'm concerned about CRC error check among other things) - but let's wait for OldMX to have a look at it.

3. Memory dumps are usually first seen as the MEMORY.dmp file no matter what the setting is. Then the memory dump mechanism will generate a minidump from that.

3.1 I don't know why there aren't any dumps. Here's a link (draft) on how dump files are generated. Please note that I haven't finished my research on how dump files are generated in Win8.1, so the information may be incomplete: BSOD Crash Dump Generation

In most cases I don't research why they aren't created, because:
- dumps early in the boot process aren't caught because the crash mechanisms haven't loaded fully (so we can't do anything about it)
- often WER will write some of the memory dump info to the error logs - so you can get an idea of what's happening from there.
- other dump generation failures usually (IME) are due to problems with the storage sub-system, so we troubleshoot that instead

3.2 Write Debugging information should be set to Automatic Memory Dump or Small Memory Dump (IMO). Complete memory dump doesn't hurt, but I suspect that it'll miss some minidumps (small memory dumps) - which are the primary dumps that we are concerned with.

3.3 Automatic restart should be checked, but this is just a convenience (it means that you won't have to press the power button to restart the system after the BSOD). I keep mine unchecked because I want to see what the BSOD says - but it's not necessary as the new (Win8+) BSOD's aren't as informative as those from Win7 and earlier.

4. Thanks for the reports, I'll get to them later on today (it's my off day and I have to do yard work

5. There are performance monitoring tools available (see this for starters: XPerf - it's an old post)
I just like to look at the list and see what's eating up the most activity
There is an option to show history for all processes - but mine is greyed out and I can't access it
If you can't figure it from there, then try the Details tab - and add the I/O Reads and I/O Other columns. (they are the one's most typically involved with hard drive/boot/performance issues) The problem with high disk usage is that it's slower than memory - so the system will slow down when that happens.

6. Thanks for running chkdsk. I'll be interested in seeing the results on the SSD

7. I don't know why this is (slow boots vs fast boots). If I did, I suspect that we'd have already fixed your problem! :0)

Just FYI - I specialize in BSOD analysis. As such, I have a great deal of knowledge in a small area - there are many areas that I just don't know anything significant about. I will try to help in those areas - or I will refer you to others who know more than I do (if necessary).

 

[sasha007]

Hi Usasma ,

Thanks for detailing your reply for each and every point . Yes , i meant reply .

Please find some more points below :-


1. I ran CHKDSK /R /F on my Hard disk and here are the results :-

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
190976 file records processed.
File verification completed.
1393 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
247268 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.

Stage 3: Examining security descriptors ...
Cleaning up 897 unused index entries from index $SII of file 0x9.
Cleaning up 897 unused index entries from index $SDH of file 0x9.
Cleaning up 897 unused security descriptors.
Security descriptor verification completed.
28147 data files processed.
CHKDSK is verifying Usn Journal...
35399520 USN bytes processed.
Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
190960 files processed.
File data verification completed.

Stage 5: Looking for bad, free clusters ...
10315480 free clusters processed.
Free space verification is complete.
CHKDSK discovered free space marked as allocated in the volume bitmap.

Windows has made corrections to the file system.
No further action is required.

104316927 KB total disk space.
62685688 KB in 108660 files.
73048 KB in 28148 indexes.
0 KB in bad sectors.
296267 KB in use by the system.
65536 KB occupied by the log file.
41261924 KB available on disk.

4096 bytes in each allocation unit.
26079231 total allocation units on disk.
10315481 allocation units available on disk.

Internal Info:
00 ea 02 00 6c 16 02 00 dd f8 03 00 00 00 00 00 ....l...........
2c 01 00 00 87 00 00 00 00 00 00 00 00 00 00 00 ,...............

Windows has finished checking your disk.
Please wait while your computer restarts.






2. I do not have any partitions on my SSD . Basically it is used to accelerate my Hard disk using Intel rapid storage technology/Smart response technology . Screenshot :-




Details of the SSD :-



3. I've set Write debugging information to Small memory dumps as you've advised .

But what should i do since dumps did not generate previously as i did not find any ?

And it's Okay . Please look at the logs when you've got time

 

[sasha007]

Hi,

Again encountered a Slow boot , but it was more like boot to desktop in about 30-35 seconds , and the desktop was unresponsive for about 5-6 min .

Took some screenshots of the task manager and the disk was at 100% usage most of the time :-



















See if this helps ..

BTW dmp are created only when a crash/BSOD occurs ?

Bcoz i did not find any dmp still ( after this slow boot ) ..


UPDATE :- I just experienced my first BSOD upon a fresh boot after a shutdown . Apparently , The Dell logo appeared and then i received this BSOD :-



Here is the dropbox link for the dump from SF Diagnostic tool :-

https://www.dropbox.com/s/0jkhejpzu2jjlv5/SF_29-10-2013.zip

This time i did find the Minidump folder and a .dmp in it . Since i did set Small memory dump now .
The dmp is included in the zip above .

Kindly analyse it and advise .

 

[usasma]

Took a quick break from yardwork to look at the screenshots.
First thing that pops out is Norton 360
Try this:

Anti-Virus Removal:
Please do the following:
- download a free anti-virus for testing purposes: Free AntiVirus If using Windows 8, enable Windows Defender and the Windows Firewall instead (after removing Norton).
- un-install the Norton from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Norton using this free tool: http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN
- IMMEDIATELY enable Windows Defender, then check to ensure that the Windows Firewall is turned on.
- perform a full system scan to ensure that no malware has snuck onto your system while the anti-virus was malfunctioning.
- check to see if this fixes the BSOD's
NOTE: NEVER run more than 1 anti-virus, firewall, Internet Security/Security Center application at the same time.

Will post more later on (probably in 4 hours or so).

 

[sasha007]

I've removed Norton 360 and rebooted . Disk usage info :-



Disk usage still 100% . Is that Normal for disk usage to be 100% ?

Wil run a scan through Windows defender .

BTW this install of Windows 8.1 is barely 6 days old when i freshly installed it .
Also , please analyse the dmp and tell what caused the BSOD..

I'm installing a fresh copy of windows 8.1 on a different partition along-with this installation . Is that fine ?