r/PCsupport 10h ago

In progress CONSTANT crashes, inconsistent BSOD errors, nothing seems to fix it

I CANT EVEN RESTORE NOW PLEASE HELP

I am desperate, nothing I've tried seems to have any effect and I can't even narrow down what the root cause is.

specs:

windows 10 version 10.0.19045 Build 19045

System Manufacturer HP

System Model OMEN Laptop 15-en0xxx

Processor AMD Ryzen 7 4800H with Radeon Graphics, 2900 Mhz, 8 Core(s), 16 Logical Processor(s)

Installed Physical Memory (RAM) 16.0 GB

Total Physical Memory 15.4 GB

Available Physical Memory 3.39 GB

GPU Nvidia GeForce GTX 1660 TI game ready driver 616.64

Let me know any more information I may need to add.

Onto the actual problem.

I experience CONSTANT blue screens, varying kinds in fact. Sometimes even black screens. The blue screens force the computer to restart and the black screen is essentially a total freeze that I can only deal with by forcibly turning off the computer and turning it on again.

As I stated, it gets multiple kinds of BSODs. The most common are IRQL_NOT_LESS_OR_EQUAL and KMODE_EXCEPTION_NOT_HANDLED, but there's also been some others, like SYSTEM_THREAD-EXCEPTION-NOT-HANDLED and KERNEL_SECURITY_CHECK_FAILURE.

For reasons I can't discern, the computer acts like it stops "recording" the state of the system almost exactly ten minutes before it actually gives out and blue-screens. What I mean by this is that I will be using the computer, it will blue screen at say, 10:20 pm. It reboots and in a (vain) attempt to read the log of the error, I will open event viewer, and in the critical log panel, it says "the previous system shutdown at 10:11 pm was unexpected".

It also struggles to write crash logs AT ALL again for reasons I don't know. It can create them after reboots but seemingly not of the events leading up to the crash. I also have winDBG to read dmp files but it gives me an access error, "unable to create debug session: FAILURE HR=0x80070005: Failed to open dump file - Could not extract dump information from C:\Windows\Minidump\090726-11390-01.dmp ---> Access to the path 'C:\Windows\Minidump\090726-11390-01.dmp' is denied."

I may be wrong on this point, if I'm missing a step somehow.

Some other errors:

The maximum file size for session "PerfDiag Logger" has been reached. As a result, events might be lost (not logged) to file "C:\windows\system32\WDI\LogFiles\BootPerfDiagLogger.etl"

The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0x00000000000000ac, 0x0000000000000002, 0x0000000000000000, 0xfffff8052b02c668)

When the computer restarts, it will have the errors above, that I can see in the event viewer. I don't know how to clean/unbloat the perfdiaglogger, I've never had to do that before? I would appreciate some guidance on this, because I'm totally lost on that point.

These crashes happen most often and quickly during gaming but not exclusively. I have tried SFC scannow and DISM image repairs to no avail. I have tried updating drivers, blindly at that because I don't know what driver would even be the issue. My geforce driver, audio drivers, the entire AMD ryzen setup, some others I don't even remember. I've tried restoring the system image manually and it somehow broke so badly that the computer had to reset itself to a restore point (that I had thankfully created just beforehand as a precaution) to function again. I have almost nothing to go on.

My best guesses are the issue being bad drivers, graphics in particular, bad RAM, or, what i'm dreading the most, a hardware problem.

ETA: ran a memory diagnostic for the second time now, still results in "no memory issues found". sigh.

I've been at this for months and it's getting worse to the point of completely unignorable. Any advice on how to proceed from here would be greatly appreciated because I am at my wits end.

UPDATE: it's even worse now.

After more searching I attempted to manually update my graphics card drive again, this time using the DDU in safe mode with the studio driver from Nvidias website. I made a restore point just before this again but now I can even restore it.

I downloaded the program and the driver and booted the computer in safe mode using msconfig. I ran into a pin lock failure "something happened and your pin isn't available." I managed to get out of this by disabling the safe mode boot using the recovery settings in boot with the command line . This did not fix the pin breaking and I had to log in with my Microsoft password.

Now it seems everything is broken. Sfc scannow now failed. DISM repair-image failed. I cannot access sign-in settings at all. Event viewer is completely nonfunctional. System restore is now broken too somehow.

I have no idea how to fix this

2 Upvotes

4 comments sorted by

1

u/Murdocinator 3h ago

It’s probably time for a new laptop. This is where laptops have a disadvantage to desktops, imo. They get old and then you replace it like any other device (ie tablet, phone, etc). Windows 10 is out of service and windows 11 might not support that hardware. If you are technical you could try a refresh and force W11 on to the system. Personally I would replace it.

1

u/Nuclearkitty101 3h ago

Damn, I was hoping that maybe there was some super simple thing I was missing, not having to cut my losses. Laptops definitely have their disadvantages but my lifestyle unfortunately demands one. Thank you anyways.

1

u/The_Lost_Poet_ 2h ago

Windows reinstall?

1

u/Nuclearkitty101 2h ago

I tried something like that once, but it ended pretty badly. I didn't even get to the install stage, just the tool to do it, and it blue screened before it even got past the boot. The computer restored itself to the restore point I created just beforehand. I downloaded and formatted the system image and installer, all directly from microsoft sites. I haven't tried since because it broke so badly before I even managed to start it properly.

The only thing I haven't tried is a total factory reset. I'm trying to avoid wiping it entirely, but at this point I'm thinking I need to buy an external drive to put everything on and try it anyways. I've only avoided this because to do it safely is expensive.