New
#1
Daily BSOD!
At random times I'll get at least one BSOD throughout the day. Most of the time it's Kernel Power 41.
Here's the log of the error: V2 log collector 1.09.zip - Google Drive
At random times I'll get at least one BSOD throughout the day. Most of the time it's Kernel Power 41.
Here's the log of the error: V2 log collector 1.09.zip - Google Drive
"Kernel Power" isn't a BSOD. It's Windows detecting an improper shutdown. It includes being rebooted unexpectedly.
Please follow the BSOD Posting Instructions and upload the file as requested. The one you uploaded is the original download not the results from running it.
ECKOGEN-(2020-07-21_14-43-09).zip - Google Drive
I think I uploaded the correct file now.
One dump in the zip file;
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: ffff930f2c0c5028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.Bug Check 0x124: WHEA_UNCORRECTABLE_ERRORCode:3: kd> !errrec ffff930f2c0c5028 =============================================================================== Common Platform Error Record @ ffff930f2c0c5028 ------------------------------------------------------------------------------- Record Id : 01d65f5583ad681a Severity : Fatal (1) Length : 936 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 7/21/2020 18:35:27 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffff930f2c0c50a8 Section @ ffff930f2c0c5180 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffff930f2c0c50f0 Section @ ffff930f2c0c5240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffff930f2c0c5138 Section @ ffff930f2c0c52c0 Offset : 664 Length : 272 Flags : 0x00000000 Severity : Fatal Error : Unknown (Proc 0 Bank 0) Status : 0x0000000000000000
The WHEA_UNCORRECTABLE_ERROR bug check has a value of 0x00000124. This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
Looks like the symbols for 19041 have not been uploaded to the symbol servers yet by Microsoft so I'm getting symbol errors.
Cause
This bug check is typically related to physical hardware failures. It can be heat related, defective hardware, memory or even a processor that is beginning to fail or has failed. If over-clocking has been enabled, try disabling it. Confirm that any cooling systems such as fans are functional. Run system diagnostics to confirm that the system memory is not defective. It is less likely, but possible that a driver is causing the hardware to fail with this bug check.
You have 32GB of DDR4 RAM so it would be good to test it with memtest86 running four passes back to back for a total of 8 passes. This is going to take a long time so start it at night before you go to bed and let it run overnight and into the next day until it completes:
===================================================
Up through DDR3, follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums
DDR4, follow this tutorial: MemTest86 v8.1 Free Memory Testing Tool Review
Both of these are diagnostic tools designed to test Random Access Memory (RAM) for faults. They will verify that:
- RAM will accept and keep random patterns of data sent to it
- There are no errors when different parts of memory try to interact
- There are no conflicts between memory addresses
They run from bootable media to isolate the RAM from the system, no other components are taken into account during the test.
WarningMemTest86+ and Memtest86 need to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM. The new version of Memtest86 only allows 4 passes for the free version so run it twice, back to back.
If you are asked to run MemTest86+ or Memtest86 by a Ten Forums member make sure you run the full 8 (or 4+4) passes for conclusive results. If you run less than 8 passes you will be asked to run it again.
NoteBoth of these diagnostics has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.
Running 8 passes of MemTest86+ or 4+4 passes of Memtest86 is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run it overnight, starting just before you go to bed and leave it overnight.
Take a picture when done and post in the forum please.
Thank you. I will run it tonight and post results when done.
- - - Updated - - -
I tried to run memtest (the one without the +) and during the boot selection it had USB partition 1 and 2. Inside the test menu, I couldn't select any of the menu items on the left side.
So, I decided to just run Windows Memory Diagnostic in the mean time. I set it to extended test, 15 passes. I left it on overnight to run (8 hours+) and it froze on pass 0 at 15%. When I tried to navigate to exit it literally rendered each letter of the word one by one. It was extremely slow.
Are you overclocking your CPU cores? If you are, wouldn't be surprised if the core temps are too high.
The lag could be thermal-throttling.
Base clock speeds and I'm using a Noctua NH-D15 as the CPU cooler.