New
#11
Have you taken memtest?
Do you mean again?
Or the one I did before:
Stick 1 - 7 passes nor errors
Stick 2 - 16 passes no errors
Stick 1 and 2 at the same time: 7 passes no errors
(I previously removed stick 3 because it found two errors after 15 passes)
So should I make another memtest with these sticks? (1 and 2)
Did you remove the stick or did you replace it?
How many sticks of RAM do you have exactly?
Is the firmware for your SSD up to date?
If you are overclocking your system, please return all overclocked components to their stock speeds.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 ******************************************************************************* * * * 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: 0000000080050033 Arg3: 00000000000006f8 Arg4: fffff80003a8051b Debugging Details: ------------------ BUGCHECK_STR: 0x7f_8 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: d LAST_CONTROL_TRANSFER: from fffff80003a89569 to fffff80003a89fc0 STACK_TEXT: fffff880`0368eee8 fffff800`03a89569 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000006f8 : nt!KeBugCheckEx fffff880`0368eef0 fffff800`03a87a32 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`0368f030 fffff800`03a8051b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2 ffff7880`036b0a40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeAccumulateTicks+0x2b STACK_COMMAND: kb FOLLOWUP_IP: nt!KiDoubleFaultAbort+b2 fffff800`03a87a32 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: 503f82be FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2 BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2 Followup: MachineOwner ---------
If the BSOD's are found not to be caused by the overclock, you can re-overclock the components
to a stable speed once we have finished the diagnostics.
Check for a more recent BIOS version.Code:!sysinfo cpuspeed CPUID: "Intel(R) Core(TM) i7 CPU X 990 @ 3.47GHz" MaxSpeed: 3470 CurrentSpeed: 3549
Uninstall any overclocking software because it can lead to system instability and BSOD's.Code:BIOS Version/Date American Megatrends Inc. 1401, 5/12/2011
Please reset all components to their stock speeds and then remove the software.
For monitoring the heat/celsius of the system, use Speccy or HWinfo:
- Speccy - System Information - Free Download
- CPUID - System & hardware benchmark, monitoring, reporting
Perform a System File Check:
- Click on the start
- Type CMD on Search
- Left click and Run as Administrator
- Type SFC /scannow
Full tutorial here:
Disk Check on your hard drive for file system errors and bad sectors on it:
I have 3 RAM sticks.
There are three slots on my motherboard.
So when I test each stick I just remove the other two.
So stick one is in slot one, and stick two is in stick two.
The SSD, BIOS and overclocking seems complicated. I'll find out how to chack and do it, and get back to you later :).
The my graphics card's max temperature is 91, and the processor's way below that.
File check found no errors, or corruptions.
Checking disk right now, will edit post when I get the results.
Thnaks for your help.
Disk Check found no errors.
Now I'll try to figure out the hard stuff. Will post when done.
Thank you
Ok. The bios is now updated, and the SSD was already updated.
I reseted the bios to defaults and the overclocking is gone. However every time I boot I get a message: "CPU Fan 1 Error". (I have water cooling in my processor, but everything else is fans)
I can just dismiss it with F1 and boot normally, but it keeps bothering me.
Will post again when a crash appears.
Thank you so much. :) Toxic
Good to hear that the system is stable now.
I've requested a friend to take a look at your thread.
Please wait for a reply.
I just got a crash. This one is different though, it's not a Blue Screen, my computer completely froze (but I was able to move my mouse). When I ctrl-alt-deleted it said Preparing Security Options or something like that, and it stayed like that until I plugged the computer off.
It was as if everything stopped responding, my mouse had the loading sign.
This isn't new though, a few days ago I started getting these along with the BSODs but I don't get the BSODs anymore.
I would also like to mention that when I boot right back again, and windows just starts, it happens again in the same way. (The freezing) I have to wait a few minutes to boot the computer again for it to be usable, and not get freezes at start-up.
I got this while playing BF3, although it's fair to say that my computer crashes way less after I removed the overclocking.
Thanks so much for your help guys, I appreciate it with all my being.
Here's my new crashlog: :)