Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 80050031, 6f8, fffff80002ecaf18}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80002ecaf18
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: steam.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002ebe1e9 to fffff80002ebec40
STACK_TEXT:
fffff880`02fdbce8 fffff800`02ebe1e9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`02fdbcf0 fffff800`02ebc6b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02fdbe30 fffff800`02ecaf18 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`0a524000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x8
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b2
fffff800`02ebc6b2 90 nop
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiDoubleFaultAbort+b2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 50e79935
FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2
BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2
Followup: MachineOwner
---------
Code:
STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
Usual causes: Memory corruption, Hardware (memory in particular), Overclocking
failure, Installing a faulty or mismatched hardware (especially memory) or a
failure after installing it, 3rd party firewall, Device drivers, SCSI/network/
BIOS updates needed, Improperly seated cards, Incompatible storage devices,
Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack
If you are overclocking your system, please return all overclocked components to their stock speeds. If the BSOD's are found not to be caused by the overclock, you can re-overclock the components once we have finished the diagnostics.
This is overclocking software and can lead to system instability and BSOD's. Please reset all components to their stock speeds and then remove the software.
Code:
Start Menu\Programs\MSI Afterburner ELIO-PC\ELIO:Start Menu\Programs\MSI Afterburner ELIO-PC\ELIO
Start Menu\Programs\MSI Afterburner\SDK ELIO-PC\ELIO:Start Menu\Programs\MSI Afterburner\SDK ELIO-PC\ELIO
For monitoring the heat/celsius of the system, use Speccy or HWMonitor:
Make scans with the following:
-Kaspersky TDSSKiller
-ESET online scanner
Perform a System File Check to check the integrity of all protected Windows 7 :
- Click on the start
- Type CMD on Search
- Left click and Run as Administrator
- Type
Full tutorial here:
Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
Note
Pay close attention to part 3 of the tutorial in order to rule out the faulty stick.
Information
Errors are sometimes found after 8 passes.
Tip
Do this test overnight, before going to bed.
If Memtest86+ does not find any errors with ram run Windows Memory Diagnostics for 7-8 passes following its tutorial:
Let us know the results.