Getting many different BSOD errors on new custom pc build

[Rednick]

Hello folks,

I am having issues with custom gaming rig I built not too long ago. It started basically after I finally got everything installed and happens randomly throughout gaming or even just my wife doing online school. Even the BSOD crash errors are random not showing any particular pattern at least not to my eyes.

On to the troubleshooting I have done. I have ran sfc \scannow, dxdiag, chkdsk \r, and memtest86. All of these come back with no issues except SFC says there are corrupted files that windows could not fix. I have ran full scans using Windows Security Essentials which did kill some Trojans. I also have ran Malwarebytes Anti-Malware free edition (yes with rootkits) which killed a lot of PUP optionals as well as a few malware infections and a couple more Trojans. After both killing these I have run these scans again with no threats found.

The Blue screens seem to happen when the PC is left alone for a while I stopped sleep mode thinking that might be it but even when the monitor goes to sleep and the PC is running normally if I come back to it an hour or so later it will be sluggish then BSOD as soon as you do anything that wasn't already on. It will also happen after gaming for more than a few hours.

Any help I could get sorting this out would be appreciated! I have attached what the Batch file did to this post.

Thanks for your time,


Nick

 

[axe0]

Hi Rednick,

Welcome to the 7forums.

Please remove Gigabyte software, it is known for causing BSOD's.

There are a few crashes consistent, the 0x24, 0x4E and 0x1A.
The 0x4E and 0x1A are related to the memory and the 0x24 to the hard drive.
I suggest you run a few tests to determine if the problems are hardware.
I am aware you have performed some already, but please run them again according to the instructions below.

With SSD, only run chkdsk.
With HDD and SeaTools, prefered at least SMART, short generic and long generic tests.

Diagnostics Test

 HDD TEST

Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk http://www.sevenforums.com/tutorials/433-disk-check.html

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Forums

   Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

 

[Rednick]

Thanks for the response.

I have one question regarding the Gigabyte software. ET6 is what is currently making my cpu cooling fans operate. Is there another way to control the fan power through the actual BIOS? also does this include HWMonitor? I will check back in once I am home and have performed your tests.

 

[axe0]

I am sorry, but I can't tell you what other way you could control the fans. My BIOS is extremely basic with my laptop and I don't need any software for the fans.

 

[Rednick]

Update:

Haven't finished Memtest yet but Seatools SMART, Short Generic, and Long Generic tests all passed. I have also removed all Gigabyte software.

 

[Rednick]

Okay over 24 hours later memtest is finished. 9 pass no errors. Any other thoughts?

 

[axe0]

Have there been new crashes?

 

[Rednick]

so far no BSOD but internet browsers are crashing now...

 

[axe0]

Crashes that give no messages you mean?

 

[Rednick]

Yes says internet explorer stopped working. Also had another BSOD today.

 

[axe0]

When you have another BSOD, just run the BSOD tool and upload the new zip

 

[Rednick]

Here is the new zip. Thoughts?

 

[axe0]

Read the instructions for driver verifier carefully!

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

[Rednick]

Ran the driver verifier over night got on this morning and windows explorer crashed and the display crashed no BSOD just locked up no display just lines of color with a mouse cursor that would not move. I did the BSOD ZIP just in case you want something from it.

 

[axe0]

The crash would be from the performance.
I can search until I am sick of it, but I doubt I would find something useful.

 

[Rednick]

Okay what should the next step be?

 

[axe0]

Just keep driver verifier running for a max of 48 hours, or when you have a bluescreen, whatever comes first.

Please keep the performance issue in your mind.

 

[Rednick]

so no BSOD over 48 hours although I did have another graphics crash.

 

[axe0]

And this graphics crash succesfully recovered?
Any moment noticed when it happens?

 

[Rednick]

No the graphics crash and pc locks up have to force reboot machine and tell windows start normally. With verifier running for at least 12 hours if I get on the PC (say after running through he night) PC freezes then graphics crash and will not recover by itself no matter how much time goes by(gave it a work day so 9 hours).