BSOD Playing games ntoskrnl.exe+175880 0x00000139 0x0000007a

Hello Everyone,

So story is since start of December last year I been having issues when I play video games (Spellforce3, World of Warcraft, Arma3)

What would happen is I hear a loud screech in headphones and my computer would freeze and can not click anything and have to do a hard reboot.

Since then I have sent my 1080 card back to where I bought it from for them to check it and it was found no problems with it. I used DDU to remove old drivers see if that solves it, And it did not.

I sold the 1080 card and bought a 1080 TI Strix again used DDU before installing and after couple days having same issues.

I then looked at checking my memory using memtest 86 there was no errors found I even checked the ram individually there was no errors. I only did 1 parse (25mins) on each one.

I done a checkdisk \ f \ r

And no fix for it and has gotten worst. It now happens 4-5 times a day compared to december and jan which was every couple days.

Computer Freeze in game and it now restarts on its own and has now started to create crash dumps.

I have been told before I send this computer back to try and reinstall the os and see if that helps so before I do that I posting on here to see if anyone else have ideas on the problem.

I have included the TFDebug files crash dumps, drivers, dxdiag, hosts, msinfo, systeminfo and task lisk..

Welcome to the BSOD forum.

1) Files within the log collector were missing event log, installed, uninstalled, etc.
Please run this version and post a zip into this thread:
log collector v2-beta08.zip

2) Update the BIOS: BIOS Version/Date American Megatrends Inc. 3504, 29/06/2017 > 3703

Version 3703
2018/01/158.16 MBytes
MAXIMUS VIII HERO
Fixed SAMSUNG M.2 device issue.
Fixed SanDisk M.2 device issue.
Fixed AMD RADEON SSD device issue.
Improved DRAM compatibility.

3) Uninstall AVG
How to uninstall AVG software | AVG Support

4) Turn on Windows defener

5) AVG can be reinstalled in 2 weeks if there are no recurrent BSOD. If there are recurrent BSOD after reinstalling the AV software > find alternative AV software. If there are no recurrent BSOD > continue using AVG.

6) Make sure that there is no over clocking during the troubleshooting process.

7) Open administrative command prompt and type or copy and paste:
8) sfc /scannow
9) dism /online /cleanup-image /restorehealth
10) chkdsk /scan
11) 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

Code:

19/12/2017 23:30    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 119
P2: a
P3: 20536e9
P4: 20536ea
P5: ffffe480a961f010
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\121917-4781-01.dmp
\\?\C:\WINDOWS\TEMP\WER-6875-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER287A.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER287D.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER288E.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_119_c00e11aa58ed11fd3aee20844da8eefa459be_00000000_cab_20c0bd74

Analysis symbol: 
Rechecking for solution: 0
Report Id: 2f9dc062-f4ef-4628-9fac-2a8153178774
Report Status: 2049
Hashed bucket:19/12/2017 23:29    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 119
P2: a
P3: 20536e9
P4: 20536ea
P5: ffffe480a961f010
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\121917-4781-01.dmp
\\?\C:\WINDOWS\TEMP\WER-6875-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER287A.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER287D.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER288E.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_119_c00e11aa58ed11fd3aee20844da8eefa459be_00000000_03fc2887

Analysis symbol: 
Rechecking for solution: 0
Report Id: 2f9dc062-f4ef-4628-9fac-2a8153178774
Report Status: 4
Hashed bucket:
13/02/2018 18:28    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 139
P2: 3
P3: ffff8387e2ff6c10
P4: ffff8387e2ff6b68
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\021318-4968-01.dmp
\\?\C:\WINDOWS\TEMP\WER-6687-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2D3A.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2D59.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2D6A.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_139_e9847b7f54804b33e2e1d6912b7674dbceccb7c9_00000000_cab_1f383539

Analysis symbol: 
Rechecking for solution: 0
Report Id: ee7dce83-690b-48ac-a820-d6083c5ef16b
Report Status: 2049
Hashed bucket:
13/02/2018 18:28    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 139
P2: 3
P3: ffff8387e2ff6c10
P4: ffff8387e2ff6b68
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\021318-4968-01.dmp
\\?\C:\WINDOWS\TEMP\WER-6687-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2D3A.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2D59.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2D6A.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_139_e9847b7f54804b33e2e1d6912b7674dbceccb7c9_00000000_03202d69

Analysis symbol: 
Rechecking for solution: 0
Report Id: ee7dce83-690b-48ac-a820-d6083c5ef16b
Report Status: 4
Hashed bucket:
10/02/2018 20:45    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 1e
P2: ffffffffc0000005
P3: fffff8029e3d9422
P4: 0
P5: ffffffffffffffff
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\021018-4562-01.dmp
\\?\C:\WINDOWS\TEMP\WER-6234-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2A0D.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2A1D.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2A2D.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1e_7df2a40c3754ffef352f24664fb7d7366483dd2_00000000_cab_206c33a2

Analysis symbol: 
Rechecking for solution: 0
Report Id: 873d4a56-803d-40c1-b42f-f3991be2c88b
Report Status: 2049
Hashed bucket:
10/02/2018 20:45    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 1e
P2: ffffffffc0000005
P3: fffff8029e3d9422
P4: 0
P5: ffffffffffffffff
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\021018-4562-01.dmp
\\?\C:\WINDOWS\TEMP\WER-6234-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2A0D.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2A1D.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2A2D.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1e_7df2a40c3754ffef352f24664fb7d7366483dd2_00000000_03282a2c

Analysis symbol: 
Rechecking for solution: 0
Report Id: 873d4a56-803d-40c1-b42f-f3991be2c88b
Report Status: 4
Hashed bucket:
13/02/2018 17:53    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 7a
P2: 1
P3: ffffffffc0000005
P4: ffff998deef59580
P5: ffffc00144b58000
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\021318-15156-01.dmp
\\?\C:\WINDOWS\TEMP\WER-17234-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER53BE.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER53BF.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER53D0.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_7a_f13e3681b38db3ef1d84899b6573831d74692fd0_00000000_cab_219c40a2

Analysis symbol: 
Rechecking for solution: 0
Report Id: 6436b014-be72-4cb0-9409-ef2c8d6f8ae2
Report Status: 2049
Hashed bucket:
13/02/2018 17:34    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 7a
P2: 1
P3: ffffffffc0000005
P4: ffff998deef59580
P5: ffffc00144b58000
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\021318-15156-01.dmp
\\?\C:\WINDOWS\TEMP\WER-17234-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER53BE.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER53BF.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER53D0.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_7a_f13e3681b38db3ef1d84899b6573831d74692fd0_00000000_031853cd

Analysis symbol: 
Rechecking for solution: 0
Report Id: 6436b014-be72-4cb0-9409-ef2c8d6f8ae2
Report Status: 4
Hashed bucket:

1) open file explorer > this PC > C: > in the right upper corner search for:
a) win32kbase.sys
b) win32kbase.sys-20180210-2045.dmp
c) win32kbase.sys-20180210-2045.dmp
C:\windows\memory.dmp
Post zips or share links into the thread.
2) Turn off Windows fast start up:
Turn On or Off Fast Startup in Windows 10 | Windows 10 Tutorials
3) In the left lower corner search type: system > open system control panel > on the left pane click advanced system settings >
a) under performance click settings > on performance options click the advanced tab > under virtual memory click change > post an image of the virtual memory window into the thread
b) under startup and recovery click settings > post an image of the startup and recovery window into the thread
4) Open Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread
5) Open administrative command prompt and type or copy and paste:
6) sfc /scannow
7) dism /online /cleanup-image /restorehealth
8) chkdsk /scan
9) 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
10) Modify the free space on drive C: so that there is 15% - 20% or more free space



Drive: C:
Free Space: 15.5 GB
Total Space: 241.3 GB
File System: NTFS
Model: SAMSUNG MZHPV256HDGL-00000

Code:

Event[4295]:  Log Name: System  Source: ACPI  Date: 2018-02-06T16:07:41.225  Event ID: 15  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Windows10  Description: : The embedded controller (EC) returned data when none was requested. The BIOS might be trying to access the EC without synchronizing with the operating system. This data will be ignored. No further action is necessary; however, you should check with your computer manufacturer for an upgraded BIOS.

Code:

Event[1121]:  Log Name: System  Source: Application Popup  Date: 2018-01-17T23:54:39.111  Event ID: 26  Task: N/A  Level: Information  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: Windows10  Description: Application popup: Windows - Virtual Memory Minimum Too Low : Your system is low on virtual memory. Windows is increasing the size of your virtual memory paging file. During this process, memory requests for some applications may be denied. For more information, see Help.

Code:

Event[3682]:  Log Name: System  Source: Volsnap  Date: 2018-02-03T01:47:51.779  Event ID: 24  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Windows10  Description: There was insufficient disk space on volume C: to grow the shadow copy storage for shadow copies of C:.  As a result of this failure all shadow copies of volume C: are at risk of being deleted.

Code:

Event[2999]:  Log Name: System  Source: Volsnap  Date: 2018-01-27T13:58:39.207  Event ID: 33  Task: N/A  Level: Information  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Windows10  Description: The oldest shadow copy of volume C: was deleted to keep disk space usage for shadow copies of volume C: below the user defined limit.

Code:

Event[747]:  Log Name: System  Source: Display  Date: 2018-01-17T11:44:46.857  Event ID: 4115  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Windows10  Description: Display driver failed to start; using Microsoft Basic Display Driver instead. Check Windows Update for a newer display driver.

1) For Ccleaner:
a) un-check memory dumps
b) un-check Windows log files

2) For Virtual memory:
a) un-check no paging file
(uncheck automatically manage paging file size for all drives > move the dot from no paging file to system managed file > recheck automatically manage paging file size for all drives > reboot)

If @zbook does not object I'd like to make a couple of observations.

1. The memory testing that you did is not sufficient to detect any problems with your RAM. You would need to run the Memtest86+ for at least 8 passes which would take the best part of 1-2 days to complete. In my view you should complete these tests properly to rule out any problems with your RAM. One of your crash dumps showed memory corruption as a possible cause.

Code:

BugCheck 7A, {1, ffffffffc0000005, ffff998deef59580, ffffc00144b58000}
Probably caused by : memory_corruption ( nt!MiMakeSystemAddressValid+1e8 )

2. AVG is definitely implicated when debugging the crash, best to run with it completely removed and rely on Windows Defender for now:

Code:

BugCheck 139, {3, ffff8387e2ff6c10, ffff8387e2ff6b68, 0}
*** WARNING: Unable to verify timestamp for avgMonFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for avgMonFlt.sys
Probably caused by : avgMonFlt.sys ( avgMonFlt+299f )

Hello,

I just done a 6 hour memtest 86 with 9 passes no errors.

AVG is removed now.

Not sure what next to do

Just use it as normal and see if you get any new BSOD events. If you do then post a new set of logfiles.
Thanks!

It appears that Memetest86+ version 5.01 was not used.
Please confirm.
Were you able to use a camera to take a picture to post into the thread?