Jump to content

MagicAndre1981

Patron
 View Profile  See their activity

  • Posts

    6,232

  • Joined

  • Last visited

  • Donations

    0.00 USD 

  • Country

    United Kingdom

 Content Type 

Everything posted by MagicAndre1981

  1. MagicAndre1981
    Checking for changes in the folder C:\Users\olei\AppData\Local\Microsoft\Windows\Burn takes 39s. Have you started (and not finished) a new DVD with the internal burning tool? 18:06:00,0231255 Explorer.EXE 00:00:34.7338565 39.2838022 1940 NotifyChangeDirectory C:\Users\olei\AppData\Local\Microsoft\Windows\Burn SUCCESS Filter: FILE_NOTIFY_CHANGE_FILE_NAME, FILE_NOTIFY_CHANGE_ATTRIBUTES, FILE_NOTIFY_CHANGE_LAST_WRITE Also 1 VMWare service takes 5s: 18:05:52,9318306 vmware-usbarbitrator.exe 00:00:27.6425616 4.8712852 1604 NotifyChangeDirectory C:\Windows\SysWOW64\config\systemprofile\AppData\Roaming\VMware NOTIFY ENUM DIR Filter: FILE_NOTIFY_CHANGE_FILE_NAME, FILE_NOTIFY_CHANGE_SIZE, FILE_NOTIFY_CHANGE_LAST_WRITE, FILE_NOTIFY_CHANGE_CREATION I start the VMWare services with a batch file when I need them and set the to start on demand.
  2. MagicAndre1981
    use a path withput _ and try again. If it still fails, run Process Monitor from Sysinternals, enable boot logging in ProcMon and reboot. After the boot is finished, run ProcMon again and save the trace as PML file. Compress it to 7z (ULTRA, LZMA2) and upload it.
  3. MagicAndre1981
    Install the hotfixes from here: and try again. Also post the error message. I'm German so I can read the message
  4. MagicAndre1981
    Happy Birthday puntoMX
  5. MagicAndre1981
    don't use vLite any longer. Use this: to safely remove functions you don't need.
  6. MagicAndre1981
    Happy Birthday Tripredacus
  7. MagicAndre1981
    why? You don't get DirectX11 and also Windows 2000 doesn't use the CPU cores that efficient compared to NT6.x systems.
  8. MagicAndre1981
    // // MessageId: STATUS_DLL_NOT_FOUND // // MessageText: // // The program can't start because %hs is missing from your computer. Try reinstalling the program to fix this problem. // #define STATUS_DLL_NOT_FOUND ((NTSTATUS)0xC0000135L) // winnt Repair Windows with your CD. Boot from it and select Repair install.
  9. MagicAndre1981
    You can zip and upload the new trace and I take a short look at it. The Windows Search service causes some longer durations: try to disable the Search service and try again.
  10. MagicAndre1981
    ok, I only see that the service was running so I thought it was set to automatic. I highlighted Avast in the first trace. Look how long Avast takes this time to start.
  11. MagicAndre1981
    the dump is damaged. So check the HDD for SMART data failures.
  12. MagicAndre1981
    automatic. This is already done on your system.
  13. MagicAndre1981
    Run the xboot comand in C:\Temp where you stored the data. ProcMon is easy. Configure it to log the data into a file (not the pagefile), start the logging, next run the xbootmgr command. After you resumed, run ProcMon again and stop the logging. Now look at the duration column what takes so long. For me it was reading the MFT and hibernationfile, so I defragged the $MFT and the hibernation file and the issue was gone. I only saw this with ProcMon. the XML told be a driver was slow to resume, but it was the HDD.
  14. MagicAndre1981
    Happy Birthday FIZBAN2.
  15. MagicAndre1981
    Your boot prefetcher (ReadyBoot) is completely broken and doesn't work the way the prefetcher should. This casues the HDD to be busy all the time: Install the hotfixes from here: http://www.msfn.org/board/index.php?showtopic=152622 and optimize the Prefetcher: http://www.msfn.org/board/index.php?showtopic=140262 That's how Hybrid sleep works. If something happens during standby Windows doesn't loose data it resumes from the hibernation file. this is the complete command: to get the overview XML: xperf -i standby_BASE+CSWITCH+DRIVERS+POWER_1.etl -o summary_standby.xml -a suspend This time the following USb device takes 5s to wake up and resume: - <resumedevices start="163018123" duration="5922378"> - <device start="163582798" duration="4157050" name="USB\VID_04A9&PID_107F\101HJL"> From what I see this is USB Printing Support. So try to disconnect your Canon Inkjet i860 before resuming Windows and it takes 11s to read the hibernation file: hiberread="11470000" But I can't see why it takes so long before you forced the reboot. Here you must run Process Monitor, start the logging and next run the xbootmgr command to start tracing and this don't reboot. Wait several minutes. I had an issue with my PC where hibernation takes 10minutes to resume. Which the ProcMon log I was able to solve it.
  16. MagicAndre1981
    can you upload the dmp files so that we can see in detail what happens?
  17. MagicAndre1981
    compress the etl file with 7Zip to a 7z archive and upload the 7z file. I'm German so I can read it
  18. MagicAndre1981
    The resume of the nVIDIA driver takes 3 seconds which is a bit long. Try the 285.27 instead of the 280.26. It seams you use the Hybrid Sleep which write the data also in the hiberfile.sys. And reading the data takes 7.4s to read the data.
  19. MagicAndre1981
    you must set the name of the connection as you see it the network sharing center
  20. MagicAndre1981
    follow my guide and make a boot trace: zip and upload the trace.
  21. MagicAndre1981
    ok, get this download from my SkyDrive, extract it and run the Run Job.cmd https://skydrive.live.com/self.aspx/.Public/msfn/Hibernate%5E_performance%5E_assessment.7z?cid=128fc518635be2dc&sc=documents This runs the hibernation traces. After the tool is finished, zip and upload all result files.
  22. MagicAndre1981
    please make a xperf trace and upload the trace.
  23. MagicAndre1981
    I think you miss a part of the command: admin=disabled
  24. MagicAndre1981
    as I already posted the CUSTUM version includes Sp1 files: GDR: amd64_microsoft-windows-d..nese-eacommonapijpn_31bf3856ad364e35_6.0.6001.18671_none_edc7a2f288b90c67.manifest LDR: amd64_microsoft-windows-d..nese-eacommonapijpn_31bf3856ad364e35_6.0.6001.22947_none_ee77b509a1b8eab6.manifest So the update applies to Sp1 systems, too. But Vista Sp1/Server 2008 are out of support starting with 12th July. And this means, no newer updates are released for this unsupported Windows versions. That's why I'm confused.
  25. MagicAndre1981
    ok. This may happen.
×
×
  • Create New...