lots of BSOD issues mini dmps attached

[jaryd.l]

I am at my wits end with this i have tried everything i can to fix it, i have updated drivers, reset the motherboard, done all the scans i can, reformatted the hard drive and nothing. but i still get random blue screens, i dont know what to do anymore please help.

dmp files are here these are only from this month it has been going on since i got the PC

https://1drv.ms/f/s!AmY7tsrpMHfBhRgPO2OJSFCX0cec

 

[jaryd.l]

tried a memory diagnostic came up with nothing

 

[gardenman]

Hi jaryd.l, the built in Windows Memory Diagnostic probably isn't the best. Use [MemTest86] and only test 1 RAM stick at a time. It appears as if you are using 2 x 8 GB sticks of Kingston RAM (if I'm reading the info correctly).

BSODs are usually caused by either bad drivers or bad hardware (including overheating).

I've ran your dump files through the debugger and got these results: https://pastebin.com/RQ0ud67E

Spoiler

File: 081417-10500-01.dmp (Mon Aug 14 02:21:16 2017)
BugCheck: [KMODE_EXCEPTION_NOT_HANDLED (1E)] {ffffffffc0000005, fffff8024c5f40b4, 0, ffffffffffffffff}
Probably caused by: amdppm.sys (Process: System)

File: 080217-5421-01.dmp (Wed Aug 2 00:57:02 2017)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)] {24, ff, 0, fffff80213a79c0a}
Probably caused by: memory_corruption (Process: System)

File: 080417-6875-01.dmp (Thu Aug 3 22:52:15 2017)
BugCheck 3D, {ffffa1809065bd08, ffffa1809065b550, 0, 0}
Probably caused by: memory_corruption (Process: System)

File: 080517-6750-01.dmp (Sat Aug 5 01:42:32 2017)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)] {2184ac3, e, 1, fffff803c220b222}
Probably caused by: win32kfull.sys (Process: Steam.exe)

File: 080517-7843-01.dmp (Fri Aug 4 20:44:39 2017)
BugCheck: [KMODE_EXCEPTION_NOT_HANDLED (1E)] {ffffffffc000001d, fffff8020916fbd5, ffff898054ba9d80, 0}
Probably caused by: memory_corruption (Process: System)

File: 080617-15484-01.dmp (Sun Aug 6 01:11:30 2017)
BugCheck: [DRIVER_VERIFIER_DETECTED_VIOLATION (C4)] {62, ffffae086c26ffb0, ffffae086eb2f350, 1}
Probably caused by: memory_corruption (Process: System)

File: 081017-5843-01.dmp (Wed Aug 9 19:34:52 2017)
BugCheck: [KMODE_EXCEPTION_NOT_HANDLED (1E)] {ffffffffc0000096, fffff80235176146, 0, 0}
Probably caused by: ntkrnlmp.exe (Process: System)

File: 081017-35671-01.dmp (Wed Aug 9 17:35:23 2017)
BugCheck: [DRIVER_VERIFIER_DETECTED_VIOLATION (C4)] {e2, fffff105b17ca990, 28f04a20080, 0}
Warning: Unable to verify timestamp for: BEDaisy.sys
Probably caused by: memory_corruption (Process: BEService.exe)

File: 081417-5781-01.dmp (Sun Aug 13 19:34:13 2017)
BugCheck: [PAGE_FAULT_IN_NONPAGED_AREA (50)] {ffffbac1f47da748, 0, ffffbaa1f23dc1e4, 2}
Probably caused by: memory_corruption (Process: dwm.exe)

File: 081417-5828-01.dmp (Sun Aug 13 19:24:49 2017)
BugCheck: [DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1)] {0, 2, 8, 0}
Probably caused by: ntkrnlmp.exe (Process: System)

File: 081417-5875-01.dmp (Sun Aug 13 20:04:09 2017)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)] {6938, 2, 1, fffff8000a08763a}
Probably caused by: memory_corruption (Process: System)

File: 081417-6390-01.dmp (Sun Aug 13 19:54:33 2017)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)] {0, e, 1, fffff80379d79b8c}
Probably caused by: memory_corruption (Process: System)

File: 081417-6921-01.dmp (Sun Aug 13 19:47:35 2017)
BugCheck 101, {18, 0, ffffa4011fe80180, 3}
Probably caused by: memory_corruption (Process: DriverBooster.exe)

File: 081417-7765-01.dmp (Mon Aug 14 01:53:54 2017)
BugCheck: [DRIVER_OVERRAN_STACK_BUFFER (F7)] {ffff978038838b00, b98dc697082b, ffff46723968f7d4, 0}
Probably caused by: ntkrnlmp.exe (Process: System)

File: 081417-7796-01.dmp (Sun Aug 13 19:09:43 2017)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)] {100005bbf, e, 1, fffff80256b742c2}
Probably caused by: ntkrnlmp.exe (Process: System)

I'm no expert at reading dump files. There are experts here and if you are lucky one will stumble upon us and help.

Updating older drivers may help. You said you have already updated your drivers, but I see a few older drivers and I've listed them below. Try to update these if possible. You may find drivers at your PC manufacturers website, or the motherboard manufacturers website.

Spoiler

Image name: amdide64.sys
Possible Info: AMD SATA Controller driver http://support.amd.com/
Timestamp : Tue Dec 4 2012

Image name: HWiNFO64A.SYS
Possible Info: HWiNFO AMD64 Kernel Driver https://www.hwinfo.com/
Timestamp : Tue Mar 31 2015

Image name: cpuz140_x64.sys
Timestamp : Sun Aug 14 2016

I've noticed that you have used Driver Booster (one of the crashes above blamed DriverBooster.exe). Uninstall it. Automatic driver update programs such as this often get drivers wrong causing BSODs and other problems. This issue [comes up here often].

Your BIOS is outdated (2012). I recommend updating to the latest version. It can be downloaded [here]. I would write down all of your BIOS settings before hand (or better yet, use your phone and take pictures of all of the screens) because it says on the page that all settings will be reset when you update.

For the next few days of testing, I recommend unplugging all external devices from your PC. Try to strip it down as much as possible to eliminate any devices that could be causing the BSODs. (Webcams, Printers, etc.) Once the BSODs stop, you can gradually plug the devices back in, 1 per week to see if they are causing the crashes.

If the above doesn't help, there are a few more tests we can run and if I can't help you I'll bring someone else in. Take your time and work on all of the above, write back with the results. Good luck.

 

[Hscumbie]

Specs? Mostly concerned with PSU.

 

[jaryd.l]

specs:

PSU: thermaltake litepower 550W

I have now updated my bios but cant find those old drivers that were shared with me in particular the kernel driver

 

[jaryd.l]

also i dont have anything plugged in aside from 3.5mm jack speakers and a usb mouse and usb keyboard, but i know they arent the problem because ive changed them a few times since ive gotten the pc

 

[Hscumbie]

also i dont have anything plugged in aside from 3.5mm jack speakers and a usb mouse and usb keyboard, but i know they arent the problem because ive changed them a few times since ive gotten the pc

And its my understanding that you've done a clean install?

 

[jaryd.l]

Correct I have preformed 2 clean install, currently running the first of the two memtest86 so far 60% through one stick with no errors

 

[Hscumbie]

Correct I have preformed 2 clean install, currently running the first of the two memtest86 so far 60% through one stick with no errors

It almost sounds like it could be a PSU issue. I'd keep doing some mem tests. You might wanna take a look at this:http://www.tomshardware.com/forum/id-2547993/psu-tier-list.html

 

[jaryd.l]

Funny you say that actually when I bought the pc the original psu died after about 6 hours so I got this one, should I go up in wattage?

 

[Hscumbie]

Funny you say that actually when I bought the pc the original psu died after about 6 hours so I got this one, should I go up in wattage?

i don't think it needs to be wattage, just take a look at the PSU tier list. yours falls into tier 3 which isn't bad at all but also isn't the best. Have you noticed any behaviours that will trigger a BSOD?

 

[jaryd.l]

Generally when I am running multiple programs, chrome, steam, a game, spotify etc. Just the regular things like that. But sometimes it's also completely fine or I'll just be browsing the internet and it will blue screen, I wish I could tie it to something but it just seems to happen randomly

 

[jaryd.l]

So I just finished both memtest86 for each ram stick and there have been no errors found on either of them. Not sure where to go from here

 

[gardenman]

Ok so you have:
- Checked the RAM with MemTest86 - no errors.
- Updated BIOS - was 2012, now 2016.

Have you had any additional crashes since the BIOS update? My next ideas were a hard drive test and a CPU test.

Give [CrystalDiskInfo] Standard Edition a try. I honestly don't know anything about it. I guess if it shows errors, you have problems. [Post a screen shot] of it.

I'm not sure which is the best test for an AMD CPU. I believe that MemTest86 has a CPU test built into it that you might want to try. Another one is [Prime95].

Do you have anything to monitor the temperatures? Do you still have HWInfo installed? (That was one of the old drivers so try an updated version of it). If so, what are your temps while idle and while stressed?

 

[jaryd.l]

No blue screens yet
Temps idle around 30c-40c and under heavy load between 50c-70c at most
I will give crystal disk a go now

 

[jaryd.l]

crystal disk shows: http://imgur.com/a/ZIhjO
results of prime95

[Tue Aug 15 15:57:59 2017]
First 2 workers:
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.

4 following workers:
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.

remaining 2 workers:
no errors

 

[gardenman]

Ok so you have:
- Checked the RAM with MemTest86 - no errors.
- Updated BIOS - was 2012, now 2016.
- Passed Disk check.
- Failed CPU test.

If you have any additional crashes, upload the dump files (I prefer at least 3 or so at a time). I'm still hopeful that the BIOS update helped.

I'll try to find help from someone who know what they are talking about with the CPU errors.

Processor Version: AMD FX(tm)-8350 Eight-Core Processor
MHZ: 4000

Until then, you can look around here: https://www.google.com/search?q=prime95+ERROR%3A+ILLEGAL+SUMOUT

 

[gardenman]

Can you upload the results of the Prime95 test and the Readme.txt file too. Any and all TXT files and results would be helpful (stress.txt, etc). You can ZIP them up if you like.

Do you have the 8350 Black edition?

I've been told that a max of 70c is a little warm for FX chips, they start to slow down around 60.

 

[RedJaron]

What motherboard are you using? The higher end FX-8000 CPUs have a higher power draw and need a more robust motherboard to deal with it. Most 760 boards can't reliably power an 8350 and even some cheaper 970 boards have problems with it. Even at stock clocks the VRMs sometimes cough a little and destabilize the CPU.

 

[gardenman]

Hi RedJaron, this page shows the info that I pulled directly from the dump file: https://pastebin.com/RQ0ud67E

It says his motherboard is: ASRock 970 Pro3 R2.0
(and I gave him a link to update the BIOS for it and he did).

He hasn't replied in a day so maybe he'll reply later on.

I appreciate the help.

 

[RedJaron]

Well, in case he does come on, here's something to try if it is indeed the mboard's VRM. Many AMD CPUs of that generation had more voltage at stock settings than they really needed. It wasn't uncommon to overclock the CPU while undervolting it below stock. If you want to keep it at stock clocks, you should be able to drop the power consumption pretty well. That would make it easier on the VRM.

 

[Rogue Leader]

That board has 4+1 VRM setup, known to be inadequate for the FX-8350

http://www.overclock.net/t/946407/amd-motherboards-vrm-info-database

I'd bet dollars to doughnuts that his motherboard is the issue here.

 

[jaryd.l]

hi guys sorry have been without the net a few days, got a few more bsods! here they are:

https://1drv.ms/f/s!AmY7tsrpMHfBhRqhLF96cIO6X-kD

and no i just have the regular 8350, i do think the bios update helped a bit but still getting a few bsods here and there.
as for clocking i actually have no idea how that works to be quite honest i just reset everything to the default on the bios.

 

[Rogue Leader]

hi guys sorry have been without the net a few days, got a few more bsods! here they are:

https://1drv.ms/f/s!AmY7tsrpMHfBhRqhLF96cIO6X-kD

and no i just have the regular 8350, i do think the bios update helped a bit but still getting a few bsods here and there.
as for clocking i actually have no idea how that works to be quite honest i just reset everything to the default on the bios.

As I said, that board straight up is not cut out to handle the FX-8350 even at stock speeds and settings. Thats the source of your BSODs.

 

[jaryd.l]

ah bummer 🙁 any cheap recommendations?