MagicAndre1981

the digital signature is broken. Install xperf from the Visual Studio Toolkit.

check the RAM with memtest86+ and the HDD with chkdsk C: /r /f

to diagnostic such non genuine messages, please run the Microsoft Genuine Diagnostics Tool (MGADiag). Inside the tool click "Copy" and paste the output here.

the Sp1 symbols are on the symbol server. You don't need the offline installer.: srv*C:\Windows\symbols*http://msdl.microsoft.com/download/symbols; the 7-Zip tool tells you how much RAM is needed to compress the file. Select a dictionary with 32MB. This uses 1GB to compress the data. So 1GB is left in the address space of 7-zip.

yes, wait for the crash and upload it, so that cluberti can look at the dump

The "World Police" USA can't do steps if the servers are outside the USA. but the leak of internal tools inside the last ISOs is a bit critical because those builds are FBL (feature build lab) builds and no WinMain builds.

try it. if you have other issues, you can remove the hotfix again.

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: 0000000000000003, Process Arg2: fffffa80055f2b30, Terminating object Arg3: fffffa80055f2e10, Process image file name Arg4: fffff80002f96db0, Explanatory message (ascii) the dump only shows this: fffff800`02f96db0 "Terminating critical process 0x%" fffff800`02f96dd0 "p (%s)." fffffa80`055f2e10 "csrss.exe" the csrss.exe was terminated and this caused the bug check: fffff880`027f50e8 fffff800`0301b982 nt!KeBugCheckEx fffff880`027f50f0 fffff800`02fc90ab nt!PspCatchCriticalBreak+0x92 fffff880`027f5130 fffff800`02f4c698 nt! ?? ::NNGAKEGL::`string'+0x17ad6 fffff880`027f5180 fffff800`02c928d3 nt!NtTerminateProcess+0xf4 fffff880`027f5200 fffff800`02c8ee70 nt!KiSystemServiceCopyEnd+0x13 fffff880`027f5398 fffff800`02cdf11f nt!KiServiceLinkage fffff880`027f53a0 fffff800`02c92cc2 nt! ?? ::FNODOBFM::`string'+0x49974 fffff880`027f5a40 fffff800`02c9183a nt!KiExceptionDispatch+0xc2 fffff880`027f5c20 00000000`76fc8e3d nt!KiPageFault+0x23a 00000000`00d609a0 00000000`00000000 0x76fc8e3d 3: kd> !process fffffa80055f2b30 3 GetPointerFromAddress: unable to read from fffff80002ec4000 PROCESS fffffa80055f2b30 SessionId: none Cid: 0198 Peb: 7fffffd7000 ParentCid: 0190 DirBase: 9ee49000 ObjectTable: fffff8a0073ab0e0 HandleCount: <Data Not Accessible> Image: csrss.exe VadRoot fffffa8005231170 Vads 89 Clone 0 Private 463. Modified 311. Locked 0. DeviceMap fffff8a000006090 Token fffff8a001600550 ReadMemory error: Cannot get nt!KeMaximumIncrement value. fffff78000000000: Unable to get shared data ElapsedTime 00:00:00.000 UserTime 00:00:00.000 KernelTime 00:00:00.000 QuotaPoolUsage[PagedPool] 0 QuotaPoolUsage[NonPagedPool] 0 Working Set Sizes (now,min,max) (1139, 50, 345) (4556KB, 200KB, 1380KB) PeakWorkingSetSize 1139 VirtualSize 45 Mb PeakVirtualSize 46 Mb PageFaultCount 1586 MemoryPriority BACKGROUND BasePriority 13 CommitCharge 589 *** Error in reading nt!_ETHREAD @ fffffa800523f6d0 if the RAM is ok, run sfc /Scannow maybe the exe is damaged on the HDD. Best would be to provide a full dump. Zip it with 7z (LZMA2 - ULTRA compression to compress the dmp extremely) and upload it to mediafire.com

0x124 = Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR - This bug check indicates that a fatal hardware error has occurred. ------------------------------------------------------------------------------- Record Id : 01cc0367a248bc04 Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 4/25/2011 22:25:33 Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ fffffa8004c5a0a8 Section @ fffffa8004c5a180 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : Cache error Operation : Data Read Flags : 0x00 Level : 1 CPU Version : 0x0000000000100f42 Processor ID : 0x0000000000000002 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ fffffa8004c5a0f0 Section @ fffffa8004c5a240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000002 CPU Id : 42 0f 10 00 00 08 04 02 - 09 20 80 00 ff fb 8b 17 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 Proc. Info 0 @ fffffa8004c5a240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ fffffa8004c5a138 Section @ fffffa8004c5a2c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : DCACHEL1_DRD_ERR (Proc 2 Bank 0) you have a Cache Error: AMD Phenom II X4 B50 Processor looks like you unlocked some CPU Cores which maybe damaged. So undo this unlock and go back to X2 and check if your PC is stable again.

Win7 Sp1 or RTM?

which nVIDIA card and which driver do you use?

this is only the temp file, so xperf can't use it. run xperf -merge standby_BASE+CSWITCH+DRIVERS+POWER_1_km_premerge.etl standby_BASE+CSWITCH+DRIVERS+POWER_1_um_premerge.etl standby_BASE+CSWITCH+DRIVERS+POWER_1.etl the merge both files. Are you now able to open the merged file?

but includes interesting stuff. I can't wait to see the beta on connect.

don't limit the size. Compress it with 7z (LZMA2 - ultra). This reduces the size a lot.

next time write the name of the tool

it takes 365s to access the the NTFS USN Journal folder C:\$Extend\$UsnJrnl:$J so it is again a HDD issue.

ok, nice to hear this. it maybe the USB HDD. Does it happen if you unplug the HDD?

try this: http://pacmani.deviantart.com/art/HideBlur-Tool-for-Windows-7-137636666

try it out. Create a system restore point first.

use the drivers from Fernando: http://www.win-lite.de/wbb/board195-windows-7/board198-win7-treiber/3857-win7-treiber-speziell-f%C3%BCr-die-integration/

the dump is damaged, I can't read the data: Kernel Complete Dump File: Full address space is available ************************************************************ WARNING: Dump file has been truncated. Data may be missing. Unable to read KLDR_DATA_TABLE_ENTRY at 8b3b33a0 - Win32 error 0n38 GetContextState failed, 0x80070026 0: kd> !vm *** Virtual Memory Usage *** Physical Memory: 783871 ( 3135484 Kb) 00000000: Unable to get page file 00000000: Unable to get paged pool info unable to get nt!MmTotalFreeSystemPtes unable to get nt!MmTotalPagesForPagingFile unable to get nt!MiSpecialPagesNonPaged unable to get nt!MiSpecialPagesNonPagedMaximum Error reading free nonpaged PTEs 00000004 unable to get nt!MmSpecialPagesInUse Available Pages: 666391 ( 2665564 Kb) ResAvail Pages: 695793 ( 2783172 Kb) Locked IO Pages: 0 ( 0 Kb) Free System PTEs: 0 ( 0 Kb) ********** Running out of system PTEs ************** Free NP PTEs: 0 ( 0 Kb) Free Special NP: 0 ( 0 Kb) Modified Pages: 4353 ( 17412 Kb) Modified PF Pages: 0 ( 0 Kb) 80564d20: Unable to get pool descriptor NonPagedPool Usage: 0 ( 0 Kb) NonPagedPool Max: 65536 ( 262144 Kb) PagedPool Usage: 0 ( 0 Kb) PagedPool Maximum: 92160 ( 368640 Kb) Unable to get Session WsListEntry Session Commit: 0 ( 0 Kb) Shared Commit: 2278 ( 9112 Kb) Special Pool: 0 ( 0 Kb) Shared Process: 2202 ( 8808 Kb) PagedPool Commit: 10330 ( 41320 Kb) Driver Commit: 4535 ( 18140 Kb) Committed pages: 61417 ( 245668 Kb) Commit limit: 755565 ( 3022260 Kb) ProcessCommitUsage could not be calculated so I can't see the process memory usage of the svchost.exe. Do you really only have 768MB RAM? Try to upgrade the RAM.

8 minutes? Autocheck runs 60s.Does it happen all time or only sometimes?

which PCI IDE devices (HDD, DVD ROM/Burner) do you still use?

I have no idea what causes your other hard drive issues. The driver is used by ISO mounting tools, no burning tools.

those are the values of my working system with NOD32. It shows that Superfetch/ReadyBoot do well.