Random BSODs after x2 rebuilds - suspect hardware!

Hi all,

I built a new machine back in September (not my first) and I'm pretty sure I have a dud piece of hardware. I initially thought it was the RAM (it could still well be), but it's passed 4.5 hrs of Memtest (2 passes). It could be the RAM, mobo or processor (I transferred my gfx card to this new box, so I'm less suspicious of that. The latest BSOD crash dump that's uploaded is a mini one; apologies, but the BSOD happened before I remembered to change the caching option.

Any help will be much appreciated - I'm pulling my hair out with this thing! The BSOD is always different and has been happening roughly once a week for the last couple of months.

Many thanks!

Hi Flump ,

Welcome to Ten Forums BSOD forum.

There was 1 BSOD mini dump file debugged at it did not display a misbehaving driver.
The bugcheck was 0xEF: CRITICAL_PROCESS_DIED
The CRITICAL_PROCESS_DIED bug check has a value of 0x000000EF. This indicates that a critical system process died.

Please update the system specs in the "My Computer" section:
How To Fill Out Your System Specs
System Specs - Fill in at Ten Forums:
System Specs - Fill in at Ten Forums General Tips Tutorials
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums

Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, etc.)

Performed the following steps:
1) open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online-cleanup-image /restorehealth
4) when these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
5) chkdsk /x /f /r
This may take many hours so plan to run overnight.

C:\Windows\system32>chkdsk /x /f /r
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)
Type: Y
reboot
6) Find the chkdsk report in the event viewer and post the results into the thread:
Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials
7) Make a backup image using Macrium
Macrium Software | Your Image is Everything
8) place the backup image onto another drive or into the cloud
9) backup all important files
10) create a brand new restore point
11) read these links on windows driver verifier:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
Enable and Disable Driver Verifier in Windows 10 Performance Maintenance Tutorials
12) wait for comments into the thread to start using windows driver verifier
Please learn the 3 methods to turn off windows driver verifier using the windows advanced troubleshooting menu
13) in the left lower corner search type system > open system control panel > on the left pane open advanced system settings > on the advanced tab in startup and recovery click settings > post an image into the thread
Take Screenshot in Windows 10 General Tips Tutorials


[

Code:

Event[1168]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-General
  Date: 2017-11-15T17:37:15.821
  Event ID: 5
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-TDUJTG5
  Description: 
{Registry Hive Recovered} Registry hive (file): '\SystemRoot\System32\Config\SOFTWARE' was corrupted and it has been recovered. Some data might have been lost.

Code:

Event[1140]:
  Log Name: System
  Source: volmgr
  Date: 2017-11-15T17:37:09.744
  Event ID: 46
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-TDUJTG5
  Description: 
Crash dump initialization failed!

Code:

15/11/2017 22:02    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: ef
P2: ffff97097b8587c0
P3: 0
P4: 0
P5: 0
P6: 10_0_15063
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\111517-11765-01.dmp
\\?\C:\Windows\TEMP\WER-13046-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER42D5.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4333.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4334.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ef_9c6be1ddb1b9a3ae39ae4016deda79484fc2185a_00000000_cab_15804c99

Analysis symbol: 
Rechecking for solution: 0
Report Id: 09d8919d-2eff-431a-bc3d-5de958f4c6e0
Report Status: 2049
Hashed bucket:
15/11/2017 22:02    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: ef
P2: ffff97097b8587c0
P3: 0
P4: 0
P5: 0
P6: 10_0_15063
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\111517-11765-01.dmp
\\?\C:\Windows\TEMP\WER-13046-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER42D5.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4333.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4334.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_ef_9c6be1ddb1b9a3ae39ae4016deda79484fc2185a_00000000_03104342

Analysis symbol: 
Rechecking for solution: 0
Report Id: 09d8919d-2eff-431a-bc3d-5de958f4c6e0
Report Status: 4
Hashed bucket:

Hello,

Updated my info - got to chkdsk and then had to reinstall windows again. Now on basic setup and ran Prime95 which appears to have BSOD'd the machine, so I've attached it (did remember to do full memory dump this time as it's 16GB). Also, I did notice that in speccy and system information, my RAM is listed as unknown and with the incorrect timings (even though in the BIOS the timings look fine):



Thank you in advance!

There was 1 new BSOD with bugcheck 12B
Bug Check 0x12B: FAULTY_HARDWARE_CORRUPTED_PAGEThe FAULTY_HARDWARE_CORRUPTED_PAGE bug check has a value of 0x0000012B. This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.

What happened with chkdsk /x /f /r?
Did something happen before the reboot of after the reboot?
In addition to the steps in post #2 perform the following steps:
Run memtest86+ version 5.01 for at least 8 passes.
Memtest86+ - Advanced Memory Diagnostic Tool
This may take hours so plan to run it overnight.
Please make sure you use the Memtest86+ version 5.01 with the link below.
Memtest86+ - Advanced Memory Diagnostic Tool
The testing is done not by time but by passes.
The more passes the better.
There are a significant number of false negatives if fewer than 8 passes are made.
A false negative is a test pass when there is malfunctioning RAM.
There is 16 GB of RAM on the computer.
Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
Just 1 error is a fail and you can abort testing.
Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
When Memtest86+ has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
Memory problems. - Microsoft Community
MemTest86+ - Test RAM BSOD Tutorials

It did the initial chkdsk and then it asked for a reboot, which I did. Then upon reloading to the welcome screen it would jump between that and the "ring of loading" as I like to call it. Tried start up repair et al., and nothing worked - just an error, since it seemed to not be able to find the OS when I did a /bootrec scanos. Formatted and reinstalled. I'll get this memtest up and running now before work.

Thanks again!

Did you perform a clean install deleting all partitions, formatting, making an unallocated drive and reinstalling the windows 10 version 1709 using a windows 10 iso? Or did you use the windows advanced troubleshooting menu?

Please indicate the progress with each step in post #2.

I booted from USB (1703, though!) formatted and then deleted the partitions before re-install. Memtest failed before I even left to work:

Attachment 164284

I'll test using one at a time in each DIMM slot for further analysis.

Okay. That confirmed the bugcheck findings.

OK, one stick seems to throw up errors between 40 - 50 minutes (between 80 - 200 errors) in both DIMM slots, whilst the other can go 4+ hours without any issues. I think it's unlikely to be a DIMM/Mobo issue, unless you have other thoughts? I've taken out the suspect RAM and have been re-installing stuff successfully and smoothly. Wondering if I should run Prime95 again to see if it crashes the system. Good news is that I can return the RAM once 100%

When there are more than 1 RAM module and there is Memtest86+ failure perform the following tests:
Place each RAM module in the same DIMM to determine which RAM module is faulty.
There is no need to check the other RAM modules if you find 1 malfunctioning RAM module.
If there are no malfunctioning RAM modules when tested 1 at a time in the same DIMM then test other DIMM.
So you have done some nice testing and have found faulty RAM.
If you plan to replace the RAM or get more or larger RAM modules it is always best to purchase in pairs with the identical SKU.
This way there is no RAM mismatch which can cause BSOD.
To best check the single RAM module it should be checked for 8 or more passes and the test can be run overnight.
Again the test is not by time but by passes and the more the passes the better.
The number of errors can be ignored as just 1 error is a fail and the RAM needs to be removed or replaced.


Once you have a working ram please check the drive file system:
Open administrative command prompt and type or copy and paste:
chkdsk /x /f /r
It may take many hours so plan to run overnight.
To find the results in the event viewer and post into the thread use the information in this link:
Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials

Also see post#2 for the steps to report into the thread.