Frequent BSOD with various errors after failed Chrome installation

Mayday121 · 23 Aug 2017

My internet crashed while installing Chrome (thanks, Spectrum) and ever since, I've been suffering from repeated BSOD's under all sorts of conditions. With that said, I'm inclined to think the timing may be a coincidence.

I've used the Win10 installer to repair/reinstall Windows to no avail. It even crashed several times when booted from the Win10 USB, which leads me to believe it may be a hardware issue.

Errors I've seen include:

IRQL_Not_less_or_equal
Driver_Overran_Stack_Buffer
Attempted_Write_to_Readonly_Memory
Page_Fault_In_Nonpaged_Area
System_Service_Exception
0xc000021a

I've also had the screen become 'blurry' or half of it discolored several times when Windows launched, along with Explorer repeatedly crashing or locking up. Everything is very glitchy.

The Win10 installation is fresh and I have almost no drivers, as it won't run long enough to even install drivers. Sometimes it crashes before the login screen, sometimes it will log on then crash, sometimes it runs for a while. Messing with it has improved it somehow (before it wouldn't even make it into Windows) but it's still essentially unusable.

When running sfc /SCANNOW (through an admin level cmd prompt), it gets partway through verification (47% last I tried) and says "Windows Resource Protection could not perform the requested operation. I've tried scanning from the command prompt via Windows Repair and had similar results.

All of the BIOS settings have been restored to standard speeds with XMP off, I've updated to the latest BIOS version, removed the graphics card and gone back to onboard video, swapped/installed known good RAM, removed and reinstalled the processor -- pretty much done everything I can think of.

I've attached the .dmp files that were in the "Minidump" directory -- I installed windbg but only see "0x8007001E" which appears to be a problem with the latest version of WinDBG.

I'm hoping someone can help direct me toward a path to take, but I'm beginning to think it's a hardware issue we'll have to solve by throwing some parts at it.

Thanks in advance!!!

BSODHunter · 23 Aug 2017

Attention:

Before posting a BSOD thread, please read the instructions here: Blue Screen of Death (BSOD) Posting Instructions

If you need to add new information, please make a new post in your initial BSOD thread. Please do not make an extra new thread.

Mayday121 · 23 Aug 2017

I'm still trying but I can't get the computer to run long enough to run the DM Log collector program.

Spectrum · 23 Aug 2017

If you are seeing crashes even when you boot to a live image you'll want to start testing hardware components. I know you stated you've used known-good RAM, but please test it anyways with MemTest86+ - Test RAM Windows 10 BSOD Tutorials

It's very possible your motherboard is causing these problems, and they may show up when testing the RAM as it could be corrupting the data as it is going to your CPU registers/caches. This would need to run for 8+ passes, which can take quite a while depending on the amount of RAM you have installed.

I'd also suggest testing your processor. Assuming you are using an Intel CPU, run their diagnostics utility.

Download Intel Processor Diagnostic Tool

If you aren't able to run this long enough on Windows, you can try using the Linux version using a live image, the link to that is listed on the above site.

My internet crashed while installing Chrome (thanks, Spectrum) and ever since, I've been suffering from repeated BSOD's

You're welcome.

Mayday121 · 23 Aug 2017

Thank you so much, Spectrum! Oh the irony there...

I have memtest running. Apparently there is a UEFI version of the processor diagnostic tool, so I believe I will try it and report back with findings.

I was figuring it was hardware -- the direction on diagnostic tools is a huge help and hopefully will let me pinpoint the problem without just having to swap processors and motherboards.

I'll let Memtest run overnight to get enough passes, run the processor diagnostic in the morning and report back.

Thanks again!

Mayday121 · 23 Aug 2017

Got bored and stopped the memtest after 1 successful pass (will re-run for 8+ later to confirm) to run the processor scan. I got a bit of a strange result...

Processor is an i7-7700K

--- Reading CPU Frequency ---

Expected CPU Frequency is --> 4.20GHz

Detecting CPU Frequency ...

Detected CPU Frequency --> 5.5999

CPU Frequency Test Passed with Warning!!!

The processor frequency could be affected by power management features. In

order to ensure the processor frequency is not affected by a power management

setting, enter BIOS, load defaults, and disable any 'Over-Clocking' or power

management features that may affect processor frequency. Also, set any

software applications which control power management features to default.

Also, a bit further down...

--- Running Base Clock test ---

Expected Base Clock --> 133 MHz
Detected Base Clock --> 133 MHz
Tolerance accepted --> 7
Base Clock test Pass ---

Everything in the UEFI is set back to default/auto, and it states the BCLK 100Mhz. I manually set the base clock to 100Mhz and re-scanned, and got the same results. I've attached a zip file of the latest scan results along with just the IPDT result with the above results.

A 133Mhz baseclock versus the standard 100Mhz would explain the high processor speed, but why is it expected a 133Mhz baseclock in the test when it is set to 100Mhz in the UEFI? I'm guessing that would be a motherboard issue of some sort...

Spectrum · 24 Aug 2017

There's likely a setting (or settings) in your firmware that allows you to disable turboboost/speedstep as well as power management. You will of course want to re-enable them after the diagnostic.