ghostmedic171
New member
- Apr 5, 2013
- 1
Hello all; thanks for reading. Bear with me while I newb my way through this!
Ever since I went from an LGA 1155 i5 3570k, to the 3770k i7 about three weeks ago, I've been running into BSODs. Most often, immediately upon log in to windows 7 64 bit.
This last instance, I was watching a youtube video. Suddenly, the power completely dropped out. It stayed down, maybe 5 seconds, and powered back up on its own. It posted fine, got to log in to W7, and the log-in sound began to skip and I got the BSOD; same thing happened on next start up.
I was having some trouble a couple nights ago; I thought I had it solved by lower clock speeds on my RAM. It was working fine until the first shut off. System specs as follows (forgive me if I list something unimportant... I'm kind of new to this!):
Windows 7 Home Premium (64)
LGA 1155 i& 3770k (Ivy) - under closed loop w/c
ASUS ROG Maximus V Extreme
16gb (4x4) of 2133mhz G.Skill Ripjaws RAM
2 ea EVGA GTX 670 4gb ftw
1200w PC Power and Cooling PSU
I think that about does it... Nothing there is real new, except for the i7, installed several weeks ago. It's currently under a preload Overclock profile that came with the maximus; @ 4.6. Obviously I may need to roll back, but I was hoping somebody could help me understand what exactly should I look for?
The crash dump is as follows:
---------
Ever since I went from an LGA 1155 i5 3570k, to the 3770k i7 about three weeks ago, I've been running into BSODs. Most often, immediately upon log in to windows 7 64 bit.
This last instance, I was watching a youtube video. Suddenly, the power completely dropped out. It stayed down, maybe 5 seconds, and powered back up on its own. It posted fine, got to log in to W7, and the log-in sound began to skip and I got the BSOD; same thing happened on next start up.
I was having some trouble a couple nights ago; I thought I had it solved by lower clock speeds on my RAM. It was working fine until the first shut off. System specs as follows (forgive me if I list something unimportant... I'm kind of new to this!):
Windows 7 Home Premium (64)
LGA 1155 i& 3770k (Ivy) - under closed loop w/c
ASUS ROG Maximus V Extreme
16gb (4x4) of 2133mhz G.Skill Ripjaws RAM
2 ea EVGA GTX 670 4gb ftw
1200w PC Power and Cooling PSU
I think that about does it... Nothing there is real new, except for the i7, installed several weeks ago. It's currently under a preload Overclock profile that came with the maximus; @ 4.6. Obviously I may need to roll back, but I was hoping somebody could help me understand what exactly should I look for?
The crash dump is as follows:
Code:
Loading Dump File [C:\Windows\Minidump\040513-12948-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*[url]http://msdl.microsoft.com/download/symbols[/url]
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`03657000 PsLoadedModuleList = 0xfffff800`0389b670
Debug session time: Fri Apr 5 20:02:15.372 2013 (UTC - 5:00)
System Uptime: 0 days 0:00:39.169
Loading Kernel Symbols
...............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 80050033, 406f8, fffff8800c991952}
*** WARNING: Unable to verify timestamp for avckf.sys
*** ERROR: Module load completed but symbols could not be loaded for avckf.sys
Probably caused by : avckf.sys ( avckf+32952 )
Followup: MachineOwner
---------
1: 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: 0000000080050033
Arg3: 00000000000406f8
Arg4: fffff8800c991952
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: EVGAPrecision.
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff800036cc1e9 to fffff800036ccc40
STACK_TEXT:
fffff880`009f3de8 fffff800`036cc1e9 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000406f8 : nt!KeBugCheckEx
fffff880`009f3df0 fffff800`036ca6b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009f3f30 fffff880`0c991952 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00000000`0005ea9a 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : avckf+0x32952
STACK_COMMAND: kb
FOLLOWUP_IP:
avckf+32952
fffff880`0c991952 0300 add eax,dword ptr [rax]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: avckf+32952
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: avckf
IMAGE_NAME: avckf.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 50f05302
FAILURE_BUCKET_ID: X64_0x7f_8_avckf+32952
BUCKET_ID: X64_0x7f_8_avckf+32952
Followup: MachineOwner
Last edited by a moderator:
