4770K - Where am I going wrong?

Don't get me wrong, I'm sure it has its benefits in some games but particularly in BF4 when I was experiencing random drops in FPS for a split second I found it totally went when I disabled hyper threading.

Same occurs in BF3 with my Brother. He reckons he gets better performance from his 6 core Sandy Bridge E when overlocking. He even states that he gets higher fps with only 6 physical cores verses 12 threads.

BF3 likes real cores over virtual cores.

Because BF4 is cpu heavy normally if you run dual gpu's it max's the cpu out below 4.5Ghz.

Increase your overclock to 4.5Ghz if possible.
 
Ive yet to try it at 4.5ghz mate, at stock it's fine with ht enabled, particularly bf3. Bf4 is still in to bad a state to use as a benchmark for performance. Disabling ht effectively turns my 4770k into an i5. Which i used to own, (3570k). The moment i went to sli on that chip performance in bf3 nosedived. Sorted this by moving to a 3770k which i later sold to fund the move to haswell.
 
Ive yet to try it at 4.5ghz mate, at stock it's fine with ht enabled, particularly bf3. Bf4 is still in to bad a state to use as a benchmark for performance. Disabling ht effectively turns my 4770k into an i5. Which i used to own, (3570k). The moment i went to sli on that chip performance in bf3 nosedived. Sorted this by moving to a 3770k which i later sold to fund the move to haswell.

Right,
Did you get the old i5 up to a high overclock? I'm not getting an i7 just yet as I want to see the so called Mantle effect on cpu load. I'd also get a chip mail order so I can DSR if it dont perform much better than my current cpu which seems to be very stable at 4.7Ghz but wont move 1Mhz higher for some reason!!!

It would be very interesting if you get a chance try out your Haswell with 4 Physical cores at 4.5Ghz. Your Haswell obviously has better IPC, more Cache and is probably a better binned chip compared to the average i5 so who knows.
 
Heat is an issue on this chip if i run synthetic stress tests, (mid 90's on a few cores). But in game with ht enabled 65c is the max ive seen. Tbh it would need to be delidded if i was going to push it higher.
 
Heat is an issue on this chip if i run synthetic stress tests, (mid 90's on a few cores). But in game with ht enabled 65c is the max ive seen. Tbh it would need to be delidded if i was going to push it higher.

65oC is really low for a 4.5Ghz Haswell. Thats pretty good. I'd probably stick to running BF4 and fraps plus Hwbot. If its stable in BF4 then thats good enough for most.
 
Mine also runs at 4.5ghz about 65 degrees when on BF4.

Just had a blue screen of death - apparently ntoskrnl.exe caused it. Frankly I have no idea what it is, why it did it or what I can do to fix it. I just lose more patience every time it goes wrong.
 
You can get the error codes from the system log in Event Viewer. You don't need a third party tool to get that information.

If you suspect that your BSODs are caused by something else like drivers, then you will need WinDBG (part of the Windows debugging toolkit) and the associated symbols.

Windows Debugging
Download symbols
 
Just used WhoCrashed and got this...

On Mon 02/12/2013 15:07:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120213-3359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x139 (0x3, 0xFFFFF88007567590, 0xFFFFF880075674E8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

As you can see from the screenshot below, this ntoskrnl.exe thing seems to be a common issue for me. You can also see how frequently I'm BSOD'ing.

PaRS02M.png
 
Run "sfc /scannow" to see if the integrity of the system files is okay.

I learned something quite useful yesterday. If you want to know which driver is causing the BSOD, run "verifier.exe /standard /all" and reboot. The next time it BSODs, boot into safe mode and run "verifier.exe /reset" and then boot back to Windows.

Afterwards, use WinDBG and the symbols to find out which driver is fubar. This gave me a lot more useful info than a normal minidump or even full memory dump.
 
Back
Top Bottom