Windows 8.1 freeze, attempted restart, asks for a boot media

[IMTECH]

I've installed Windows 8.1 Pro about a month ago and then upgraded to Windows 10. I was having a lot of issues on 10 (even after a clean install), so I decided to do a clean install of Windows 8.1 and wait for a while until Windows 10 becomes stable. However, I am experiencing almost the same problems in both 8.1 and 10.

Occasionally, Windows freezes, "BSODs" and restarts. Then it asks for a boot media ("Reboot and select proper boot device or Insert Boot Media in selected device and press a key"). It's easy from here. I insert the Windows installation disc and enter the Windows Installation Setup. I select an option to repair my computer and then restart it from there. Now it boots normally and everything seems to be working properly.

The problem is that it keeps happening randomly. I cannot figure out what causes this to occur. Something I've noticed, though... Disk usage on boot is 100% (indexing maybe), but that wouldn't be enough for a freeze and BSOD later to occur. I haven't played any games recently, so I cannot say for sure whether this could happen during a gameplay or not.

I have all the latest drivers installed (MB and graphics drivers). The only thing I haven't updated is BIOS (the latest update does say something about memory compatibility improvement...). I've been monitoring the temps using HWMonitor and no major irregularities, in my opinion.

I am seriously starting to doubt some piece of my hardware (HDD or RAM?), but I'd like some thoughts on this and, of course, maybe even a solution.


PC (nothing is overclocked):

CPU i5-4670K
Cooler Cooler Master Hyper 412S
MB MSI Z87-GD65 GAMING
GPU MSI GTX 760 GAMING 2GB OC
RAM Kingston HyperX Blu 2x4GB DDR3 1600
HDD Seagate Barracuda 1TB
PSU Seasonic X-series SS-750KM3 (750W)
Case CM HAF 932 Advanced
OS Windows 8.1 Pro

I may update this thread later with some new details or finds. For now, any kind of help is appreciated.

 

[basroil]

It certainly seems like a HDD issue more than a memory one (by just a small bit), have you tried running diagnostics on both? CheckDisk is a good place to start (and reading the SMART data), if there are several corrupted sectors it could be a sign that the disk is starting to wear out. Might as well check for memory errors too, most systems come with a boot time memory checker, and that shouldn't take too long if you only have 8GB ram (one of my machines has 32GB, so even with a multithreaded memory check it still takes forever!)

 

[IMTECH]

It certainly seems like a HDD issue more than a memory one (by just a small bit), have you tried running diagnostics on both? CheckDisk is a good place to start (and reading the SMART data), if there are several corrupted sectors it could be a sign that the disk is starting to wear out. Might as well check for memory errors too, most systems come with a boot time memory checker, and that shouldn't take too long if you only have 8GB ram (one of my machines has 32GB, so even with a multithreaded memory check it still takes forever!)

Thanks for the suggestion. I ran both Check Disk and Memory Diagnostic Tool. The latter reported no errors (I guess RAM is fine then) and Check Disk took a while to complete (about 30-40 min) but I got no report of any sort so I am not sure of the situation status.

Also, since I have only one HDD but 2 partitions (c,d), do I have to run Check Disk for both or it already scanned the whole hard drive? I issued this command in an elevated cmd: chkdsk /f /r c:

 

[basroil]

You should try it per volume, it's a bit more complicated but it allows you to check the non-lettered "drives" like the boot sections as well. Each partition will probably need to be scanned independently. You can also try chkntfs to see if there are other errors.


If the memory and drives are clean, it might be harder to pinpoint the issue, since simple PSU failure doesn't normally corrupt your boot process. It could be mobo failure, but that's harder to diagnose. Go ahead and try updating to the newest motherboard firmware, if the mobo can't complete the upgrade then you know there's something wrong.

 

[IMTECH]

You should try it per volume, it's a bit more complicated but it allows you to check the non-lettered "drives" like the boot sections as well. Each partition will probably need to be scanned independently. You can also try chkntfs to see if there are other errors.


If the memory and drives are clean, it might be harder to pinpoint the issue, since simple PSU failure doesn't normally corrupt your boot process. It could be mobo failure, but that's harder to diagnose. Go ahead and try updating to the newest motherboard firmware, if the mobo can't complete the upgrade then you know there's something wrong.

I just flashed the BIOS to the latest version and everything is fine so far. I don't know if it fixed the freezing/BSOD, but I guess that I will find out eventually.

I'll try to scan the whole hard drive when I get the chance to see if it is the culprit here.

Thank you for your suggestions up till now, basroil.
Any other suggestions/ideas are appreciated.

 

[basroil]

Just checked up the mobo and it looks like it's bios already on it's 11th revision (12th version), so it might have been a known or related issue that was fixed in later revisions. Hopefully nothing happens, but if it does make sure to update the thread with the newest errors.

 

[IMTECH]

Just checked up the mobo and it looks like it's bios already on it's 11th revision (12th version), so it might have been a known or related issue that was fixed in later revisions. Hopefully nothing happens, but if it does make sure to update the thread with the newest errors.

So... got BSOD again. "Your PC ran into a problem and needs to restart."

Some more details: I left the PC overnight to download a game via Steam and also left HWMonitor on to monitor the temps. Max temps were fine: ~42°C for CPU (maxes around 51-52°C during gaming); GPU had no reason to be that active, so the max temp was ~32°C (maxes around 73°C when playing graphically intensive games with V-sync off). CPU also reached around 95-96% utilization.

After waking up, I went to browse the Net and only had few tabs open when BSOD suddenly occurred. The rest is the same as in the OP.

UPDATE: I ran CrystalDIskInfo and got status "GOOD". I also installed Blue Screen View but when I opened it there were no files. Then, I configured Windows to create small dump files and now I guess I'll have to wait for another BSOD to occur?

 

[basroil]

Try using the system with only one stick for a while (if both passed memtest), and then try with the other. If one has issues and not the other, it's memory related (and will cost you a new pair unless you want to manually check timings to make sure the two are balanced)

Also, does your screen flicker every once in a while? Might sound strange, but if the event viewer shows issues driver faults or the screen flickers, it might be video memory that's the issue. Try running blender's GPU test, if it's a video memory issue that thing will shred your computer a new one.

 

[IMTECH]

Try using the system with only one stick for a while (if both passed memtest), and then try with the other. If one has issues and not the other, it's memory related (and will cost you a new pair unless you want to manually check timings to make sure the two are balanced)

Also, does your screen flicker every once in a while? Might sound strange, but if the event viewer shows issues driver faults or the screen flickers, it might be video memory that's the issue. Try running blender's GPU test, if it's a video memory issue that thing will shred your computer a new one.

Could you give me a link to a guide on how to test memory, please? I've never done that before. Also, how to do that "blender's GPU test"?

Again, thank you for the help.

 

[basroil]

Memory checkers are built into pretty much every computer if you go to the boot menu and select "diagnostics". If not, download memtest and burn it to a CD.

As for blender, download blender and visit their forums, they usually have multiple threads regarding GPU tests.