[Man O' War]

Hi, for the past couple of days I have been getting BSOD's while using my computer for general use.

I have tried a different HDD, re-installing the OS and re-setting my BIOS. But this has not helped.

As I do not have a spare CPU/GPU/MoBo/RAM I have run stress tests with all but seemingly the CPU passing. Because when I run Prime95 1 of the cores does not complete a test before I get a BSOD. And all the other cores have done 8-10.

Here are the BSOD's I get:





So yeah, I am not exactly sure what is wrong any help will be very much appreciated!

Thanks.

Also I cannot remember if my specs are properly in my sig so here they are:

CPU: AMD 1055T stock

GPU: MSI 6950 stock

MB: Gigabyte GA-990FXA-UD7 (rev. 1.0)

RAM: Patriot ViperX 6GB 1600MH/z

SSD: Crucial M4 128GB

HDD: 5 times 2TB Seagate

PSU: Akasa 1000W

 

[MrPerforations]

hello,
iam not a tech wiz,but i had epic bsod episode and it was ram related.i would run memtest off a usb stick on each strip. i eventully found that the ram was fine,but was unable to run in dual channel,odd as it worked like it before.
give it a try.

could be memory controller on chip has fault,ram is fault or memory slots have a fault.

is it bsoding at stock clocks?

 

[1337LutZ]

Quote:

Originally Posted by MrPerforations

hello,
iam not a tech wiz,but i had epic bsod episode and it was ram related.i would run memtest off a usb stick on each strip. i eventully found that the ram was fine,but was unable to run in dual channel,odd as it worked like it before.
give it a try.
could be memory controller on chip has fault,ram is fault or memory slots have a fault.
is it bsoding at stock clocks?

yea, i would suggest the ram at first. Try running memtest and try running on only 1 stick, and swapping the sticks in the slots on the mobo. if that works and solves the BSOD u know its the RAM.

 

[Man O' War]

Turns out slot 2 did have a problem, but that has not solved the BSODs.

 

[sumitlian]

Ntfs.sys error written in BSOD may be a result of bad File System. You must check your all partitions with chkdsk command in command prompt.
Tell us, What overclocking settings are you using ?
If you are using SSD as OS drive, this might be a cause of unexpected BSOD, if you haven't updated to latest BIOS. 990FXA UD5 and UD7 had problems running SSD stable with some older BIOS.

 

[haazenpfeffer]

I was having issues like this not too long ago.
Turned out that the problem was caused by the mobo/processor getting too hot.
I originally configured my BIOS settings in December, when it was about 10C cooler in my room; turned out that is what was causing the problem!
Lowered the clocks slightly and now I get no more BSODs.

 

[rdr09]

have you updated your m4's firmware?

edit: as well as your mobo;s bios version?

 

[PunkX 1]

I suspect its a memory issue.

For reference, here's a list of BSOD codes:

0x101 = increase vcore
0x124 = increase/decrease vcore or QPI/VTT
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1E = increase vcore
0x3B = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary
0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)
0x1a = Memory Management