Aurora R9, no boot, WHEA ERROR - BSOD boot loop

Question

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). Noticed explorring thru CMD showed boot drive with wrong letter (X) which may explain boot failure.   Got back into Win using a restore point through WinRE. 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.   Many Thanks!   DMP File Link:  https://drive.google.com/file/d/1EbXctFYZDI9JCWxP4grpd65nAfTactXV/view?usp=sharing   ---------------------------------------------------   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 ---------

M One · Accepted Answer

Tested memory and drive integrity. New SSD, cloned older image, booted fine. Unsintalled Alienware OC app (suspect culprit) and updated Win to currrent without issue. Thanks for the advice all.

Vanadiel · Answer

https://github.com/MicrosoftDocs/windows-driver-docs/blob/staging/windows-driver-docs-pr/debugger/bug-check-0x122---whea-internal-error.md

speedstep · Answer

sdbus.sys

Windows 10 Insider Preview 10.0.18362.1 (19H1_RELEASE) amd64 2019-03 is very old and no longer supported.

WHEA error

Corrupt or missing components in the Windows registry.
Malware attack.
Incomplete or incorrect software installation.
Memory (RAM) issues.
Low disk space.
Faulty hardware.

M One · Answer

Thanks Speedstep - have run Malwarebytes / Defender scans nothing (I am on the ball with security so would have been surprised).

The auto recovery point that works (though worrried this may self delete soon) is "Alienware OC Controls" installation. Suspect this may be responsible.

Afraid to reboot yet as may not get back in - anything I can do in terms of fixing a fauly driver without reinstalling win from scratch (and spending a week rebuilding apps)?

M One · Answer

Thanks - seen this already. Unfortunately does not help with identifying cause or solution.

speedstep · Answer

Rollback is never a good option;

https://support.microsoft.com/en-us/windows/update-windows-10-3c5ae7fc-9fb6-9af1-1984-b5e0412c556a

You haven't done a feature update in a very long time.

These are no longer optional.

Malwarebytes may be interfering with windows updates

UPDATE NOW

https://go.microsoft.com/fwlink/?LinkID=799445

media creation tool for usb 2 fat32 FLASH DRIVE 16 or 32 GIG

https://go.microsoft.com/fwlink/?LinkId=691209

M One · Answer

'Windows 10 Insider Preview 10.0.18362.1 (19H1_RELEASE) amd64 2019-03 is very old and no longer supported.' Sorry, not sure what you mean by this. Where are you getting the info? I am on Intel i7 & and sysinfo showing Win 10 Home: 10.0.18363. Assumed I was up to date - something wrong with windows update then?

M One · Answer

Is a Windows update my best option do you think or likely to cause more issues?

One reason might be showing old version is that I uised WinRE to rollback WIndows Wuality update and it booted straight in.

M One · Answer

OK thanks. My prob as don't know what that means. How can build be so old if windows constantly updating apparently without issue. Honestly thought I was fully up to date.

speedstep · Answer

Windows 10 Insider Preview 10.0.18362.1 (19H1_RELEASE) amd64 2019-03   is very old and no longer supported.

speedstep · Answer

The system dump has windows 10 insider build

Thats where I got that.

10.0.18363 is a very old build. And its an Insider build not a production release.

20H2 is the current build.

C:\windows\system32\winver

20H2	2020-10-20	19042.870
2004	2020-05-27	19041.870
1909	2019-11-12	18363.1443
1809	2019-03-28	17763.1823
1809	2018-11-13	17763.1823
1803	2018-07-10	17134.2090
1803	2018-04-30	17134.2090

Enterprise and IoT Enterprise LTSB/LTSC editions

Version	Servicing option	OS build	Extended support end date
1809	Long-Term Servicing Channel (LTSC)	17763.1823	2029-01-09
1607	Long-Term Servicing Branch (LTSB)	14393.4288	2026-10-13
1507 (RTM)	Long-Term Servicing Branch (LTSB)	10240.18875	2025-10-14

speedstep · Answer

We are done.

Rolling back will get worse and worse until its dead.

Neither dell nor Microsoft support going backwards in terms of required feature updates.

Windows 10: "feature updates" are not optional "quality updates are optional.

Vanadiel · Answer

Are you sure you are booting from the correct drive? Maybe there's an older partition with an old windows version on it?

M One · Answer

Boots from correct drive after restore point but as soon as I restart it fails with BSOD - opening CMD shows boot drive now labeled X: rather than C:

r72019 · Answer

Some thoughts:

1. The X: drive aspect is normal when you're looking at it from a recovery environment

2. Yeah, you're out of date because you did a system restore. That rolls you backwards.

3. Could be a number of things, driver, hard drive failure, virus, etc.

4. Create an imaged backup before you start working on the PC and/or lose your restore point.

5. Suggest booting into safe mode while you try and repair it. That could potentially prevent an offending driver from loading if it's driver related.

6. Try running system file checker and check disk.

7. I suggest putting this question to a more windows specific forum, like tenforum's BSOD section

That's all, good luck.

Alienware Desktops

Windows 10 Insider Preview 10.0.18362.1 (19H1_RELEASE) amd64 2019-03 is very old and no longer supported.

Windows 10 Insider Preview 10.0.18362.1 (19H1_RELEASE) amd64 2019-03 is very old and no longer supported.

Was this post helpful?