BSOD caused by bad motherboard, still continues after replacement

stiyix · 03 Jun 2015

Built a custom computer a month ago and have been having BSODs ever since. Took it back to get checked and was told I had a faulty motherboard. The brand is MSI Z97S SLI Krait edition. I had my motherboard, ram, and CPU replaced.

Wiped everything and replaced windows but the BSOD returned. Had my BIOS changed to stop UEFI and updated all my drivers. Was told that would fix the problem but less than 30 mins after using a VPN the BSOD returned.

My suspicion is that I might have an issue with my PCI card since it s the only component I didnt get from my local electronic store and most of the BSODs occur when using WiFi. I've also been having "limited connectivity issues" but im not sure if these 2 are connected. The PCI brand is Tp-link TL-WDN4800.

Mini dump file and pic of blue screen also attached.

Any help would be greatly appreciated.

Boozad · 03 Jun 2015

Welcome to 7F stiyix, I'll see if I can help you resolve your issues.

All of your dumps are pointing to your hard drive, can you let us know if you have an HDD or SSD and how many? They're not in your system specs.

Code:

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000006, fffff80002d6c12a, fffff880009a96c8, fffff880009a8f20}

Probably caused by : hardware_disk

Followup: MachineOwner

Code:

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

FAULTING_IP: 
nt!LookupEntryPoint+3a
fffff800`02d6c12a 8b4024          mov     eax,dword ptr [rax+24h]

Code:

ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000077a9020c

EXCEPTION_PARAMETER3:  00000000c000000e

IO_ERROR: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

BUGCHECK_STR:  0x7E

EXCEPTION_STR:  0xc0000006_c000000e

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

FOLLOWUP_IP: 
+3a
00000000`77a9020c ??              ???

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware_disk

IMAGE_NAME:  hardware_disk

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  

STACK_COMMAND:  kb

FAILURE_BUCKET_ID:  X64_0x7E_IMAGE_hardware_disk

BUCKET_ID:  X64_0x7E_IMAGE_hardware_disk

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x7e_image_hardware_disk

FAILURE_ID_HASH:  {ff6dd2a9-5b68-7234-db8c-58a7e01b4a8f}

Can you check your SATA cables are seated correctly at both the motherboard and the hard drive, then run the following checks.

Run SeaTools to check the integrity of your HDD (Do not use on an SSD). SeaTools for DOS and Windows - How to Use

Run chkdsk. Disk Check

Please fill out your System Specs.

Information

At 7F we rely heavily on knowing what hardware you have in your system, by filling out your system specs in the manner outlined below your specs will follow you round in every single post so we can see your hardware configuration at the click of a button without having to trawl through threads to find them.

Follow System Info - See Your System Specs to fill in your System Specs with as much info as possible. We're looking for something like the example below.

stiyix · 03 Jun 2015

First of all, thanks for the help! Ive updated my system specs and run the Seatools and disk check. There was an HDD error while first running Seatools but it hasnt come when i ran it a second time. Is there a similar way to check out the SSD?

Boozad · 04 Jun 2015

You can run chkdsk on the SSD. There's also Samsung Magician you can download, I'll link it later for you as I'm on my phone at the moment.

stiyix · 04 Jun 2015

I ran the Samsung Magician and my SSD checked out fine. At this point I've ran tests on both the HDD and SSD and the results have been good. Does anyone know if Crystal Disk Info checks compatibility between drives? Im not sure if it's necessary to run more tests after checking both drive individually.

If the F4 error is related to a drive issue and both my drives check out fine, what else could be causing my BSODs?

Boozad · 04 Jun 2015

Possibly the SATA cable or port on the motherboard. Try changing cables and see if the BSODs persist, then try different SATA ports on the motherboard.