Sick PC (Blue screens, multiple issues) Baffled, help!!

OnionHead

Honorable
Jan 28, 2014
67
0
10,630
Morning :) It's 3am and I'm ready for kicking this computer. I'll try and keep this as brief as possible. I was originally going to stick this in the windows 10 forum, but now I'm not so sure, sounds more hardware related now.

Recent upgrade machine that's run flawlessly for a couple of weeks now.

Windows 10
6700k
Asus z170i pro gaming mini itx
16gb crucial ram (2x 8gb)
Samsung Evo SSD
1TB HDD
H100i cooler
R9 280

As I said the computer ran perfectly since build, this evening though its failed horribly.

The machine is in a constant blue screen of death loop with multiple issues. Here's a selection of faults :

IRQL NOT LESS OR EQUAL
PAGE FAULT IN NONPAGED wdf01000.sys
SYSTEM THREAD EXCEPTION NOT HANDLED storport.sys / ACPI.sys
PAGE FAULT IN NONPAGED AREA

I've tried the obvious, firstly trying to go back to the restore point (Before windows update a couple of days ago). I can't get that far as the computer reboots with blue screen before I get that far.

Unplugged the SSD (This is where windows 10 is installed), and it's still giving the same blue screen messages.

Removed graphics card and used on board (No luck)

Removed ram trying individual sticks, re seated etc (Same, no change)

So screw this I thought I'd try a fresh install, a real pain but left with not much options I thought I'd give it a go. Plugged in my USB drive with windows 10 install, set boot to USB drive in bios, guess what, still getting blue screen. What!!!!!!!!!!!!!!!!!!!!!!!!!


Any help would be much appreciated as I'm almost broken here :)


 
Hello... Relax B )... You got a hardware communication problem... can you just BOOT to just the MB BIO's with a Good screen?
1) try clearing your BIO's CMOS/battery removal... this will set the MB to factory presets.

I have seen problems with Windows updates of hardware drivers, and never recommend you to downloading them or using them, use the ones from the maker of the product. Shut Off your Windows auto update setting to avoid this... only manually pick and choose the update you are interested in. ( if it ain't broken don't try and fix it with updates) Common sense here.
 

OnionHead

Honorable
Jan 28, 2014
67
0
10,630
Thanks for the reply Ironsounds, I've just tried clearing CMOS, same blue screen of death loop.

Will try the battery now, I'm used to the old battery sockets, on this board it's a small 2 pin plug attaching the battery to the board (Via a wire), I presume I just unplug and see how it goes.

Edit :

Yes, I thought I had windows update disabled :( I'll make sure next time.

 

OnionHead

Honorable
Jan 28, 2014
67
0
10,630
Removed battery, no luck, blue screen loop. This is bizarre. Faulty board perhaps? Saying that I've been building since the Socket A days and have very rarely experienced hardware failure.

I even plugged in my USB dvd drive with Windows 8.1 DVD "Click any button to install windows/or enter setup" sorry can't remember, I'm sure you know the one :) If I hit a button it skips to the Asus boot screen and then back to blue screen death loop.

Sorry you asked me originally, to confirm the bios seems to work perfectly, no reboots etc
 

OnionHead

Honorable
Jan 28, 2014
67
0
10,630
Will run memtest this evening, I think it's safe (Assuming memtest results are ok) that the board is faulty. I presume an Intel CPU is less likely to be faulty or produce these faults. It's a first for me :(

Glad now I purchased all through Amazon as there was some cheaper less reliable vendors that tempted me at the time of build. I've dropped Asus an email also
 

OnionHead

Honorable
Jan 28, 2014
67
0
10,630
Do you ever get the feeling your talking to yourself? Don't worry I'm used to it :)

To update (As you may be arriving via google in a similar emotional mess as me), the 6700k is the culprit. After receiving and fitting a brand new board I was getting the same faults. This made a stressful day even more perfect. Anyway, almost broken I plodded on changing settings in the bios. The 6700k will run on a single core, boots to windows perfect. So unless I'm majorly mistaken here, the CPU was at fault.