6 Month old PC just died - repeating BSOD's

Crux

Active Member
Joined
Aug 26, 2014
Messages
49
Reaction score
2
Hi everyone.

I'm at my wits end and I hope someone can assist.

In February I built a new PC (specs to follow), and it's been running perfectly. About 2 weeks ago I was playing a game when everything just froze and the PC became unresponsive.

Now when I start the PC, it basically goes into a repeating cycle of doing a POST, trying to load Windows 10, crashing to a Windows 10 blue screen with a different error code each time, telling me an error has occurred and windows will attempt to repair the problem and restart, and then the cycle just starts again.

I've had the PC at a PC-shop who informed me it's definitely the motherboard that's faulty. So, I returned only the motherboard to the place where I bought it from, which in turn sent it back to their supplier who sent it back to us because their tests found no problem with it.

When I disconnect all the hard drives and try to boot from a Windows 7 installation flash drive, the same thing happens, namely, BSOD as soon as the OS tries to load. Even when I try to boot up with Fedora from a flash drive, it crashes.

I've swapped out the DIMM's, placed them in different slots, installed only the one and then the other, same story.

I've also replaced the power supply unit with another one, but still the problem persists.

When I boot up with a ms-dos flash drive, I can run memtest86 to diagnose any memory problems, only to find none.

I can also access the BIOS setup, make changes and save without a problem.

So i have no idea what the problem can be. Would I be able to boot ms-dos or access the BIOS if the CPU were faulty?

Specs as follows:

Motherboard: ASUS Maximus Ranger VIII
CPU: Intel core i7 6700K
RAM: 2 x 8GB Corsair Vengeance Lpx DDR4-2400 CL14 1.2V
Cooler: Corsair h80i GT
Kingston 240GB ssdNOW V 300 with Windows 10 installed
Secondary 1TB Seagate Barracuda HDD

Any help would be appreciated.

Cheers.
 
Last edited:
Try using the USB boot drive but with a empty hard drive. I suspect that when you're using the boot drive it is immediately detecting your W7 installation.
 
Do a clean install. Afterwards you can connect your drive and access the data
 
Have you set the BIOS to its default settings?
 
Sorry I just saw that you tried that with no drives connected
 
Do you have a different device? Put the ram in it, test. Put the HDD in it and boot from it (though you've eliminated it via disc/flash drive boot). If you can find another mobo with the same socket, try seating your CPU in it and see what happens.
Sadly that's the easiest way to check BSOD errors.
 
You might want to try another CPU. Seems about the only component not swap tested. Once had a problem with a bad CPU and it took about a month to have it replaced. It is not a common fault. Good luck!
 
Try either pull the motherboard battery or short the reset jumpers on the mobo ( While the Motherboard is not powered at all ).
 
It might be a good idea to regularly clean out your fans and just monitor your temps in future to help identify issues before they lead to this type of disaster. Anyway, try to boot from a bootcd like Hirens Bootdisk and then run the Windows XP on the disk to run your diagnostics in a graphical user interface. Good luck!
 
Your best option is to test each individual part in another PC.
 
where did you get that game from and did you download any torrent around that time? You may also need to try to use a Rescue Disk of some sort like Kaspersky to find out whether did you pick up any nasties
 
Hi everyone.
.. repeating cycle of doing a POST

read up your BIOS for what beep codes you are getting.

.. when I try to boot up with Fedora from a flash drive, it crashes.

What's the kernel panic message?

When I boot up with a ms-dos flash drive, I can run memtest86 to diagnose any memory problems, only to find none.

I can also access the BIOS setup, make changes and save without a problem.

I would think that eliminates Memory and CPU issues.

Specs as follows:

Is graphics onboard? I don't see it listed in specs.

Have you flashed your BIOS and if so for what reason?
 
I've had a similar problem before.

In the bios there are different boot support options.

If it's set to legacy change it uefi, if set to uefi change it to legacy.

I had to change mine to legacy and do a fresh install on my one pc and the other way around on another pc.

The legacy and uefi option together didn't work on either pc.

I have no idea what the difference is just that one way works and one doesn't.

It can't hurt to try.
 
Hi Drake2007

I've checked the Q-codes as displayed on the Q-code LED and it doesn't seem to stop at any specific error code. The last code displayed before it restarts again is A0, which for my board means 'IDE initialization is started'.

Unfortunately, I didn't make a note of the Fedora kernel panic message, but here's a list of some of the errors given on the Windows 10 BSOD's:

MEMORY_MANAGEMENT
REFERENCE_BY_POINTER
KMODE_EXCEPTION_NOT_HANDLED
IRQL_NOT_LESS_OR_EQUAL
THREAD_EXCEPTION_NOT_HANDLED (ACPI.sys)
DRIVER_OVERRAN_STACK_BUFFER
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (FLTMGR.SYS)

The graphics card (ASUS Strix GTX 970) was the first thing I removed when the problem began and I haven't re-installed it since. I'm currently running the montor from the m-board display port.

Regards.
 
Hi Scary_Turtle, I forgot to mention that I tried this already, but thanks anyway.
 
When I boot up with a ms-dos flash drive, I can run memtest86 to diagnose any memory problems, only to find none.
It gives indicatiion of faulty CPU, while there is a chance of corrupt BIOS/ACPI configutation data. It should be detected during checkup, but you didn't mention motherboard was sent to the authorised repair centre. Reset BIOS to defaults, as Windows 10 is able to corrupt BIOS data. If doesn't help you should also flash BIOS using DOS utility.
 
Last edited:
Top
Sign up to the MyBroadband newsletter
X