Random BSOD's occuring (During Regular Use)

So, I'm gonna try explaining everything as best I can, in case it helps

A few months ago, I ordered a brand new custom PC, only shipped about a month ago. Since then, I've been using it and for the most part it was working fine, a BSOD here and there but nothing too concerning. Unfortunately, without realizing the consequences, I disabled "Wi-Fi 2" and that led me to not be able to even login to the computer let alone do anything else (it would freeze at the login menu). Eventually after many failed attempts I decided just to reformat my SSD and re-install Windows. After doing so, I immediately installed all the drivers I could think of, making sure to create a shit ton of restores along the process. All seemed well apart from 2 instances, the first being when I played a video that was downloaded on my computer, played using VLC Media Player, the computer would get a BSOD with the 'Machine Check Exception' error. However, since it was only that one video that was causing crashes (I also tested other videos) I tried dismissing that. The 2nd, comes from watching some videos on Firefox using their (i.e., different websites) video players, which again gave a BSOD only this time with a 'WHEA UNCONTROLLABLE ERROR'. Since I could still game perfectly fine, and browse Chrome and Edge without any issues I once again chose to ignore it

Not too long ago, I installed the EVGA Precision X1 app from Steam, which ended up installing I believe Microsoft VC Redist package. Alongside that, I also tried updating Windows to version 1909, but I get the error message that some files are missing/have problems with the error code 0x80073712.

Now we move on to these past few days, I assume from the results of above (i.e., the Windows Update and VC Redist Package), the problems have gotten even worse. 'MACHINE CHECK EXCEPTION' crashes happen more often now, even doing regular tasks such as starting to type on Chrome or exiting a window on a program (like Event Viewer for instance). On top of that, I can no longer run any game on Full screen without the screen going black (monitor says no signal) and while the audio plays in the background, eventually it cuts to that "crashed audio" noise and I have to manually reset the PC. Running in Windowed Mode works fine though. I would System Restore back to my infinitely created restore points, but unfortunately the Windows Update unknowingly got rid of them all

What I have done so far:

Run MemTestx86 and found no errors for 8 passes
Installed all latest drivers I could find
Scanned all hard drives and found no errors on any of them
Updated BIOS to the latest one (at least I think it is the latest)
No Overclocking being done

Running CMD Prompt Tests:

Code:

Microsoft Windows [Version 10.0.18363.418]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 0% 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.18362.1

Image Version: 10.0.18363.418

[==========================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.18362.1

Image Version: 10.0.18363.418

[==========================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 0% 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 ...
  224000 file records processed.
File verification completed.
  1940 large file records processed.
  0 bad file records processed.

Stage 2: Examining file name linkage ...
  424 reparse records processed.
  300584 index entries processed.
Index verification completed.
  0 unindexed files scanned.
  0 unindexed files recovered to lost and found.
  424 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
  38293 data files processed.
CHKDSK is verifying Usn Journal...
  33725168 USN bytes processed.
Usn Journal verification completed.

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

 976746495 KB total disk space.
  52156328 KB in 142184 files.
     96204 KB in 38294 indexes.
         0 KB in bad sectors.
    356979 KB in use by the system.
     65536 KB occupied by the log file.
 924136984 KB available on disk.

      4096 bytes in each allocation unit.
 244186623 total allocation units on disk.
 231034246 allocation units available on disk.

Currently running Windows 10 Version 1909

Some other specs:

CPU:
Intel® Core™ Processor i7-9700KF 3.60GHZ
Motherboard:
ASUS Prime Z390-P ATX
Memory:
16GB (8GBx2) DDR4/3000MHz Dual Channel Memory (GSKILL Trident Z RGB)
Graphics Card(s):
EVGA GeForce® RTX 2070 SUPER™ XC GAMING 8G GDDR6 (Turing)

Part of me thinks it's a CPU error. All of me hopes it's something software related like a driver, because the main reason why I decided to go custom built was since I was afraid of frying a component during installation (which happened to me before), so especially something like a CPU would spell hell.

Please let me know if there's anything else I can provide that would give help to this issue

Looks like a defective CPU.

Two dumps show:

Code:

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
    x86 Processors
        If the processor has ONLY MCE feature available (For example Intel
        Pentium), the parameters are:
        1 - Low  32 bits of P5_MC_TYPE MSR
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of P5_MC_ADDR MSR
        4 - Low  32 bits of P5_MC_ADDR MSR
        If the processor also has MCA feature available (For example Intel
        Pentium Pro), the parameters are:
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
    IA64 Processors
        1 - Bugcheck Type
            1 - MCA_ASSERT
            2 - MCA_GET_STATEINFO
                SAL returned an error for SAL_GET_STATEINFO while processing MCA.
            3 - MCA_CLEAR_STATEINFO
                SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
            4 - MCA_FATAL
                FW reported a fatal MCA.
            5 - MCA_NONFATAL
                SAL reported a recoverable MCA and we don't support currently
                support recovery or SAL generated an MCA and then couldn't
                produce an error record.
            0xB - INIT_ASSERT
            0xC - INIT_GET_STATEINFO
                  SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
            0xD - INIT_CLEAR_STATEINFO
                  SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
            0xE - INIT_FATAL
                  Not used.
        2 - Address of log
        3 - Size of log
        4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
    AMD64 Processors
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 0000000000000000
Arg2: ffffc4005676fd50
Arg3: 0000000000000000
Arg4: 0000000000000000

References INTELPPM.sys as the failing module:

Code:

FOLLOWUP_IP: 
intelppm!MWaitIdle+1f
fffff806`2a9b138f 4585c9          test    r9d,r9d
FAULT_INSTR_CODE:  75c98545
SYMBOL_STACK_INDEX:  8
SYMBOL_NAME:  intelppm!MWaitIdle+1f
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: intelppm
IMAGE_NAME:  intelppm.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  0
IMAGE_VERSION:  10.0.18362.387
STACK_COMMAND:  .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET:  1f
FAILURE_BUCKET_ID:  0x9C_GenuineIntel_STACKPTR_ERROR_intelppm!MWaitIdle
BUCKET_ID:  0x9C_GenuineIntel_STACKPTR_ERROR_intelppm!MWaitIdle
PRIMARY_PROBLEM_CLASS:  0x9C_GenuineIntel_STACKPTR_ERROR_intelppm!MWaitIdle

Two dumps show:

Code:

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffff8c0dc576d028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000030005, Low order 32-bits of the MCi_STATUS value.

Code:

0: kd> !errrec  ffff8c0dc576d028
===============================================================================
Common Platform Error Record @ ffff8c0dc576d028
-------------------------------------------------------------------------------
Record Id     : 01d5afaeb85bfbbc
Severity      : Fatal (1)
Length        : 872
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 12/10/2019 23:09:34 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffff8c0dc576d0a8
Section       @ ffff8c0dc576d180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000906ec
Processor ID  : 0x0000000000000000

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffff8c0dc576d0f0
Section       @ ffff8c0dc576d240
Offset        : 536
Length        : 64
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : ec 06 09 00 00 08 10 00 - bf fb fa 7f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffff8c0dc576d138
Section       @ ffff8c0dc576d280
Offset        : 600
Length        : 272
Flags         : 0x00000000
Severity      : Fatal

Error         : Unknown (Proc 0 Bank 0)
  Status      : 0xb200000000030005

Second is similar with the last part being:

Code:

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffb48bfbd3b138
Section       @ ffffb48bfbd3b2c0
Offset        : 664
Length        : 272
Flags         : 0x00000000
Severity      : Fatal

Error         : DTLBL0_ERR (Proc 1 Bank 2)
  Status      : 0xb200000000000014

This is unlikely to be a driver caused problem. I would return (RMA) the CPU or entire computer to Cyperpower. A new one should resolve this problem.

Ah, that sucks, it is what I feared. Is there any way I can test to make sure the CPU is faulty or not (like any software tests)?

The main issue with returning it back is that I'm in Canada, so there's already all the shipping issues with sending it back to Cyberpower in the states and whatnot (especially UPS can be really annoying to deal with) so I'd have to send it somewhere locally. But then, that's a pretty expensive CPU so that already sets me back some funds


EDIT: So I ran Intel CPU Diagnostic just in case, and it came back with all passes. Now I'm confused. For sure I don't doubt your analysis, but could it be the diagnostic missed something?

Attachment 259117

I've said this before and I'll say it again. Test do not catch all problems. I think Zbook has said the same too. Tests will pass and yet the hardware can be defective. The best test software you have unfortunately is the Operating System.

There is no definitive test you can run that will tell you "Yup, the CPU is definitely bad" or "the GPU is definitely bad". Prime95 may show you something but it also may not. Same for FurMark.

Maybe in your case the best thing to do is contact Cyberpower and see what they suggest you do. They may ask you to reinstall Windows 10 again, so make sure you have a good image backup of your system using Macrium Reflect to an external hard drive, if there is anything on there you are not willing to lose.

I'm sure you didn't order the system with a 2TB boot drive and two 1TB drives in a RAID setup. How was it originally configured and what did you add? Also add that info to System specs under My Computer please.

You can hold off talking to Cyberpower until you finish with Zbook.

When you uninstalled/reinstalled the GPU (Nvidia) driver, did you install only the Graphics and PhysX drivers?

If not, try it, see if that gets rid of the problem.