Welcome to our peer-to-peer forums, where owners help owners. Need help now? Visit eSupport here.

English Community

ThinkPad NotebooksThinkPad: X Series Laptops
All Forum Topics
Options

40 Posts

11-28-2011

usa

41 Signins

165 Page Views

  • Posts: 40
  • Registered: ‎11-28-2011
  • Location: usa
  • Views: 165
  • Message 1 of 6

X!20E "Critical" error in MMC "Diagnostics-Performance" Boot: Diags : atapi miniport?

2015-09-29, 12:26 PM

Friends I love my old X120E and I am a tech - I use it for all sorts of strange issues, carry it with me on appointments etc.

Windows 10 is a bust so far:  I'm disappointed at the lousy performance so keeping it forever a Windows 7 system.

 

I use a Samsung Pro SSD.  Recently, due to something that changed it has become consistently slow on bootup, both cold start & restart.  Looking in the Windows MMC at the Operational Diagnostics-Performance I get Critical errors on every startup; time logged required vs. the MS established acceptable norm.  These routines are supposed to root-cause the issue but I am not seeing a clear identity of the culprit.  Need help from the group

 

Log Name:      Microsoft-Windows-Diagnostics-Performance/Operational
Source:        Microsoft-Windows-Diagnostics-Performance
Date:          9/29/2015 7:06:43 AM
Event ID:      100
Task Category: Boot Performance Monitoring
Level:         Critical
Keywords:      Event Log
User:          LOCAL SERVICE
Computer:      Shire-X
Description:
Windows has started up:
     Boot Duration        :    113499ms
     IsDegradation        :    false
     Incident Time (UTC)    :    ‎2015‎-‎09‎-‎29T12:04:15.890000700Z
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Diagnostics-Performance" Guid="{CFC18EC0-96B1-4EBA-961B-622CAEE05B0A}" />
    <EventID>100</EventID>
    <Version>2</Version>
    <Level>1</Level>
    <Task>4002</Task>
    <Opcode>34</Opcode>
    <Keywords>0x8000000000010000</Keywords>
    <TimeCreated SystemTime="2015-09-29T12:06:43.526450100Z" />
    <EventRecordID>2854</EventRecordID>
    <Correlation ActivityID="{03112C48-F800-0001-2857-66F6AEFAD001}" />
    <Execution ProcessID="1388" ThreadID="2148" />
    <Channel>Microsoft-Windows-Diagnostics-Performance/Operational</Channel>
    <Computer>Shire-X</Computer>
    <Security UserID="S-1-5-19" />
  </System>
  <EventData>
    <Data Name="BootTsVersion">2</Data>
    <Data Name="BootStartTime">2015-09-29T12:04:15.890000700Z</Data>
    <Data Name="BootEndTime">2015-09-29T12:06:42.261377700Z</Data>
    <Data Name="SystemBootInstance">367</Data>
    <Data Name="UserBootInstance">360</Data>
    <Data Name="BootTime">113499</Data>
    <Data Name="MainPathBootTime">30699</Data>
    <Data Name="BootKernelInitTime">40</Data>
    <Data Name="BootDriverInitTime">681</Data>
    <Data Name="BootDevicesInitTime">371</Data>
    <Data Name="BootPrefetchInitTime">0</Data>
    <Data Name="BootPrefetchBytes">0</Data>
    <Data Name="BootAutoChkTime">0</Data>
    <Data Name="BootSmssInitTime">8130</Data>
    <Data Name="BootCriticalServicesInitTime">1088</Data>
    <Data Name="BootUserProfileProcessingTime">16413</Data>
    <Data Name="BootMachineProfileProcessingTime">209</Data>
    <Data Name="BootExplorerInitTime">2440</Data>
    <Data Name="BootNumStartupApps">4</Data>
    <Data Name="BootPostBootTime">82800</Data>
    <Data Name="BootIsRebootAfterInstall">false</Data>
    <Data Name="BootRootCauseStepImprovementBits">0</Data>
    <Data Name="BootRootCauseGradualImprovementBits">1024</Data>
    <Data Name="BootRootCauseStepDegradationBits">0</Data>
    <Data Name="BootRootCauseGradualDegradationBits">0</Data>
    <Data Name="BootIsDegradation">false</Data>
    <Data Name="BootIsStepDegradation">false</Data>
    <Data Name="BootIsGradualDegradation">false</Data>
    <Data Name="BootImprovementDelta">0</Data>
    <Data Name="BootDegradationDelta">0</Data>
    <Data Name="BootIsRootCauseIdentified">true</Data>
    <Data Name="OSLoaderDuration">1437</Data>
    <Data Name="BootPNPInitStartTimeMS">40</Data>
    <Data Name="BootPNPInitDuration">411</Data>
    <Data Name="OtherKernelInitDuration">541</Data>
    <Data Name="SystemPNPInitStartTimeMS">935</Data>
    <Data Name="SystemPNPInitDuration">641</Data>
    <Data Name="SessionInitStartTimeMS">1594</Data>
    <Data Name="Session0InitDuration">5827</Data>
    <Data Name="Session1InitDuration">397</Data>
    <Data Name="SessionInitOtherDuration">1904</Data>
    <Data Name="WinLogonStartTimeMS">9724</Data>
    <Data Name="OtherLogonInitActivityDuration">1912</Data>
    <Data Name="UserLogonWaitDuration">5769</Data>
  </EventData>
</Event>

 

Reply
Options

2032 Posts

11-28-2007

Czech Republic

12108 Signins

124962 Page Views

  • Posts: 2032
  • Registered: ‎11-28-2007
  • Location: Czech Republic
  • Views: 124962
  • Message 2 of 6

Re: X!20E "Critical" error in MMC "Diagnostics-Performance" Boot: Diags : atapi

2015-09-29, 14:39 PM

Are you sure it is Samsung Pro SSD ? Samsung 840 Evo has known performance degradation issues.

__________________________________
ThinkPad (1992 - 2012): R51, X31, X220, Tablet 8.
Reply
Options

40 Posts

11-28-2011

usa

41 Signins

165 Page Views

  • Posts: 40
  • Registered: ‎11-28-2011
  • Location: usa
  • Views: 165
  • Message 3 of 6

Re: X!20E "Critical" error in MMC "Diagnostics-Performance" Boot: Diags : atapi

2015-09-29, 16:52 PM

"840 Pro"

the issue is not the speed of the disk, it appears to be related to the MS miniport driver but I cannot prove that since the RootCause routine appears to fail.  or I don't know how to find.  In some of the past instances [this happens on every bootup] I would get alongside the "Critical" a "Warning" related to the atapi.sys driver, which is MS issue.

 

this belongs in another thread, but it is fairly well known that the ATI SATA driver set is terrible.   in the worst case, installing the ATI SATA device drivers results in background traffic that will keep the CPU at 10%+ utilization no matter what else is going on.  At best, the benchmarking of the SSD will clearly show a huge degradation regardless of what drive it is, compared to just the plain ancient Microsoft Standard AHCI device driver.  everybody that is tech inclined and likes[otherwise] the amd APU families sees this.  obviously the diff is covered up in A10 or A8-based systems because there is a lot of spare CPU to muscle over the difficulties.  bottom line is that if one uses the AMD SATA drivers, you suffer a big performance hit.

All that has nothing to do with this issue.  this bootup issue is a more obscure than just disk performance

 

Shutdown and return-from-standby are also consistently out off bounds but a lot less annoying that the startup lag. Example below:

 

Log Name:      Microsoft-Windows-Diagnostics-Performance/Operational
Source:        Microsoft-Windows-Diagnostics-Performance
Date:          9/29/2015 10:14:47 AM
Event ID:      300
Task Category: Standby Performance Monitoring
Level:         Warning
Keywords:      Event Log
User:          LOCAL SERVICE
Computer:      Shire-X
Description:
Windows has resumed from standby:
     Standby Duration        :    3327ms
     Standby Incident Time (UTC)    :    ‎2015‎-‎09‎-‎29T13:23:46.447226100Z
     Resume  Duration        :    1502ms
     Resume  Incident Time (UTC)    :    ‎2015‎-‎09‎-‎29T15:14:36.820865900Z
     IsDegradation            :    false
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Diagnostics-Performance" Guid="{CFC18EC0-96B1-4EBA-961B-622CAEE05B0A}" />
    <EventID>300</EventID>
    <Version>1</Version>
    <Level>3</Level>
    <Task>4003</Task>
    <Opcode>36</Opcode>
    <Keywords>0x8000000000010000</Keywords>
    <TimeCreated SystemTime="2015-09-29T15:14:47.097213300Z" />
    <EventRecordID>2856</EventRecordID>
    <Correlation ActivityID="{03112C40-F800-0000-2A57-66F6AEFAD001}" />
    <Execution ProcessID="1388" ThreadID="3048" />
    <Channel>Microsoft-Windows-Diagnostics-Performance/Operational</Channel>
    <Computer>Shire-X</Computer>
    <Security UserID="S-1-5-19" />
  </System>
  <EventData>
    <Data Name="StandbyTsVersion">1</Data>
    <Data Name="StandbyAppCount">17</Data>
    <Data Name="StandbyServicesCount">17</Data>
    <Data Name="StandbyDevicesCount">146</Data>
    <Data Name="StandbyStartTime">2015-09-29T13:23:46.447226100Z</Data>
    <Data Name="StandbyEndTime">2015-09-29T13:23:49.774226100Z</Data>
    <Data Name="StandbySuspendTotal">3327</Data>
    <Data Name="StandbySuspendTotalChange">0</Data>
    <Data Name="StandbySuspendQueryApps">0</Data>
    <Data Name="StandbySuspendQueryAppsChange">0</Data>
    <Data Name="StandbySuspendQueryServices">0</Data>
    <Data Name="StandbySuspendQueryServicesChange">0</Data>
    <Data Name="StandbySuspendApps">2188</Data>
    <Data Name="StandbySuspendAppsChange">0</Data>
    <Data Name="StandbySuspendServices">31</Data>
    <Data Name="StandbySuspendServicesChange">0</Data>
    <Data Name="StandbySuspendShowUI">0</Data>
    <Data Name="StandbySuspendShowUIChange">0</Data>
    <Data Name="StandbySuspendSuperfetchPageIn">9</Data>
    <Data Name="StandbySuspendSuperfetchPageInChange">0</Data>
    <Data Name="StandbySuspendWinlogon">385</Data>
    <Data Name="StandbySuspendWinlogonChange">0</Data>
    <Data Name="StandbySuspendLockPageableSections">0</Data>
    <Data Name="StandbySuspendLockPageableSectionsChange">0</Data>
    <Data Name="StandbySuspendPreSleepCallbacks">0</Data>
    <Data Name="StandbySuspendPreSleepCallbacksChange">0</Data>
    <Data Name="StandbySuspendSwapInWorkerThreads">1</Data>
    <Data Name="StandbySuspendSwapInWorkerThreadsChange">0</Data>
    <Data Name="StandbySuspendQueryDevices">1</Data>
    <Data Name="StandbySuspendQueryDevicesChange">0</Data>
    <Data Name="StandbySuspendFlushVolumes">18</Data>
    <Data Name="StandbySuspendFlushVolumesChange">0</Data>
    <Data Name="StandbySuspendSuspendDevices">689</Data>
    <Data Name="StandbySuspendSuspendDevicesChange">0</Data>
    <Data Name="StandbySuspendHibernateWrite">0</Data>
    <Data Name="StandbySuspendHibernateWriteChange">0</Data>
    <Data Name="ResumeStartTime">2015-09-29T15:14:36.820865900Z</Data>
    <Data Name="ResumeEndTime">2015-09-29T15:14:37.565459000Z</Data>
    <Data Name="StandbyResumeTotal">1502</Data>
    <Data Name="StandbyResumeTotalChange">0</Data>
    <Data Name="StandbyResumeHibernateRead">0</Data>
    <Data Name="StandbyResumeHibernateReadChange">0</Data>
    <Data Name="StandbyResumeS3BiosInitTime">758</Data>
    <Data Name="StandbyResumeS3BiosInitTimeChange">0</Data>
    <Data Name="StandbyResumeResumeDevices">744</Data>
    <Data Name="StandbyResumeResumeDevicesChange">0</Data>
    <Data Name="StandbyRootCauseDegradationGradual">0</Data>
    <Data Name="StandbyRootCauseImprovementGradual">0</Data>
    <Data Name="StandbyRootCauseDegradationStep">0</Data>
    <Data Name="StandbyRootCauseImprovementStep">0</Data>
    <Data Name="StandbyIsDegradation">false</Data>
    <Data Name="StandbyIsTroubleshooterLaunched">true</Data>
    <Data Name="StandbyIsRootCauseIdentified">false</Data>
  </EventData>
</Event>.

 

 

Reply
Options

9644 Posts

12-27-2009

Canada

3313 Signins

95283 Page Views

  • Posts: 9644
  • Registered: ‎12-27-2009
  • Location: Canada
  • Views: 95283
  • Message 4 of 6

Re: X!20E "Critical" error in MMC "Diagnostics-Performance" Boot: Diags : atapi

2015-09-30, 22:06 PM
Did you make any changes to startup settings for any services recently?

W520: 2960XM, Q2000M @ 1091/1380, 32GB RAM, 500GB&750GB HDD & 500GB SSD, FHD&MB168B+
X61T: L7500, 4GB RAM, 500GB HDD, XGA screen, Ultrabase
W550s: 5600U, K620M at 1164/1281, 16GB RAM, 512GB SSD, 3K touchscreen
X200s: SL9400, 6GB RAM, 64GB SD card, WXGA+ screen
TPT1: 1839-23U
Reply
Options

40 Posts

11-28-2011

usa

41 Signins

165 Page Views

  • Posts: 40
  • Registered: ‎11-28-2011
  • Location: usa
  • Views: 165
  • Message 5 of 6

Re: X!20E "Critical" error in MMC "Diagnostics-Performance" Boot: Diags : atapi

2015-10-07, 12:48 PM

still not resolved.  

no I did not make any changes that would afflict it.

I turn off absolutely every startup Item except the bare essentials

I have pretty good windows skills but this one is just infuriating.  in the past the system would boot in about 25 seconds - not world-shaking but pretty good for such a weak little system.  Now it runs 80 seconds or so.

 

verifier bails quickly with bsod and no minidump.  i'm going to work it a bit more and see if I can get a crash dump with it and analyze that.

 

the shutdown process also exceeds threshold but I'm less concerned about it, and I get no real root cause info either way [though it is working the rootcause process].

 

the good news:  it is FAR WORSE under Windows 10.  I have every device configured "correctly" in Windows 10 and the bootup time is nearly 2 minutes.  Looking at the Diags/Performance log is just a sea of red errors and Criticals and yellow splashes of warnings.

 

of course [back to windows 7]:  in safe mode it boots very fast. doesn't really add anything toward a fix.

I used msconfig to disble half the services, reboot, measure.  then disable the other half and re-enable the first half. that step was suggested by a MS expert.  no help.  it boots slowly, populates a string of errors of course related to teh services not starting and the dependency-damage from that.   pointless.

 

If I could get good data from verifier I think I could find the offending device/s but so far, it is not capturing useful info.

 

it goes without saying, there is nothing remarkable in Device Manager. everything looks healthy.  there are no errors [amazingly] in the windows Error logs under "System".  lots of info, the occasional warning, nothing odd or new

Reply
Options

9644 Posts

12-27-2009

Canada

3313 Signins

95283 Page Views

  • Posts: 9644
  • Registered: ‎12-27-2009
  • Location: Canada
  • Views: 95283
  • Message 6 of 6

Re: X!20E "Critical" error in MMC "Diagnostics-Performance" Boot: Diags : atapi

2015-10-08, 14:48 PM
I'm not the greatest at picking apart a boot trace myself, maybe try the MSFN forums:
http://www.msfn.org/board/topic/140247-trace-windows-7-bootshutdownhibernatestandbyresume-issues/

I don't recall having issues with my X100e and the AMD SATA driver, but that was years ago.

W520: 2960XM, Q2000M @ 1091/1380, 32GB RAM, 500GB&750GB HDD & 500GB SSD, FHD&MB168B+
X61T: L7500, 4GB RAM, 500GB HDD, XGA screen, Ultrabase
W550s: 5600U, K620M at 1164/1281, 16GB RAM, 512GB SSD, 3K touchscreen
X200s: SL9400, 6GB RAM, 64GB SD card, WXGA+ screen
TPT1: 1839-23U
Reply
Forum Home

Community Guidelines

Please review our Guidelines before posting.

Learn More

Check out current deals!

Go Shop
X

Save

X

Delete

X

No, I don’t want to share ideas Yes, I agree to these terms