Windows 10: BSODs randomly, different errors

So I've been using Windows 10 since I was able to upgrade with little to no problems. Then suddenly, on October 8th I think, during a Windows update all hell broke loose. Audio cut out, network connections went up and down, and the computer crashed within minutes. Removing the graphics card eased the amount of crashes, but even when stripped down to motherboard+CPU+hard drive, it still crashes (also, I tried putting the graphics card in a friend's computer with Win7, it ran flawlessly, were started up some GTA5 and no problems).

I get different errors, the ones I've had are:
CRITICAL_PROCESS_DIED
WHEA_UNCORRECTABLE_ERROR
KERNEL_DATA_INPAGE_ERROR
UNEXPECTED_STORE_EXCEPTION

I've "reset" my installation of Windows, but the error remains. When I restart the computer, I have to do it 2 or 3 times. Other times it just crashes, shows a blank "active" screen, or BSOD. I've updated the motherboard BIOS, downloaded the latest drivers, but still it keeps crashing and failing to reboot.

I'd like to do a clean install of Windows 10 (instead of a reset), but I am unsure how, since I upgraded from Windows 7: I don't have a 25-digit product key to enter. Any ideas?

My computer:
MBR: Asus H97M-E (mATX)
CPU: Intel i7-4790K
RAM: 16 GB DDR3 (8 GB x 2)
GFX: GeForce GTX 780 3 GB

:)

 

Multiple BSODs with differen't errors

I uninstalled AVIRA as suggested and ran the verifier for another 24 hours. There were no crashes so I turned the verifier off, reinstalled the bluetooth drivers and the computer ran fine for a day. The crashing has started again today to the point where
I cant even get to the log in screen. I will post any new minidumps when I make it to the desktop.

Computer runs in safemode but there are no new minidumps past 11/07/16 to upload.

Thanks,

Lewis

 

Multiple BSODs with differen't errors

I left the computer on overnight running the verifier and when I came to it this morning it had frozen with no BSOD or minidump. Should I continue running the verifier?

Thanks,

Lewis

 

Hi fill,

Welcome to the 10forums.

All of the most recent crashes are 0xEF(CRITICAL_PROCESS_DIED), but only the most recent one releaved the following
Code: Debugging Details: ------------------ ----- ETW minidump data unavailable----- DISK_IO_READ_FAILURE: WARNING: Disk IO Read of 0 Bytes Occurred 1f time(s). PROCESS_OBJECT: ffffe00023c52840 IMAGE_NAME: svchost.exe DEBUG_FLR_IMAGE_TIMESTAMP: 0[/quote] Meaning there is an Input/Output error with the hard drive, meaning the data can't be read from your hard drive.






Diagnostics Test

HDD & SSD TEST


Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums



Note Do not run SeaTools on an SSD as the results will be invalid.



Run chkdsk Disk Check - Windows 7 Help Forums

 

Hello,

Thank you for the reply! I do have an SSD (15 months old), so I ran a Windows 10 chkdsk (Disk -> Properties -> Tools -> Check) instead of the recommended SeaTools, but it came up empty:
Code: Chkdsk was executed in scan mode on a volume snapshot. Checking file system on C: Stage 1: Examining basic file system structure ... 413184 file records processed. File verification completed. 24535 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 495008 index entries processed. Index verification completed. Stage 3: Examining security descriptors ... Security descriptor verification completed. 40913 data files processed. CHKDSK is verifying Usn Journal... 41679200 USN bytes processed. Usn Journal verification completed. Windows has scanned the file system and found no problems. No further action is required. 233865215 KB total disk space. 209825968 KB in 248333 files. 163064 KB in 40914 indexes. 533899 KB in use by the system. 65536 KB occupied by the log file. 23342284 KB available on disk. 4096 bytes in each allocation unit. 58466303 total allocation units on disk. 5835571 allocation units available on disk. ---------------------------------------------------------------------- Stage 1: Examining basic file system structure ... Stage 2: Examining file name linkage ... Stage 3: Examining security descriptors ... Windows has scanned the file system and found no problems. No further action is required.[/quote] Any other suggestions, or another disk check tool to recommend?

 

HDTune is a good one, I use it to keep an eye on my HDD.

 

No dice there either:
Code: HD Tune: Crucial_CT240M50 Error Scan Scanned data : 228845 MB Damaged Blocks : 0.0 %[/quote] Oh well, I've managed to exctract the product key, create a Windows 10 install USB stick and I've ordered a new disk, so I'm going to try a new, clean, install tomorrow, and that will hopefully help.

 

Diagnostics Test

System File Check
Please try following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.






Diagnostics Test

Malware scan
Please run a threat scan with Malwarebytes*, a full scan with your AV, scan your system with Adwcleaner, Kaspersky TTDSKiller and ESET Online Scanner
*(Uncheck trial version in the installation process)

 

Did the system file check, first time:
Code: 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.[/quote] Second time (had to restart twice because of crash):
Code: 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.[/quote] Downloading malware tools now...

 

Malwarebytes: No threats found
TDSSKiller: No threats found
AdwCleaner: Found no malicious programs
ESET Online Scanner: No threats found

 

Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.






Diagnostics Test

Clean boot
Please try the following:

• Open taskmanager
  • Go to the tab startup
  • disable everything
• Search msconfig and open it
  • Go to the tab services
  • Check 'hide microsoft services'
  • Uncheck all other services
  • Click apply and click ok
• Reboot if asked

See if the problem persist, if the problem does not persist enable in the startup tab in taskmanager 1 item and in the services tab in msconfig also 1 service, reboot and see if the problem persist. Keep doing this until you find the culprit or there is nothing left.
If the problem still persist, try booting in safe mode and see if the problem still persist

Please fill in your system specsPlease follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU and cooling system.How to fill in your system specs:

 

I let the memory test run during the night, no errors.

I deactivated all startup programs and non-MS services, still crashed (multiple times) on startup.

Booted up in safe mode (with networking), and it does seem to work now... it started up fine, and so far so good.

I've ed in the rest of my case components in my profile now too.

 

Good to hear, please stay in safe mode for a few hours to be sure.
Safe mode rules out most of the hardware components as with some software and drivers that are loaded in safe mode.

 

Will do, and glad to hear that.

Because I have so much trouble with the reboots, I decided to reboot from safe mode into safe mode with msconfig to see what would happen, and it booted and let me log in flawlessly again.

I'll let the system run for a few hours now!

 

Just wanted to share how it ended:

I could start it up in safe mode, but whenever I started it up normally it crashed before starting, and then finally crashed (though it could take a couple of hours). I finally did a complete reinstall, and now it all works fine. I guess we'll never know exactly what it was, but I thank you for all the help!

Should I mark it as solved?