MagicAndre1981

I think the Intel® Management Engine Interface and the nVIDIA card use both the same IRQ (16) and this may cause the high interrupt issue in the function DpiFdoLineInterruptRoutine from the driver dxgkrnl.sys. Can you change the IRQs in the BIOS?

your link is for the 100MBit. I think your card should be a 1GBit card: http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false

the trace shows that one of the latest SetValue calls is this: My last idea is to create a new user profile and if it works there, run the Windows Easy Transfer program to migrate the user data and settings to the new account.

can you make a xperf tarce and uplaod the Ziped ETL file?

the Windows hangs while saving registry keys. Now I don't have the knowledge to see which key. But you can run a new xbootmgr trace and add +REGISTRY after POWER to trace registry access. But I don't know if this works for XP

For your Realtek PCIe FE Family Controller go to http://www.realtek.com.tw/downloads/ and download the drivers. For your Dell DW1501 Wireless-N WLAN Half-Mini Card go to Dell and get the latest driver from there.

I can't see anything from it Was it taken at the point you see the hang? Wait what cluberti writes. In the meantime use msconfig (clean boot) to stop loading all 3rd party tools (killing the processes still leaves the loaded drivers on the system) and see if this helps because you use really old drivers: BANTExt.sys Thu May 28 04:43:29 1998 sorry that I can't help more :'(

try to generate a Memory dump of the entire system when it hangs at shutdown: compress it with 7zip (7z file with ULTRA compression). Maybe we can see what causes this __report_gsfailure issue.

it is still the same __report_gsfailure issue. stop all 3rd party software and try again.

1 thing. the thread which causes the high cpu usage is __report_gsfailure. This looks like NX Bit, buffer overflow issues. try to eliminate all 3rd party applications.

when do you get the 25% cpu usage? try to run xperf at the time you get it.

it doesn't changed anything. stop the search service and the other tools and look if it is fixed.

Hi Dave, I got the trace and I can see that the winlogon.exe causes a high CPU usage for a long time. I see that the function HvpFindFreeCellInThisViewWindow is the cause. Before that starts, a symantec driver (Norton Unerase Protection) is loaded. Stop the tool and try again. Also check if it happens if you disable your Trend Micro (maybe a virus update definition from July 17th causes the issue). If this doesn't work stop the Windows Search service and check if it solves it. Maybe the index is corrupt, so try to reindex. Also what is this Rapport Management Service? André

is it allowed to redistribute the files outside the SDK/WPT setup?

Which issue do you currently have? Do you have audio glitches in TeamSpeek? The current tarce says everything is fine. The highest spikes are 128 - 256µs (which is fine) and the DPC CPU usage is 5%.

strange, but nice to hear that it works.

you can try to use Universal Extractor to extract the MSI file on the XP system to get the tool working. Use here the x86 MSI.

tell us more about your hardware (which motherboard do you use?).

Nice to hear that it worked. If you only loose 1 day it is ok to do a system restore.

I looked at the trace and saw many UNKNOWN entries: CPU 0 Usage, CPU 1 Usage, CPU 2 Usage, CPU 3 Usage, 1892904 3.53, 1897061 3.54, 2006537 3.74, 1893732 3.53, "Unknown" this shows that a driver uses dynamically generated code. In your case it is the SPTD driver which installs with tools like Daemon Tools. So, run the SPTD driver setup and remove the driver. Now make a new trace to see if an other driver causes the issues.

Do you have a vista/7 installation? if yes, install xbootmgr there and copy the files to the XP system and run there the shutdown trace command: http://www.msfn.org/board/index.php?showtopic=140247 and upload the shutdown_BASE+CSWITCH+DRIVERS+POWER_1.etl (the processing of the ETL with xperf (Summary.XML) and the viewer don't work on XP)

make a new trace which captures the 100% CPU usage with those commands: xperf -start perf!GeneralProfiles.InBuffer NOW Run the programs which cause the cpu usage xperf -stop perf!GeneralProfiles.InBuffer 100CPUUsage.etl zip and upload the 100CPUUsage.etl.

do a system-restore to restore the Windows to the point before you installed that software.

the taskmgr (updating the data, drawing the graphs) and the DWM periodically causes a lot of cpu usage. You can see this in the 'CPU usage per Process' graph. Your driver for the NVIDIA GeForce 9400M G is very old: 7.15.11.7962 (2009.02.28) So update the driver, please: http://www.nvidia.com/object/notebook-win7-winvista-64bit-275.50-beta-driver.html http://www.nvidia.com/object/notebook-win7-winvista-64bit-275.33-whql-driver.html now check if the new driver fixed it.