Hey guys! I dont know why but i get BSOD with the massage 0x0000001E. Sometimes i dont get it like for 3 days, but sometimes i get it like 3 times in less than 12 hours. Here is a log from dm log collector. Hope u can help me with this one.
A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 - What it means and what to tryCode:Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\YUSRA\Downloads\Compressed\MARKO-PC-26_05_2015_151631,15\052615-28532-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Symbol Path validation summary ************** Response Time (ms) Location Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.18839.amd64fre.win7sp1_gdr.150427-0707 Machine Name: Kernel base = 0xfffff800`02c11000 PsLoadedModuleList = 0xfffff800`02e58730 Debug session time: Tue May 26 19:04:52.096 2015 (UTC + 6:00) System Uptime: 0 days 0:00:19.751 Loading Kernel Symbols . Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long. Run !sym noisy before .reload to track down problems loading 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, fffffa8004a8c8f8, 0, 0} Probably caused by : GenuineIntel Followup: MachineOwner --------- 1: 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: fffffa8004a8c8f8, 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: WIN7_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre STACK_TEXT: fffff880`031bd6f0 fffff800`02ed5cb9 : fffffa80`04a8c8d0 fffffa80`039fb660 fffff8a0`00000003 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c fffff880`031bdc10 fffff800`02db4697 : fffffa80`04a8c8d0 fffff800`02e2f2d8 fffffa80`039fb660 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49 fffff880`031bdc40 fffff800`02d1b6e5 : fffff800`02e91ba0 00000000`00000001 fffffa80`04a71820 fffffa80`039fb660 : nt!WheapProcessWorkQueueItem+0x57 fffff880`031bdc80 fffff800`02c8f4b5 : fffff880`011c1e00 fffff800`02d1b6c0 fffffa80`039fb600 ffffffff`0000055a : nt!WheapWorkQueueWorkerRoutine+0x25 fffff880`031bdcb0 fffff800`02f1f456 : 00000000`00000000 fffffa80`039fb660 00000000`00000080 fffffa80`039e9040 : nt!ExpWorkerThread+0x111 fffff880`031bdd40 fffff800`02c772c6 : fffff880`02f63180 fffffa80`039fb660 fffff880`02f6dfc0 ffefefb7`ffdf9bff : nt!PspSystemThreadStartup+0x5a fffff880`031bdd80 00000000`00000000 : fffff880`031be000 fffff880`031b8000 fffff880`03d2d780 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: GenuineIntel IMAGE_NAME: GenuineIntel DEBUG_FLR_IMAGE_TIMESTAMP: 0 IMAGE_VERSION: FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_processor_bus_prv FAILURE_ID_HASH: {ca6433e5-0c8f-9db0-d4cf-d171805006d5} Followup: MachineOwner ---------
Quote