Having bsods relating to ntoskrnl.exe+75c00

Your latest logs show:

Code:

 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff880008b48a0, 0, fffff80002e4cc38, 0}
 
Could not read faulting driver name
Probably caused by : cng.sys ( cng!GatherRandomKey+294 )
Followup: MachineOwner
---------
7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)

This crash was caused by cng.sys part of MS cryptolgy.
Since it is a protected OS file, it is not likely the cause, but you should run a
system file check to verify and repair OS files:





Run SFC to check the integrity of all Windows 7 system files:

• Click on Start > Type in search cmd
  Right-click cmd after results are displayed and Run as Administrator
  Type SFC /scannow at the prompt
  (Note: There is a space between SFC and /scannow)

SFC Tutorial

I did see some suggestion of networking related issues but nothing concrete,
so I would suggest updating all your networking devices to the latest versions.

As your logs are not showing anything definitive:

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

Driver Verifier - Enable and Disable

Before enabling DV, make it sure that you have earlier System restore points made in your computer.

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a system restore to a point you made earlier.

Also run windows update.

cheers
Dave

I'll try the SFC scan soon, do you think i should use the diagnostic tool again?

I am pretty sure the network drivers are upto date i did dl them from the Asus site.

Done sfc scan, it reported some corrupted files unable to repair after doing 3 times....must be due to what i said previously.

Ok, unfortunately repairing SFC errors is not my field, and the member who deals with this
type of issue is on holiday till end of month and will most likely have a backlog.

Do you have a Windows 7 installation disk? If so this tutorial to repair missing or corrupted files
may be of some help, if not then there is a link in the tutorial to download the ISO :):

https://www.sevenforums.com/tutorials/42776-extract-files-windows-7-installation-dvd.html

If it will not repair, then I will flag up another member to assist.

Cheers

Dave

Hi,

To be honest I'm unsure about the correct settings and wouldn't like to advise
you about something I'm not sure of, please take a look at this link which may or may not help:

http://www.overclock.net/t/1411077/haswell-overclocking-thread

Windows 8!!

Haven't you ran Memtest a few times now with no errors?

I'm wondering if the DIMM's weren't seated properly or suffering from some for of "Chip creep" :)

Yeah, try one stick until you BSOD, if you don't crash then it may be a slot issue or incompatible memory

Follow Part 3 in the memtest tutorial if you get any errors etc.

There is a utility on the Asus website for memory tweaks, it may help, but try the above first:

MAXIMUS VI HERO - Motherboards - ASUS

If the above doesn't correct the issue, then I will send up the Bat signal and call for
help as I'm running out of ideas.

Also looking at your RAM specs again, it seems they are the correct type and size!!