BSOD Errors 3-4 times a day and I cant find the reason

[MART3R]

I recently bought a new motherboard, PSU and another GPU to add to my pc to run in SLI. I have been getting BSOD errors ever since I put them in my PC.

List of things Ive done to try to solve the problem:
- Brand new 700w Bronze PSU
- Reinstalled graphics drivers and some others
- Reinstalled windows
- Swapped GPU places
- Swapped SLI bridge
- Underclocked RAM
- Used CCleaner to find registry errors
- Windows BSOD TroubleShoot & Hardware Troubleshoot
- Checked power connectors to everything
- SuperAntiSpyware & Malwarebytes scans
- Cried

*When I got the new motherboard I had to change the voltage to my CPU in the bios cuz it was at 1.46V (overheating af) at stock its at 1.27V now.

*These Blue screens happen at random about 3-4 times a day.

*(System Thread Exception Not Handled)&(System Service Exception) are the errors

Dont really know how to read the event log but it says Kernel-Power 41 under Critical and its been saying that since before the new PSU. Im pretty sure its the problem but beside changing the PSU idk what to do.

Please help.


My box:
- Gigabyte GA-970 Gaming SLI (new)
- FX8350 @4Ghz w/ HyperT4 (Old & worked fine before)
- 8GB Kingston HyperX Fury 1333mhz Ram (Old & worked fine before)
- 2TB Seagate + 1TB Seagate HDDs & 120Gb Sandisk SSD (Old & worked fine before)
- MSI gtx960 4g (new)
- MSI gtx960 4g (Old & worked fine before)
- EVGA 700w BRONZE (new)

I have no idea what to even look for at this point maybe I should just givew up and buy a console.

Any advice helps.

 

[kaptainkuftic]

Have you tried Display Driver Uninstaller?

Also, next time your machine BSODs, hit start, type 'event viewer', hit enter, open 'Windows logs', click 'system', and look for anything that comes up as an error. Click that entry and read the information it gives at the bottom of the screen. Try and find the root cause of the BSOD that way.

 

[Jesse_20]

I'd double check system temps in msi commnd center. Make sure the cpu is not overheating still. Try re-applying thermal paste if it's hot, or if cores report different temps (over 3-5 degrees difference).
Also, double check all your connections in the case and make sure you don't have a loose or misplaced wires.

A kernel power warning on the cpu means that it isn't getting enough power from the motherboard, or it is a failing cpu, usually.
Also, make sure you have updated the bios of the new board to rule that out as a cause.

 

[cryoburner]

Have you tried temporarily removing one of the GPUs and testing the system running with a single GPU? You might try one GPU on its own for one day, and the other on its own another day and see whether the crashes still occur with each of those configurations, to help find whether there might be a problem with one of the cards.

 

[t53186]

I don't see anything listed about reinstalling the OS after changing out that motherboard. Blue screens usually mean hardware/drivers.

 

[MART3R]

I'd double check system temps in msi commnd center. Make sure the cpu is not overheating still. Try re-applying thermal paste if it's hot, or if cores report different temps (over 3-5 degrees difference).
Also, double check all your connections in the case and make sure you don't have a loose or misplaced wires.

A kernel power warning on the cpu means that it isn't getting enough power from the motherboard, or it is a failing cpu, usually.
Also, make sure you have updated the bios of the new board to rule that out as a cause.

Ive run PRIME95 for an hour with HWMONITOR and CPU-Z and MSI Afterburner monitoring temps and my CPU never went above 42 degrees Celsius. My motherboard went up to 58C on one of it's heatsinks and my gpus go up to 78C when I benchmark them but those are the two hottest temps in my PC.

When I go the new motherboard I had to underclock the voltage because the stock voltage was way too high (1.46V) when the recommended stock voltage is 1.3V. I brought it down to 1.27V do you think maybe thats too low even though it ran fine when I stress tested it for an hour?

 

[Jesse_20]

It's possible the low voltage might be throttling the cpu, which would toss the error.
I'd start with the bios update, then set the mobo to default settings and see what voltage it hits.
It might have misidentified your hardware.

One other thing I'd check is to make sure your motherboard isn't trying to run power saving features if it offers that feature (in the bios).

 

[MART3R]

It's possible the low voltage might be throttling the cpu, which would toss the error.
I'd start with the bios update, then set the mobo to default settings and see what voltage it hits.
It might have misidentified your hardware.

One other thing I'd check is to make sure your motherboard isn't trying to run power saving features if it offers that feature (in the bios).

How do you update the bios? I saw on the drivers website that there was a version of the bios called F1 available but thats the same version that I have, Ive only just bought the motherboard last week and Im pretty sure it has the most recent bios version.

 

[t53186]

It's possible the low voltage might be throttling the cpu, which would toss the error.
I'd start with the bios update, then set the mobo to default settings and see what voltage it hits.
It might have misidentified your hardware.

One other thing I'd check is to make sure your motherboard isn't trying to run power saving features if it offers that feature (in the bios).

How do you update the bios? I saw on the drivers website that there was a version of the bios called F1 available but thats the same version that I have, Ive only just bought the motherboard last week and Im pretty sure it has the most recent bios version.

Did you do a fresh install of the operating system or move that drive over to this motherboard from and existing system

 

[MART3R]

It's possible the low voltage might be throttling the cpu, which would toss the error.
I'd start with the bios update, then set the mobo to default settings and see what voltage it hits.
It might have misidentified your hardware.

One other thing I'd check is to make sure your motherboard isn't trying to run power saving features if it offers that feature (in the bios).

How do you update the bios? I saw on the drivers website that there was a version of the bios called F1 available but thats the same version that I have, Ive only just bought the motherboard last week and Im pretty sure it has the most recent bios version.

Did you do a fresh install of the operating system or move that drive over to this motherboard from and existing system

I fresh installed Windows 10 x64 the day I got the mobo, and again yesterday hoping that it would fix the problem. It them proceeded to BSOD error in the middle of reinstalling my apps.

 

[t53186]

Then you got a real hardware problem and no point in installing apps. You need to get a clean load of windows before proceeding. No amount of bios tweaking or other adjustments is going to fix an underlying hardware problem. That reused CPU and memory needs to confirmed to be 100% compatible with the new motherboard-find that info on the MB site. If you can't get a clean load of windows 10 without blue screens and the hardware is compatible it would be time to send that MB back or consider a different manufacturer.

 

[Jesse_20]

After looking, you are correct in that there are no bios updates for that board yet.

What is the BSOD error that you are getting exactly?
(something to the effect of 0x000000008b)

Have you tried your old PSU with only s ingle GPU installed to see if it still occurs?
Have you tried the new PSU with only 1 GPU to see if it still occurs?

You could try (from cmd prompt as administrator) "sfc /scannow" and "chkdsk /f" to see if there are any issues with the drive file system.
Those probably won't help, but worth a shot.

If your old motherboard can support sli, have you tried booting everything in it with the new PSU to rule out the new mobo?

One last thing I can think of atm is to set the voltage to 1.3 and see if that helps matters at all.

 

[MART3R]

Then you got a real hardware problem and no point in installing apps. You need to get a clean load of windows before proceeding. No amount of bios tweaking or other adjustments is going to fix an underlying hardware problem. That reused CPU and memory needs to confirmed to be 100% compatible with the new motherboard-find that info on the MB site. If you can't get a clean load of windows 10 without blue screens and the hardware is compatible it would be time to send that MB back or consider a different manufacturer.

It says that all AMD FX cpus are supported so I guess it is the motherboard. I really wanted to avoid RMAing it because I did tamper the the cpu voltage to underclock it so Im not sure if theyll accept it but I will try. That really blows, thanks for the advice tho.

 

[t53186]

Then you got a real hardware problem and no point in installing apps. You need to get a clean load of windows before proceeding. No amount of bios tweaking or other adjustments is going to fix an underlying hardware problem. That reused CPU and memory needs to confirmed to be 100% compatible with the new motherboard-find that info on the MB site. If you can't get a clean load of windows 10 without blue screens and the hardware is compatible it would be time to send that MB back or consider a different manufacturer.

It says that all AMD FX cpus are supported so I guess it is the motherboard. I really wanted to avoid RMAing it because I did tamper the the cpu voltage to underclock it so Im not sure if theyll accept it but I will try. That really blows, thanks for the advice tho.

How about the RAM? and when or if you do another clean install try loading the chipset drivers before anything software or drivers.

 

[MART3R]

After looking, you are correct in that there are no bios updates for that board yet.

What is the BSOD error that you are getting exactly?
(something to the effect of 0x000000008b)

Have you tried your old PSU with only s ingle GPU installed to see if it still occurs?
Have you tried the new PSU with only 1 GPU to see if it still occurs?

You could try (from cmd prompt as administrator) "sfc /scannow" and "chkdsk /f" to see if there are any issues with the drive file system.
Those probably won't help, but worth a shot.

If your old motherboard can support sli, have you tried booting everything in it with the new PSU to rule out the new mobo?

One last thing I can think of atm is to set the voltage to 1.3 and see if that helps matters at all.

I dont know where to find the BSOD error that Im getting.
Ive tried using that scan via CMD and no problems were found. Ive also tried different combinations of my hardware as I was waiting for other parts to arrive and stuff:
Old PSU + 1GPU + Old Mobo = No BSOD
Old PSU + 1GPU + New Mobo = No BSOD (used it a very short time)
Old PSU + 2GPU + New Mobo = BSOD
New PSU + 2GPU + New Mobo = BSOD
I initially thought it could be the new GPU but I cant find a single thing about GPUs causing this type of problem.

Today I will try raising CPU Voltage, should it persist I will remove my new GPU, should it persist further I will return my motherboard and hope for the best. Maybe save up a while to buy a better one from the dudes down at ASUS.

 

[MART3R]

Then you got a real hardware problem and no point in installing apps. You need to get a clean load of windows before proceeding. No amount of bios tweaking or other adjustments is going to fix an underlying hardware problem. That reused CPU and memory needs to confirmed to be 100% compatible with the new motherboard-find that info on the MB site. If you can't get a clean load of windows 10 without blue screens and the hardware is compatible it would be time to send that MB back or consider a different manufacturer.

It says that all AMD FX cpus are supported so I guess it is the motherboard. I really wanted to avoid RMAing it because I did tamper the the cpu voltage to underclock it so Im not sure if theyll accept it but I will try. That really blows, thanks for the advice tho.

How about the RAM? and when or if you do another clean install try loading the chipset drivers before anything software or drivers.

Kingston HyperX Fury Ram 8GB(2x4g) DDR3 @1333mhz = Worked fine for more then a few months before I bought my new hardware and this problem started. I dont know how to check compatibility but Im pretty sure its not dying and wouldnt even start up if it wasnt compatible right?

 

[t53186]

Then you got a real hardware problem and no point in installing apps. You need to get a clean load of windows before proceeding. No amount of bios tweaking or other adjustments is going to fix an underlying hardware problem. That reused CPU and memory needs to confirmed to be 100% compatible with the new motherboard-find that info on the MB site. If you can't get a clean load of windows 10 without blue screens and the hardware is compatible it would be time to send that MB back or consider a different manufacturer.

It says that all AMD FX cpus are supported so I guess it is the motherboard. I really wanted to avoid RMAing it because I did tamper the the cpu voltage to underclock it so Im not sure if theyll accept it but I will try. That really blows, thanks for the advice tho.

How about the RAM? and when or if you do another clean install try loading the chipset drivers before anything software or drivers.

Kingston HyperX Fury Ram 8GB(2x4g) DDR3 @1333mhz = Worked fine for more then a few months before I bought my new hardware and this problem started. I dont know how to check compatibility but Im pretty sure its not dying and wouldnt even start up if it wasnt compatible right?

http://www.gigabyte.us/Motherboard/GA-970-Gaming-SLI-rev-10#support-doc is the memory support list, need the part # off the memory module to verify, and yes your cpu is on the compatible list

 

[MART3R]

Then you got a real hardware problem and no point in installing apps. You need to get a clean load of windows before proceeding. No amount of bios tweaking or other adjustments is going to fix an underlying hardware problem. That reused CPU and memory needs to confirmed to be 100% compatible with the new motherboard-find that info on the MB site. If you can't get a clean load of windows 10 without blue screens and the hardware is compatible it would be time to send that MB back or consider a different manufacturer.

It says that all AMD FX cpus are supported so I guess it is the motherboard. I really wanted to avoid RMAing it because I did tamper the the cpu voltage to underclock it so Im not sure if theyll accept it but I will try. That really blows, thanks for the advice tho.

How about the RAM? and when or if you do another clean install try loading the chipset drivers before anything software or drivers.

Kingston HyperX Fury Ram 8GB(2x4g) DDR3 @1333mhz = Worked fine for more then a few months before I bought my new hardware and this problem started. I dont know how to check compatibility but Im pretty sure its not dying and wouldnt even start up if it wasnt compatible right?

http://www.gigabyte.us/Motherboard/GA-970-Gaming-SLI-rev-10#support-doc is the memory support list, need the part # off the memory module to verify, and yes your cpu is on the compatible list

HX313C9FK2/8 is the model number I believe

 

[crosslhs82]

Don't know if this will help you but
The max voltage ocing the fx 8350 is 1.55. So the 1.46 is still safe.
Your setting of 1.46 in bios is very close to my ga 970 gaming sli /8350.
On mine @4.0ghz turbo upto 4.2ghz hwinfo64 shows 1.36 idle , stressing with prime95 blend will go to 1.42.
I would say reset cmos start over at stock bios settings.
Just know that this board my NOT TAKE OC mine is throttling me at anything over 4.3ghz which I'm thinking it's the vrm's even with a fan on them.
Ga-970 gaming sli
Fx8350
H100i w/cooler
Zotac gtx 960
Corsair Cs or cx 750 psu
Crucial ballistix elite 1866 cl9
Crucial 525gb ssd os
Pny 120gb programs
Toshiba 1tb storage
Hope this helps.

 

[MART3R]

This problem ended up being a CPU under-voltage issue. During my initial stress test before posting this issue I tested for 1 hour showing no problems. After being out of ideas I tested for 10 hours and it finally showed issues with my chosen voltage. After raising the voltage accordingly I never had this issue again.