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

usasma · Oct 29, 2013

Please post the same set of screen shots that you did previously - that way we can compare them. The single screen shots don't give sufficient evidence for us to draw any conclusions (but the reports that you posted may help here).

Did you run the Norton Removal Tool after uninstalling Norton 360? If not, please do so now.

We've covered some of this already - but this is my standard BSOD analysis:

SSD's were temperamental when they first came out, but their reliability has improved greatly over the last year or two. There are 2 things that MUST be checked on systems with BSOD's and SSD's:

1) That the SSD firmware is the latest available for the SSD. I usually can't see this info in the reports, so I rely on you to check it.
2) That the storage controller drivers on the motherboard are the most recent. They must date from late 2012 or later. This is ALL controllers, not just the one that the SSD is attached to. If involved these should be visible in the memory dump - but it doesn't hurt to check manually.

The raw stack text shows both hal.dll and nVidia graphics drivers. I have to wonder if there is a hardware problem with the video. Try the video stress tests - but watch the system very, very carefully when doing so. It can damage your system!!!

Intel Management Engine has not been updated.
Try these links:
https://downloadcenter.intel.com/Se...dType=Drivers&keyword=intel+management+engine
https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=21888
If that doesn't work, then try the Lenovo links in this Google search: https://www.google.com/search?q=intel+management+engine+windows+8&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US;official&client=firefox-a

The memory dump has lot's of Norton stuff in it. Let's wait and see if the system BSOD's again without the Norton installed. Please upload the contents of C:\Windows\Minidump if it does BSOD again.

If it doesn't BSOD in the next 2 days or so, try running Driver Verifier according to these directions: Driver Verifier Settings

Analysis:
The following is for informational purposes only.

Code:

[FONT=lucida console]**************************Tue Oct 29 12:41:34.777 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\102913-97734-01.dmp]
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Built by: [B]9600[/B].16404.amd64fre.winblue_gdr.130913-2141
System Uptime:[B]0 days 4:51:08.553[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+382cd )[/B]
BugCheck [B]1E, {ffffffffc0000005, ffffffffffa5cc84, 0, 12dd218}[/B]
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x0000001E"]KMODE_EXCEPTION_NOT_HANDLED (1e)[/URL]
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: ffffffffffa5cc84, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 00000000012dd218, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0x1E_c0000005_R_nt!_??_::FNODOBFM::_string_[/B]
CPUID:        "Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: [B]2395[/B]
  BIOS Version                  A07
  BIOS Release Date             08/16/2012
  Manufacturer                  Dell Inc.         
  Product Name                  Inspiron 7720
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

Code:

[FONT=lucida console]**************************Tue Oct 29 12:41:34.777 2013 (UTC - 4:00)**************************
Apfiltr.sys              Sun Feb  5 20:05:29 2012 (4F2F2759)
GEARAspiWDM.sys          Thu May  3 15:56:17 2012 (4FA2E2E1)
HECIx64.sys              Mon Jul  2 18:14:58 2012 (4FF21D62)
stwrt64.sys              Thu Sep  6 02:16:11 2012 (50483FAB)
Rt630x64.sys             Fri May 10 05:59:08 2013 (518CC4EC)
vmci.sys                 Fri May 17 21:19:18 2013 (5196D716)
LHidEqd.Sys              Thu May 23 02:09:49 2013 (519DB2AD)
LEqdUsb.Sys              Thu May 23 02:09:50 2013 (519DB2AE)
LMouFilt.Sys             Thu May 23 02:09:56 2013 (519DB2B4)
LHidFilt.Sys             Thu May 23 02:10:00 2013 (519DB2B8)
irstrtdv.sys             Fri Jun 28 16:09:48 2013 (51CDED8C)
IntcDAud.sys             Tue Jul  2 06:31:16 2013 (51D2ABF4)
RtsUVStor.sys            Mon Jul 15 03:27:46 2013 (51E3A472)
VMNET.SYS                Thu Jul 18 15:42:50 2013 (51E8453A)
vmnetadapter.sys         Thu Jul 18 15:43:00 2013 (51E84544)
vmnetbridge.sys          Thu Jul 18 15:43:47 2013 (51E84573)
iwdbus.sys               Wed Jul 24 21:06:12 2013 (51F07A04)
SYMEVENT64x86.SYS        Fri Jul 26 22:26:58 2013 (51F32FF2)
SRTSPX64.SYS             Fri Jul 26 22:45:06 2013 (51F33432)
Ironx64.SYS              Mon Jul 29 20:59:35 2013 (51F70FF7)
SYMDS64.SYS              Tue Jul 30 19:29:08 2013 (51F84C44)
vsock.sys                Wed Jul 31 22:46:10 2013 (51F9CBF2)
igdkmd64.sys             Mon Aug 19 19:08:25 2013 (5212A569)
nvvad64v.sys             Tue Aug 20 07:29:10 2013 (52135306)
EraserUtilDrv11311.sys   Wed Aug 21 17:36:34 2013 (521532E2)
eeCtrl64.sys             Wed Aug 21 17:36:34 2013 (521532E2)
intelppm.sys             Thu Aug 22 04:46:35 2013 (5215CFEB)
NdisVirtualBus.sys       Thu Aug 22 07:36:25 2013 (5215F7B9)
ahcache.sys              Thu Aug 22 07:39:54 2013 (5215F88A)
hiber_storport.sys       Thu Aug 22 07:40:18 2013 (5215F8A2)
werkernel.sys            Thu Aug 22 07:40:24 2013 (5215F8A8)
EX64.SYS                 Thu Aug 22 16:36:51 2013 (52167663)
ENG64.SYS                Thu Aug 22 16:38:20 2013 (521676BC)
NETwew00.sys             Thu Aug 22 17:20:34 2013 (521680A2)
dump_iaStorA.sys         Wed Aug 28 18:13:22 2013 (521E7602)
hiber_iaStorA.sys        Wed Aug 28 18:13:22 2013 (521E7602)
iaStorA.sys              Wed Aug 28 18:13:22 2013 (521E7602)
SYMEFA64.SYS             Sat Aug 31 00:02:36 2013 (52216ADC)
intelpep.sys             Thu Sep 19 03:12:46 2013 (523AA3EE)
SYMNETS.SYS              Mon Sep 23 22:41:10 2013 (5240FBC6)
ccSetx64.sys             Mon Sep 23 23:58:04 2013 (52410DCC)
BHDrvx64.sys             Tue Sep 24 00:07:00 2013 (52410FE4)
SRTSP64.SYS              Wed Sep 25 20:23:42 2013 (52437E8E)
idmwfp.sys               Tue Oct  1 19:17:49 2013 (524B581D)
hcmon.sys                Wed Oct  9 11:03:51 2013 (52557057)
nvlddmkm.sys             Tue Oct 15 16:27:18 2013 (525DA526)
nvpciflt.sys             Tue Oct 15 16:28:03 2013 (525DA553)
IDSvia64.sys             Wed Oct 16 18:10:26 2013 (525F0ED2)
vmnetuserif.sys          Fri Oct 18 14:19:38 2013 (52617BBA)
vmx86.sys                Fri Oct 18 15:34:39 2013 (52618D4F)
[/FONT]

usasma · Oct 29, 2013

Nothing in the Admin Event Viewer log that we didn't suspect already.
Some storage related errors that repeat (NTFS, irstrtsv, iaStor, etc errors)
So it's hard drive/SSD, the connections, or the storage controllers (motherboard is a possibility, but is much less likely as there aren't any other motherboard type issues).

If it's the SSD, then the new installation (I presume it's on the HDD and not the SSD) shouldn't have problems
If it does have problems, then it's most likely the storage controller.

Also, the Intel Management Engine gets it's little fingers in there - so it's important to update it also.

sasha007 · Oct 29, 2013

usasma said:
Please post the same set of screen shots that you did previously - that way we can compare them. The single screen shots don't give sufficient evidence for us to draw any conclusions (but the reports that you posted may help here).

Did you run the Norton Removal Tool after uninstalling Norton 360? If not, please do so now.

We've covered some of this already - but this is my standard BSOD analysis:

SSD's were temperamental when they first came out, but their reliability has improved greatly over the last year or two. There are 2 things that MUST be checked on systems with BSOD's and SSD's:

1) That the SSD firmware is the latest available for the SSD. I usually can't see this info in the reports, so I rely on you to check it.
2) That the storage controller drivers on the motherboard are the most recent. They must date from late 2012 or later. This is ALL controllers, not just the one that the SSD is attached to. If involved these should be visible in the memory dump - but it doesn't hurt to check manually.

Click to expand...

The raw stack text shows both hal.dll and nVidia graphics drivers. I have to wonder if there is a hardware problem with the video. Try the video stress tests - but watch the system very, very carefully when doing so. It can damage your system!!!

Intel Management Engine has not been updated.
Try these links:
https://downloadcenter.intel.com/Se...dType=Drivers&keyword=intel+management+engine
https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=21888
If that doesn't work, then try the Lenovo links in this Google search: https://www.google.com/search?q=intel+management+engine+windows+8&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US;official&client=firefox-a

The memory dump has lot's of Norton stuff in it. Let's wait and see if the system BSOD's again without the Norton installed. Please upload the contents of C:\Windows\Minidump if it does BSOD again.

If it doesn't BSOD in the next 2 days or so, try running Driver Verifier according to these directions: Driver Verifier Settings

Analysis:
The following is for informational purposes only.

Code:

[FONT=lucida console]**************************Tue Oct 29 12:41:34.777 2013 (UTC - 4:00)************************** Loading Dump File [C:\Users\John\SysnativeBSODApps\102913-97734-01.dmp] Windows 8 Kernel Version 9600 MP (8 procs) Free x64 Built by: [B]9600[/B].16404.amd64fre.winblue_gdr.130913-2141 System Uptime:[B]0 days 4:51:08.553[/B] Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+382cd )[/B] BugCheck [B]1E, {ffffffffc0000005, ffffffffffa5cc84, 0, 12dd218}[/B] BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x0000001E"]KMODE_EXCEPTION_NOT_HANDLED (1e)[/URL] Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: ffffffffffa5cc84, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 00000000012dd218, Parameter 1 of the exception BUGCHECK_STR: 0x1E_c0000005_R PROCESS_NAME: System FAILURE_BUCKET_ID: [B]0x1E_c0000005_R_nt!_??_::FNODOBFM::_string_[/B] CPUID: "Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz" MaxSpeed: 2400 CurrentSpeed: [B]2395[/B] BIOS Version A07 BIOS Release Date 08/16/2012 Manufacturer Dell Inc. Product Name Inspiron 7720 ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` [/FONT]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

Code:

[FONT=lucida console]**************************Tue Oct 29 12:41:34.777 2013 (UTC - 4:00)************************** Apfiltr.sys Sun Feb 5 20:05:29 2012 (4F2F2759) GEARAspiWDM.sys Thu May 3 15:56:17 2012 (4FA2E2E1) HECIx64.sys Mon Jul 2 18:14:58 2012 (4FF21D62) stwrt64.sys Thu Sep 6 02:16:11 2012 (50483FAB) Rt630x64.sys Fri May 10 05:59:08 2013 (518CC4EC) vmci.sys Fri May 17 21:19:18 2013 (5196D716) LHidEqd.Sys Thu May 23 02:09:49 2013 (519DB2AD) LEqdUsb.Sys Thu May 23 02:09:50 2013 (519DB2AE) LMouFilt.Sys Thu May 23 02:09:56 2013 (519DB2B4) LHidFilt.Sys Thu May 23 02:10:00 2013 (519DB2B8) irstrtdv.sys Fri Jun 28 16:09:48 2013 (51CDED8C) IntcDAud.sys Tue Jul 2 06:31:16 2013 (51D2ABF4) RtsUVStor.sys Mon Jul 15 03:27:46 2013 (51E3A472) VMNET.SYS Thu Jul 18 15:42:50 2013 (51E8453A) vmnetadapter.sys Thu Jul 18 15:43:00 2013 (51E84544) vmnetbridge.sys Thu Jul 18 15:43:47 2013 (51E84573) iwdbus.sys Wed Jul 24 21:06:12 2013 (51F07A04) SYMEVENT64x86.SYS Fri Jul 26 22:26:58 2013 (51F32FF2) SRTSPX64.SYS Fri Jul 26 22:45:06 2013 (51F33432) Ironx64.SYS Mon Jul 29 20:59:35 2013 (51F70FF7) SYMDS64.SYS Tue Jul 30 19:29:08 2013 (51F84C44) vsock.sys Wed Jul 31 22:46:10 2013 (51F9CBF2) igdkmd64.sys Mon Aug 19 19:08:25 2013 (5212A569) nvvad64v.sys Tue Aug 20 07:29:10 2013 (52135306) EraserUtilDrv11311.sys Wed Aug 21 17:36:34 2013 (521532E2) eeCtrl64.sys Wed Aug 21 17:36:34 2013 (521532E2) intelppm.sys Thu Aug 22 04:46:35 2013 (5215CFEB) NdisVirtualBus.sys Thu Aug 22 07:36:25 2013 (5215F7B9) ahcache.sys Thu Aug 22 07:39:54 2013 (5215F88A) hiber_storport.sys Thu Aug 22 07:40:18 2013 (5215F8A2) werkernel.sys Thu Aug 22 07:40:24 2013 (5215F8A8) EX64.SYS Thu Aug 22 16:36:51 2013 (52167663) ENG64.SYS Thu Aug 22 16:38:20 2013 (521676BC) NETwew00.sys Thu Aug 22 17:20:34 2013 (521680A2) dump_iaStorA.sys Wed Aug 28 18:13:22 2013 (521E7602) hiber_iaStorA.sys Wed Aug 28 18:13:22 2013 (521E7602) iaStorA.sys Wed Aug 28 18:13:22 2013 (521E7602) SYMEFA64.SYS Sat Aug 31 00:02:36 2013 (52216ADC) intelpep.sys Thu Sep 19 03:12:46 2013 (523AA3EE) SYMNETS.SYS Mon Sep 23 22:41:10 2013 (5240FBC6) ccSetx64.sys Mon Sep 23 23:58:04 2013 (52410DCC) BHDrvx64.sys Tue Sep 24 00:07:00 2013 (52410FE4) SRTSP64.SYS Wed Sep 25 20:23:42 2013 (52437E8E) idmwfp.sys Tue Oct 1 19:17:49 2013 (524B581D) hcmon.sys Wed Oct 9 11:03:51 2013 (52557057) nvlddmkm.sys Tue Oct 15 16:27:18 2013 (525DA526) nvpciflt.sys Tue Oct 15 16:28:03 2013 (525DA553) IDSvia64.sys Wed Oct 16 18:10:26 2013 (525F0ED2) vmnetuserif.sys Fri Oct 18 14:19:38 2013 (52617BBA) vmx86.sys Fri Oct 18 15:34:39 2013 (52618D4F) [/FONT]

http://www.carrona.org/drivers/driver.php?id=Apfiltr.sys
http://www.carrona.org/drivers/driver.php?id=GEARAspiWDM.sys
http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
http://www.carrona.org/drivers/driver.php?id=stwrt64.sys
http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
http://www.carrona.org/drivers/driver.php?id=vmci.sys
http://www.carrona.org/drivers/driver.php?id=LHidEqd.Sys
http://www.carrona.org/drivers/driver.php?id=LEqdUsb.Sys
http://www.carrona.org/drivers/driver.php?id=LMouFilt.Sys
http://www.carrona.org/drivers/driver.php?id=LHidFilt.Sys
http://www.carrona.org/drivers/driver.php?id=irstrtdv.sys
http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
http://www.carrona.org/drivers/driver.php?id=RtsUVStor.sys
http://www.carrona.org/drivers/driver.php?id=VMNET.SYS
http://www.carrona.org/drivers/driver.php?id=vmnetadapter.sys
http://www.carrona.org/drivers/driver.php?id=vmnetbridge.sys
http://www.carrona.org/drivers/driver.php?id=iwdbus.sys
http://www.carrona.org/drivers/driver.php?id=SYMEVENT64x86.SYS
http://www.carrona.org/drivers/driver.php?id=SRTSPX64.SYS
http://www.carrona.org/drivers/driver.php?id=Ironx64.SYS
http://www.carrona.org/drivers/driver.php?id=SYMDS64.SYS
http://www.carrona.org/drivers/driver.php?id=vsock.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
EraserUtilDrv11311.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=eeCtrl64.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
NdisVirtualBus.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
ahcache.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
hiber_storport.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
werkernel.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=EX64.SYS
http://www.carrona.org/drivers/driver.php?id=ENG64.SYS
NETwew00.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=dump_iaStorA.sys
hiber_iaStorA.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
http://www.carrona.org/drivers/driver.php?id=SYMEFA64.SYS
intelpep.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=SYMNETS.SYS
http://www.carrona.org/drivers/driver.php?id=ccSetx64.sys
http://www.carrona.org/drivers/driver.php?id=BHDrvx64.sys
http://www.carrona.org/drivers/driver.php?id=SRTSP64.SYS
http://www.carrona.org/drivers/driver.php?id=idmwfp.sys
http://www.carrona.org/drivers/driver.php?id=hcmon.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=nvpciflt.sys
http://www.carrona.org/drivers/driver.php?id=IDSvia64.sys
http://www.carrona.org/drivers/driver.php?id=vmnetuserif.sys
http://www.carrona.org/drivers/driver.php?id=vmx86.sys

Hi,

I've removed Norton using the latest Norton Removal tool .
The screenshots that i posted were all from within 2-3 minutes of Boot. Here is a present set of screenshots :-

1) That the SSD firmware is the latest available for the SSD. I usually can't see this info in the reports, so I rely on you to check it.
2) That the storage controller drivers on the motherboard are the most recent. They must date from late 2012 or later. This is ALL controllers, not just the one that the SSD is attached to. If involved these should be visible in the memory dump - but it doesn't hurt to check manually.

How do you suggest i check if the SSD firmware and the storage controller drivers are recent or not ?

Just FYI -

1. I installed the latest drivers from Dell support page for my model and these drivers were specifically released for Windows 8.1 on 17 October 2013 . Here is the link to the driver page :-

Drivers & Downloads | Dell US

There is a latest version of BIOS released A16 , which i haven't updated yet because some users reported low FPS in Games using the Nvidia card .

2. To give you a recap , my system ran was shipped with Windows 8 and ran just fine until my last reinstallation of Windows 8 (did this just for removing Dell Blot ) , where i had a weird problem of Windows restarting when i shut it down . ( This happened once every 3-4 shutdowns ) . I did not analyse the issue and simply re-formatted my HDD to make a fresh install of Windows 8.1 ( my current installation ).

3. My system is under warranty now and whatever we figure out i can get them to replace the same .

The raw stack text shows both hal.dll and nVidia graphics drivers. I have to wonder if there is a hardware problem with the video. Try the video stress tests - but watch the system very, very carefully when doing so. It can damage your system!!!

The raw stack text means ?
hal.dll is used for ?
What would the stress test determine ? And for how long should i run it ? And what to watch the system for ? Temperature increase ? I'm very skeptic about stress test since it fried my GPU on my 1 day old HP System , so can you please kindly elaborate on how to carry it out safely ?

FYI :- I used the latest Nvidia drivers from Nvidia's site instead of using the prescribed drivers for my system by dell , if this does help in any way .

4. Will update Intel Management Engine . BTW any idea what it is used for ?

5. According to Symantec , Norton 360 v21 ( the one i was using ) was made compatible with Windows 8.1 . But seeing all the messy behaviour it showed , i doubt !

6. What would Driver verifier suggest ? And is it safe to run ?

7.3rd Party Drivers:

Is that my driver analysis or just an example ?

Is it is my driver analysis , There are no drivers in RED so nothing to update/remove right ?

sasha007 · Oct 29, 2013

usasma said:
Nothing in the Admin Event Viewer log that we didn't suspect already.
Some storage related errors that repeat (NTFS, irstrtsv, iaStor, etc errors)
So it's hard drive/SSD, the connections, or the storage controllers (motherboard is a possibility, but is much less likely as there aren't any other motherboard type issues).

If it's the SSD, then the new installation (I presume it's on the HDD and not the SSD) shouldn't have problems
If it does have problems, then it's most likely the storage controller.

Also, the Intel Management Engine gets it's little fingers in there - so it's important to update it also.

Here ,

NTFS errors suggest Disk releated transfers right ?

Regarding irstrtsv, iaStor these are for Intel rapid start and intel rapid storage technology respectively.

As i told before my SSD is an mSATA SSD used primarily for caching my 1TB hard drive .

Just in case you are not famaliar with caching with SSD , here are some resources :-

How it Works: Intel SSD Caching - Puget Custom Computers

How to Enable Caching on mSata SSD for Alienware Laptops? | Dell US

So i have enabled my SSD as a cache to my HDD to speed up the operations for which Intel rapid storage technology is used .

Also , i've used my SSD for fast resume from Hibernate by creating a hibernate partition on SSD . For this Intel rapid start is used .

So have these operations anything to do with out problem here ? How to determine if the SSD is fine ?

sasha007 · Oct 30, 2013

Hi ,

Did a fresh startup from a clean shut-down yesterday .

This time i faced some new issues . First When powered on the laptop stuck at Dell logo for about 2-3 minutes and nothing happened .

I turned my computer off and back on multiple times after this but the computer stuck at Dell logo .

Screenshot :-

Then i tried to enter BIOS and while entering the BIOS also , there was a 20-25 sec delay . I did BIOS Factory reset but in vain .

Then again powered on and waited and the system booted after remaining stuck at Dell logo for about 2 minutes .

But again Windows threw an error while i entered my password :-

Also, then again entered password and now it worked fine . But then again windows was very slow and unresponsive for about 2-3 minutes . Disk usage was 100% during this time and the screenshots of task manager and resource manager is posted in my above edited post .

Also , My Windows clock was 1 hour behind and not synchronized .

usasma · Oct 30, 2013

Raw stack text is the output of the set of instructions in memory when the crash occurred.
I use the extension commented upon here: BSOD Method and Tips - Page 3 - Sysnative Forums

hal.dll basically translates between Windows (and drivers) and the actual hardware on the system. More info here: Microsoft Windows library files - Wikipedia, the free encyclopedia

The stress test will determine if the system is working properly. If nothing goes wrong - all is well. If there are problems with the stress test, then there's a problem with the system.

If all is well, you run it until the temperatures stabilize (use a temp monitoring utility).
If all isn't well, you'll see problems/excessively high temps (over 90ºC). In that case - stop the test immediately (if you can't stop the test quick enough - just pull the plug to shut the system off). The point here is to carefully watch the system. I once had a video card that wasn't reporting correct temps - and the system started crashing/having video problems.

Link to a brief description of the Intel Management Engine: Intel® vPro™ technology — Intel® Management Engine Verification Utility frequently asked questions

Norton products are very complicated. So, when they break, they often don't show clear signs that they are broken. As such when we suspect them the "test" is to uninstall them to see if the system's performance improves.

Driver Verifier is a tool that stresses drivers. As such, it's supposed to cause BSOD's (f there is a problem). In doing so, it's designed to attempt to catch the name of the actual faulting driver - not the end result of a crash. If you follow my instructions there shouldn't be any problems. The last problem using my instructions was a system that couldn't boot to Safe Mode (this was back in the XP days). In that case we have to edit the registry while outside of Windows - so that's what that registry string at the very end of the instructions is for.

That is your driver analysis - and there aren't any outdated drivers in red - so they don't need updating.
There are other things that I mentioned, so be sure to do them.

I do not like SSD "boosters" and think that they just make things more difficult for you.
That being said, you have to run a test (such as CrystalDiskInfo) to see what's going on with it - which you have done.
I've sent a PM out to have someone take a look at the report (as I'm not well versed with this tool)
Nice links on SSD Caching! I wish that I'd had them back in the Vista days!

NTFS, irstrtsv, iaStor are all related to the storage sub-system. Trying to make them point to anything more precise isn't a good idea until we have more info confirming our suspicion(s). Right now let's just say that the problem is in the storage sub-system.

Just a thought, but can you turn off the caching (disable acceleration) in the Intel Smart Response Technology application?
Then test to see if that stops the crashing?
Disable hibernation while you're at it also.
Make sure that all of the Intel drivers are updated to Win8.1 compatible versions (to include the Intel Management Engine).
This should help to remove the SSD from the equation - and may make troubleshooting easier.

Have you changed any of the values in the UEFI? If so, please reset the values to default and reboot (to see if that helps fix things). If you still have issues with the UEFI, then I'd suggest that it's time to contact Dell for a return.

sasha007 · Oct 30, 2013

Okay .

BTW did you see my post#25 ?

Since the BIOS also took time to enter does it point to a hardware fault only ?
Any more comments after reading post #25 if you already have not ?

daglesj · Oct 30, 2013

Switch off Fastboot in the Power Options. I had the same issue with cold boots. The irony is not lost.

sasha007 · Oct 30, 2013

usasma said:
Raw stack text is the output of the set of instructions in memory when the crash occurred.
I use the extension commented upon here: BSOD Method and Tips - Page 3 - Sysnative Forums

hal.dll basically translates between Windows (and drivers) and the actual hardware on the system. More info here: Microsoft Windows library files - Wikipedia, the free encyclopedia

The stress test will determine if the system is working properly. If nothing goes wrong - all is well. If there are problems with the stress test, then there's a problem with the system.

If all is well, you run it until the temperatures stabilize (use a temp monitoring utility).
If all isn't well, you'll see problems/excessively high temps (over 90ºC). In that case - stop the test immediately (if you can't stop the test quick enough - just pull the plug to shut the system off). The point here is to carefully watch the system. I once had a video card that wasn't reporting correct temps - and the system started crashing/having video problems.

Link to a brief description of the Intel Management Engine: Intel® vPro™ technology — Intel® Management Engine Verification Utility frequently asked questions

Norton products are very complicated. So, when they break, they often don't show clear signs that they are broken. As such when we suspect them the "test" is to uninstall them to see if the system's performance improves.

Driver Verifier is a tool that stresses drivers. As such, it's supposed to cause BSOD's (f there is a problem). In doing so, it's designed to attempt to catch the name of the actual faulting driver - not the end result of a crash. If you follow my instructions there shouldn't be any problems. The last problem using my instructions was a system that couldn't boot to Safe Mode (this was back in the XP days). In that case we have to edit the registry while outside of Windows - so that's what that registry string at the very end of the instructions is for.

That is your driver analysis - and there aren't any outdated drivers in red - so they don't need updating.
There are other things that I mentioned, so be sure to do them.

I do not like SSD "boosters" and think that they just make things more difficult for you.
That being said, you have to run a test (such as CrystalDiskInfo) to see what's going on with it - which you have done.
I've sent a PM out to have someone take a look at the report (as I'm not well versed with this tool)
Nice links on SSD Caching! I wish that I'd had them back in the Vista days!

NTFS, irstrtsv, iaStor are all related to the storage sub-system. Trying to make them point to anything more precise isn't a good idea until we have more info confirming our suspicion(s). Right now let's just say that the problem is in the storage sub-system.

Just a thought, but can you turn off the caching (disable acceleration) in the Intel Smart Response Technology application?
Then test to see if that stops the crashing?
Disable hibernation while you're at it also.
Make sure that all of the Intel drivers are updated to Win8.1 compatible versions (to include the Intel Management Engine).
This should help to remove the SSD from the equation - and may make troubleshooting easier.

Have you changed any of the values in the UEFI? If so, please reset the values to default and reboot (to see if that helps fix things). If you still have issues with the UEFI, then I'd suggest that it's time to contact Dell for a return.

Hi,

1. I've re-formatted my system and made a fresh installation of Windows 8.1 . Then I've just installed the chipset drivers , video/Audio , Touch pad , Quick settings and card reader drivers . Not installed Intel smart response and intel rapid storage . So My SSD is not being used now .

On software part , just installed chrome and dropbox .

Seeing some error in the event log .

Link :- https://www.dropbox.com/s/2pcgc341yd4bp2e/Event Viewer 30-10-2013.zip

Can you please study them ?

2. Also , while running SF Diagnostic Tool , I'm receiving the following errors :-

Code:

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.


************** Exception Text **************
System.IO.FileNotFoundException: Could not find file 'C:\Windows\EventApp.txt'.
File name: 'C:\Windows\EventApp.txt'
   at Microsoft.VisualBasic.FileIO.FileSystem.CopyOrMoveFile(CopyOrMove operation, String sourceFileName, String destinationFileName, Boolean overwrite, UIOptionInternal showUI, UICancelOption onUserCancel)
   at Microsoft.VisualBasic.FileIO.FileSystem.CopyFile(String sourceFileName, String destinationFileName, UIOption showUI, UICancelOption onUserCancel)
   at Microsoft.VisualBasic.MyServices.FileSystemProxy.CopyFile(String sourceFileName, String destinationFileName, UIOption showUI, UICancelOption onUserCancel)
   at SF_Diagnostic_Tool.Form1.Button4_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)




************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.7905 (win9rel.050727-7900)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
SF Diagnostic Tool
    Assembly Version: 5.0.0.6
    Win32 Version: 5.0.0.6
    CodeBase: file:///C:/Users/Sasha/Desktop/SF_Diagnostic_Tool.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.7905 (win9rel.050727-7900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.7905 (win9rel.050727-7900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.7905 (win9rel.050727-7900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.7905 (win9rel.050727-7900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.7905 (win9rel.050727-7900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------


************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.


For example:


<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>


When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.


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


See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.


************** Exception Text **************
System.IO.FileNotFoundException: Could not find file 'C:\Windows\DriverList.txt'.
File name: 'C:\Windows\DriverList.txt'
   at Microsoft.VisualBasic.FileIO.FileSystem.CopyOrMoveFile(CopyOrMove operation, String sourceFileName, String destinationFileName, Boolean overwrite, UIOptionInternal showUI, UICancelOption onUserCancel)
   at Microsoft.VisualBasic.FileIO.FileSystem.CopyFile(String sourceFileName, String destinationFileName, UIOption showUI, UICancelOption onUserCancel)
   at Microsoft.VisualBasic.MyServices.FileSystemProxy.CopyFile(String sourceFileName, String destinationFileName, UIOption showUI, UICancelOption onUserCancel)
   at SF_Diagnostic_Tool.Form1.Button7_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)




************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.7905 (win9rel.050727-7900)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
SF Diagnostic Tool
    Assembly Version: 5.0.0.6
    Win32 Version: 5.0.0.6
    CodeBase: file:///C:/Users/Sasha/Desktop/SF_Diagnostic_Tool.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.7905 (win9rel.050727-7900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.7905 (win9rel.050727-7900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.7905 (win9rel.050727-7900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.7905 (win9rel.050727-7900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.7905 (win9rel.050727-7900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------


************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.


For example:


<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>


When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Why am i getting these errors ?

I'm trying to dump all logs with it but getting error .

OldMX · Oct 30, 2013

sasha007, after reading all the thread, i think your cache SSD is incompatible with your laptop :\ Can you remove it or disable for testing purposes?

sasha007 · Oct 30, 2013

OldMX said:
sasha007, after reading all the thread, i think your cache SSD is incompatible with your laptop :\ Can you remove it or disable for testing purposes?

I've disabled caching with SSD for now . Will monitor . BTW System shipped with SSD and it ran fine until now .

usasma · Oct 31, 2013

1. All the errors (with the exception of the 2 SF Diagnostic Tool errors) are fixed later on in the logfile.

2. The issues with the SF Diagnostic Tool are best addressed with the author - Captain Jack (I don't see him here, but you may be able to contact him over at Seven Forums). I suspect that his response will be that you have to install everything and fully update the system - which may interfere with our troubleshooting.

Don't worry about the reports for now.
I only use the systeminfo.txt and the MSINFO32.nfo logs when we first start
I only use the Admin Event Log stuff when I request it - there's no need to supply it until (if) I ask for it again.
After that, I only use the memory dumps.

I agree with daglesi - Turn off FastBoot - I've seen issues with it in previous versions of Windows

Then I'd agree with OldMX - there's an issue with your SSD and it's most likely compatibility (with 8.1 - not with 8) or a defect.
I would contact Dell for resolution. They may be able to assist in specific issues relating to 8.1 (or may be able to replace the SSD)

Good luck!

daglesj · Oct 31, 2013

Ahem.......Fastboot! I'm quite surprised this hasnt been flagged more. When I had this issue searching didnt turn up much at all. The fact that Restarts were fine but Cold boots were taking 13+ minutes led me to think it might be a hibernation type thing. So as my motherboard was 2009 spec I figured something new (and by the sound of it not very well tested) was screwing with it. Fastboot seemed the most likely culprit and it was.

sasha007 · Oct 31, 2013

daglesj said:
Ahem.......Fastboot! I'm quite surprised this hasnt been flagged more. When I had this issue searching didnt turn up much at all. The fact that Restarts were fine but Cold boots were taking 13+ minutes led me to think it might be a hibernation type thing. So as my motherboard was 2009 spec I figured something new (and by the sound of it not very well tested) was screwing with it. Fastboot seemed the most likely culprit and it was.

I hear you !

Disabled Fast boot but still the issue

sasha007 · Oct 31, 2013

usasma said:
1. All the errors (with the exception of the 2 SF Diagnostic Tool errors) are fixed later on in the logfile.

2. The issues with the SF Diagnostic Tool are best addressed with the author - Captain Jack (I don't see him here, but you may be able to contact him over at Seven Forums). I suspect that his response will be that you have to install everything and fully update the system - which may interfere with our troubleshooting.

Don't worry about the reports for now.
I only use the systeminfo.txt and the MSINFO32.nfo logs when we first start
I only use the Admin Event Log stuff when I request it - there's no need to supply it until (if) I ask for it again.
After that, I only use the memory dumps.

I agree with daglesi - Turn off FastBoot - I've seen issues with it in previous versions of Windows

Then I'd agree with OldMX - there's an issue with your SSD and it's most likely compatibility (with 8.1 - not with 8) or a defect.
I would contact Dell for resolution. They may be able to assist in specific issues relating to 8.1 (or may be able to replace the SSD)

Good luck!

I'm contacting Dell now .

BTW they told me to download and run an application called PC doctor and it reported that the hard disk is bad and needs to be replaced .

Is that in line with our findings ?

daglesj · Oct 31, 2013

Have you got an old mechanical HDD you can slot in and put the build on with? If thats all okay then it narrows down and confirms the drive is the suspect. Time for a RMA. By the way as an alternative I can recommend the newer Seagate 500GB SSHD hybrid drives. They work a treat and good value.

sasha007 · Oct 31, 2013

daglesj said:
Have you got an old mechanical HDD you can slot in and put the build on with? If thats all okay then it narrows down and confirms the drive is the suspect. Time for a RMA. By the way as an alternative I can recommend the newer Seagate 500GB SSHD hybrid drives. They work a treat and good value.

I'm under warranty so Dell would replace it with 1TB 5400RPM drive only i guess !

usasma · Oct 31, 2013

Let Dell send you a new HDD and try it. It may fix things or it may not. But that is the path you have to follow in order to work with Dell Support.

As for FastBoot - that is technically a "workaround". We use it when, for some reason, the system is not compatible with it. It is NOT a fix. And, quite frankly, I forget to consider it quite often. Thanks for reminding me!

Sent fm my phone

sasha007 · Oct 31, 2013

usasma said:
Let Dell send you a new HDD and try it. It may fix things or it may not. But that is the path you have to follow in order to work with Dell Support.

As for FastBoot - that is technically a "workaround". We use it when, for some reason, the system is not compatible with it. It is NOT a fix. And, quite frankly, I forget to consider it quite often. Thanks for reminding me!

Sent fm my phone

Hi usasma ,

Just again ran the Dell Pre diagnostic before boot , and this time it threw an error :-

So apparently the problem is with the HDD . What do you say ?

daglesj · Oct 31, 2013

usasma said:
As for FastBoot - that is technically a "workaround". We use it when, for some reason, the system is not compatible with it. It is NOT a fix. And, quite frankly, I forget to consider it quite often. Thanks for reminding me!

Ahhh the term I would use is 'not fit for purpose'. But no one likes testing stuff these days. Especially on tech more than 12 months old.

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

Mr. Cranky Pants

My Computer

Mr. Cranky Pants

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

Mr. Cranky Pants

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

Member

My Computer

New Member

My Computer

Mr. Cranky Pants

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

Mr. Cranky Pants

My Computer

New Member

My Computer

New Member

My Computer