Can't determine what caused computer to fail - HotUKDeals
We use cookie files to improve site functionality and personalisation. By continuing to use HUKD, you accept our cookie and privacy policy.
Get the HUKD app free at Google Play

Can't determine what caused computer to fail

Taz1529 Avatar
1y, 10m agoPosted 1 year, 10 months ago
I had 2 x 8gb XMS3 DDR3 sticks in my computer, sold one and had the other. I then went to 4 x crucial tactical, which I sold recently. I put back in the XMS3 stick and then I started getting blue screens. Firstly stuff relating to microsoft drivers (ntskrnl), then "memory_management".

I stuck in a 2 gb DDR3 stick with hardly any use, and then installed windows 10, which it worked fine for (would have given errors with the 8gb stick in). I've now put the 8gb back in and haven't had a bluescreen, albeit, for a few minutes as I am typing this.

I ran memtest on the 8gb stick and it froze after 26 minutes, but up to that point, no errors.

Has anyone any idea what might be the problem? I thought it was the ram but seemingly not, I thought it was storage but all worked fine plugged in as external drives and now all plugged in and no problems with them... The computer isn't old, built this time last year. The ram is the oldest component (march 2013), but like I said, hasn't been used that much.
Taz1529 Avatar
1y, 10m agoPosted 1 year, 10 months ago

All Responses

(6) Jump to unreadPost an answer
Voltage of the sticks that aren't playing nice could need looking at in the bios.

I had two sticks that worked wonderful for over a year, then created havoc with crashing. Voltage was set to auto in the bios, I manually put in my values and have been fine ever since.
Could be your psu has issues. how hot is your vrms and northbridge underload ?
Were your 8gb sticks dual channel ? and if so is every component ok with a single stick ? Also had an OS give me similar messages when firstly the RAM wasnt seated properly and tgen seated too well ( MB shorted on backplate ) Hope you get it sorted.
You've probably knackered your memory sockets by arsing around so much.
A number of things can cause BSOD in regards to memory. It could be the voltage is wrong, but when that happens, the PC usually won't post.

Another could be memory timings, as you have been changing around a lot, you may have forgot that you adjusted the timings and that's causing the BSOD (you can easily reproduce this by messing with timings and running something intensive like a game).

The sockets could be damaged, but in this case, again, the system probably wouldn't boot up.

The RAM is broken.

To take the first 2 points out of the equation, clear the CMOS.

Edited By: rev6 on Dec 21, 2014 15:45
yeah clear cmos then id test psu

Post an Answer

You don't need an account to leave a response. Just enter your email address. We'll keep it private.

...OR log in with your social account

...OR comment using your social account

Thanks for your comment! Keep it up!
We just need to have a quick look and it will be live soon.
The community is happy to hear your opinion! Keep contributing!