BSOD even after Windows 10 reset, 0x000000e

DownRoad · 07 Feb 2020

(Note: I've also posted my question to the microsoft forums because I'm really desperate at this point).

Windows Version 10.0.18363 Build 18363

Hello guys, I'm coming to you as my last resort. I have no idea what's wrong with my computer, and I don't know how to fix it. Ever since I upgraded to the newest Windows 10 build, I've been running into BSODs constantly. It's too late for me to revert back to my previous version of windows 10. A piece of this error is that while I'm using the PC, randomly I'll get a BSOD. The Stopcodes have varied, I've gotten:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
KERNEL_DATA_INPAGE_ERROR
UNEXPECTED_STORE_EXCEPTION
CRITICAL_PROCESS_DIED

And other codenames. What's consistent about them is that it says "Collecting data", but it never actually does that. The percentage hangs at 0% and then my computer will restart. Once restarted, I get a blue screen that tells me:

"Your PC/Device needs to be repaired.

The application or operating system couldn't be loaded because a required file is missing or contains errors.

File:\WINDOWS\System32\winload.efi

Error code: 0xc000000e

You'll need to use recovery tools. If you don't have any installation media, contact your PC administrator or PC/Device manufacturer."

This screen has 4 options. I press enter to try again and it doesn't do anything. I can't access Startup Settings. I can only go into the recovery environment or UEFI Firmware Settings.

I've tried system restore and it hasn't worked. I've tried different cmds like "sfc /scannow" and it says there are no errors. Eventually I get to a point where I can "Continue into Windows 10" (from the Recovery Environment), and it usually boots like normal and then lets me into Windows 10 again, only for it to crash either shortly after or a few hours after, and then I'm back into the loop again. I got fed up of it earlier today and I decided to reset my pc, but I kept all of my files (because I can't afford to lose them). For a while, everything was working the way that it was supposed to and I started to reinstall my programs, only for me to eventually run into the BSOD again, despite this being a new install.

I don't know what's going on and I'm really worried because I use this desktop for work and for fun. I should also mention that I built this myself in 2017, but I don't know if it's hardware related because I haven't changed the hardware since then and everything appears to be working fine. Please let me know what I should do, and I hope that I don't have to completely wipe everything because I can't afford to right now. Thanks in advance.

I was able to get into my desktop between crashes (it's now having wifi problems) and I've attached the crash file too.

philc43 · 07 Feb 2020

Hello DownRoad and welcome to TenForums BSOD section

The first thing I would try is to reduce the clock speed of your memory. Currently it is running at 2400MHz which is too fast for the spec of the processor you are using. The Intel i5-6600K is recommended to work with memory at a maximum speed of 2133MHz.

Reduce the Memory clock speed in the BIOS settings and see if this makes a difference.

DownRoad · 07 Feb 2020

philc43 said:

Hello DownRoad and welcome to TenForums BSOD section

The first thing I would try is to reduce the clock speed of your memory. Currently it is running at 2400MHz which is too fast for the spec of the processor you are using. The Intel i5-6600K is recommended to work with memory at a maximum speed of 2133MHz.

Reduce the Memory clock speed in the BIOS settings and see if this makes a difference.

Hi and thanks for the quick reply!

I hadn't noticed this. I went into BIOS and switched it to 2133MHz. So far so good but I'm waiting if another crash happens.

zbook · 07 Feb 2020

Hi DownRoad,

Welcome to the TF BSOD forum.

The logs displayed BSOD however there were no dump files.

The opening post did not mention the use of tools to cause BSOD.
The logs displayed the current use of Windows driver verifier.
When was the tool started?
Which reference was viewed to run the tool?

What is the overclocking history?

Turn off Windows driver verifier.
The tool may be used later in the thread.

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}

12) 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

13) Make sure that there is no over clocking while troubleshooting

14) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

15) Run HD Tune (free version) (all drives)
HD Tune website
Post images into the thread for results on these tabs:
a) Health
b) Benchmark
c) Full error scan

16) Run Sea Tools for Windows
long generic test
Post an image of the test result into the thread
SeaTools for Windows |
Seagate
How to use SeaTools for Windows | Seagate Support US

17) The RAM is overclocked for the Intel CPU.
Philc43 had commented on the overclock.
Intel(R) Core™ i5-6600K Processor (6M Cache, up to 3.90 GHz) Product Specifications
DDR4-1866/2133
Speed: 2400

18) The BIOS is out of date (missed seven upgrades)
Upgrade the BIOS: 3020 > 3805
Z170I PRO GAMING Driver & Tools | Motherboards | ASUS USA

philc43 · 07 Feb 2020

DownRoad said:

Hi and thanks for the quick reply!

I hadn't noticed this. I went into BIOS and switched it to 2133MHz. So far so good but I'm waiting if another crash happens.

You are welcome. I think this should be the answer.

Do make sure you turn Driver Verifier off (as pointed out by zbook) because this will slow down you system and should only be used for short periods of testing (no more than 48hrs).

DownRoad · 07 Feb 2020

@zbook,

So after limiting my memory speed my desktop hasn't crashed yet, but I still went through all of these things in anticipation for a crash.

I think I started the Driver Verifier tool yesterday, but I've since turned it off on your guys' recomendations.

I used to overclock, but as of right now I haven't overclocked since at least last November.

I'm going to update the BIOS now, but I've done all of the rest of the work that you've prescribed and I'm attaching the screenshots to this thread. Note that I technically have 3 drives (2 internal SSDs and 1 HDD attached via a 3.0USB drive), but the tools only let me check/test the SSDs. The Sandisk SSD is my boot drive.

The CMD prompt info is below:

Code:

Microsoft Windows [Version 10.0.18363.628]
(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 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.18362.1

Image Version: 10.0.18363.628

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

[==========================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.
Volume label is Sandisk SSD.

Stage 1: Examining basic file system structure ...
  717824 file records processed.
File verification completed.
  19852 large file records processed.
  0 bad file records processed.

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

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

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

 233415995 KB total disk space.
 165420380 KB in 388668 files.
    260476 KB in 78306 indexes.
         0 KB in bad sectors.
    842763 KB in use by the system.
     65536 KB occupied by the log file.
  66892376 KB available on disk.

      4096 bytes in each allocation unit.
  58353998 total allocation units on disk.
  16723094 allocation units available on disk.

C:\WINDOWS\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\DESKTOP-45A0HFF\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Education|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\DESKTOP-45A0HFF\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Education|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'
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>bcdedit /enum {badmemory}

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

C:\WINDOWS\system32>

zbook · 07 Feb 2020

Is the drive detected by disk management or Mini Tool?

Open disk management > by default some columns are compressed > widen each Status and Volume > make sure the contents within the parenthesis are in full view and that none of the characters are cutoff > view disk 0 > widen this row as needed so that all of the characters are in full view > post an image into the thread
Disk Management - How to Post a Screenshot of

Download and install Minitool Partition Wizard > post an image of the results into this thread
MiniTool Partition Wizard Free Edition - Free download and software reviews - CNET Download.com

Run this additional drive test to see if the external drive is or is not detected:

Run HD Sentinel: (free or trial edition)
Hard Disk Sentinel - HDD health and temperature monitoring
Hard Disk Sentinel - HDD health and temperature monitoring
Post images of each of these tabs into the thread:
Overview tab
Temperature
SMART
Disk performance

DownRoad · 07 Feb 2020

@zbook @philc43 So I have bad news. In the middle of collecting data about my external drive (And yes, the computer does recognize it as a drive, but maybe because it's connected by a USB and not a SATA it's missing from the other applications?), I got another BSOD. It says

CRITICAL_PROCESS_DIED

It says the "We're just collecting some error info, then you can restart" but it's been stuck at 0% for 10 minutes now. This is after I did everything in @zbook 's initial post and I just finished updating the BIOS to the latest version.

philc43 · 07 Feb 2020

After the Bios update did you check the memory clock speeds were correct and not set too high again.

zbook · 07 Feb 2020

1) Power off and on
2) Upload a new V2 into the thread
3) Plan to run overnight RAM testing

4) For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

5) Run Memtest86 version 8.3 (or newer version if available) for four passes.
Repeat the test so that eight passes are performed.

MemTest86 - Official Site of the x86 Memory Testing Tool

Use a camera or smart phone camera to take pictures and post images into the thread.
In case there are any problems uploading images use share links (one drive, drop box, or google drive)

Memtest86 has a feature to produce a text report.
Please post this in addition to the images.

6) Make a new restore point:
Create System Restore Point in Windows 10