whea_uncorrectable_error

Sovereign · 28 Nov 2020

Hello, I have been having blue screen issues with my computer for some time now and I have been having a very hard time trying to pinpoint what the cause is. At this point I am pretty sure the issue is hardware related but I am not sure exactly which component and was hoping you could assist me. As requested here is the V2 Log collector files:

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

In short I have updated all my drivers, updated the bios, went as far to reinstall the OS to make sure it was not software related in any form. I have run hardware tests of all kinds etc and I have come up empty handed. So when it blue screens the system does not create any dump files which leads me to believe that it is a hardware issue (whea_uncorrectable_error indicates that its likely that).

OS Build 19041.630

Thank you for you time, I greatly appreciate it.

Macboatmaster · 29 Nov 2020

It appears from my first examination of your logs that the main problem is
Logitech Gaming Software

Event[3067]:
Log Name: Application
Source: Application Error
Date: 2020-11-28T09:01:13.5110000Z
Event ID: 1000
Task: Application Crashing Events
Level: Error
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: WHITE-STAR
Description:
Faulting application name: LCore.exe, version: 9.2.65.0, time stamp: 0x5bb72085
Faulting module name: LCore.exe, version: 9.2.65.0, time stamp: 0x5bb72085
Exception code: 0xc0000005
Fault offset: 0x0000000000053cda
Faulting process id: 0x3414
Faulting application start time: 0x01d6c554df10491c
Faulting application path: C:\Program Files\Logitech Gaming Software\LCore.exe

HOWEVER that report can be caused by the mouse, keyboard or whatever other Logitech hardware you have - rather than the app itself
You have it as a startup item -
Name : Launch LCore
Command : C:\Program Files\Logitech Gaming Software\LCore.exe /minimized
Location : HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

I suggest as a starting point you check as far as possible the connections for the hardware controlled by Logitech
Disable the Logitech Gaming Software
from running at start-up

There are no reports of apparent disk errors, however what hardware checks have you made
IF the Logitech apparent problem gets you no further
Memtest would be a good starting point
MemTest86 - Official Site of the x86 Memory Testing Tool

Create a USB as on this link
MemTest86 - Creating a MemTest86 boot disk in Windows

boot the computer from the USB and run FOUR complete passes, each pass consisting of 11/13 tests
As memtest site states

Generally a single pass is sufficient to catch all but the most obscure errors.

THAT is not a single test, but one complete pass.
However to be sure run FOUR complete passes.

If it fails see this
MemTest86 - Test Results

With your four sticks of
Corsair
MemoryType : DDR4
FormFactor : DIMM
Capacity : 8GB
Speed : 2133
Serial : 00000000
PartNumber : CMW16GX4M2D3000C16

Corsair 8GB each - keeping record of which stick is in which DIMM slot
test by taking two out, leaving two in the required slots as recommended on your board - often A2 and B2 but check your manual
if it still fails
change those one at a time - using the two you took out in turn. etc.
The main point is to keep a record on a piece of card with the ram stick next to it
So you know which stick was in which slot and which stick has been tested.

Whilst you have the case open, you should of course check for dust build up just in case heat is the problem, although I do not expect it to be that.

Sovereign · 30 Nov 2020

Hello Macboatmaster, thanks for assisting me. I went ahead and ran the MemTest86 with the default being 4 passes of 13 tests. I did it and it came back with no errors, I ran it a second time to make sure and still reported no errors. I have already tried putting two memory sticks at a time on several occasions (recently was this weekend) but the results are always a blue screen. I went ahead and disabled the Logitech Gaming Software at start up (rebooted the pc), the PC still blue screened. I uninstalled the software but the PC still blue screened. I removed my Logitech G600 mouse and replaced it with a G502 (also by logitech but it's the only other mouse I have) the computer still blue screened. I dusted the PC last weekend but have been having bluescreen issues for a few months now (may be I missed cleaning something? I should double check I guess).

So the bluescreens have been hard to narrow down. For a time I would go many days without a blue screen, then on other occasions it would blue screen on back to back uses. It used to blue screen when waking up the PC, other times it would blue screen just by watching youtube videos. Now it blue screens while playing warframe, it does it so consistently now that this is how I test whether what I do works or not (usually within 5 minutes). I don't have to be playing it, just running it on the background will make it happen. Now while that would lead me to believe warframe is the issue it does it when nothing is running at all and has done it with other games as well.

As for the tests that I have done, I have check hard drive health, memory health tests, swapping ram sticks, cpu stress tests, gpu stress test and nothing has made the PC crash during the tests or give error messages. What other things do you think I should test?

Macboatmaster · 30 Nov 2020

A second choice is
NZXT CAM 4.16.0
Name : NZXT.CAM
Command : C:\Program Files\NZXT CAM\NZXT CAM.exe --startup
Location : HKU\S-1-5-21-3515179463-1201472174-829782729-1001\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

I suggest for testing purposes you uninstall it
The logs show it has crashed a number of times

That said, at this time I cannot say it is the CAUSE

If that proves to have no positive result we will try other possible tests

What is the make and full model of the PSU please

Ztruker · 30 Nov 2020

There are no dumps available on your system.

Please run Tuneup.bat from the BSOD Batch Repository. Follow Part One, Part Two and Part Three to download, run and collect the output to post here please.

Sovereign · 30 Nov 2020

Here is the info requested:

Code:

sfc /scannow
dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /restorehealth
sfc /scannow

chkdsk /scan

wmic recoveros get autoreboot
wmic recoveros set autoreboot = false
wmic recoveros get autoreboot
wmic recoveros get DebugInfoType
wmic recoveros set DebugInfoType = 7
wmic recoveros get DebugInfoType

wmic pagefile list /format:list
wmic Computersystem where name="WHITE-STAR" get AutomaticManagedPagefile
wmic Computersystem where name="WHITE-STAR" set AutomaticManagedPagefile=True
wmic Computersystem where name="WHITE-STAR" get AutomaticManagedPagefile

bcdedit /enum {badmemory}


C:\Windows\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.572

Image Version: 10.0.19041.630

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\Windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.572

Image Version: 10.0.19041.630

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
  352512 file records processed.
File verification completed.
 Phase duration (File record verification): 2.24 seconds.
  9120 large file records processed.
 Phase duration (Orphan file record recovery): 0.00 milliseconds.
  0 bad file records processed.
 Phase duration (Bad file record checking): 0.18 milliseconds.

Stage 2: Examining file name linkage ...
  1087 reparse records processed.
  503240 index entries processed.
Index verification completed.
 Phase duration (Index verification): 6.82 seconds.
  0 unindexed files scanned.
 Phase duration (Orphan reconnection): 301.34 milliseconds.
  0 unindexed files recovered to lost and found.
 Phase duration (Orphan recovery to lost and found): 0.71 milliseconds.
  1087 reparse records processed.
 Phase duration (Reparse point and Object ID verification): 4.02 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 12.35 milliseconds.
  75365 data files processed.
 Phase duration (Data attribute verification): 0.92 milliseconds.
CHKDSK is verifying Usn Journal...
  38765880 USN bytes processed.
Usn Journal verification completed.
 Phase duration (USN journal verification): 107.30 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

 487747642 KB total disk space.
  63436132 KB in 251593 files.
    179600 KB in 75366 indexes.
         0 KB in bad sectors.
    475058 KB in use by the system.
     65536 KB occupied by the log file.
 423656852 KB available on disk.

      4096 bytes in each allocation unit.
 121936910 total allocation units on disk.
 105914213 allocation units available on disk.
Total duration: 9.50 seconds (9504 ms).

C:\Windows\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


C:\Windows\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\WHITE-STAR\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk2\\Partition3"'
Property(s) update successful.

C:\Windows\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


C:\Windows\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


C:\Windows\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\WHITE-STAR\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk2\\Partition3"'
Property(s) update successful.

C:\Windows\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


C:\Windows\system32>wmic pagefile list /format:list


AllocatedBaseSize=4864
CurrentUsage=0
Description=C:\pagefile.sys
InstallDate=20200812184334.591562-240
Name=C:\pagefile.sys
PeakUsage=1
Status=
TempPageFile=FALSE




C:\Windows\system32>wmic Computersystem where name="WHITE-STAR" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE


C:\Windows\system32>wmic Computersystem where name="WHITE-STAR" set AutomaticManagedPagefile=True
Updating property(s) of '\\WHITE-STAR\ROOT\CIMV2:Win32_ComputerSystem.Name="WHITE-STAR"'
Property(s) update successful.

C:\Windows\system32>wmic Computersystem where name="WHITE-STAR" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE


C:\Windows\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier              {badmemory}

I have uninstalled the Cam software, will update if the system BSOD. The power supply that I have is a EVGA SuperNOVA 850 G2 220-G2-0850-XR 80+ GOLD 850W

EVGA SuperNOVA 850W Fully Modular Power Supply - Newegg.com

EDIT: I may have posted the wrong information?

EDIT2: System blue screened after having removed the Cam software (made sure to reboot after having removed it).

Ztruker · 01 Dec 2020

Whenever you get a BSOD, please run V2 log collector and upload he zip file and post a share link to it.

Sovereign · 01 Dec 2020

Ok here it is, it just crashed and then when I tried to open windows explorer it crashed again:

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

Edit: So I see that there are now additional entries for the CORSAIR iCUE Software compared to the original one I posted so I went ahead and uninstalled it (rebooted too) and see if this makes a difference.

RJARRRPCGP · 01 Dec 2020

More likely a faulty CPU, with a "WHEA_UNCORRECTABLE_ERROR" BSOD, unless overclocking the CPU too much.

Macboatmaster · 01 Dec 2020

There is still no dump file
and in event log
Event[7864]:
Log Name: System
Source: volmgr
Date: 2020-12-01T17:34:24.0810000Z
Event ID: 161
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: WHITE-STAR
Description:
Dump file creation failed due to error during dump creation.

As the dump settings seem correct from the logs requested by my colleague Ztruker - - auto reboot is off which if it was on would be a cause of no dump file.

Another cause can be system clean up software running on boot, for instance CCleaner in default mode will delete dump files, I think, it certainly did so last time I looked

Disk errors can be responsible but on the face of it we can eliminate that from the chkdsk.

Can be ram errors but again on the evidence memtest said it was OK
When you say

. I have already tried putting two memory sticks at a time on several occasions (recently was this weekend) but the results are always a blue screen.

WAS that an IMMEDIATE Blue screen with two sticks

HOW old is that PSU - please.