New
#1
Frequent BSOD with various errors after failed Chrome installation
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!!!
Last edited by Mayday121; 23 Aug 2017 at 10:27.