I cant figure it out?!?!?

So I've recently built for a friend and there's something weird going on. This is the build:
CPU - AMD fx 6300
MOBO - AsRock 970 Pro 3 r2.0
GPU - AMD R9 270
RAM - 8 Gb Patriot signature 1600 mHz clocked at 1333 mHz (ill discuss this later)
SSD - Samsung 850 evo 120 Gb
The others don't really matter just a case and storage HDD.
The weird thing is that it would get random BSOD errors.

So there are a few different errors that come up but these seem to be the main. Also IRQL NOTLESS_OR_EQUAL comes up a lot.
From what i've read so far there's something wrong with the memory or the drivers. In the motherboard manual is says is cannot support 1600 mHz without an OC so i've changed the clock speed to 1333 and after that it became slightly more stable.
I have also reinstalled windows 8.1 and wiped the ssd. I don't really have any other ideas. Perhaps I might have done something wrong with the parts that I chose.
I haven't updated drivers I usually just install from disc (yeah what a pleb i know) I'm not sure how much its gonna help but I expect it to be the first thing you suggest. If I do take into account the out of date drivers from the disc what and how should I go about installing the freshest?
I went for an AMD build because it was the best price to performance I could get from the retail. Any thoughts and suggestions is appreciated.
I'll try to keep this thread updated until I find a solution.

has this got anything to do with it?
its a very small list of supported memory but I honestly don't see how it can be the problem. Usually any ram will work as long as its the right speed. Does this cause problems if its not on the list.

You could try System Rescue. Among other tools, it has a memory tester.

Link: http://www.sysresccd.org/SystemRescueCd_Homepage

What BIOS version are you using?

  • run a linux distro off usb - if system is stable for a good while in that environment start looking at the windows install
  • drivers (obviously..)
  • memtest86
  • update motherboard bios incase there are some shitty bugs present
  • update windows completely

This happened

few options:
- gpu drivers are up to shit and need updating/reinstallation - do the advanced clean install as a habit
- gpu is overclocked to hard and is unstable - if oc'd then revert to stock.
- gpu could be faulty - test system with another gpu.

It's definitely not overclocked I don't bother doing that for friends builds who don't know too much about computers.
I've reinstalled all the latest drivers and I'm currently waiting on results from him. Also I really hope it's nothing faulty that's just going to be a massive pain to get replaced.

run linux distro (ill try that one later)
drivers (done still blue screens)
memtest (gonna take it to his place tomorrow and find out)
update motherboard bios (need to learn to do that uhh... any useful links would be appreciated)
update windows completely (im pretty sure he said its done)

motherboard bios update >> http://www.asrock.com/mb/AMD/970%20Pro3/?cat=Download&os=BIOS
just follow the instructions & you cant go wrong.
Any chance you can test the system with another gpu? The 270 should still be under warranty if it comes down to it.

I researched the bios update earlier it seems easy just hope the power doesnt go out xD
im going to his tomorrow i have a usb with memtest
a usb with bios files
and im going to bring my computer so i can swap the gpu and ram if i need to
thanks for the help btw

We just did windows updates (all of them)
We also did a quick stress test with prime 95 and the cpu is stable at around 45 C. I think that seems fair for an amd 6300
and if it helps then main games we're trying to play are dota2 and batman (cant remember which one)
Ill update progress later and let everyone know how we fixed it for future reference.

Probably RAM, what does event viewer say? Event viewer kicks ass for troubleshooting, Wendell did a video on it. Some AMD cpu's have trouble supporting higher RAM clocks, you should try one stick at a time when testing. Not sure if raising voltage for dimms would help, does AMD have the option to raise vccsa or whatever their equivelent is?

I think a few other BSOD codes are 0x00...50 which most likely is RAM, and 0x0...124 Or a number close to that which would be CPU. If RAM is not stable it will throw out a few different errors. Weird stuff happens when memory doesn't work properly.

So I lived with a machine that had this issue (not your startup issue). My screen would work real hard and artifact like crazy and then it would recover with this exact message. Short of the Long of it, it was my video card. Every time I rebooted I would have to run a program called AMDTools? and intentionally crash my drivers before it would work. It didn't matter if I had new or old drivers, my video card was simply bad. Years down the road I upgraded my card and poof issue was gone. What I should of done was purchased another gpu and installed it and confirmed the issue and then sent it back still under warranty proving it was the card, because AMD blamed the motherboard and the motherboard blamed AMD.

All that said, you appear to be having a slightly different issue due to your boot up issues so my issue may not apply to you. Regardless, figure it all out while it is under warranty.

I would run Memtest overnight see if you get any errors. If you do take one stick out run it again. If it has errors put the other stick in run it again. If no errors you have found your problem. If you run memtest and get no errors overnight You have other problems.

You could follow these steps also

Now unplug everything from the board take out all expansion cards etc.

Uninstall the Processor.
Inspect the processor make sure pins are not bent. Clean off old thermal compund.
Reinstall the processor making sure the arrows are lined up
Reinstall the cooler plug in fan into the CPU 4pin fan plug.

Clear Cmos

Plug in all the power connectors. The ATX 24 pin the 6 pin ATX12v. Make sure the snap correctly. DO this before install memory.

Install your F_Panel connector for power button.

Do not plug in Front panel USB yet.

Install 1 stick of memory.

install the GPU into the expansion slot.

Connect 1 Harddrive.

Plug in HDMI cable into the HDMI on the 750TI

Plug in the Power cable.

Now turn on the Computer. Wait up to 5 min to see if it boots. If it boots congratulations. Turn off Computer and install the rest of your hardware one at a time. Each time you install something boot the computer up. If it was some hardware causing the issue you will find it.

If it does not boot up take out the memory stick and use the other stick you did not install. If it does not boot try putting each stick in the second Slot.

If it still does not boot you have a DOA product. Could be video/memory/motherboard/processor/psu.

This will eliminate some hardware culprits.

The idea of running USB linux for awhile is also A great idea. This will be easier then going thru my steps. If you run linux and still getting errors then Follow my steps.

The latest was installed from the box 1.8

Well ok guys im running memtest86 at the moment im going to wait untill it passes 2 or 3 times... perhaps someone with more experience can let me know whats best. I wanna try to get the computer back to him today.
After memtest im going to swap the graphics cards with my own personal 560 see if that helps

So far it seems to be either graphics or memory issue. If its none of these then ill rebuild the computer and try and linux distro (ill need to get help with making bootable usb so any links would be helpful).
Running linux is really the point of this computer its for a friend and they paid for 8.1 so we really wanna be using that

The latest is 2.0 - 1.8 is from 2013.

Enable crashdumps (dumping the memory to disk in case of a BSOD) and then see if you can get something out of the dumps. It's been a while since I last used them so I can only refer you to google (but give you some google-fu on the way out).

Something like this may help you: Click me for I am a link!

It takes a while for the geek to recognize that there are some logging tools that can provide valuable information. Maybe the tool will even just simply tell you what is wrong.

1 Like

Along with reading minidump files, check out Wendell's video about the Windows Event Log. It should help you sniff out most issues.

1 Like