Windows 10: Rebooted from bugcheck, W10/pro x64

This is something new. I figured it was a reboot from an OS update. But when I checked my update settings, I have notify for update, not automatic update set. My event log said there was a reboot from a bugcheck about 1130pm last night (while the PC was unattended). My PC runs 24/7.

Asus P8Z68V-pro
i5-2500k
16 GB ram
256GB SSD for OS and programs
1GB data drive
2GB internal backup drive
3GB external backup drive
Win 10 pro x64

I'd appreciate some help identifying the culprit here.

Thanks!

:)

 

Windows 10 bugcheck 0x000000ea

I have a R7 260X with 2gb. I encountered this crash while Alt + Tab in For Honor game.

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000ea (0xffff8e00daf06800, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 6bf93779-cb05-4f29-84ca-566fc6cc9437.

I have W10 x64 , i5 4440, 8 gb ddr3, z87 d3hp mobo.

 

Windows 10 Clean Install

I was told that a W10 license would probably have to be purchased. I was running W8.1 Pro x64 and performed the auto update to W10 Pro x64 and I ended up having to do a clean install.

 

Hi speedlever,

The crash is a 0x12B(FAULTY_HARDWARE_CORRUPTED_PAGE) which is usually caused by memory.
Please test your memory using MemTest86+ to be sure it is fine.





Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

 

Thanks axe0. Just burned a v5.01 cd and will test now.

 

Ok, 3+ hours into running memtest+86 v5.01 and no errors to report yet. Still on pass 1 though.

8+ hours, 3rd pass. No errors yet.

 

I left Memtest+86 running for just over 24 hours and 9 passes. No errors were found.

Any other thoughts?

 

Please check the BIOS for the RAM frequenty and check if it is supported by the motherboard.
In case it is, please test the hard drive





Diagnostics Test

HDD & SSD TEST


Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums



Note Do not run SeaTools on an SSD as the results will be invalid.



Run chkdsk Disk Check - Windows 7 Help Forums

 

The ram freq should be good. I set it all up several years ago when I built this PC and it has been running fine for a long time. IIRC, I used the XMP profile when I set it up.

I can run a chkdsk /r next time I boot if you think that will help. (My OS/programs drive is a 256GB SSD).

The ram is a matched set of 4x4GB G.Skill:

 

Please fill in your system specsPlease follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely.How to fill in your system specs:

 

System specs completed.

 

Thank you.

Please run chkdsk /r to rule out the hard drive(s)

 

I finally got around to running the tools (C:\ drive, properties\tools\error checking). It said it fixed errors.

Then for good measure, I ran chkdsk /r from an elevated cmd prompt. By the time I took a look at it, the chkdsk had finished and it was back to the log-in screen.

Here's is what was reported in the event log after I ran the error checking tool:

 

*Thumbs

Please check your other hard drives too, to make sure they're fine too.

 

OK. I ran the error checking tool on my 2 other internal drives (d:\ and e:\, both spinners). No errors were found.

I assume that is sufficient and equivalent to running chkdsk /r on them? If not, chkdsk wants to dismount those drives before running. I'm not sure of the implications of dismounting a drive.