B
Broadeye
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: 032121-24921-01.dmp
---------------------------------------------------
Minidump analysis of file (linked above):
[COLOR=rgba(30, 30, 30, 1)]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 ([/COLOR][COLOR=rgba(0, 0, 255, 1)]!blackboxntfs[/COLOR][COLOR=rgba(30, 30, 30, 1)])
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: [/COLOR][COLOR=rgba(0, 0, 255, 1)]nt
[/COLOR][COLOR=rgba(30, 30, 30, 1)]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
---------[/COLOR]
Continue reading...
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: 032121-24921-01.dmp
---------------------------------------------------
Minidump analysis of file (linked above):
[COLOR=rgba(30, 30, 30, 1)]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 ([/COLOR][COLOR=rgba(0, 0, 255, 1)]!blackboxntfs[/COLOR][COLOR=rgba(30, 30, 30, 1)])
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: [/COLOR][COLOR=rgba(0, 0, 255, 1)]nt
[/COLOR][COLOR=rgba(30, 30, 30, 1)]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
---------[/COLOR]
Continue reading...