Unable to boot - can anyone help with WHEA ERROR - BSOD Boot Loop  

Can anybody please advise on this. Returned after a couple of days away last weekend to find Aurora R9 / Win 10 PC on BS - had ben shut down so assume an update responsible. Used WinRE to undo last Win quality updated and rebooted straight into Windows. Rebooted again and BS WHEA_INTERNAL_ERROR again. Tried reverting latest quality update through WinRE again bit it failed (none found).

Got back into Win using a restore point through WinRE. Note auto restore point named "Alienware OC Controls" which may be a clue.

Which is where I am right now. Critical work PC and a single restore point seems my only way back into windows as every restart results in BS error again - can anybody please advise on this error. If it's a driver I can't track it down.

Basically I'm trrying to avoid a full install if poss as will lose a week installing and reconfiguring apps. I do have an Acronis disc image from a couple of weeks ago which I will try to remount if all else fails - but update may repeat error and maybe there's a simpler solution.

Many Thanks!

Alienware Aurora R9
i7-9700
Bios: 1.0.11 (latest)
Memory: 16gb
Nvidia Geo RTX 2060 Super
Win 10 Home - 10.0.1.18363 (old version presumable result of rolling back updates).

TenForums Log Collector V2 file: MG-ALIEN-(2021-03-22_16-09-39).zip - Google Drive

DMP File Link: 032121-24921-01.dmp - Google Drive

---------------------------------------------------

Minidump analysis of file (linked above):

WHEA_INTERNAL_ERROR (122)
Arguments:
Arg1: 0000000000000006
Arg2: ffffffffc0000002
Arg3: 0000000000000001
Arg4: 0000000000000010

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3093

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 15809

Key : Analysis.Init.CPU.mSec
Value: 1358

Key : Analysis.Init.Elapsed.mSec
Value: 49700

Key : Analysis.Memory.CommitPeak.Mb
Value: 70

Key : WER.OS.Branch
Value: 19h1_release

Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z

Key : WER.OS.Version
Value: 10.0.18362.1


BUGCHECK_CODE: 122

BUGCHECK_P1: 6

BUGCHECK_P2: ffffffffc0000002

BUGCHECK_P3: 1

BUGCHECK_P4: 10

BLACKBOXNTFS: 1 (!blackboxntfs)


CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffc702`938078b8 fffff807`7782f8ea : 00000000`00000122 00000000`00000006 ffffffff`c0000002 00000000`00000001 : nt!KeBugCheckEx
ffffc702`938078c0 fffff807`77805fe9 : fffff807`716348f0 00000000`00000004 00000000`00000000 ffffc702`00000000 : nt!WheaInitialize+0x2cac6
ffffc702`93807970 fffff807`7780f549 : fffff807`7ae4d000 fffff807`716348f0 fffff807`775573e0 00000000`000007ea : nt!IoInitSystemPreDrivers+0xb9d
ffffc702`93807ab0 fffff807`77557422 : fffff807`716348f0 fffff807`716348f0 fffff807`775573e0 fffff807`716348f0 : nt!IoInitSystem+0x9
ffffc702`93807ae0 fffff807`76f33585 : ffffe70e`7126e040 fffff807`775573e0 fffff807`716348f0 00000000`00000000 : nt!Phase1Initialization+0x42
ffffc702`93807b10 fffff807`76fcb128 : fffff807`7199b180 ffffe70e`7126e040 fffff807`76f33530 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffc702`93807b60 00000000`00000000 : ffffc702`93808000 ffffc702`93801000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nt!WheaInitialize+2cac6

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.18362.1316

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 2cac6

FAILURE_BUCKET_ID: 0x122_ERRSOURCEINITFAILED_C0000002_nt!WheaInitialize

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ce1e5536-c3e1-9576-d01d-a513822f25e7}

Followup: MachineOwner

Both dumps are the same, You had a total of 3 according to the msinfo32,nfo WERDATA:

Code:

3 Bluescreen entries detected ...
1 Unique Bug Check code:  122
 
 P1: 0X00000122 16/03/2021 12:02 P1: 
 P1: 0X00000122 21/03/2021 17:45  P1:
 P1: 0X00000122 21/03/2021 19:29  P1:

Code:

Bug Check 0x122:  WHEA_INTERNAL_ERROR
The WHEA_INTERNAL_ERROR bug check has a value of 0x00000122. 
This bug check  indicates that an internal error in the Windows Hardware Error Architecture  (WHEA) has occurred. 
Errors can result from a bug in the implementation of a  platform-specific hardware error driver (PSHED) plug-in supplied by a vendor, 
 the firmware implementation of error records, or the firmware implementation of  error injection
.

So my suspicion is this is caused by a driver. The dump doesn't indicate which one so I would like you, if you can, enable Driver Verifier and see if that gives us any more info to go on:

Run Driver Verifier

Driver Verifier-- tracking down a mis-behaving driver.

Following the instructions in the above link will check for problems in all non-Microsoft drivers.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.

To check if verifier is active, open a Command Prompt and enter:

verifier /query

If not active it will respond with

No drivers are currently verified.

Follow instructions here to decide which drivers you want to test. 3-5 is a good start. Add 3-5 more every two hours until all are selected or you get a BSOD.

Enable and Disable Driver Verifier in Windows 10

Familiarize yourself with how to get out of Driver verifier from the above link and from the first link.

Sounds good Mark.