Nonstop BSODs make me afraid to touch my PC

QCesarJr · 15 Jan 2016

Hello Everyone,

I've had an issue for a while now. I bought my PC about 2 years ago with Windows 8.1. I've since updated to Windows 10, and I also run a dual boot with Server 2012 R2. It's a CyberPowerPC Fangbook HX7-300. About 7 months ago, I started experiencing BSODs. I don't remember what I did that started causing them. I don't have any overclocking.

Well, the issue is that I'll randomly get these BSODs. It's 100% guaranteed I'll get multiple in a day. I've updated all my drivers. The problem seems to be aggravated severely by running Virtual Machines. But, even when I'm not, I'll have at least 3 or 4 in a day, and I only use it maybe 2 to 3 hours at most. Also, the BSODs happen in both Windows 10 and Windows Server 2012 R2, but I can only remember them happening on the server when running VMs.

I hope someone can help. I'd really appreciate it. I'm at wits end! I'm also ashamed that I haven't been able to identify it myself, since I work in IT. I've just never had to deal with debugging via memory dumps. Finally, driver verifier is enabled on the last 3 of these dumps, I believe. Thanks!!

axe0 · 17 Jan 2016

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.

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.

QCesarJr · 19 Jan 2016

Hello axe0,

I haven't yet run MemTest86+, but I did run System File Check. There's errors it can't fix.

Here's the Google Drive link to CBS.log. CBS.log - Google Drive

I'll post MemTest86+ results soon.

Thanks for helping out! I really appreciate it.

axe0 · 19 Jan 2016

Please try following command in admin command prompt

Code:

DISM /Online /Cleanup-Image /RestoreHealth

If there are problems with RestoreHealth, please follow step 6 or 7 (depending on the file you have from the download) from the tutorial DISM - Repair Windows 10 Image - Tutorial.

After DISM restorehealth has succesfully finished run SFC + reboot + SFC again, that should resolve the corruption found by SFC.

SFC can't fix it, because the source is also corrupted. To fix the source corruption DISM is required and another SFC for the file corruption.