Code:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\USER\Downloads\SF_08-11-2013\SF_08-11-2013\110113-20061-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 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0x83442000 PsLoadedModuleList = 0x83582230
Debug session time: Fri Nov 1 12:30:35.816 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:09.595
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, 85c63024, 0, 0}
Probably caused by : GenuineIntel
Followup: MachineOwner
---------
0: 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: 00000000, Machine Check Exception
Arg2: 85c63024, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000, 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
STACK_TEXT:
80e4dcc4 83505e85 85c63008 835a0be8 835a0be0 nt!WheapCreateTriageDumpFromPreviousSession+0x32
80e4dce4 83506cbd 835a0be0 85c63008 835a0c10 nt!WheapProcessWorkQueueItem+0x56
80e4dd00 8349d3ab 835a0be0 00000000 84eb6a70 nt!WheapWorkQueueWorkerRoutine+0x1f
80e4dd50 8362a53a 00000001 9c12c4c6 00000000 nt!ExpWorkerThread+0x10d
80e4dd90 834cb899 8349d29e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_BUS_PRV
BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_BUS_PRV
Followup: MachineOwner
---------
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 try
Based on the bugchecks, I would recommend you follow and complete the steps given below:1. If you are overclocking any hardware, please stop. Reset any changed values back to default and reset/clear CMOS:
Clear CMOS - 3 Ways to Clear the CMOS - Reset BIOS. Uninstall any overclocking tool as these can also be a reason of blue screens.
2. Uninstall your current antivirus software. It can be a cause of BSOD very often. Please remove it with its
removal tool and use
Microsoft Security Essentials in its place.
Malwarebytes is a great combination with it. Go through
this thread for more info.
3. Run
Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors. Post back your logs for the checks after finding them using
Check Disk (chkdsk) - Read Event Viewer Log
4. Run
SFC /SCANNOW Command - System File Checker to check windows for integrity violations. Run it up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
5. Make scans with
Kaspersky TDSskiller and
ESET Online scanner.
6. Perform a
Clean Start up, this will help avoid any problematic applications from bugging the system.
7. Use
Revo Uninstaller Free to uninstall stubborn software. Opt for Advanced Mode and uninstall the software, delete the leftover registry entries.
8. Use
Crystal Disk Info to
upload a screenshot of your Hard Drives (s). Test your Hard Drives (s) running a
Hard Drive Diag.
9. Test and Diagnose RAM issues with
RAM - Test with Memtest86+. Pay close attention to Part 3 of the tutorial "If you have errors" Take the test for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.
10. Monitor hardware temperature for overheating issues with system monitoring software like Speccy or HWMonitor. Upload a screen shot of the Summary tab as well:
Quote