Jump to content

So I RMAd a kingston HyperX 8GB DDR3 memory module HX 318C10F/8 thinking it was faulty because the last one gave me BSODs too. I plug this one in, and I'm still getting a BSOD.

 

System Specs:

DH55TC Intel mobo

GTX750Ti card

i3 540 CPU

Seagate 1TB hard drive.

 

BSOD error code:

 

STOP: 0x0000007E (0xFFFFFFFFC0000005,OxFFFFF9000C344BE1,0xFFFFF880027C3808,0xFFFFF990027C3060 )

I tried looking up the minidump folder but it doesn't exist in the %systemroot%.

 

I incidentally have an old 2GB DDR3 RAM lying around, which I'm using as I type this. This has been posted from the same PC using this old RAM stick.

 

Are there any settings in the BIOS or anywhere else that I've missed? Please help, because I've not the foggiest idea why this isn't working.

 

EDIT:

 

OS is Win x64 Ultimate

Link to comment
https://linustechtips.com/topic/468727-kingston-ram-causing-bsod/
Share on other sites

Link to post
Share on other sites

All right. I just want to make sure I've covered any mistakes I may have made before taking that road

Yeah. Pretty sure the RAM is defective. I've never has that problem, but my friend did with some Patriot RAM. He just had to wait the RMA time.

GAMING PC "Ol' Bessie":

Ryzen 7 7800X3D | Radeon RX 9070 XT | Gigabyte B650M AORUS Elite AX | G.Skill Flare X5 6000MT/s CL36 16GBx2 | 5TB of SSD POWER | EVGA SuperNOVA 850W GT | Noctua NH-U14S | Fractal Design Pop! Mini AirCachyOS

 

Kind Of A Home Lab "Bay":

Ryzen 9 5900XT | Intel ARC A310 | ASUS PRIME B550-PLUS | T-FORCE 3200MT/s 16GBx2 + Corsair 3200MT/s 32GBx2 = 96GB!!! WOW!! | 2TB boot SSD + 8TBx6 HDD RaidZ2 | EVGA SuperNOVA 650W G2 | Phanteks Enthoo Pro M | Ubuntu 24.04 LTS

 

The Laptop:

Framework Laptop 13 | Intel i5-1340p | G.Skill Ripjaws 3200MT/s 16GBx2 | Solidigm P44 Pro 2TB | CachyOS

Link to post
Share on other sites

Lol this'll be the second RAM module I've got. Even if the first was defective, what are the odds of receiving another defective piece after RMAing?

 

Just  in case I've made this sound confusing (I apologise profusely fo' dat), I bought this module, put it in my system, got a BSOD, sent it for a RMA, got a replacement, put it in my system, and am still getting a BSOD.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×