Share via

Constant BSOD after about 3-5 minutes of booting

Anonymous
2024-05-09T17:11:41+00:00

This problem has now been like this for months and I was trying to find a solution to this. The error codes are seemingly random; Namely, CRITICAL_PROCESS_DIED, UNEXPECTED_STORE_EXCEPTION, SYSTEM_SERVICE_EXCEPTION and KERNEL_DATA_INPAGE_ERROR from what I remember. Here is everything I have tried so far-

  • Updating old drivers (that did fix a lot of error messages but not all. And it certainly didn't put a stop to the BSOD)
  • Installing and reinstalling the latest Windows updates (including the optional ones)
  • Scanning for corrupted hardware from multiple methods
  • Disabling a few startup apps, including my anti-virus
  • running virus and malware scans from Avast and Malwarebytes
  • first enabling UAC and then disabling it because it didn't help, although doing that raised an issue of its own (it seems)

Now almost every app is unable to save files to the PC without my permission and it seems that the security settings have been ramped up without my knowledge, not allowing anything to do anything on its own (I have no idea how it works)

Before the permission problem, the BSOD was still the same but event viewer logs showed some error messages relating to luafv. Enabling UAC seemed to fix it and even after disabling it now, I don't see any log messages about it. Now, there are mainly three types of red error messages in the event viewer logs-

Error: "The previous system shutdown at (time) on (date) was unexpected.", Error: "Dump file creation failed due to error during dump creation." and Critical: "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.".

Apart from the red ones, there are also quite a few yellow ones saying something like Warning: "LSA package not signed as expected", Warning: "The driver \DRIVER... failed to load for the device USB\VID...", Warning: "Credential Guard and/or VBS Key Isolation are configured but the secure kernel is not running; continuing without them." and a few others.

Also, my Windows minidump folder is empty.

This problem (after it started) has never really been fixed. If I get lucky, it would last for a good amount of hours before inevitably going into a BSOD but for the most part, it is just me trying to fix the issue while constantly getting BSODs and having to start all over again every 5 minutes or something.

I am trying to run the Startup Repair Tool from the recovery settings of advanced startup (whatever it's called) and it lands me on the recovery key page (BitLocker I assume), where I correctly enter mine and double-check only for it to tell me that it's invalid. This exact same key has been working perfectly fine earlier and on the website aka.ms/myrecoverykey, it still is the same key

Right before it crashes, I head the audio buzz if one is playing and my cursor behaves weirdly then stops

Here are my specs if that's necessary-

Windows 11 Home 22H2, Lenovo Ideapad, 512GB SSD (no partition), 8GB RAM, AMD Ryzen 7 4700U with Radeon Graphics 2.00 GHz Processor

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

13 answers

Sort by: Most helpful
  1. DaveM121 880.3K Reputation points Independent Advisor
    2024-05-12T15:35:06+00:00

    Click your Start Button, then just type sysdm.cpl and press Enter.

    On the resulting dialog, select the Advanced tab.

    Click the Settings button in the Startup and Recovery section.

    Please provide a screenshot of the next dialog.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-05-12T13:51:00+00:00

    I did just that but the minidump folder remains empty in any case

    Was this answer helpful?

    0 comments No comments
  3. DaveM121 880.3K Reputation points Independent Advisor
    2024-05-11T11:06:21+00:00

    Okay, please wait for your PC to crash a couple of times normally without Verifier enabled, hopefully your system will create minidump files, then upload any new minidump files you may get and upload them for analysis.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-05-11T10:56:56+00:00

    Hi and thanks for replying to my issue. I tried the Driver Verifier but that doesn't seem to work.

    I created a restore point. Enabling the verifier after starting the PC wasn't possible since it takes some time to set-up and the BSOD was giving me 2-3 minutes at best. So I ran the advanced restart from recovery settings and ran the verifier through the elevated command prompt. I set it up and waited for it to crash three times, and it did. In between the crashes, anytime I ran the command 'verifier /query' or 'verifier /querysettings', it would show 'None' beneath 'Verified Drivers'. After disabling the verifier and restarting, the minidump folder was still empty. I repeated these steps some more times and it still doesn't seem to work.

    Was this answer helpful?

    0 comments No comments
  5. DaveM121 880.3K Reputation points Independent Advisor
    2024-05-09T17:45:47+00:00

    Hi, I am Dave, I will help you with this.

    Since no minidump files are being created, to try to force Windows 11 to create minidump files and show any faulting drivers, the best option would be to turn on Driver Verifier, let your PC crash 3 times, then you must turn off Driver Verifier, and finally, upload any newly created minidump files

    Before you run Driver Verifier, please create a new System Restore Point

    https://answers.microsoft.com/en-us/windows/for...


    Note, if you have any difficulty getting into Windows with Driver Verifier enabled:

    Start your PC, just as Windows attempts to load (spinning dots), press and hold Power Button for 5 - 10 seconds to perform a Hard Shut Down

    Do this twice

    On the third start Windows will boot into the Recovery Environment and from there you can access System Repair, Safe Mode, Command Prompt... etc.

    Go to Troubleshoot - Advanced Option - Startup Settings and click Restart

    Upon restart, press 4 to enter Safe Mode

    Open Command Prompt as Administrator and run these two commands, then restart your PC.

    verifier /reset

    verifier /bootmode resetonbootfail

    Was this answer helpful?

    0 comments No comments