MagicAndre1981

the trace you gave me doesn't show the high CPU usage. Your 80 is idle for 80%. But I can see that you use ProcessHacker. Inside the tool click on Hacker->Options->advanced and uncheck the option "enable cycle based CPU usage". Now restart ProcessHacker. Do you still have the high CPU usage reported?

this time it is again the nVIDIA driver with 2 small spikes: do you have an audio or video glitches caused by DPCs?

But the CPU still remains at over 60% all the time, I don't know what's the average but I was told that 60% is very much having opened only Firefox, Chrome, a small editor and Explorer the trace you gave me doesn't show the CPu usage. you must capture the trace at the time you have the issue

make a new boottrace.

the updates are included in Win7 Sp1, but WU is stupid and wants to install all those RTM updates first. That's why you should always install Win7 with an ISO which has Sp1 included or download the Sp1 from downloadcenter and install it your own without using WU.

Startup Menu and Orb Powered by Rainmeter http://exper1mental.deviantart.com/art/Startup-Menu-and-Orb-Powered-by-Rainmeter-341889726

ok. Please reply here when you get the new Mobo and tell us if it is fixed or not.

the values are ok now: only 1 spike between 256 and 512µs. So removing battery fixed it.

much better now: this activity comes from World of Warcraft. Do you have any issues? it looks ok, now.

smss.exe runs so long because autochk runs during boot (smss:BootExecute)

you can start a new topic here in the Win8 section. Is it based on the old tool "TrueTransparency"?

the trace shows autochk runs at this time. Delete the autochk entry from BootExecute in the registry and run chkdsk yourself.

the PSu is fine. Change the PCIe slot of the GPU. Does this help? Also look in the BIOS/UEFI if you have an option High Precision Event Timer (HPET). Change it's state and look if this fixes anything.

it is the same APCI issue again. ry to switch to the powerplan "High Perfomance". this disables the power saving options. Does this fix the issue?

I also have no idea, because I've never seen this.

remove the SSD from the PC/laptop. Is it now fast again? if yes, the SSD is mabe broken. Buy a newer one like the Samsung 830 with 128GB so that you can install Win + Programs on it.

Have you talked to the ASRock support? Do they have an idea?

@both make new traces and upload them.

compress the ETL file, upload it to SkyDrive or Dropbox and send me the link.

@Furyclaw we posted the same time. The new tarce shows you have high CPU usgae caused by he ACPI driver. ACPI.sys!OSNotifyDeviceWake looks like Windows has issues to enable devices after they were send to sleep. so disable the powersaving options in device manager for all devices.

have you tried to connect the SSD to a different SATA port on the motherboard? Does this solve it?

it works fine for me. copy and paste the complete command into the command prompt

ok, starting your both SSDs takes extremely long: - <phase name="bootStart" startTime="38" endTime="398449" duration="398411"> <pnpObject name="IDE\DiskSanDisk_SSD_i100_32GB___________________11.50.00\5+2ed543ff+0+1.0.0" type="Device" activity="Start" startTime="2841" endTime="283250" duration="280409" prePendTime="280409" description="Disk drive" friendlyName="SanDisk SSD i100 32GB ATA Device" /> <pnpObject name="IDE\DiskSanDisk_SSD_i100_32GB___________________11.50.00\5+2ed543ff+0+1.0.0" type="Device" activity="Enum" startTime="283250" endTime="323310" duration="40060" prePendTime="40060" description="Disk drive" friendlyName="SanDisk SSD i100 32GB ATA Device" /> the first one takes 283s and the second one 40s! This causes the long PreSMSS time of nearly 400s!!!!!!: <interval name="PreSMSS" startTime="0" endTime="398863" duration="398863"> next, the session init takes also over 160s: <interval name="SMSSInit" startTime="398863" endTime="559569" duration="160706"> and this is caused by a long registry init time: fix the SSD issue by installing the latest AHCI drivers and test again.

make a new tarce, this timw when using AHCI. I can't really use the trace because it misses several events Increasing the buffer can help. Please run this: xperf -on latency -stackwalk profile -buffersize 2048 -MaxFile 256 -FileMode Circular && timeout -1 && xperf -d DPC_Interrupt.etl

starting the SATA HACI driver takes 2 minutes: <phase name="bootStart" startTime="10" endTime="124885" duration="124875"> <pnpObject name="PCI\VEN_8086+DEV_1E02+SUBSYS_1E021849+REV_04\3+11583659+0+FA" type="Device" activity="Start" startTime="3412" endTime="123781" duration="120368" prePendTime="120368" description="Intel(R) 7 Series/C216 Chipset Family SATA AHCI Controller" friendlyName="" /> prePendTime = driver issue. So updaet the Intel AHCI drivers.