MagicAndre1981

thanks. I tried the x86 version, but this version doesn't work: Crash.log: Writing crash log... DWMGlass: 0x74ACAD49: d:\projekty\aeroglass\mydwm-dx11\dwmhook\iatfunctions.h (22:0), function: myWndProc d2d1: 0x74614462: ?

I missed this set id. Is this important? The rest is the same as I did. I'll try it again this evening.

ataport.SYS!AtaPortReadPortUchar is causing the high ISR usage. Run your HDDs in AHCI mode instead of IDE to fix this.

ok, I found the cause. The generated VHD from the Powershell script is MBR style, but you need GPT. So I created a VHD, converted it to GPT and used DISM to apply the WIM into the VHD. Now I can select the VHD, I can see the text "Starting Windows" but it freezes here. What's this? What do I miss now?

I saw this in the callstack of the CPU sampling summary table.

I can't see see if you have a hang or not (not with the public version we have). I only saw a lot of DiskIO (caused by the syncs) at the end of the trace. So I think you stopped the trace after having the hangs.

boot is ok (10s to UI and fully booted in 16s). Before you stopped the trace I see a high disk IO on the WD drive (skydrive syncs data on drive O:). Office also syncs data and MSE scans the data. this seams to be too much stress for the WD green. I hate WD green drives because they cause hangs. reduce the IO activity for the WD green drive and also disable the Power saving for the HDD.

I have a question. Does this native Boot works with UEFI? I want to boot a Win7 Ultimate on a Win8 Laptop which uses UEFI (secure boot off). I converted the Win7 WIM with the Convert-WindowsImage.ps1 script, added it to the bootmenu but when I select the Win7 VHD, nothing happens and wIn7 doesn't boot.

update the BIOS to 5206 and try to use the GPU in the 2nd PCIe x16 slot (no matter what is written in the manual). if you don't play games, you can also remvoe the 9800 completely and use the HD7540d which is included in the AMD CPU.

you should check the PC for malware when IE reconnects to you somewhere else. To see what is wrong with the updates, we need the folder C:\Logs\CBS, the files C:\Windows\WindowsUpdate.log, C:\Windows\inf\setupapi.dev.log and "C:\Windows\winsxs\poqexec.log". Copy them to your desktop, zip the files and upload the zip (skydrive, dropbox) and post a link here.

still the same. Try to plug the card into a different PCIe slot and make sure all offloading settings are enabled in the driver options.

great Now you learned how to read the data and next time you can analyze it yourself

is it now better with driver verifier disabled?

now you only have 4 spikes: update the Intel® Gigabit CT Desktop Adapter drivers.

you have DPC issues: Total = 3164 for module iaStor.sys Elapsed Time, > 512 usecs AND <= 1024 usecs, 1005, or 31.76% Elapsed Time, > 1024 usecs AND <= 2048 usecs, 25, or 0.79% Total, 3164 Total = 23 for module netbt.sys Elapsed Time, > 2048 usecs AND <= 4096 usecs, 4, or 17.39% Elapsed Time, > 4096 usecs AND <= 8192 usecs, 17, or 73.91% Elapsed Time, > 8192 usecs AND <= 16384 usecs, 1, or 4.35% Total, 23 Total = 423 for module tcpip.sys Elapsed Time, > 512 usecs AND <= 1024 usecs, 220, or 52.01% Elapsed Time, > 1024 usecs AND <= 2048 usecs, 34, or 8.04% Total, 423 udate the Intel AHCI, Realtek and Broadcom network drivers. I can also see this call: ntkrnlmp.exe!VerifierExAllocatePoolEx this means you have driver verifier enabled. Didi you get several BSODs? Did you enable the verifier for better dumps? Please disable driver verifier and reboot. Your PC should be faster without DriverVerifer.

upload the zipped ETL file. I look what is wrong

I see it in the ETL file.

yes, run a new trace without OC.

he needs the 32Bit drivers. The 64Bit would be netr28x.sys

By default Windows should use the fastBoot if you simply click shutdown. When you use 3rd party tools, you must make sure they support the new FastStartUp. The Firewall and Windows Defender cause a high CPU usage during boot.. Try a different Firewall/AV suite.

Update the netr28.sys. This driver causes the spikes. This is your RAlink network driver. Update to the latest version 5.0.21.0.

great, that you found the cause

go to the UEFI/BIOS and look for OC settings.

I posted the fastBoot command at the end of the 1st post.

upload it to skydrive, dropbox and send me the link via PM.