Plagued with over a year of countless BSOD loops.

Question

Plagued with over a year of countless BSOD loops.

Anonymous

Plagued for over a year with countless BSOD loops. I’ve tried most things, swapped hardware, reinstalled windows, clean installs, memory tests, disk cleanups, new drives, disconnecting USB hubs, Windows 11, Windows 10, disabling fast boot, turning off anything that even smells like overclocking or increased performance, disabling XMP, removing, disabling, updating, everything and their cousins. You name it, it still happens. The latest manifestation of this disaster happened out of nowhere, with no significant event that I can recall or identify bringing it to the surface:

Starts with one of numerous BSOD errors:

IRQ_NOT_LESS_OR_EQUAL

KERNEL_blablabla something or other

ATTEMPED_WRITE_TO_READONLY_MEMORY

Then, we enter a BSOD loop. After 3x, performs auto-recovery. Fails. Asks to restore. Restore fails. Goes to recovery environment. Then:

Automatic Repair: LOL. Yeah right.

Command Prompt:

Crashes after x amount of time, regardless of what I’m doing
SFC /scannow = Errors out
DISM = Errors out

Uninstall Updates: Fails

Startup Settings:

Crashes if Boot to Safe Mode with Networking
Crashes if Boot to Safe Mode with Command Prompt
Crashes if Enable Boot Logging
Crashes if Enable Debugging Mode
etc.

System Restore: Successful restore, then continues boot loop.

Currently, the only fix is:

1. Enter boot loop

2. System Restore from the recovery environment

3. Boot loop again for 3x

4. Startup Settings in the recovery environment

5. Choose Enable Boot Logging.

Yes, ONLY THIS performed in that exact way will get me into my computer. You can probably imagine how long it took for me to figure that out.

I will then experience another BSOD loop in the first minute of getting into Windows. After going through this an infinity number of times, I have been able to stop it from crashing. I immediately uninstalled my GPU drivers from Device Manager, and also immediately went into MSConfig and disabled virtually all non-Microsoft services. So, I do believe I turned on a few lights in regards to what the issue could be, I just do not know where to go from here. It's worth noting that my PC is performing very sluggishly, without showing the appropriate amount of resources being utilized. Something is definitely awry.

It seems completely ridiculous that Windows cannot discern **** is causing the crash, and offer to disable it. Also, I find it equally ridiculous that this information is not even accessible to an average or even well above average PC user. Bug in driver? Sure cool, but where? What? Why?

Please help. I would like to regain my sanity. I’ve spent far too much time dealing with this and need to get it settled once and for all. What usually ends up happening is I lose a day trying to fix, eventually just say “screw it” and perform a clean install, and once I am back to square one and after hours of reinstalling software and authenticating, etc. I have zero energy to continue pursuing the issue that I know is just waiting to come back again.

I was in the throes of hell with this early this week, which had me neglecting my business, and unfortunately missed a very important, very time-sensitive email that ultimately ended up costing me over $50,000. I am not kidding.

Please, do not just reply with the standard cookie-cutter template that lists a slew of generic fixes, among which a multitude are blatantly unrelated to my issue. It really is destroying this forum.

Useful info about my PC:

SYSINFO:

OS Name Microsoft Windows 11 Pro Version 10.0.22000 Build 22000

Other OS Description Not Available

OS Manufacturer Microsoft Corporation System

Name MAINFRAME-PC System

Manufacturer ASUS

System Model

System Product

Name

System Type x64-based PC System

SKU

Processor 12th Gen Intel(R) Core(TM) i9-12900K, 3201 Mhz, 16 Core(s), 24 Logical Processor(s)

BIOS Version/Date American Megatrends Inc. 1601, 7/7/2022

SMBIOS Version 3.4 Embedded Controller Version 255.255

BIOS Mode UEFI

BaseBoard Manufacturer ASUSTeK COMPUTER INC.

BaseBoard Product TUF GAMING H670-PRO WIFI D4

BaseBoard Version Rev 1.xx

Platform Role Desktop

Secure Boot State Off

PCR7 Configuration Elevation Required to View

Hardware Abstraction Layer Version = "10.0.22000.778"

Installed Physical Memory (RAM) 128 GB

Total Physical Memory 128 GB

Available Physical Memory 117 GB

Total Virtual Memory 147 GB

Available Virtual Memory 132 GB

Page File Space 19.0 GB

Page File C:\pagefile.sys

Kernel DMA Protection Off

Virtualization-based security Not enabled

Device Encryption Support Elevation Required to View

Hyper-V - VM Monitor Mode Extensions Yes

Hyper-V - Second Level Address Translation Extensions Yes

Hyper-V - Virtualization Enabled in Firmware Yes

Hyper-V - Data Execution Protection Yes

Crash Dump Analysis

Crash dumps are enabled on your computer.

Crash dump directories:

C:\WINDOWS

C:\WINDOWS\Minidump

On Sat 8/20/2022 1:26:57 PM your computer crashed or a problem was reportedCrash dump file: C:\WINDOWS\Minidump\082022-34421-01.dmp (Minidump) Uptime:00:00:29 (hh:mm:ss)Bugcheck code: 0xA(0x203A02D8FE, 0xFF, 0xFF, 0xFFFFF807824B4D2A)Bugcheck name:IRQL_NOT_LESS_OR_EQUALDriver or module in which error occurred: ntkrnlmp.exe (nt!KiBugCheckDispatch+0x69)This is the core Windows kernel module. No offending driver has been revealed.Description: NT Kernel & SystemProduct: Microsoft® Windows® Operating SystemCompany: Microsoft Corporation**Bug check description:**This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.**Analysis:**This is a typical software problem. Most likely this is caused by a bug in a driver. The crash analysis did not reveal an offending driver. Possibly this problem was caused by a driver that cannot be identified at this time.

On Sat 8/20/2022 1:26:57 PM your computer crashed or a problem was reportedCrash dump file: C:\WINDOWS\MEMORY.DMP (Kernel memory dump) Uptime:00:00:29 (hh:mm:ss)Bugcheck code: 0xA(0x203A02D8FE, 0xFF, 0xFF, 0xFFFFF807824B4D2A)Bugcheck name:IRQL_NOT_LESS_OR_EQUALDriver or module in which error occurred: ntkrnlmp.exe (nt!KiBugCheckDispatch+0x69)This is the core Windows kernel module. No offending driver has been revealed.Description: NT Kernel & SystemProduct: Microsoft® Windows® Operating SystemCompany: Microsoft Corporation**Bug check description:**This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.**Analysis:**This is a typical software problem. Most likely this is caused by a bug in a driver. The crash analysis did not reveal an offending driver. Possibly this problem was caused by a driver that cannot be identified at this time.

On Mon 8/15/2022 7:54:31 PM your computer crashed or a problem was reportedCrash dump file: C:\WINDOWS\Minidump\081522-24953-01.dmp (Minidump) Uptime:00:00:18 (hh:mm:ss)Bugcheck code: 0xA(0x18631888AC, 0xFF, 0x0, 0xFFFFF8015BCB4D2A)Bugcheck name:IRQL_NOT_LESS_OR_EQUALDriver or module in which error occurred: ntkrnlmp.exe (nt!KiBugCheckDispatch+0x69)This is the core Windows kernel module. No offending driver has been revealed.Description: NT Kernel & SystemProduct: Microsoft® Windows® Operating SystemCompany: Microsoft Corporation**Bug check description:**This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.**Analysis:**This is a typical software problem. Most likely this is caused by a bug in a driver. The crash analysis did not reveal an offending driver. Possibly this problem was caused by a driver that cannot be identified at this time.

On Mon 8/15/2022 5:58:32 PM your computer crashed or a problem was reportedCrash dump file: C:\WINDOWS\Minidump\081522-29078-01.dmp (Minidump) Uptime:00:00:29 (hh:mm:ss)Bugcheck code: 0xA(0x2076E3CB34, 0xFF, 0xA4, 0xFFFFF80654CB4D2A)Bugcheck name:IRQL_NOT_LESS_OR_EQUALDriver or module in which error occurred: ntkrnlmp.exe (nt!KiBugCheckDispatch+0x69)This is the core Windows kernel module. No offending driver has been revealed.Description: NT Kernel & SystemProduct: Microsoft® Windows® Operating SystemCompany: Microsoft Corporation**Bug check description:**This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.**Analysis:**This is a typical software problem. Most likely this is caused by a bug in a driver. The crash analysis did not reveal an offending driver. Possibly this problem was caused by a driver that cannot be identified at this time.

On Sun 8/14/2022 12:30:07 PM your computer crashed or a problem was reportedCrash dump file: C:\WINDOWS\Minidump\081422-25703-01.dmp (Minidump) Uptime:00:00:17 (hh:mm:ss)Bugcheck code: 0xA(0x1903772371, 0xFF, 0x21, 0xFFFFF8002E6B4D2A)Bugcheck name:IRQL_NOT_LESS_OR_EQUALDriver or module in which error occurred: ntkrnlmp.exe (nt!KiBugCheckDispatch+0x69)This is the core Windows kernel module. No offending driver has been revealed.Description: NT Kernel & SystemProduct: Microsoft® Windows® Operating SystemCompany: Microsoft Corporation**Bug check description:**This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.**Analysis:**This is a typical software problem. Most likely this is caused by a bug in a driver. The crash analysis did not reveal an offending driver. Possibly this problem was caused by a driver that cannot be identified at this time.

On Sun 8/14/2022 12:27:01 PM your computer crashed or a problem was reportedCrash dump file: C:\WINDOWS\Minidump\081422-34453-01.dmp (Minidump) Uptime:3 days, 18:48:18 (hh:mm:ss)Bugcheck code: 0xA(0xFFFFAD092866F9D8, 0xFF, 0x8A, 0xFFFFF80406AB5B5E)Bugcheck name:IRQL_NOT_LESS_OR_EQUALDriver or module in which error occurred: ntkrnlmp.exe (nt!KiBugCheckDispatch+0x69)This is the core Windows kernel module. No offending driver has been revealed.Description: NT Kernel & SystemProduct: Microsoft® Windows® Operating SystemCompany: Microsoft Corporation**Bug check description:**This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.**Analysis:**This is a typical software problem. Most likely this is caused by a bug in a driver. The crash analysis did not reveal an offending driver. Possibly this problem was caused by a driver that cannot be identified at this time.

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

3 answers

Answer 1

Performed a clean install of Windows as per the instructions found in various replies throughout this forum ...

That was a mistake.

On its website, Microsoft describes in great detail what you need to do. It's not difficult, but you do need to follow Microsoft's directions exactly. Don't leave out a single detail. You should read through the whole thing before you start. I'll give you a quick summary of what will happen, and then I'll give you the link to the page on Microsoft's website.

First, you'll download Microsoft's media creation tool, to your computer or to any other Windows computer. The media creation tool is what creates a Windows installer for you. ("Media" is a fancy word for something that holds data - could be a USB flash drive, a DVD, a floppy disc, etc.)

Next, you'll run the media creation tool, which will create a Windows installer on a USB flash drive.

Finally, you'll boot your computer from the USB flash drive, and then you're on your way. Here's the link: Create Windows 11 installation media

Here's an unsolicited tip: Let the Windows installer do whatever it wants to do to your computer, even if you don't like it. Just humor it. You can change anything afterwards. The idea is to give the installer every reason to succeed and no excuses to fail.

Answer 2

Performed a clean install of Windows as per the instructions found in various replies throughout this forum. Made it two days before getting a new BSOD:

On Mon 8/22/2022 8:37:32 AM your computer crashed or a problem was reported

Crash dump file:	C:\Windows\MEMORY.DMP (Kernel memory dump)
Bugcheck code:	0x20001(0x11, 0x2B3634, 0x1005, 0x10001005BE0)
Bugcheck name:	HYPERVISOR_ERROR
Bug check description:	The hypervisor has encountered a fatal error.
Analysis:	This is likely a software problem which means that it was probably caused by a bug in a driver. <br>There is a possibility that this is caused by memory corruption. Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues

On Mon 8/22/2022 3:04:11 AM your computer crashed or a problem was reported

Crash dump file:	C:\Windows\Minidump\082222-24734-01.dmp (Minidump)
Bugcheck code:	0x20001(0x11, 0x2B3634, 0x1005, 0x10000205BE0)
Bugcheck name:	HYPERVISOR_ERROR
Bug check description:	The hypervisor has encountered a fatal error.
Analysis:	This is likely a software problem which means that it was probably caused by a bug in a driver. <br>There is a possibility that this is caused by memory corruption. Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues

For analysis of this file, run !analyze -v

8: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

HYPERVISOR_ERROR (20001)

The hypervisor has encountered a fatal error.

Arguments:

Arg1: 0000000000000011

Arg2: 00000000002b3634

Arg3: 0000000000001005

Arg4: 0000010001005be0

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec 

Value: 781 

Key  : Analysis.DebugAnalysisManager 

Value: Create 

Key  : Analysis.Elapsed.mSec 

Value: 1236 

Key  : Analysis.Init.CPU.mSec 

Value: 3999 

Key  : Analysis.Init.Elapsed.mSec 

Value: 97928 

Key  : Analysis.Memory.CommitPeak.Mb 

Value: 97 

Key  : WER.OS.Branch 

Value: co\_release 

Key  : WER.OS.Timestamp 

Value: 2021-06-04T16:28:00Z 

Key  : WER.OS.Version 

Value: 10.0.22000.1

FILE_IN_CAB: 082222-24593-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

BUGCHECK_CODE: 20001

BUGCHECK_P1: 11

BUGCHECK_P2: 2b3634

BUGCHECK_P3: 1005

BUGCHECK_P4: 10001005be0

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: lsass.exe

STACK_TEXT:

ffffa4818054fca8 fffff8036794723b : 0000000000020001 0000000000000011 00000000002b3634 0000000000001005 : nt!KeBugCheckEx

ffffa4818054fcb0 fffff8036785af1e : ffffeb8e51e96250 fffff803676088ec ffffa481803fc3d0 ffffa4818054fd30 : nt!HvlSkCrashdumpCallbackRoutine+0x6b

ffffa4818054fcf0 fffff80367823e82 : ffffeb8e51e96250 ffffa4818054fef0 0000000000000000 ffffeb8e51e96340 : nt!KiProcessNMI+0x2530be

ffffa4818054fd30 fffff80367823c03 : ffffeb8e51e96250 0000000000000000 0000000000000000 0000000000000000 : nt!KxNmiInterrupt+0x82

ffffa4818054fe70 fffff8036fd57b4b : fffff8036fd4f7e9 ffffeb8e51e96230 ffffeb8e51e96201 0000000000000e6f : nt!KiNmiInterrupt+0x243

ffffeb8e51e96178 fffff8036fd4f7e9 : ffffeb8e51e96230 ffffeb8e51e96201 0000000000000e6f ffff928200000008 : 0xfffff803`6fd57b4b

ffffeb8e51e96180 ffffeb8e51e96230 : ffffeb8e51e96201 0000000000000e6f ffff928200000008 ffffeb8e51e96208 : 0xfffff803`6fd4f7e9

ffffeb8e51e96188 ffffeb8e51e96201 : 0000000000000e6f ffff928200000008 ffffeb8e51e96208 0000000020207050 : 0xffffeb8e`51e96230

ffffeb8e51e96190 0000000000000e6f : ffff928200000008 ffffeb8e51e96208 0000000020207050 ffffeb8e51e96230 : 0xffffeb8e`51e96201

ffffeb8e51e96198 ffff928200000008 : ffffeb8e51e96208 0000000020207050 ffffeb8e51e96230 fffff8036784ce6c : 0xe6f

ffffeb8e51e961a0 ffffeb8e51e96208 : 0000000020207050 ffffeb8e51e96230 fffff8036784ce6c ffffeb8e51e96230 : 0xffff9282`00000008

ffffeb8e51e961a8 0000000020207050 : ffffeb8e51e96230 fffff8036784ce6c ffffeb8e51e96230 ffffeb8e51e96250 : 0xffffeb8e`51e96208

ffffeb8e51e961b0 ffffeb8e51e96230 : fffff8036784ce6c ffffeb8e51e96230 ffffeb8e51e96250 ffffeb8e51e967b0 : 0x20207050

ffffeb8e51e961b8 fffff8036784ce6c : ffffeb8e51e96230 ffffeb8e51e96250 ffffeb8e51e967b0 ffffeb8e51e96340 : 0xffffeb8e`51e96230

ffffeb8e51e961c0 fffff803678fc4a8 : 0039003900000000 0000000000000000 0000000000000001 fffff803678fc42d : nt!HalEfiGetEnvironmentVariable+0x58

ffffeb8e51e96200 0000000000000000 : 0000000000000000 0000000000000000 ffffeb8e51e963c1 fffff80367c70e73 : nt!HalGetEnvironmentVariableEx+0x126978

SYMBOL_NAME: nt!HvlSkCrashdumpCallbackRoutine+6b

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.22000.856

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 6b

FAILURE_BUCKET_ID: 0x20001_11_2b3634_nt!HvlSkCrashdumpCallbackRoutine

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e408489b-3e35-7650-d4d8-d697fd1b5d6e}

Followup: MachineOwner

8: kd> !blackboxbsd

Version: 0xc0

Product type: 1

Auto advanced boot: FALSE

Advanced boot menu timeout: 30

Last boot succeeded: TRUE

Last boot shutdown: FALSE

Sleep in progress: FALSE

Power button timestamp: 0x0

System running: TRUE

Connected standby in progress: FALSE

User shutdown in progress: FALSE

System shutdown in progress: FALSE

Sleep in progress: 0

Connected standby scenario instance id: 0

Connected standby entry reason: 12

Connected standby exit reason: 31

System sleep transitions to on: 0

Last reference time: 0x1d8b623eb86e9f0

2022-08-22T12:37:19.902Z

Last reference time checksum: 0xd62ed41f

Last update boot id: 9

Boot attempt count: 1

Last boot checkpoint: TRUE

Checksum: 0x99

Last boot id: 9

Last successful shutdown boot id: 7

Last reported abnormal shutdown boot id: 8

Error info boot id: 0

Error info repeat count: 0

Error info other error count: 0

Error info code: 0

Error info status: 0x0

Power button last press time: 0x0

Power button cumulative press count: 0

Power button last press boot id: 0

Power button last power watchdog stage: 0

Power button watchdog armed: FALSE

Power button shutdown in progress: FALSE

Power button last release time: 0x0

Power button cumulative release count: 0

Power button last release boot id: 0

Power button error count: 0

Power button current connected standby phase: 0

Power button transition latest checkpoint id: 0

Power button transition latest checkpoint type: 0

Power button transition latest checkpoint sequence number: 0

Power transition Shutdown Device Type: 0

Power transition Setup In Progress: FALSE

Power transition OOBE In Progress: FALSE

Power transition Sleep Checkpoint Source: 0

Power transition Sleep Checkpoint: 0

Power transition Connected Standby Entry Reason Category: 0

Power transition Connected Standby Exit Reason Category: 0

Power transition Connected Standby Entry Scenario Instance Id: 0x1

Feature Configuration State : Committed

8: kd> !blackboxntfs

NTFS Blackbox Data

0 Slow I/O Timeout Records Found

0 Oplock Break Timeout Records Found

8: kd> !blackboxpnp

PnpActivityId      : {00000000-0000-0000-0000-000000000000} 

PnpActivityTime    : 133056454401855716 

PnpEventInformation: 3 

PnpEventInProgress : 0 

PnpProblemCode     : 24 

PnpVetoType        : 0 

DeviceId           : SWD\MMDEVAPI\{0.0.0.00000000}.{fa1d2ffd-0db1-4060-8ac1-fea7c59ac6a2} 

VetoString         :

Answer 3

No one can reliably solve a crash without knowing what's causing the crash in the first place. When a computer has multiple different crashes, and you are truly at a loss to understand what's causing them, there are only three logical things to:

1- Restore a backup of your computer that was made before the crashing started.

Even if you had a backup to restore, that won't help now because it would be at least a year old.

2- Show your computer to a professional.

3- Do a clean install.

Share via

Plagued with over a year of countless BSOD loops.

3 answers