BSOD under load

Joined
Mar 20, 2017
Messages
8
Reaction score
0
I seem to randomly blue screen when my pc is under load, it seems to be when under heavy cpu load but not necessarily 100% load. Using prine95 a BSOD happens after 1 minute. Been happening for a while now and is becoming more frequent. I have reinstalled windows 10 once and reinstalled my AMD drivers multiple times using DDU to remove them.
Specs: FX 8350 4.0Ghz
GPU: r9 390x msi gaming 9gb
Motherboard: gigabyte 970a-ds3p
PSU: EVGA NEX650G- 80plus Gold
Windows 10 Ver 1607
 

Attachments

  • Dumps.zip
    372.3 KB · Views: 303

Regedit32

Moderator
Joined
Mar 4, 2016
Messages
3,617
Reaction score
1,139
Have you checked your air vents are clear and the fan is operational?

Could be a heating issue.
 

Trouble

Noob Whisperer
Moderator
Joined
Nov 19, 2013
Messages
13,411
Reaction score
2,319
AS an experiment uninstall Avast, using the Control Panel, Programs and Features applet.
Follow that up by running their vendor specific, proprietary removal tool from here https://www.avast.com/uninstall-utility
Afterwards, reboot and test run the system for a while and see if the Blue Screens persist.
 
Joined
Mar 20, 2017
Messages
8
Reaction score
0
Have you checked your air vents are clear and the fan is operational?

Could be a heating issue.

Ive bought an aftermarket cooler which has been fine for years and the cpu under load stays below 70 and around the 60s in degrees c
 
Joined
Mar 20, 2017
Messages
8
Reaction score
0
AS an experiment uninstall Avast, using the Control Panel, Programs and Features applet.
Follow that up by running their vendor specific, proprietary removal tool from here https://www.avast.com/uninstall-utility
Afterwards, reboot and test run the system for a while and see if the Blue Screens persist.

i tried this and the computer BSOD after 30 seconds of prime95
 

Attachments

  • 032017-12828-01.zip
    91.5 KB · Views: 264

Trouble

Noob Whisperer
Moderator
Joined
Nov 19, 2013
Messages
13,411
Reaction score
2,319
Download Memtest86+ from this location here. Burn the ISO to a CD and boot the computer from the CD from a cold boot after leaving it off for an hour or more.

Ideally let it run for at least 7 passes / 6-8 hours. If errors appear before that you can stop that particular test. Any time Memtest86+ reports errors, it can be either bad RAM or a bad Mobo slot. Perform the test RAM sticks individually as well as all possible combinations. When you find a good one then test it in all slots. Post back with the results.

See this Guide to using Memtest 86+

Just had a quick look at the most recent dump file you attached 032017-12828-01.dmp
IN that..... there is still references to multiple Avast drivers present on your system.
Specifically aswSP.sys (Avast Self Protection driver) aswbidsdrivera.sys (Avast Application Activity Monitor Driver) aswSnx.sys (Avast Virtualization driver)
ffffb380`19b0c488 fffff809`5e9263b1*** WARNING: Unable to verify timestamp for aswSP.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSP.sys
aswSP+0x263b1
ffffb380`19b0c490 00000000`00000000
ffffb380`19b0c498 ffffb380`1282f000
ffffb380`19b0c4a0 ffffcc00`8323c500
ffffb380`19b0c4a8 00000000`00000001
ffffb380`19b0c4b0 00000000`41735300
ffffb380`19b0c4b8 ffffb380`19b0db00
ffffb380`19b0c4c0 fffff802`36e80000 nt!WerLiveKernelInitSystem <PERF> (nt+0x0)
ffffb380`19b0c4c8 fffff809`00000000
ffffb380`19b0c4d0 ffffb380`19b0d378
ffffb380`19b0c4d8 00000000`00000000
ffffb380`19b0c4e0 fffff802`37157190 nt!_ymm+0x5acf0
ffffb380`19b0c4e8 00000000`00000000
ffffb380`19b0c4f0 ffffb380`19b0ca40
ffffb380`19b0c4f8 fffff802`371e2dac nt!BcpDisplayParameters <PERF> (nt+0x362dac)
ffffb380`19b0c500 ffffb380`19b08000
ffffb380`19b0c508 ffffb380`19b0e000
ffffb380`19b0c510 ffffb380`19b0cba0
ffffb380`19b0c518 ffffb380`19b0c900
ffffb380`19b0c520 fffff802`36fd9493 nt!KiSystemServiceCopyEnd+0x13
ffffb380`19b0c528 fffff802`36e80000 nt!WerLiveKernelInitSystem <PERF> (nt+0x0)
ffffb380`19b0c530 fffff802`371e2dac nt!BcpDisplayParameters <PERF> (nt+0x362dac)
ffffb380`19b0c538 ffffb380`19b0db00
ffffb380`19b0c540 fffff809`5e979cb0 aswSP+0x79cb0
ffffb380`19b0c548 ffffb380`19b0c570
ffffb380`19b0c550 fffff802`36fd9040 nt!KiSystemServiceHandler
ffffb380`19b0c558 fffff802`37157190 nt!_ymm+0x5acf0
ffffb380`19b0c560 ffffb380`19b0ca40
ffffb380`19b0c568 ffff8700`00000000
ffffb380`19b0c570 00000000`00000000
ffffb380`19b0c578 fffff809`5e92566c aswSP+0x2566c
ffffb380`19b0c580 ffffb380`19b0ca0c
ffffb380`19b0c588 ffffb380`19b0c7d0
ffffb380`19b0c590 00000000`00000000
ffffb380`19b0c598 fffff809`5e92513c aswSP+0x2513c
ffffb380`19b0c5a0 00001f80`0010000f
ffffb380`19b0c5a8 00000000`00000010
ffffb380`19b0c5b0 00010082`00000000
ffffb380`19b0c5b8 00000000`0000001d
ffffb380`19b0c5c0 00000000`00d400d4
ffffb380`19b0c5c8 ffff8700`a4df7840
ffffb380`19b0c5d0 00000000`00000000
ffffb380`19b0c5d8 fffff809`5e92a495 aswSP+0x2a495

In addition to another possibly suspect driver EasyAntiCheat.sys
 
Last edited:
Joined
Mar 20, 2017
Messages
8
Reaction score
0
Download Memtest86+ from this location here. Burn the ISO to a CD and boot the computer from the CD from a cold boot after leaving it off for an hour or more.

Ideally let it run for at least 7 passes / 6-8 hours. If errors appear before that you can stop that particular test. Any time Memtest86+ reports errors, it can be either bad RAM or a bad Mobo slot. Perform the test RAM sticks individually as well as all possible combinations. When you find a good one then test it in all slots. Post back with the results.

See this Guide to using Memtest 86+

I had already ran a memtest on my computer using a 16GB usb pendrive (16GB of system ram to match it) and i left it overnight and it said pass
 
Joined
Mar 20, 2017
Messages
8
Reaction score
0
Download Memtest86+ from this location here. Burn the ISO to a CD and boot the computer from the CD from a cold boot after leaving it off for an hour or more.

Ideally let it run for at least 7 passes / 6-8 hours. If errors appear before that you can stop that particular test. Any time Memtest86+ reports errors, it can be either bad RAM or a bad Mobo slot. Perform the test RAM sticks individually as well as all possible combinations. When you find a good one then test it in all slots. Post back with the results.

See this Guide to using Memtest 86+

Just had a quick look at the most recent dump file you attached 032017-12828-01.dmp
IN that..... there is still references to multiple Avast drivers present on your system.
Specifically aswSP.sys (Avast Self Protection driver) aswbidsdrivera.sys (Avast Application Activity Monitor Driver) aswSnx.sys (Avast Virtualization driver)


In addition to another possibly suspect driver EasyAntiCheat.sys

So I have tried to uninstall avast again using the link you provided and I did notice a folder called avast in my program data folder so i just deleted that although i doubt that would do anything to remove the avast drivers, I ran the test again and crashed after about a minute but this time when using windbg it said speccy.exe was running when it crashed so i uninstalled that and now the test lasts about 10 minutes and throws up a different bsod message.
 

Attachments

  • 032017-12828-01.zip
    91.5 KB · Views: 250

Trouble

Noob Whisperer
Moderator
Joined
Nov 19, 2013
Messages
13,411
Reaction score
2,319
It would appear that you have attached the same dump file now..... three (3) times 032017-12828-01.dmp
At least they appear to be exactly the same and therefore are not revealing much in the way of new information.
Stil showing Avast in the file above
aswbidsdrivera.sys
aswKbd.sys
aswMonFlt.sys
aswNetSec.sys
aswRdr2.sys
aswSnx.sys
aswSP.sys
aswStm.sys

I would expect to see at least some of them gone by now.
Are you certain that your machine is producing new dump files and that you are retrieving them from the proper location?
 
Joined
Mar 20, 2017
Messages
8
Reaction score
0
It would appear that you have attached the same dump file now..... three (3) times 032017-12828-01.dmp
At least they appear to be exactly the same and therefore are not revealing much in the way of new information.
Stil showing Avast in the file above
aswbidsdrivera.sys
aswKbd.sys
aswMonFlt.sys
aswNetSec.sys
aswRdr2.sys
aswSnx.sys
aswSP.sys
aswStm.sys

I would expect to see at least some of them gone by now.
Are you certain that your machine is producing new dump files and that you are retrieving them from the proper location?

My apologies, windows decided it didnt need to order the dumps by time, let me send you the most recent one.
 

Attachments

  • 032017-5796-01 - Copy.zip
    73.6 KB · Views: 268

Trouble

Noob Whisperer
Moderator
Joined
Nov 19, 2013
Messages
13,411
Reaction score
2,319
Well that's new (sort of)
Probably caused by : memory_corruption
Followup: memory_corruption
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE
STACK_COMMAND: .cxr 0xffff90017bdfd090 ; kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
BUCKET_ID: MEMORY_CORRUPTION_LARGE
PRIMARY_PROBLEM_CLASS: MEMORY_CORRUPTION_LARGE
So, I'm still thinking memory although I wouldn't necessarily still dismiss a possible third party driver. You have several
npf.sys
speedfan.sys
vbaudio_vmvaio64_win7.sys
vbaudio_vmauxvaio64_win7.sys
LGJoyXlCore.sys
LGBusEnum.sys
CorsairVBusDriver.sys
CorsairVHidDriver.sys
lgcoretemp.sys
RTKVHD64.sys
rzendpt.sys
rzudd.sys
rzpnk.sys
rzpmgrk.sys
rt640x64.sys
CorsairGamingAudioamd64.sys
ladfGSS.sys
A couple of which are a little old. So....
to the extent possible you may want to consider addressing these in a manner or fashion so as to eliminate them from the diagnostic process. Update / Upgrade, uninstall or break them by renaming.
It is important to note that none of these are actually called out in the dump file or enumerated in any back trace, I've seen, so....

That leaves us with memory and perhaps
1. Confirm that you are not overclocking the installed memory, nor the installed video adapter.
2. Since, associated with the memory corruption issue, there is mention of
fffff802282fa17c-fffff802282fa17d 2 bytes - nt!MiInsertLargePageInNodeListHelper+4c
[ 80 fa:00 a6 ]
fffff802282fa998-fffff802282fa999 2 bytes - nt!RemoveListHeadPte+8c (+0x81c)
Both of which suggesting possible "pagefile" involvement, so.....
You may want to use a hard disk diagnostic utility to assess the system drive's health.
AND
IF it is an SSD, assure that you have the most recent manufacturer's firmware installed.
 
Joined
Mar 20, 2017
Messages
8
Reaction score
0
Well that's new (sort of)

So, I'm still thinking memory although I wouldn't necessarily still dismiss a possible third party driver. You have several

A couple of which are a little old. So....
to the extent possible you may want to consider addressing these in a manner or fashion so as to eliminate them from the diagnostic process. Update / Upgrade, uninstall or break them by renaming.
It is important to note that none of these are actually called out in the dump file or enumerated in any back trace, I've seen, so....

That leaves us with memory and perhaps
1. Confirm that you are not overclocking the installed memory, nor the installed video adapter.
2. Since, associated with the memory corruption issue, there is mention of

Both of which suggesting possible "pagefile" involvement, so.....
You may want to use a hard disk diagnostic utility to assess the system drive's health.
AND
IF it is an SSD, assure that you have the most recent manufacturer's firmware installed.

My memory is running at its stock frequency, which is fairly low i think it was 1600Mhz, my gpu is overclocked out of the box but it has been fine for a long time. My C(windows installation) drive is an SSD so i will attempt to see if there is any updated firmware for it. I will try this and then post results
 
Joined
Mar 20, 2017
Messages
8
Reaction score
0
This time with prime95 one of the worker threads failed as it had repeated Illegal sumouts but then a few minutes later got another bsod. Ive installed the sandisk firmware for my ssd, i moved my pagefile to my D drive which is a 1tb samsung ssd, i set the minimum pagefile to 1gb (windows wanted 800 minimum) and the maximum to 16gb.
 

Attachments

  • 032017-5765-01.zip
    92 KB · Views: 253

Trouble

Noob Whisperer
Moderator
Joined
Nov 19, 2013
Messages
13,411
Reaction score
2,319
That one is all about page file issues (page file number / page table entry, etc., )

Normally this is where I would recommend running Driver Verifier. You need to be aware that under some very rare circumstance the use of Driver Verifier can result in unexpected consequences you should probably only consider running it if you are relatively certain that you have the skill set to recover from a worst case scenario.
Please do some research and make sure you know how to run DV (how to start it and what to check) start by reading this reference Driver Verifier - Windows 7 & Vista (read it carefully) and probably just as important if not more how to stop running it.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top