Windows 7 ntoskrnl.exe BSOD

[jdez99]

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

 

[Arc]

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.
________________________________________

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

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

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

 

[jdez99]

Thanks for the reply, Arc! I have uninstalled MagicDisc, and have already updated my SSD's firmware. (After your comment I verified this with Samsung's Magician software) and the system is still giving a BSOD. Although there are some new ones now. I'll edit this post with the updated log files.

 

[jdez99]

Interesting to say the least...

 

[Arc]

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

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

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

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

See the description of the bugcheck .....

*******************************************************************************
*                                                                             *
*                        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 [COLOR=Red][B]if someone is persistent enough in mucking with
the registry they will need to reinstall or use the Emergency
Repair Disk.[/B][/COLOR]
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]

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?

 

[Arc]

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.

 

[jdez99]

After attempting to reinstall, a few weird things began happening. My input devices were not being recognized (had to reboot 3 or 4 times before it would allow me to use my mouse/keyboard) and then this error message. I am attempting to install from a burned iso of w7, not an original copy. Could my iso be corrupt or something to that effect?

 

[Arc]

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:

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?

 

[jdez99]

Just downloaded and created a Bootable USB for memtedt86+, as I incorrectly used the wrong version. Upon booting to the USB however, it states "operating system not found." as I had reformatted the drive in preparation of reinstalling windows. I still cannot install windows however, getting tons of strange warning messages. At this point I suspect it's the motherboard, as the USB devices are still occasionally going undetected when booting to the win7 install disc/Bootable USB.

 

[Arc]

Just downloaded and created a Bootable USB for memtedt86+, as I incorrectly used the wrong version. Upon booting to the USB however, it states "operating system not found."

Have you taken this one for memtest86+?

View attachment 357131
​

Ans still it is not working?

 

[jdez99]

That is correct.

 

[Arc]

Can you try the bootable cd version?

 

[jdez99]

Made the bootable cd, have been running it since early yesterday morning. After 12 passes, memtest86+ still hasn't found any errors.

 

[Arc]

12 passes are more than enough.

As a next step, try any other installation media, see if it works.

 

[jdez99]

I've tried discs, USB, everything. The drives show up and then when I go to format them or create a partition it keeps erroring until the drives eventually disappear from the list. It happens with all the hard drives, I'm thinking it's a motherboard or sata problem.

 

[Arc]

I am thinking that it might be a corrupted SSD.

If multiple installation media goes the same, better you install on any other disc.

 

[jdez99]

I have tried three separate hard drives. They all give the same error.

 

[Arc]

Then two options are left (before blaming the motherboard), either a bad sata cable or a bad sata port.

 

[jdez99]

So over the past week I have taken my build to memory express (Where I got the components) and had them run a test on it. All of the hardware passed, and they installed windows 7. After running it for a while they claimed no BSOD occurred. I was happy, but wary as well. After receiving it and taking it home, I booted it up and blue screened instantly. The only peripherals plugged in were my Razer Naga and my Logitech bluetooth keyboard, an MX5500. I'm at my wit's end with this one.