Windows 7 ntoskrnl.exe BSOD

Hello everybody.

Currently getting a BSOD related to ntoskrnl.exe..

It seems to occur randomly, though there are some events (plugging in a USB device, jostling the system in any way) that seem to spur it on more quickly.

I have run virus scans, Memtestx86, and other hardware diagnostics; everything has come back fine. I'm fairly certain it is a hardware problem however, as I have done three or four clean installs of windows to no avail. The system also crashes in safe mode.
Specs:
Asus Z97-A
Intel i7 4790k
2x 8GB Kingston Hyper-X
Nvidia GTX 560
Samsung 840 EVO (240GB)
Hitachi HDD (500GB)
Asus DVD Drive

Hi jdez99.

First of all, make it sure that your SSD is having the latest firmware.
How to Upgrade Samsung SSD Firmware | StorageReview.com - Storage Reviews

And uninstall MagicISO or MagicDisc whichever you have installed.

Let us know the result upto this point.
________________________________________

Code:

BugCheck F4, {3, fffffa800ea3c8c0, fffffa800ea3cba0, fffff8000318f940}

----- ETW minidump data unavailable-----
Probably caused by : wininit.exe

Followup: MachineOwner
---------

Interesting to say the least...

The before last one drawn my attention specially .....

Code:

BugCheck 74, {2, fffff880030729e0, 1, ffffffffc000003a}

Probably caused by : ntkrnlmp.exe ( nt!CmpLoadHiveThread+23a )

Followup: MachineOwner
---------

See the description of the bugcheck .....

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_SYSTEM_CONFIG_INFO (74)
Can indicate that the SYSTEM hive loaded by the osloader/NTLDR
was corrupt.  This is unlikely, since the osloader will check
a hive to make sure it isn't corrupt after loading it.
It can also indicate that some critical registry keys and values
are not present.  (i.e. somebody used regedt32 to delete something
that they shouldn't have)  Booting from LastKnownGood may fix
the problem, but if someone is persistent enough in mucking with
the registry they will need to reinstall or use the Emergency
Repair Disk.
Arguments:
Arg1: 0000000000000002, (reserved)
Arg2: fffff880030729e0, (reserved)
Arg3: 0000000000000001, (reserved)
Arg4: ffffffffc000003a, usually the NT status code.

I would suggest you to test your RAM modules for possible errors at first.

How to Test and Diagnose RAM Issues with Memtest86+

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If memtest86+ is free from errors, do a clean reinstall. See how that clean reinstall go.

DISC

jdez99 said:

After running memtest86 for 10 passes, no errors were found. I've also reinstalled windows several times, so I know that this will not resolve the issue. Anything else I can do?

Do a clean reinstall and report us for any further issue.

That is what we can say at this point of time.

It may be a corrupt ISO, or a corrupt optical disc drive, or even a bad destination drive, that is the SSD.

To eliminate the possibilities ....

• Use an original disc or any other known good ISO
• Try a bootable windows installation USB
• Try another hard disc.

EDIT:

jdez99 said:

After running memtest86 for 10 passes, no errors were found. I've also reinstalled windows several times, so I know that this will not resolve the issue. Anything else I can do?

Havent you used mamtest86+ as suggested?