Random BSOD on new computer build ntoskrnl.exe

[Krait killa]

Hello,

I recently decided to build my first PC and after I booted up and installed drivers in bulk using the installation disks included, I would recieve random crashes every now and then. The blue screens usually happen about within 1-15 mins of me booting up the computer. If it passes that point I'm usually in the clear to use it as long as I want. Please help.

Thanks

 

[Arc]

As the starting point, please follow this post to disable Samsung Rapid mode.

Then report us for any further BSOD.
____________________________________________________

BugCheck F4, {3, fffffa800a9ca060, fffffa800a9ca340, fffff800033d3130}

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

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

 

[Krait killa]

So I disabled Rapid mode on my samsung ssd and unfortunately the BSODs are still happening. It makes sense though because I was blue screening before I even enabled it. The BSOD are happening a bit more frequently atm so I would definitely appreciate another reply as soon as you can get back to me. I've attached a more recent zip below.

Thanks

 

[Arc]

I cannot verify if the Rapid mode is really disabled or not, because the zip you uploaded does not contain all the necessary files.

Anyway, as you are saying it, I am accepting it.

Now, as you have Magician installed, I also think that you keep the firmware updated time to time, regularly. Make it sure that the firmware is updated.

Post a screenshot of the SSD using CrystalDiskInfo - Software - Crystal Dew World

Also try to observe if the 0xF4 BSODs are anyhow occurring during the sleep to wake-up power transitions or not.

 

[Krait killa]

Samsung magician says firmware is up to date and I posted a screenshot of my ssd below.

 

[Arc]

Apparently everything is file. Keep monitoring that if the BSODs have any co-occurrence with the sleep.

Can you open the computer? Open it, check the SATA can power cables, RAMs and the graphics card. Re-seat those components.
If possible, apply the SSD to another SATA port on the motherboard.

Sww how it goes. Let us know.

 

[Krait killa]

I reseated my components yesterday morning and by the end of the day I still got 2 BSOD. So positioning doesn't seem to be the problem, I'm lost atm.

 

[Arc]

Blue Screen of Death (BSOD) Posting Instructions

 

[Krait killa]

Sorry, I thought my old files would have still been evaluated or something.

 

[Arc]

You posted some dumps only. We need the full DM Log output.

 

[Krait killa]

how exactly do I do that? Do I just run the program again?

 

[Arc]

Run DM Log collector again, as administrator obviously.

Also, run SF Diag tool too. Attach the result of that one too. Either of them will grab all the files.

Asking for those repetitively, because some other files are more important than crash dumps for stop 0xF4 troubleshooting.

 

[Krait killa]

Here you go.

 

[Arc]

Event[10111]:
Log Name: System
Source: atapi
Date: 2015-07-04T00:28:39.958
Event ID: 11
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Checkered-Venom
Description:
The driver detected a controller error on \Device\Ide\IdePort1.

So it is .....

Model    Samsung SSD 850 EVO 500GB ATA Device
[COLOR=Red]SCSI Port    1[/COLOR]

The driver is msahci, the system native storage controller by microsoft, which never fails itself.

Name    Intel(R) 9 Series Chipset Family SATA AHCI Controller  - 8C82
[COLOR=Red]Driver [/COLOR]   c:\windows\system32\drivers\[COLOR=Red]msahci.sys[/COLOR] (6.1.7601.17514, 30.38 KB (31,104 bytes), 6/28/2015 7:51 PM)

So that is an issue from the part of the hardware. Either the SSD itself or the SATA port or connectivity.

A crash dump gives the info in details.

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  [COLOR=Red]Typically caused by
a bad block in the paging file or disk controller error.[/COLOR] Also see
KERNEL_STACK_INPAGE_ERROR.
[COLOR=Red]If the error status is 0xC000000E[/COLOR], 0xC000009C, 0xC000009D or 0xC0000185,
[COLOR=Red]it means the disk subsystem has experienced a failure.[/COLOR]
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.

ERROR_CODE: (NTSTATUS) 0x[COLOR=Red][B]c000000e[/B][/COLOR] - [U]A device which does not exist was specified.[/U]

[B][COLOR=Red]DISK_HARDWARE_ERROR: There was error with disk hardware[/COLOR][/B]

So we can say that apparently there is no doubt that the disc hardware is causing the issue. Three things are falling within its scope.

1. The SATA port on the motherboard;
2. The SATA cable; and
3. The disc itself.

Troubleshoot those elements.

1. Apply the disc to another unused SATA port on the motherboard.
2. While doing 1 above, use a new SATA cable. Make it sure that the clips are properly locked at both the ends of the SATA cable. Dont do toolless mounting for now. Use screws to hold the discs with the stand, and dont leave a loose screw or an unused screw hole.

See how it goes after doing upto that stage. If things does not change, we have to go for the third possibility there.

3. The firmware is up-to-date, the SMART data is OK, still a SSD can fail. And we cannot test a SSD with the conventional disc check tools like Seatools or WinDFT. So if the issue continues even after doing 1 and 2 above, create a partition on the WD 1 TB (there is huge free space), install windows there and see how it goes. That's how we can isolate the SSD to be failing or not.

 

[Krait killa]

Are you sure it's the SSD? Things I have done since last post are swap the SATA data plug with another in my system, try another port in the motherboard and I have installed windows 7 on my hdd. I have BSOD several times after the fresh install. One shocking thing that happened was I had a BSOD when my SSD was completly unplugged (data and power cable). I ran the dm file collector as administrator but due to a corrupt NET framework (BSOD in the middle of install) I was unable to use the SF diagnostic tool.

 

[Arc]

Are you sure it's the SSD?

I am just another guy trying to help you based on your data and my knowledge, man! I am not the God.

If you need surety from me .... both of us are in the wrong place.

 

[Krait killa]

Haha, hey I'm not trying to doubt your judgement/skills or anything I just found it weird that my system would bsod even when the ssd was unplugged from the system. I do still think it could be the ssd because not 10 seconds after i plugged it in i got a bsod. Anyways I performed a secure wipe on my ssd to see if it would save it, if it doesn't, at the worst I will have to RMA it.

 

[Krait killa]

Ok, so I can now 100% confirm that the SSD is not the cause of the blue screen. A while after I secure erased it, I got a BSOD. I completely removed it from the PC and decided to see If I would get any more blue screens. Eventually I did.

 

[Arc]

Ok, so I can now 100% confirm that the SSD is not the cause of the blue screen. A while after I secure erased it, I got a BSOD. I completely removed it from the PC and decided to see If I would get any more blue screens. Eventually I did.

If you got both the discs corrupt .... that will be extreme. Still, test the HDD with WD Data Lifeguard .... taking the short test and the extended test.

If you get hard disc corruption on two different discs attached to two different ports with two different SATA cables, then I have nothing left to suggest you but replacing the motherboard.