MagicAndre1981

try to disable the Microsoft ACPI-compliant Control Method Battery in device manager and look if this fixes it.

what is new in this version?

this is the ACPI.sys usage. This is hard to debug. Do you use a laptop?

I don't use Hyper-V so I've never seen this.

NEVER do this!

I prefer TreeSizeFree to see the sizes of folders/files: http://www.jam-software.com/treesize_free/

I also told him this, he wants to do this himself with strange tools. I respect this and no longer tell him to use a proper ISO.

nice to hear this and thank for the wishes for today. I also hope we can beat Bayern

the CPU usage comes from Network operation. I often see IPHLPAPI.DLL involved. Try to stop the IP Helper Service (transfers IPv6 over IPv4). If you don't need this, stop the service and look what happens.

yeah the MULTIPLE_IRP_COMPLETE_REQUESTS BSOD comes from symantec. The other is a memory corruption wile overwriting the free memory with Zeros so that it can be used again: ******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************PFN_LIST_CORRUPT (4e)Typically caused by drivers passing bad memory descriptor lists (ie: callingMmUnlockPages twice with the same list, etc). If a kernel debugger isavailable get the stack trace.Arguments:Arg1: 0000008f, The free or zeroed page listhead is corruptArg2: 0008679f, new pageArg3: 000763ff, old pageArg4: 00000000, 0Debugging Details:------------------BUGCHECK_STR: 0x4E_8fCUSTOMER_CRASH_COUNT: 1STACK_TEXT: nt!KeBugCheckExnt!MmZeroPageThreadnt!Phase1Initializationnt!PspSystemThreadStartupnt!KiThreadStartupSTACK_COMMAND: kbFOLLOWUP_IP: nt!MmZeroPageThread+13080528529 cc int 3SYMBOL_STACK_INDEX: 1IMAGE_NAME: memory_corruptionFAILURE_BUCKET_ID: 0x4E_8f_nt!MmZeroPageThread+130Are the RAM timings fine?

thanks for pointing to the Update.

run this command after boot and minimize the cmd.exe, started as admin: xperf -on latency -stackwalk profile -buffersize 1024 -MaxFile 512 -FileMode Circular && timeout -1 && xperf -d C:\temp\HoheCPUAuslastung.etl when you have the issue, wait 30s and press a key in the cmd.exe to stop logging. compress the ETL als 7z/RAR and share it. This command limites the size to 500 MBs and forgets the useless data so that the file doesn't grow too much.

share the dumps, maybe we can see anything useful.

ok, you mean the website . I wrote a while that berlios.de will be closed. Maybe this happens today

post a picture of RAMMap which shows how much and which memory mapped files you have. http://technet.microsoft.com/en-us/sysinternals/ff700229.aspx

the trace is corrupted. I see nothing useful. Don't use the ugly UI, use my xperf command! Also please compress the ETL file pelase as 7z/RAR to reduce the size!!!!!!!!!!!!!!!!!!!!

ok, let us know if disabling the turbo mode fixed it.

run CPU-Z and make sure the SPD timings and the values from the Memory tab are the same: http://www.cpuid.com/softwares/cpu-z.html

remove Symantec and look if this fies it. I see a high usage from IDSvia64.sys.

you have driver verifier enabled, this causes the bad DPC usage: Disable the Verifier. Why have you enabled it? Do you get BSODs?

Enumerating the IDE channels causes the PreSMSS and running autochk.exe (chkdsk) the SMSSInit dealay.

have you done a RAM test? ******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffe00115f7a028, Address of the WHEA_ERROR_RECORD structure.Arg3: 00000000f2000000, High order 32-bits of the MCi_STATUS value.Arg4: 000000000020008f, Low order 32-bits of the MCi_STATUS value.Debugging Details:------------------BUGCHECK_STR: 0x124_GenuineIntelCUSTOMER_CRASH_COUNT: 1DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULTPROCESS_NAME: SystemCURRENT_IRQL: fANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64freSTACK_TEXT: nt!KeBugCheckExhal!HalBugCheckSystemnt!WheaReportHwErrorhal!HalpMcaReportErrorhal!HalpMceHandlerCorehal!HalpMceHandlerhal!HalpMceHandlerWithRendezvoushal!HalHandleMchecknt!KxMcheckAbortnt!KiMcheckAbortintelppm!C1HaltMODULE_NAME: GenuineIntel0x124_GenuineIntel_MEMORY__UNKNOWN===============================================================================Common Platform Error Record @ ffffe00115f7a028-------------------------------------------------------------------------------Record Id : 01cf6b7c5e2e7be4Severity : Fatal (1)Length : 873Creator : MicrosoftNotify Type : Machine Check ExceptionTimestamp : 5/10/2014 4:38:51 (UTC)Flags : 0x00000000===============================================================================Section 0 : Memory-------------------------------------------------------------------------------Descriptor @ ffffe00115f7a0a8Section @ ffffe00115f7a180Offset : 344Length : 73Flags : 0x00000001 PrimarySeverity : Fatal===============================================================================Section 1 : Processor Generic-------------------------------------------------------------------------------Descriptor @ ffffe00115f7a0f0Section @ ffffe00115f7a1c9Offset : 417Length : 192Flags : 0x00000000Severity : FatalProc. Type : x86/x64Instr. Set : x64Error Type : Unknown errorFlags : 0x00CPU Version : 0x00000000000106e5Processor ID : 0x0000000000000000===============================================================================Section 2 : x86/x64 MCA-------------------------------------------------------------------------------Descriptor @ ffffe00115f7a138Section @ ffffe00115f7a289Offset : 609Length : 264Flags : 0x00000000Severity : FatalError : Unknown (Proc 0 Bank 8) Status : 0xf20000000020008f

upload the ETl file

this time the crash happens while doing pool allocations (driver memory): ******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DRIVER_CORRUPTED_EXPOOL (c5)An attempt was made to access a pageable (or completely invalid) address at aninterrupt request level (IRQL) that is too high. This iscaused by drivers that have corrupted the system pool. Run the driververifier against any new (or suspect) drivers, and if that doesn't turn upthe culprit, then use gflags to enable special pool.Arguments:Arg1: fffffadd991b37a8, memory referencedArg2: 0000000000000002, IRQLArg3: 0000000000000001, value 0 = read operation, 1 = write operationArg4: fffff800011a9b28, address which referenced memoryDebugging Details:------------------BUGCHECK_STR: 0xC5_2CURRENT_IRQL: 2FAULTING_IP: nt!ExAllocatePoolWithTag+c74fffff800`011a9b28 48897008 mov qword ptr [rax+8],rsiCUSTOMER_CRASH_COUNT: 2DEFAULT_BUCKET_ID: DRIVER_FAULTPROCESS_NAME: realplay.exeSTACK_TEXT: 00 nt!KeBugCheckEx01 nt!KiBugCheckDispatch02 nt!KiPageFault03 nt!ExAllocatePoolWithTag04 nt!ObpAllocateObject05 nt!ObCreateObject06 nt!IopParseDevice07 nt!ObpLookupObjectName08 nt!ObOpenObjectByName09 nt!IopCreateFile0a nt!CcPfGetSectionObject0b nt!CcPfPrefetchSections0c nt!CcPfPrefetchScenario0d nt!CcPfBeginAppLaunch0e nt!PspUserThreadStartup0f nt!KiStartUserThread10 nt!KiStartUserThreadReturn11 0x0SYMBOL_NAME: nt!ExAllocatePoolWithTag+c74FAILURE_BUCKET_ID: X64_0xC5_2_nt!ExAllocatePoolWithTag+c74BUCKET_ID: X64_0xC5_2_nt!ExAllocatePoolWithTag+c74run the driver verifier to get new and better dumps: http://support.microsoft.com/kb/244617 The RAM timings are ok. You can also try to increase the RAM voltage a BIT to 1.825V.