Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations


Everything posted by MagicAndre1981

  1. ok, the modified memory comes directly from the game Marvel Heroes 2015.
  2. also close as many applications (Chrome) as possible before runing the game
  3. the dxdiag output shows me what I already told you. the AMD GPU uses 768MB from the 4GB system RAM.
  4. the memory usage comes from a large "modified" list. Run this command to capture more memory data: xperf -on ReferenceSet -stackwalk VirtualAlloc+VirtualFree -BufferSize 2048 -MaxFile 2048 -FileMode Circular && timeout -1 && xperf -d C:\MemUsage.etl
  5. post a link to the specs of the laptop and post reports of diag tools like AIDA64 or HWiNFO.
  6. nice to see that you were able to register here. I checked the file and the disk IO comes from accessing the pagefile (F:\pagefile.sys). Windows seems to have low free RAM (you only have 4GB RAM and the GPU seems to use 768MB so Windows has one 3.25GB to use, which is low for a 64Bit Windows) and writes data to the pagefile (ntoskrnl.exe!MiModifiedPageWriter, ntoskrnl.exe!MiGatherPagefilePages): I see you run Chrome when playing the game. Chrome is a RAM "waster". So close it and other useless programs like TuneUp before playing the game.
  7. this is called libraries since Windows 7
  8. yeah, I also suggest a scheduled task which starts at logon with a delay of 1 or 2 minutes.
  9. so, first the enumeration of IDE devices takes over 5s: - <phase name="bootStart" startTime="17" endTime="5113" duration="5096"> <pnpObject name="PCIIDE\IDEChannel\4+bff9540+0+0" type="Device" activity="Enum" startTime="223" endTime="2730" duration="2507" prePendTime="0" description="IDE Channel" friendlyName="ATA Channel 0" /> <pnpObject name="PCIIDE\IDEChannel\4+bff9540+0+1" type="Device" activity="Enum" startTime="223" endTime="2730" duration="2507" prePendTime="0" description="IDE Channel" friendlyName="ATA Channel 1" /> But the longest delay is the WinLogonInit phase: <interval name="WinlogonInit" startTime="8880" endTime="37095" duration="28215">Here I can see that restoring the network connections is slow: This is the main cause of the boot delay. Only connect the network drives on demand with net use X: \\server\share /persistent:no
  10. WIMBOOT has issues (http://www.msfn.org/board/topic/173786-whats-up-with-the-bevy-of-optional-windows-81-updates/?p=1098319) and they remove it again in Windows 10.
  11. WIMBOOT Systems are the cause. Microsoft runs into servicing issues with WIMBOOT (reason why it gets removed in Win10): https://technet.microsoft.com/en-us/library/dn594399.aspx And the large updates don't supersede each other all time, so disk usage grows and DISM can't cleanup WinSxS. With smaller updates, the chances are higher that newer fixes replace older ones, so that DISM can remove them to keep Windows smaller. Btw, update KB3022345 (Update to enable the Diagnostics Tracking Service in Windows 8.1 and Windows Server 2012 R2 ) fails to install on NON en-US Windows versions. Microsoft forgot to add MUI files for other languages.
  12. report it into the ProcessHacker forum. Have you tried the code from SVN?
  13. run this cmd file as admin (right click and select "run as admin") in the path where you extracted the archive: http://www.glass8.eu/out/schedule.bat
  14. ok, thanks for the feedback. This is always a good idea. I sue this tool to remove older drivers completely: http://www.wagnardmobile.com/DDU/ddudownload.htm
  15. I think Microsoft will try to force users to 8.1 to minimize the support for the old Windows 8.
  16. create a dmp file (procdump), open it in windbg and run !analyze -v to see which DLL is not found.
  17. yes, I noticed this and hided them in WindowsUpdate.
  18. it was now merged directly into the program. Get the code from Subversion (svn://svn.code.sf.net/p/processhacker/code/) and compile your own version.
  19. dmex coded a plugin for ProcessHacker to show which driver is used by WUDFHost.exe in the tooltip: http://processhacker.sourceforge.net/forums/viewtopic.php?t=1590&p=5334#p5334
  20. Windows 10: death of the Aero engine http://winaero.com/blog/windows-10-death-of-the-aero-engine/
  21. think what you want, but those 2 updates only upgrade to Win10. The Compatibility updates only update some Compatibility DLLs in Windows and this is NOT dangerous in any way *facepalm*
  22. I've enabled the Insider app on my Phone and hoped I only get the 8.1 GDR2 (http://www.neowin.net/news/heres-how-to-get-windows-phone-81-update-2-on-some-lumias), but I was only offered the TP which I can't deny. I made the ugrade to Win10 and it was pure horror. All apps, settings crash or hang. Nothing worked and the UI was slow as hell. Now I used the Recovery tool to go back to Windows Phone 8.1. I hope that I can get the GDR2 later and can skip Win10.
  23. only KB3035583 and KB2990214 are dangerous. The others are ok.
  24. your HDD is busy during boot. This is the bootleneck. It's time for a SSD.

  • Create New...