Random BSOD (mostly during gaming) going on for 5 years since built PC

Hey guys,

I have been having problems with my computer for years. Ever since I built my PC I have unknowingly had a counterfeit version of Windows 7 installed. I actually formatted my hard drive to install a new windows 7 which I bought, and it turned out to be counterfeit too when I went to sevenforums to try to fix my bluescreens. I was informed that upgrading to windows 10 would probably help, since it is legitimate. So I bought windows 10 off the microsoft website and upgraded. I thought my problems would be gone but they still remain. When I am playing games like Player Unknown's Battlegrounds or Overwatch I get blue screens and it is very inconvenient.

This is super frustrating and I have spent the past few days just trying to figure out what is wrong with my computer. I have all my drivers updated, I've run diagnostic tools. Last night I saw where running the MemTestx86 was recommended and so I ran that for around 15 hours - 8 passes and no errors.

If anyone could help me fix this problem or even give me a clue of faulty hardware, I would be eternally grateful. This really is time consuming and so annoying when I have to let my friends know my computer crashed again mid-game.

Thank you!

I recently ran PC-Doctor to see if my PC had any hardware problems. Everything passed. But it does have a log of previous crashes, hoping this may help.

6/16/2017 8:08 AM	Unexpected Shutdown: The previous system shutdown at 2:54:26 AM on ‎6/‎16/‎2017 was unexpected.
6/16/2017 8:06 AM	Operating System Crash: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xffffd18b6bbb7196, 0xffffe400a9c85f10, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: d97c9deb-57e0-48c9-bdea-4085422a097a.
6/16/2017 8:06 AM	Operating System Crash: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000012b (0xffffffffc00002c4, 0x00000000000005e0, 0x0000000000805740, 0xffffe20046f3a000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 0c0934ba-f355-41cb-a7b8-9e5c14a803f0.
6/16/2017 8:06 AM	Operating System Crash: No description available.
6/15/2017 9:31 PM	Application Error: Fault bucket 120768438333, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: svchost.exe_SysMain P2: 10.0.15063.0 P3: 02799ef5 P4: sysmain.dll P5: 10.0.15063.332 P6: ec6f3af6 P7: c0000305 P8: 000000000003192a P9: P10: Attached files: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_svchost.exe_SysM_ccf7cafa368e9ff386f63f96b fe34b3db449ebed_c7f5885c_cab_1b71d617\minidump.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD1D2.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD1F3.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD213.tmp.txt \\?\C:\Windows\Temp\WERD222.tmp.appcompat.txt C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_svchost.exe_SysM_ccf7cafa368e9ff386f63f96b fe34b3db449ebed_c7f5885c_cab_1b71d617\memory.hdmp These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_svchost.exe_SysM_ccf7cafa368e9ff386f63f9 6bfe34b3db449ebed_c7f5885c_0786a89a Analysis symbol: Rechecking for solution: 0 Report Id: 1494b13e-51df-427c-9c04-7c9e26bb0d78 Report Status: 268435456 Hashed bucket: 5ff9159e6434ee9ccc0d506fc6a52c3a
6/15/2017 9:31 PM	Application Error: Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: svchost.exe_SysMain P2: 10.0.15063.0 P3: 02799ef5 P4: sysmain.dll P5: 10.0.15063.332 P6: ec6f3af6 P7: c0000305 P8: 000000000003192a P9: P10: Attached files: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_svchost.exe_SysM_ccf7cafa368e9ff386f63f96b fe34b3db449ebed_c7f5885c_cab_1b71d617\minidump.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD1D2.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD1F3.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD213.tmp.txt \\?\C:\Windows\Temp\WERD222.tmp.appcompat.txt C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_svchost.exe_SysM_ccf7cafa368e9ff386f63f96b fe34b3db449ebed_c7f5885c_cab_1b71d617\memory.hdmp These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_svchost.exe_SysM_ccf7cafa368e9ff386f63f96b fe34b3db449ebed_c7f5885c_cab_1b71d617 Analysis symbol: Rechecking for solution: 0 Report Id: 1494b13e-51df-427c-9c04-7c9e26bb0d78 Report Status: 4 Hashed bucket:
6/15/2017 9:30 PM	Application Error: Faulting application name: svchost.exe_SysMain, version: 10.0.15063.0, time stamp: 0x02799ef5 Faulting module name: sysmain.dll, version: 10.0.15063.332, time stamp: 0xec6f3af6 Exception code: 0xc0000305 Fault offset: 0x000000000003192a Faulting process id: 0xb38 Faulting application start time: 0x01d2e61e6c9e8cd4 Faulting application path: c:\windows\system32\svchost.exe Faulting module path: c:\windows\system32\sysmain.dll Report Id: 1494b13e-51df-427c-9c04-7c9e26bb0d78 Faulting package full name: Faulting package-relative application ID:
6/15/2017 9:29 PM	Operating System Crash: No description available.
6/15/2017 9:29 PM	Unexpected Shutdown: The previous system shutdown at 2:23:23 PM on ‎6/‎15/‎2017 was unexpected.
6/15/2017 6:42 PM	Application Error: Fault bucket 108941564306, type 1 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: Battle.net Helper.exe P2: 0.0.0.0 P3: 5926239f P4: libcef.dll P5: 3.2623.1433.0 P6: 590b8573 P7: 80000003 P8: 0019afa9 P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3578.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3809.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3827.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3838.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Battle.net Helpe_189232126db2c81761bf57f7362a8b84a8daa43d_c64db845_16e840b3 Analysis symbol: Rechecking for solution: 0 Report Id: e1086f9d-810c-4515-841f-db09512e91e8 Report Status: 268435456 Hashed bucket: 6a356a618ae4c5910e368647c8a21d43
6/15/2017 6:42 PM	Application Error: Faulting application name: Battle.net Helper.exe, version: 0.0.0.0, time stamp: 0x5926239f Faulting module name: libcef.dll, version: 3.2623.1433.0, time stamp: 0x590b8573 Exception code: 0x80000003 Fault offset: 0x0019afa9 Faulting process id: 0x2108 Faulting application start time: 0x01d2e607278dd85d Faulting application path: C:\Program Files (x86)\Blizzard App\Battle.net.8839\Battle.net Helper.exe Faulting module path: C:\Program Files (x86)\Blizzard App\Battle.net.8839\libcef.dll Report Id: e1086f9d-810c-4515-841f-db09512e91e8 Faulting package full name: Faulting package-relative application ID:
6/15/2017 6:06 PM	Application Error: Fault bucket 127907047987, type 5 Event Name: WindowsUpdateFailure3 Response: Not available Cab Id: 0 Problem signature: P1: 10.0.15063.0 P2: 80070103 P3: C4182659-D11B-415D-8DD4-0EE8ADEC87AC P4: Install P5: 200 P6: 0 P7: 80070103 P8: Device Driver Retrieval Client P9: {9482F4B4-E343-43B6-B170-9A65BC822C77} P10: 0 Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCA62.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCA91.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCAA2.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_10.0.15063.0_2eba8ffeaa6967ea3a3a18dd 1c552f3be8ed5d8e_00000000_1da36a06 Analysis symbol: Rechecking for solution: 0 Report Id: 0c02ca5e-aec2-4cd5-810b-a294c5b5f0e3 Report Status: 268435456 Hashed bucket: 4c4dc06dead1e10e68e37d15fad06007
6/15/2017 5:41 PM	Application Error: Fault bucket , type 0 Event Name: WindowsUpdateFailure3 Response: Not available Cab Id: 0 Problem signature: P1: 10.0.15063.0 P2: 80070103 P3: C4182659-D11B-415D-8DD4-0EE8ADEC87AC P4: Install P5: 200 P6: 0 P7: 80070103 P8: Device Driver Retrieval Client P9: {9482F4B4-E343-43B6-B170-9A65BC822C77} P10: 0 Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCA62.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCA91.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCAA2.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_10.0.15063.0_2eba8ffeaa6967ea3a3a18dd1c 552f3be8ed5d8e_00000000_cab_090bcaa1 Analysis symbol: Rechecking for solution: 0 Report Id: 0c02ca5e-aec2-4cd5-810b-a294c5b5f0e3 Report Status: 4 Hashed bucket:
6/15/2017 5:41 PM	Application Error: Fault bucket , type 0 Event Name: WindowsUpdateFailure3 Response: Not available Cab Id: 0 Problem signature: P1: 10.0.15063.0 P2: 80070103 P3: C4182659-D11B-415D-8DD4-0EE8ADEC87AC P4: Install P5: 200 P6: 0 P7: 80070103 P8: Device Driver Retrieval Client P9: {9482F4B4-E343-43B6-B170-9A65BC822C77} P10: 0 Attached files: These files may be available here: Analysis symbol: Rechecking for solution: 0 Report Id: 0c02ca5e-aec2-4cd5-810b-a294c5b5f0e3 Report Status: 1074003968 Hashed bucket:

Hi Dhopk,

Open administrative command prompt and type or copy and paste:

1) winver (in the pop up about windows > view your windows version and build > type this information into the thread)

2) sfc /scannow

3) dism /online /cleanup-image /restorehealth

4) chkdsk /scan

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 copy > paste into the thread

5) Run memtest86+ version 5.01 for at least 8 runs. This may take hours so plan to run it overnight.
Memtest86+ - Advanced Memory Diagnostic Tool When 8 or more runs have been made please use the snipping tool to post images in the thread.

6) Please run one of these drive SMART tests and post images into the thread:
Hard Disk Sentinel - HDD health and temperature monitoring
CrystalDiskInfo - Software - Crystal Dew World
http://www.hdtune.com/

7) perform windows updates and post any KB# that failed to install with error code.

I'm not on my computer right now I'm away from my desktop. But I have ran all the commands earlier. The sfc, dism, chkdsk, all passed with no problems. I also ran memtest for 8 passes, took 16 hours. No errors. I have all updates none failed to install. Once I get back to my computer I can still give you this info and run a SMART test.

Code:

BugCheck 12B, {ffffffffc00002c4, 5e0, 805740, ffffe20046f3a000}

*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by : memory_corruption

Code:

BugCheck 3B, {c0000005, ffffd18b6bbb7196, ffffe400a9c85f10, 0}

Probably caused by : memory_corruption

Please make sure that all of your files are backed up.
Please create a restore point.

Pending the review of the tests and the drive test we may proceed to using windows driver verifier to stimulate the drivers. Simulation of the drivers will make the misbehaving drivers produce bsods.
The bsods will reoccur until windows driver verifier is turned off or until there are no longer any misbehaving drivers.
In order to use Windows driver verifier you must have your files backed up and must have a restore point. And you must know how to navigate through the Windows recovery or advanced troubleshooting menu to be able to enter the command to turn off Windows driver verifier.
In the left lower corner search type verifier to open windows driver verifier.
This will be done at a later time.
The method to turn off Windows driver verifier is via the windows advance troubleshooting menu with navigation to startup options (not startup repair). In startup options you will select #6 safe mode with command prompt. To turn off windows driver verifier you will type this command: verifier /reset
You then will be able to break the bsod cycle and reboot to the desktop.

Each time you return to the desktop you will use software that will immediately analyze the bsod. You will download and install each Bluescreenview and Whocrashed. They produce similar results but one may offer additional information.

When each bsod is displayed while using windows driver verifier there will be a stop code. The stop code most commonly is driver verifier detected violation. Sometimes the malfunctioning driver is displayed in addition to the stop code in the form *.sys. If you see the driver displayed please record it.

The default setting for system > advanced settings > startup and recovery settings often is automatically restart. This needs to be changed so that you have time to view the bsod windows. Make sure this box is unchecked before using windows driver verifier.
BSOD Finding and fixing them - Microsoft Community

To get practice navigating the windows advanced troubleshooting menu open administrative command prompt and type or copy and paste this command: shutdown /r /o /f /t 00
The computer will reboot to the windows recovery or advanced troubleshooting menu.
Navigate to start up options. Get familiar with the restart option and choosing safe mode with command prompt.
After each bsod you will need to be able to get to the windows advanced troubleshooting menu to turn off windows driver verifier by first opening safe mode with command prompt and then entering the stop command: verifier /reset

Each time you have a bsod please update the zip file or post a new one so that we can debug the minidump files and view the updated logs.

This is a link to study before using windows driver verifier. It has the customized settings for the test and drivers. Again you must have all files backed up, a new restore point and feel comfortable navigating the windows advanced troubleshooting menu before using the tool.
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

The above is a preview pending the results of previously ordered tests. You will need to know how to uninstall and reinstall drivers. Sometimes applications are the source of bsod. The misbehaving applications can often be uninstalled and reinstalled. Sometimes windows driver verifier will make a freshly installed application bsod. In such cases an alternative application can be chosen.

When using windows driver verifier there are generally two methods. One method is to keep running windows driver verifier until all bsod are identified, all misbehaving drivers are uninstalled and there are no more instantaneous bsod. An alternative method is to uninstall a driver and reinstall it before restarting windows driver verifier. This will retest the new driver before finding other misbehaving drivers. The method is by preference. The outcome should be the same.


Blue screen of death (STOP error) information in dump files.
http://www.resplendence.com/whocrashed

Thank you, once I get back to my computer tomorrow I will do all this and report back.

Microsoft Windows
Version 1703 (OS Build 15063.413)

Microsoft Windows [Version 10.0.15063](c) 2017 Microsoft Corporation. All rights reserved.C:\Windows\system32>winverC:\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 /restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.15063.0
Image Version: 10.0.15063.0[==========================100.0%==========================]
The restore operation completed successfully.
The operation completed successfully
.C:\Windows\system32>chkdsk /scan
The type of the file system is NTFS.
Stage 1: Examining basic file system structure ... 165376 file records processed.
File verification completed. 4488 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ... 227104 index entries processed.
Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found.
Stage 3: Examining security descriptors ...Security descriptor verification completed.
30865 data files processed.
CHKDSK is verifying Usn Journal...
37120544 USN bytes processed.
Usn Journal verification completed.
Windows has scanned the file system and found no problems.
No further action is required.
976657407 KB total disk space.
63278488 KB in 129663 files.
90316 KB in 30866 indexes.
0 KB in bad sectors.
299559 KB in use by the system.
65536 KB occupied by the log file.
912989044 KB available on disk.
4096 bytes in each allocation unit.
244164351 total allocation units on disk.
228247261 allocation units available on disk.

C:\Windows\system32>

I ran Memtest x86 for 8 passes it took 15 hours so i'm not going to do it again. I have a picture of the screen so if you need it please let me know.

Thank you!

At your earliest opportunity please post an image of the memtest86+ displaying at least 8 runs and the results.

If you have files backed up, have created a new restore point, and understand how to turn off windows driver verifier you can start using it to produce bsod.

When you have new bsod please update the zip file or create a new one so that we can analyze the minidump files and help you or guide you as needed through the uninstallations and reinstallations of drivers and applications.

Here is the memtest screen. Do I have to buy another harddrive to back up my files? I don't know how to without buying something extra
.Attachment 140304

You can make an image of your drive:
Hard Drive Image Software
https://www.sevenforums.com/tutorial...e-macrium.html
https://www.macrium.com/reflectfree?x-ca=blog