MagicAndre1981

no, Hitachi HTS547575A9E384 is your hard drive. You must update the Intel Storage driver. Go to the homepage of your laptop creator, download the latest drivers and install them.

Hi, as you can see in the picture the iastor.sys causes 16% of the CPU usage. This driver belongs to the Intel storage driver. You use version 10.1.2.1004. Is this the latest version? If not, update the driver. If this is the latest driver, use the version before this driver. If the issue still occurs, check your Hitachi HDD for errors (run chkdsk C: /r /f) and run a diagnostic tool from Hitachi. André

yes, now start vLite again and do this for all Editions.

with Vista MS moved the sound drivers in usermode. So not all drivers were updated (especially Creative has a terrible driver support). So it can be that the drivers don't work so good like the old ones from XP.

don't select to rebuild the image at at end. this keeps all editions.

Hi, your Windows takes 75s to boot to the desktop and 89s to boot completely. PrepSystem worked, the ReadyBoot prefetcher is fine. The WinlogonInit phase takes most time. I looked at the XMl and saw that the profile loading takes 32seconds. I looked at the ETL and sow that you're part of a domain. Do you use a roaming profile? How large is the profile? Try to elimiate this delay, this the part which slows down the boot most. also the driver SRTSP takes 2.6s prePendTime. I thin the driver belongs to Symantec. <pnpObject name="SRTSP" type="Driver" activity="Load" startTime="4499" endTime="7140" duration="2641" prePendTime="2641" /> Is version 10.3.3.4 the latest? Try to update the software. André

I wrote an email to somebody who should know more. I post here if I get a reply.

yes, you can do it again.

Vista and Win7 updates are language neutral, you can install them on all languages.

ok, so try a different powerplan and if this doesn't solve it, uninstall MSE and try a different free AV software.

CRITICAL_OBJECT_TERMINATION (f4) A process or thread crucial to system operation has unexpectedly exited or been terminated. Several processes and threads are necessary for the operation of the system; when they are terminated (for any reason), the system can no longer function. Arguments: Arg1: 00000003, Process Arg2: 8ad8a690, Terminating object Arg3: 8ad8a804, Process image file name Arg4: 805d2970, Explanatory message (ascii) PROCESS_NAME: csrss.exe EXCEPTION_RECORD: aca3d9d8 -- (.exr 0xffffffffaca3d9d8) ExceptionAddress: 75b7b3b9 ExceptionCode: c0000006 (In-page I/O error) ExceptionFlags: 00000000 NumberParameters: 3 Parameter[0]: 00000008 Parameter[1]: 75b7b3b9 Parameter[2]: c000009a Inpage operation failed at 75b7b3b9, due to I/O error c000009a EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - Die Anweisung bei "0x%p" verwies auf Speicher bei "0x%p". Die erforderlichen Daten wurden aufgrund eines E/A-Fehlers in "0x%x" nicht an den Arbeitsspeicher bertragen. CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT ERROR_CODE: (NTSTATUS) 0xc0000006 - Die Anweisung bei "0x%p" verwies auf Speicher bei "0x%p". Die erforderlichen Daten wurden aufgrund eines E/A-Fehlers in "0x%x" nicht an den Arbeitsspeicher bertragen. EXCEPTION_PARAMETER1: 00000008 EXCEPTION_PARAMETER2: 75b7b3b9 EXCEPTION_PARAMETER3: c000009a IO_ERROR: (NTSTATUS) 0xc000009a - Nicht ausreichend Systemressourcen, um die API abzuschlie en. EXCEPTION_STR: 0xc0000006_c000009a FAULTING_IP: +0 75b7b3b9 ?? ??? BUGCHECK_STR: 0xF4_IOERR_C000009A STACK_TEXT: aca3d520 805d1ab9 000000f4 00000003 8ad8a690 nt!KeBugCheckEx+0x1b aca3d544 805d2a1b 805d2970 8ad8a690 8ad8a804 nt!PspCatchCriticalBreak+0x75 aca3d574 8054161c 8ad8a8d8 c0000006 aca3d9b0 nt!NtTerminateProcess+0x7d aca3d574 80501151 8ad8a8d8 c0000006 aca3d9b0 nt!KiFastCallEntry+0xfc aca3d5f4 804fe806 ffffffff c0000006 aca3d9f8 nt!ZwTerminateProcess+0x11 aca3d9b0 805028bf aca3d9d8 00000000 aca3dd64 nt!KiDispatchException+0x3a0 aca3dd34 80544ee7 00c8fbe8 00c8fc08 00000000 nt!KiRaiseException+0x175 aca3dd50 8054161c 00c8fbe8 00c8fc08 00000000 nt!NtRaiseException+0x33 aca3dd50 75b7b3b9 00c8fbe8 00c8fc08 00000000 nt!KiFastCallEntry+0xfc WARNING: Frame IP not in any known module. Following frames may be wrong. 00c8fff4 00000000 00000000 00000000 00000000 0x75b7b3b9 STACK_COMMAND: kb FOLLOWUP_IP: +0 75b7b3b9 ?? ??? FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware_disk FAILURE_BUCKET_ID: 0xF4_IOERR_C000009A_IMAGE_hardware_disk BUCKET_ID: 0xF4_IOERR_C000009A_IMAGE_hardware_disk So the data can't be read from disc because the kernel memory reached the limit and so the kernel is out of memory: EXCEPTION_PARAMETER3: c000009a // // MessageId: STATUS_INSUFFICIENT_RESOURCES // // MessageText: // // Insufficient system resources exist to complete the API. // #define STATUS_INSUFFICIENT_RESOURCES ((NTSTATUS)0xC000009AL) Configure your Windows to "Enable pool tagging": http://support.microsoft.com/kb/177415 and configure your Windows to generate a kernel dump: http://support.microsoft.com/kb/316450 if you get the next crash, zip the file C:\Windows\Memory.dmp and upload the zip.

Microsoft Security Essentials is permanently causing 40% CPU usage. Because MS doesn't offer debug files for MSE I can't see which function from MSE causes the high CPU usage. So remove MSe and try other tools like Avira AntiVir or Avast. 1 other thing I can see is that the Interrupts cause some CPU usage. The Hal.dll is the cause. This is DLL for the hardware abstraction layer. Which power plan do you use? Also update the BIOS if possible.

do a normal boot trace and look at the ReadyBoot graph. If it shows much black, run it. If it is mostly green/orange Readyboot is already fully trained.

point a directory (not a single MSU) to DISM /Add-package and DISM installs all updates from that place

Which Windows? Till XP use 3rd aprty tools. Starting with Windows Vista use the included tool for best performance.

no chance. the only way to reduce the size is to uninstall old superseeded updates and unneeded MUI packs.

I'm also using MPC-HC

ok, nice to hear this So my guess was right.

run a xperf trace: and upload the ZIPPED etl to mediafire.com and post a link here.

you can delete the ETL files. Run xbootmgr -remove to stop logging. Maybe it traces every boot doe to an error. 2) this is by design. MS wants to run it without admin rights (change in Version 4.8, the version 4.6 doesn't have this limitation).

what is the file extension? xperf writes to the data into an ETL file. please download the program TreeSizeFree and run it. It shows you which folders use all the space. Now try to delete or move less important data to free some space.

Hi barley, you're welcome If you have other questions feel free to ask in the XP subforum André

from the trace I can see that the WinLogin takes too long and the RequestCredentials (entering the password takes the longest time). The trace you gave me was from a clean boot, correct?

@JCook zip the ETL file and uplaod the zip to mediafire.com and put the link here. I look at it later.

the dump to XML and xperfview don't work on XP. I can't really see why it is slow. I can only see thatthe caching for the HDDs is disabled. So check this and enable it again and see if this makes a difference.