Multiple BSODs After Windows 10 Clean Install

LACSTS · 11 Jan 2016

I recently upgraded from Windows 8.1 to Windows 10 via a clean install.

Ever since I have been getting multiple BSODs for what appears to be all different reasons. My system worked fine before this. The BSODs seem to be random. I have tried updating drivers and such to no effect. I ran Prime95 for 12 hours straight with no problems.

I'm at a loss here. Any help is greatly appreciated. I read the BSOD posting guidelines. Pretty sure I am posting this correctly. If not Im sorry.

Attachment 58425

LACSTS · 11 Jan 2016

I just took a band new Intel 530 240GB SSD and did a clean install of Windows 10. I didnt install any programs or anything. Just installed Windows 10 and activated it.

As soon as I got to the desktop I went to the updates and got a BSOD. I restarted and then managed to get into the updates and checked for and installed the 2 or 3 updates that there were.

With no programs installed or anything I have had 3 BSODs in about 15 mins with the computer just sitting there.

Attached is the BSOD info from the clean install on the new SSD.

Attachment 58435

axe0 · 13 Jan 2016

Please uninstall ESET and let me know if it improves anything
How do I manually uninstall my Windows ESET product?ESET Knowledgebase

Code:

ffffd000`214f2338  ffffe001`02a6220a em006_64+0xa20a

LACSTS · 13 Jan 2016

I will do that now. But if that does fix the BSOD problem does that mean I cannot use ESET on this system? Or is there a specific part of ESET that is causing the BSODs?

Thank you for your help

LACSTS · 14 Jan 2016

I uninstalled ESET using the directions in the link that you posted for me. Still getting multiple BSODs.

Attachment 58733

axe0 · 14 Jan 2016

Warning

Programs that claim to update your drivers install either the wrong or corrupted drivers.
If you have installed any driver with Driver Booster 3, please remove them as it may cause trouble.

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.

Diagnostic Test

RAM TEST

Run MemTest86+ to analyse your RAM. 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.

LACSTS · 14 Jan 2016

I have an update.

Responding to your last post, I installed the driver booster just to check if it found any drivers that were out of date. I have since uninstalled it.

After that I did the following.

I ran sfc/scannow and it completed successfully with the "Windows Resource Protection did not find any integrity violation" message.

So I ran MemTest86+.

Attachment 58878

Then I ran it a few times while removing DIMMs and switching them around to verify what stick it was and whether or not it was one of the motherboard DIMM slots. It ended up being a stick of RAM. I had a brand new set of DDR3 laying around. 4 X 2GB. So after verifying that it was the RAM and not the motherboard I installed the new RAM and am currently running MemTest86+ on the new RAM. I am on pass 3 with 0 errors so far. So I for sure had bad RAM. Hopoefully that is the only problem that was causing all these BSODs.

I will report back once I get 8 or more passes with the new RAM on MemTest86+.

Thank you so much for your help. I appreciate it.

axe0 · 15 Jan 2016

Let me know how it goes :)