Bsods On Fresh Reformat

Gigabyte GA-Z87M-D3H LGA 1150 CrossFireX DVI/HDMI mATX
Intel Core i7-4770K Haswell 3.5GHz
Corsair CX500M PSU
G.Skill Sniper Series 32GB (4 x 8GB) 240-Pin SDRAM DDR3 2400 (PC3 19200)
GeForce GTX 760 (4GB 256-bit GDDR5)
SanDisk Extreme II 240 GB SATA 6.0Gb/s 2.5" SSD
Pioneer BDR-209DBK 16x Blu-Ray/CD/DVD Writer
Fractal Core 1000 mATX Case
Dell U2713HM ITS Display
Win7Pro x64 SP1

https://i.imgur.com/Lm9r8aM.jpg

Any and all help greatly appreciated.

-newmy51

 

side note, memdiag comes up 100% clean.

 

The first crash, 0xf4, is frequently a disk/data throughput issue, the 0x7a I'm unsure of.

 

many more. can't even stay stable in safe mode (w/ networking)

https://i.imgur.com/8L8EBvj.jpg

 

Check all hardware cables. If the problem persists, restart in Safe Mode and run the attached batch file.
Upload the log file - it's on the Desktop.

 

in the midst of a big memtest86 run on default settings. no errors yet. every cable was unplugged and replugged once already. guess i could do it again. will run batch file and upload resulting log along with memtest86 results.

 

Please don't use Driver EASY it's a scam...

Please use Driver Booster 7.0.2.438

Driver booster will find the correct drivers.

Best idea.Been using this software for years and have zero issues with Iobit.

The only problem you might get is with your virus or malware software stating its a pup but it's fine no problems.

 

Please leave the drivers as is, it's almost certainly a hardware problem, don't waste your time.

The 0x7a bugcheck with parameter 2 = 0xC000000E:

"0xC000000E, or STATUS_NO_SUCH_DEVICE, indicates a hardware failure or an incorrect drive configuration. Check your cables and check the drive with the diagnostic utility available from your drive manufacturer. If you are using older PATA (IDE) drives, this status code can indicate an incorrect master/subordinate drive configuration.

These status codes are the most common ones that have specific causes. For more information about other possible status codes that can be returned, see the Ntstatus.h file in the Microsoft Windows Driver Kit (WDK).

Another common cause of this error message is defective hardware or failing RAM.

A virus infection can also cause this bug check."
https://docs.microsoft.com/en-us/wi...gger/bug-check-0x7a--kernel-data-inpage-error

 

change MemTest86-Report-20191025-124938.log to .html

 

@Eldon when I try to run ChkDskEW.bat I get a flickr of a cmd window and then nothing.

 

just tried that. same result... strange.

 

got the chkdsk to run, but not in safe mode. log posted.

 

The log shows no errors.

If this batch file is not Run as Administrator, a UAC window opens.
We specifically included script to check whether the batch file was Run as Administrator or not.

 

Two items ---I would try Microsoft's bug check......
https://docs.microsoft.com/en-us/wi...r/bug-check-0xf4--critical-object-termination
Follow to !analyze
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/-analyze

https://docs.microsoft.com/en-us/wi...gger/bug-check-0x7a--kernel-data-inpage-error
Follow to Bug Check 0x77 (KERNEL_STACK_INPAGE_ERROR)
https://docs.microsoft.com/en-us/wi...gger/bug-check-0x7a--kernel-data-inpage-error

 

i just learned what a QVL is, found the one for my mobo, and noticed my RAM isn't on it, which could explain everything.

https://download.gigabyte.com/FileList/Memory/mb_memory_ga-z87m-d3h.pdf

with nothing but respect to the very helpful and courteous people here who have aided me over the many years, i am sort of shocked that I had to find this out for myself.

 

You did not post the RAM's Model Name or Module P/N.

At the top of the pdf document...
"Memory modules listed below are for reference only. Due to massive memory models on the market, we can only verify some of them."

 

G.Skill Sniper Series 32GB (4 x 8GB) 240-Pin SDRAM DDR3 2400 (PC3 19200), in the original post and my sig. if P/N refers to the alphanumeric string listed on the sticks (which in this case is FC-2400C11Q-32GSR), then yes, I did not include that info and haven't in any post anywhere wrt the issues encountered with this build, only because I didn't know its importance.

i recognize the shortcomings you point out in that QVL (all QVLs?), but that doesn't rule out the possibility that this particular RAM type is not compatible. it either is or isn't, but they didn't check. correct?

 

It's possible but...
How did you install Windows?

 

USB... why?

 

Given the dump details, there was little chance that RAM would be the probable cause, priority was given to the most likely - drive-related.

How long had this RAM been in the machine?

What made you do a fresh format/install?

 

Originally 32GB (4x8GB) CORSAIR Vengeance LP SDRAM DDR3 1600 (PC3 12800), upgraded some years ago. Issues throughout. Fresh format and install when already worrying BSOD issues:

https://forums.majorgeeks.com/threads/hackintosh-help.286467/
https://forums.majorgeeks.com/threads/hackintosh-turned-win7pro-still-lags.293834/
https://forums.majorgeeks.com/threads/bsod.301083/
https://forums.majorgeeks.com/threads/the-kiss-of-death.310929/

became worse post-cross-country road trip:

https://forums.majorgeeks.com/threads/death-comes-to-the-matx.320990/
[this thread]

fully and freely admit that I did not follow up on all possibilities or all advice given. mea culpa. i forgot about certain threads when things seemed to arbitrarily self-correct.

 

If the RAM was incompatible, Windows would not have installed.

 

The first indication of a possible RAM error from those older topics is a 0x124 BSOD here

0x124s are usually 'unknown hardware' errors, the CPU can detect/report it but Windows cannot find a software cause.

Try downclocking the RAM to 1600Mhz at 1.5v (non-overclocked speed for Ivy/Haswell).

 

I just got another bsod, but this time I saw my torrent client generate i/o errors as though one of the sata-attached hdds had been disconnected right before the crash. /facepalm

confused as to how to tell which drive letter corresponds to which hd make/model. checked properties, disk management, device manager. no luck.

 

Torrenting is pretty notorious for triggering BSODs, esp. where there are 'bad' drivers in the networking stack or a 3rd party firewall installed; what was the BSOD code?

Three ways here to check drive letters etc, DevMan, DiskMan and MSInfo32:

 

minidump 7z attached, along with ss of DevMan, DiskMan and MSInfo32. drive letter appears when I click "populate" in the volumes tab of the drive properties of DevMan, but neither of the other two tools appear to link drive letter and manufacturer/model name.

 

Same 0xF4 as previously.

Screenshots are scaled too much to be readily readable, try individuals ~1024x768.

Maybe you need to change a few settings, eg. Folder options, to see what you're looking for? Can't help much, I do that on autopilot in the first ~20 minutes post-install.



What, if any, changes have you made in the last ~48 hours?

 

show drive letters already enabled.

no changes in the last 24 hours. no changes in the last 24 days. barely any changes aside from a reformat in the last 24 months.

last crash was preceded by all desktop icons disappearing other than the main ones (my comp, networking, control panel, recycle bin), icons in tray disappearing, taskbar shortcut icons becoming decoupled from their .exes, and finally cursor freezing before BSOD. no minidump written. event ID 6008.

 

Without making any changes you're flogging a dead horse. We know the RAM is suspect so change that first: 1600Mhz, 9, 9, 9, 24 and 1T at 1.5v and test it - you may need to use an XMP setting and then modify it to suit.

 

removed 1 stick (two remaining in slots 1 and 2) and disconnected the audio/video drive (the one that i/o errored during two crashes back). did as much of the mem modding as I knew how in the uefi. for some reason, despite setting ram frequency to 1600mhz, it's clocking at 800...

speccy and cpuz both consider the sticks to be single channel, but I thought they were dual...

any sense in reseating the cpu?

various ss's attached.

 

Dual channel depends on the 'board layout, often the pairs are 1+3 and 2+4 but check your manual.

DDR memory = Double Data Rate, 800Mhz doubled is 1600Mhz, compare with the SPD XMP settings/rating for 2400.

If Speccy's anything to go by, the CPU temp looks okay, more tests needed before replacing the TIM.




(My hardware settings are for cool and quiet: underclocked/undervolted.)

 

left it up and running all night, with the possibly problematic hd installed. no crashes until I started to do things, and then it tanked, slowly, gobbling up individual programs, then explorer, then cursor, etc., as before. not getting new minidumps for some reason. i'm losing hope.

 

Had you changed anything?

Describe what you were doing and exactly what happened, details, error messages, as much as you can please.