New
#1
Froze out of no where.
was messing with cpu-z click on a tab and it froze.
was messing with cpu-z click on a tab and it froze.
Looks like either your CPU or RAM caused the problem.
Read this: https://www.sevenforums.com/crash-loc...-what-try.htmlCode:Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Jonathan\Desktop\040510-19156-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02c0f000 PsLoadedModuleList = 0xfffff800`02e4ce50 Debug session time: Mon Apr 5 12:28:22.816 2010 (GMT-4) System Uptime: 0 days 0:00:08.784 Loading Kernel Symbols ................................................ Loading User Symbols Mini Kernel Dump does not contain unloaded driver list ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, fffffa8006e736a8, 0, 0} Probably caused by : hardware Followup: MachineOwner --------- 5: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: fffffa8006e736a8, Address of the WHEA_ERROR_RECORD structure. Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ BUGCHECK_STR: 0x124_GenuineIntel CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 STACK_TEXT: fffff880`033706f0 fffff800`02ec9a89 : fffffa80`06e73680 fffffa80`05522b60 00000000`00000006 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c fffff880`03370c10 fffff800`02dab547 : fffffa80`06e73680 fffff800`02e245f8 fffffa80`05522b60 00000000`00000286 : nt!WheapCreateTriageDumpFromPreviousSession+0x49 fffff880`03370c40 fffff800`02d13b95 : fffff800`02e86360 fffffa80`064da828 fffffa80`064da820 fffffa80`05522b60 : nt!WheapProcessWorkQueueItem+0x57 fffff880`03370c80 fffff800`02c8e161 : fffff880`01096e00 fffff800`02d13b70 fffffa80`05522b60 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25 fffff880`03370cb0 fffff800`02f24166 : 01ca91d5`f5ec5754 fffffa80`05522b60 00000000`00000080 fffffa80`0548d890 : nt!ExpWorkerThread+0x111 fffff880`03370d40 fffff800`02c5f486 : fffff880`03186180 fffffa80`05522b60 fffff880`031910c0 01ca91d5`f5e9f5f4 : nt!PspSystemThreadStartup+0x5a fffff880`03370d80 00000000`00000000 : fffff880`03371000 fffff880`0336b000 fffff880`04330540 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV Followup: MachineOwner ---------
Are you overclocking at all? If so, I suspect that to be the cause. Restore it back to factory settings.
doesnt say exactly which one?
Nope, hardware is all it says. That usually means RAM or CPU.
https://www.sevenforums.com/crash-loc...-what-try.html1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable ways.
2) Ensure that the machine is adequately cooled. If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.
Keep in mind overheating can be caused by overclocking.
its not overheating it was ocd then i knocked the oc down and re ran prime i get it to freeze by opening cpu z around the 7 min mark and wiggling my mouse. I have knocked all my oc settings back to clock even though i was stable for months..
i noticed the first freeze just farting around with cpu z idk if that is what making it freeze it doesnt make sense but i dont know what to blame it on.
im running memtest again for the 100th time.
also thing is.. I am not getting a BSOD it is just locking up.
As oddly as this may sound i think it is cpu z causing my pc to freeze, why i dont know. i was always freezing at 7 min mark but while messing with cpu z i didnt touch it for about 30 mins, then i closed it opened it closed it opened it, then mouse lag began i saw the mouse going slow and about to freeze i tried to hurry up and exit, and it locked up. i dont get it.
anyone have any idea why cpu z if freezing my computer?
You can try removing it and downloading it again, but the dmp pointed to hardware, not CPU-Z.
Perhaps CPU-Z is putting a load on your CPU not normally encountered in day-to-day operations. Maybe after months of over-clocking, your CPU finally decided to die.
I know, not real encouraging. Try running Prime95 and testing your CPU.
Hello Mate,
Stop 0124 doesn't mean that it's the hardware sometimes it's just a false postive. If you think that it freezes when you open or run CPU - Z please remove it. Reboot the System in selective startup and see whether that makes any difference. Maybe something is blocking CPU - Z in accessing System information resulting in crashing ir freezing.
Hope this helps,
Captain