BSOD occuring several times a week, hoping for answers, thank you!

[seanpf]

Attached is the dump/logs as per the posting instructions.

I've just disabled automatic restart so im unsure what the actual error is, but it happens frequently, several times a week.

Another oddity is that it always goes directly to bios after restarting. I have it set to halt on error and force F1 to continue, yet it always jumps straight to bios on reboot. Its a ASUS VII Maximus mobo updated to the latest bios.

Thanks for any and all advice!

 

[Arc]

The crash dumps included in the zip are all of 2015, too old to decide about the present situation.

Follow it: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Dont run any disc cleanup tool before you upload another zip.

 

[seanpf]

Thank you for the reply. Is a full memory dump or kernel dump preferred?

EDIT - Just saw you mention point 2, which I see is a mini. You would not prefer a full?
Thanks!

 

[Arc]

Do what is said, that would be enough.

 

[seanpf]

Do what is said, that would be enough.

I did and got a BSOD, KERNEL_DATA_INPAGE_ERROR

Upon checking the minidump directory there was no new dump created I went to advanced system properties in system/restore and verified that everything was setup correctly and it is. Write an event to the system log and the small memory dump to the correct path is selected as specified in your above post.

I see its related to HD/Memory, will run a chkdsk and see if there are any errors.

Is it pretty common for the system to not create a dump file?

 

[Arc]

Is it pretty common for the system to not create a dump file?

KERNEL_DATA_INPAGE_ERROR might not create a dump file, depending on some subsequent parameters.

Next time, please take a camera snap of of the BSOD screen (full screen) and upload the image here. The onscreen codes will tell the fact behind it.

 

[seanpf]

Is it pretty common for the system to not create a dump file?

KERNEL_DATA_INPAGE_ERROR might not create a dump file, depending on some subsequent parameters.

Next time, please take a camera snap of of the BSOD screen (full screen) and upload the image here. The onscreen codes will tell the fact behind it.

I actually did take a picture of it, I was just out the door in a hurry earlier so i couldn't post, so sorry about that !

Attached is the picture of the BSOD.

I had actually already ran a full memory check using memtest86 through hirens boot cd, and I believe I've already ran several chkdsk's on the HD, as well as using various SSD benchmark and health test tools all of which said the SSD was good.

Hopefully the extra info in this picture will help determine whats going on and thank you so much for helping.

 

[Arc]

The second parameter here is the error status. It says 0xC000000E. That reads as STATUS_NO_SUCH_DEVICE and means "A device that does not exist was specified".

Make it sure that the SSD is having the latest firmware, and it is properly connected.

 

[seanpf]

The second parameter here is the error status. It says 0xC000000E. That reads as STATUS_NO_SUCH_DEVICE and means "A device that does not exist was specified".

Make it sure that the SSD is having the latest firmware, and it is properly connected.

Interesting. This happened this round while just reading emails, nothing going on in the background, no work etc.

So it appears that what is happening is the SSD is getting disconnected somehow? I will follow your instructions of course and update the firmware to the latest for the SSD, I just want to understand the nature of the problem.

It could be as stupid as a faulty cable or port issue as well im thinking. Will keep testing after updating firmware.

 

[Arc]

It may not be the SSD only, but as dumps are not being recorded there might be a chance that it is the SSD that is being missing.

If the situation does not change even after doing those steps, we will have to take further steps.

 

[seanpf]

It may not be the SSD only, but as dumps are not being recorded there might be a chance that it is the SSD that is being missing.

If the situation does not change even after doing those steps, we will have to take further steps.

SSD is a crucial 512 MX100. Checked the firmware and its updated to the latest , ver MU2.

Ran a chkdsk C:/f/r/x and it did not find any issues.

Curious situation. Im going to wait until another BSOD occurs to see if the same issue occurs, but im unsure where we could go from there. Maybe change cable, use a different sata port for starters?

 

[Arc]

Maybe change cable, use a different sata port for starters?

Those two will be very appropriate and perfect steps.