BSOD WHEA_UNCORRECTABLE_ERROR, redirected into the BIOS

[Klemen]

I just had again an experience with BSOD, it was either while ideling or play a game. When i rested computer (turned it off and on, will tell later why) it happened again, quite qucikly. Same while ideling. 

When i turned off PSU and disconnected ATX (24pin cable) and disconnected RAM moduls and reseated one at the time (only one RAM modul present in the system for a test) nothing happened 

 

I tested both moduls seperately and they were working fine and even memtest run never showed anything.. 

Now, let's move on to where we left before. I said i had to turn off my computer because reset doesn't help me when it comes to BSOD situations. No matter which one I'd get I am always thrown into a BIOS screen. Even if i reset afterwards i am going to be meeting BIOS again, so the only way after BSOD for me is to turn off and turn on computer again. 

 

Also that BSOD name is WHEA_UNCORRECTABLE_ERROR 

 

Now, Drivers should be good i have good faith that i did a good job on checking every single one and every app i installed previously too. Went with LatencyMon to make sure there werent any spikes in latency or delay that would cause any instability with programs running on the system. Before BSOD occurs, system starts to become unresponsive until it feels like it completely froze.

 

Non of components is overheating. I was monitoring temps all time to multiple stresses. Max spike of CPU was 90 degrees (spike, average was 87 degrees) and GPU had max of 79 degree temp.

Otherwise CPU and GPU keep at goog 60-65 degree temps at all times while gaming. 

 

When i downloaded Prime95 and selected Blend test it crashed on me everytime with 2 RAM moduls. Then, with just one it never did.  And also BSOD never creat minidumps for somereason. I searched whole system and there isnt a single minidump. Tried searching in Windows folder under minidump but it was empty also %systemroot%\minidump and \MEMORY.DMP

 

All of my system info are on my profile page! Nothing is overclocked other than my RAM being set to 3000MHz frequency. Could be CPU/NVME? I really have no idea and this happened now twice, even after clean install, so i am kinda starting to suspect hardware fault and not any driver issue. System is now old over a year and a half and this BSOD started occuring after a year. 

 

TD:LR; BSOD WHEA_UNCORRECTABLE_ERROR, After BSOD I get redirected into BIOS set up. 

 

;;;

 

DUMPFILES found in %LOCALAPPDATA%\CrashDumps

- from yesterday 1AM - ra3_1.12.game.19880

 

KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullPtr

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.Sec
    Value: 1

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-S29IT2D

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 44

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : Timeline.Process.Start.DeltaSec
    Value: 579

NTGLOBALFLAG:  0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_FLAGS:  0

CONTEXT:  (.ecxr)
eax=00000000 ebx=00000000 ecx=00000000 edx=04e6af44 esi=04e6af00 edi=04e6af40
eip=004f8ef7 esp=0019e9bc ebp=00040080 iopl=0         nv up ei pl zr na pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
RA3_1_12+0xf8ef7:
004f8ef7 8b08            mov     ecx,dword ptr [eax]  ds:002b:00000000=????????
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 004f8ef7 (RA3_1_12+0x000f8ef7)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00000000
Attempt to read from address 00000000

PROCESS_NAME:  RA3_1.12.game

READ_ADDRESS:  00000000 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  00000000

IP_ON_HEAP:  04ee1bec
The fault address in not in any loaded module, please check your build's rebase
log at <releasedir>\bin\build_logs\timebuild\ntrebase.log for module which may
contain the address if it were loaded.

FRAME_ONE_INVALID: 1

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
0019e9b8 04ee1bec 04e6af00 77d2de30 00000000 RA3_1_12+0xf8ef7
00000000 00000000 00000000 00000000 00000000 0x4ee1bec

SYMBOL_NAME:  RA3_1_12+f8ef7

MODULE_NAME: RA3_1_12

IMAGE_NAME:  RA3_1.12.game

STACK_COMMAND:  dt ntdll!LdrpLastDllInitializer BaseDllName ; dt ntdll!LdrpFailureData ; ~0s ; .ecxr ; kb

FAILURE_BUCKET_ID:  NULL_POINTER_READ_c0000005_RA3_1.12.game!Unknown

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x86

OSNAME:  Windows 10

FAILURE_ID_HASH:  {d21d8eba-873c-e9fb-963a-893ed0cc3b42}

Followup:     MachineOwner
---------
 

2ND ra3_1.12.game.1332

KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullPtr

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.Sec
    Value: 1

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-S29IT2D

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 18

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : Timeline.Process.Start.DeltaSec
    Value: 343

NTGLOBALFLAG:  0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_FLAGS:  0

CONTEXT:  (.ecxr)
eax=00000000 ebx=00000000 ecx=00000000 edx=04f3881c esi=04d82b88 edi=04f38818
eip=004f8ef7 esp=0019e9bc ebp=00200080 iopl=0         nv up ei pl zr na pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
RA3_1_12+0xf8ef7:
004f8ef7 8b08            mov     ecx,dword ptr [eax]  ds:002b:00000000=????????
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 004f8ef7 (RA3_1_12+0x000f8ef7)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00000000
Attempt to read from address 00000000

PROCESS_NAME:  RA3_1.12.game

READ_ADDRESS:  00000000 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  00000000

STACK_TEXT:  
00200080 00000000 00000000 00000000 00000000 RA3_1_12+0xf8ef7

SYMBOL_NAME:  RA3_1_12+f8ef7

MODULE_NAME: RA3_1_12

IMAGE_NAME:  RA3_1.12.game

STACK_COMMAND:  dt ntdll!LdrpLastDllInitializer BaseDllName ; dt ntdll!LdrpFailureData ; ~0s ; .ecxr ; kb

FAILURE_BUCKET_ID:  NULL_POINTER_READ_c0000005_RA3_1.12.game!Unknown

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x86

OSNAME:  Windows 10

FAILURE_ID_HASH:  {d21d8eba-873c-e9fb-963a-893ed0cc3b42}

Followup:     MachineOwner
---------

 

 

CrashDumps.rar

[Kilrah]

9 minutes ago, Klemen said:

Nothing is overclocked other than my RAM being set to 3000MHz frequency.

Remove that for a start, run everything as stock.

[Klemen]

19 minutes ago, Kilrah said:

Remove that for a start, run everything as stock.

PRIME95 just found this;

 

[Jan 7 21:40] Worker starting
[Jan 7 21:40] Beginning a continuous self-test on your computer.
[Jan 7 21:40] Please read stress.txt.  Choose Test/Stop to end this test.
[Jan 7 21:40] Test 1, 31000 Lucas-Lehmer iterations of M9537183 using FMA3 FFT length 480K, Pass1=384, Pass2=1280, clm=1.
[Jan 7 21:40] FATAL ERROR: Rounding was 0.4994267637, expected less than 0.4
[Jan 7 21:40] Hardware failure detected, consult stress.txt file.
[Jan 7 21:40] Torture Test completed 0 tests in 0 minutes - 1 errors, 0 warnings.
[Jan 7 21:40] Worker stopped.
 

[Klemen]

I found that with stock settings it runs clearly through P95, while with increased freq in RAM it causes errors while using Large FFTs to stress Memory controller and RAM itself.

I would doubt RAM moduls are bad since they always ran clearly, but it's just whenever i put them higher they fail. And i suspect to be either mobo or CPU to support that freq range. Now CPU should handle easily 3200MHz and mobo supports up to 4400MHz DRAM Freq... 

One thing is that i am running with stock cooler which tends to provide a bit higher temps then with aftermarket cooler and i also noticed that the higher the CPU freq goes, the less problems i have with higher DRAM freq. 

 

But for example even when i put freq to 3600 for DRAM it crashes instantaneously, and that happens with everything on auto settings. Even on 3200MHz it sometimes crashes or it is rather unstable... Should i manually increase vcore voltage and LLC? or does that mean either cpu or mobo are faulty?

[Kilrah]

Probably that either the RAM or RAM controller need a bit higher voltage to run at this freq.