BSOD

Boozebeard · 21 Jul 2010 at 02:21

Is there actually anyway to tell what caused a BSOD? Here's the information windows gave me

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 2057

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA800486D028
BCP3: 00000000B6000400
BCP4: 0000000005200810
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

needforspeed · 21 Jul 2010 at 02:25

You get a minidump from a folder? Then you need a program to read it?

Boozebeard · 21 Jul 2010 at 03:16

What program would that be?

needforspeed · 21 Jul 2010 at 05:01

Go here for information: Clicky The Dump Check Utility is here: Clicky I don't know if it is the way to go. I'm a newbie.

J.B · 21 Jul 2010 at 10:38

Normally the best information is on the BSOD itself near the bottom, check the event log to see if anything interesting in there.

It was most likely a driver playing silly buggers though.

Boozebeard · 21 Jul 2010 at 14:12

J.B said:
It was most likely a driver playing silly buggers though.

You think so? Problem is that it seems to do it every 3 days or so, no matter what I'm doing, could be playing a game or just sitting at the desktop. I'm gonna leave everything at stock for a week or so to see if it was my oc.

Ph4lanx · 21 Jul 2010 at 14:29

Next time the BSOD occurs, read about 2 thirds of the way down, there should be a line with either a memory string (usually starts 0x0) or a filename, or sometimes some wording with underscores in it in capitals.

Boozebeard · 21 Jul 2010 at 14:31

Ok I will try and note that down if it happens again.

J.B · 21 Jul 2010 at 15:33

Boozebeard said:
You think so? Problem is that it seems to do it every 3 days or so, no matter what I'm doing, could be playing a game or just sitting at the desktop. I'm gonna leave everything at stock for a week or so to see if it was my oc.

Well that was an assumption it was a one off. if it happens regularly then further investigation is required.

Boozebeard · 21 Jul 2010 at 20:05

Ok, well like I said. The wierd thing is it doesn't always happen when it's underload. Sometimes I'll just be at the desktop or web browsing. Would this mean is less likely to me my OC? The problem with figuring out what it is, is that it only does it once every 3-7 days.

Boozebeard · 21 Jul 2010 at 22:12

It just did it again, with my cpu back at stock. My friend was on it so I didn't get a chance to look at the information but it seemed to go fairly quickly on it's own anyway. I'm starting to think it's the ssd. It does seem to like crashing on dawn of war 2 particuly though which isn't on the ssd.

Boozebeard · 22 Jul 2010 at 15:54

Ok, I just ran memtest and one of the sticks is faulty.

I just finished rmaing my other kit, don't understand how I missed that this one was faulty as well, memtested every stick. I'm wondering if my mobo is over volting one of the dram slots and damaging the stick, can this happen?

welshdragon · 22 Jul 2010 at 15:59

Be careful, memtest showed my ram as being faulty but when i tried it in a different system it was fine. The actual cause was the mobo. Make sure you have the latest bios and maybe try the ram in a different rig if you have access to one?

Boozebeard · 22 Jul 2010 at 16:06

Ok, I will try it in a different rig. The other stick isn't erroring at all though, no matter what slot I put it in.

Edit: Still errors in a different rig. Looks like I'm paying another £10 for admin fees + postage D:

welshdragon · 22 Jul 2010 at 16:36

At least you can say its faulty and definately not a more serious problem. Have you been having bsod's witht he pc with just the remaining sticks in?

Why you gotta pay admin fee's? And in fairness to ocuk I will get my postage back from returns of faulty stuff.

Was it bought from a competitor?

Boozebeard · 22 Jul 2010 at 16:39

I'm not the original owner of it so I have to send it to transcend directly (in the netherlands) and they charge a £10 fee if the product wasn't bought from them directly

I don't know if it's going to blue screen with just the one stick in as I've only just taken the faulty one out and sometimes it won't blue screen for days.

Boozebeard · 23 Jul 2010 at 12:18

I'd just like to make it known that the very helpful guy at transcend who dealt with my last RMA says he wont charge me for this one as it was so soon after the first. He really has been very helpful, I would recommend.

Boozebeard · 28 Jul 2010 at 19:31

Waaa, I just blue screened a couple of hours into playing Bad Company. Ran memtest and my remaining sticks are fine, I'm running intel burn test and I'm 112 runs clear so far.

There was a memory string in the error (didn't get a chance to note it down) does that provide any insight into what's causing it?

Edit: Completed 200 runs of intel burn test, this is driving me nuts

honosuseri · 29 Jul 2010 at 04:21

Check the memory timings in the bios my friend. Could be the cause of the memory errors. Worth a shot!

Boozebeard · 29 Jul 2010 at 13:59

Well I know the timings are correct and as I said I have done memtest checks. If it happens again then I will try slackening the timings.