Share via

Various Stop Codes when booting up

Anonymous
2024-03-09T18:17:16+00:00

The good news is that the problems do not appear outside of booting or sleep hibernation. The laptop is on and active, no issues. But I am worried that this might presage something truly bad coming in. I'd like hassle-free booting and not having to reboot when I close the laptop, anyway.

This has been going on for several months, actually; variously my hoping the auto-repair would resolve the issue and not sure when I could bring the laptop in for checking until recently. When I try to boot up, I'll often get anywhere from one to three different stop codes--not always the same ones, as you'll see--before it finally boots properly (often from the Restart/Advanced Settings screen). Meanwhile, if it ever sleeps or hibernates, it won't wake up unless I do a hard restart. A little over a week ago, I finally brought it in to a repair shop, and the situation seemed to be software-related; for some reason, the laptop insisted on starting up a small swarm of programs each time, and that was obstructing boot/waking. He adjusted settings on my computer so sleep would not be (and currently isn't so long as I don't actually close the laptop) an issue. For a few days, all seemed well. Then the stop codes came back, gradually reaching their old density. Here's what I've gone through so far:

--3/2: KMode Exception Not Handled

--3/3: Hypervisor Error twice in a row (quite a trick when I don't have virtual anything on here!)

IRQL Not Less or Equal

--3/5: Had to do a hard reset when it wouldn't leave hibernation

--3/6: First boot got stuck on a black screen, although I could tell it was receiving power; had to hard reset

Would not wake from closing without a hard reset

Clock Watchdog Timeout that froze at 0% reporting and needed another hard reset

--3/8: Same first boot issue as on 3/6, likewise the Watchdog frozen at 0%

Interrupt Exception Not Handled

--3/9: Hypervisor Error; when it self-reset, it froze at the Asus logo screen

Came to the blue Restart screen, tried that option without first going to Advanced Settings (Advanced Options?), but got the 0% Watchdog freeze

Hypervisor Error, same logo freeze

Hypervisor Error

I feel like all those stop codes have some overlap point for what can cause them, but I don't know what it would be.

Machine model: Asus TUF Gaming A15 laptop

Processor listed: AMD Ryzen 7 6800H with Radeon Graphics

Graphics card (just in case): AMD Radeon(tm) Graphics, NVidia GEForce RTX 3050 Ti Laptop GPU

RAM: 8 GB

Not sure what error logs I should supply. I got into Event Viewer just fine; the issue is what to paste, or whether there's a way to bundle everything as a single text file.

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

1 answer

Sort by: Most helpful
  1. Anonymous
    2024-03-10T07:25:22+00:00

    Hello ,

    Good to see you in Microsoft Community.

    Firstly, could you let me know the specific system version (OS Build)? You can check it by pressing Win + X > System > Windows specifications*, click “Copy” and paste it in your next reply*.

    Then please check the basic hardware information of your device. Win + Q to open the search box, type “msinfo32”, then open “System Information”, please take a screenshot of it and attach it to your next reply.

    You can follow the steps below:

    1. Check Event Viewer to see if there are any error messages at the same time that you shut down the system. Win + Q to open the search box, type 'eventvwr', press Enter to open Event Viewer*, and see whether there are any errors in* System in Windows Logs*.*
    2. Update all computer hardware drivers You can reinstall all drivers, especially the graphics card driver. Visit the official website of your device manufacturer to download the corresponding model driver, and then install it manually, and restart to see if it works.
    3. You may Perform a clean boot (microsoft.com) to see if it is normal, this is a troubleshooting step. In this mode, we can further confirm whether it is caused by system problem or third-party software or personalized settings. So, please be patient. Disclaimer*: A “clean boot” starts Windows with a minimal set of drivers and startup programs. It helps to determine whether a background program is interfering with your game or program and to isolate the cause of a problem.* These steps of "clean boot" might look complicated at first glance. However, to avoid any trouble for you, please follow them in order and step-by-step so that it will help you get you back on track.

    If anything is unclear, please do not hesitate to let me know.

    Best Regards,

    Mosken_L - MSFT | Microsoft Community Support Specialist

    0 comments No comments