BSOD - 0x0000001e

Aerilith · 09 Nov 2010

richc46 said:

Dont forget to test each MB slot with a known good stick of ram.

How long would it be required to run with that set-up ? 7-8 passes just as before?

richc46 · 09 Nov 2010

Yes, use the same method. We want to be sure it is not a memory problem, before moving on. I would not do it for so many passes. You can cut the number in half.

CarlTR6 · 09 Nov 2010

Rich is spot on. If a slot is bad, it will show up quickly.

richc46 · 09 Nov 2010

Thanks for the confirm, buddy

Aerilith · 09 Nov 2010

Hi, I just finished running the sticks in individual slots.

I'm not sure if I should be doing it in any specific way, but this is how I went about it:

First, 3 passes with RAM stick #1 in slot 1
then, 3 passes with RAM stick #2 in slot 2
and then, 3 passes with RAM stick #3 in slot 3.

All of them checked out fine, so I suppose that clears both RAM issues and slots being damaged - or would it be better to test all slots with the same stick?

CarlTR6 · 09 Nov 2010

It is best to use the same stick in each slot. However nothing showed up; so that means that your RAM and slots are likely OK. Memtest is not 100%. There is a chance that it did not pick up a problem.

I suggest that you now test your CPU and RAM with Prime95. Read the instructions in this tutorial: https://www.sevenforums.com/tutorials...t-prime95.html

Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Post back with your results.

Aerilith · 10 Nov 2010

How many threads would it be recommended to run?

CarlTR6 · 10 Nov 2010

I suggest you run each of the test for 12 hours. If you see errors, you can stop the test.

Aerilith · 10 Nov 2010

What I meant was; When you start up the program, before initiating the test, you have an option of how many threads to run the test with.

How many would it be suggested to run it with?
I tried running it with 8, which resulted in a crash a couple of hours in. (Although with bugcheck 0x124 instead)

I suppose this might be credited to the OC I'm currently running.

The crashes while gaming and being idle, however, are not explainable based on that though. When I ran the tests, the temps went almost 30 degrees celsius above anything I see when gaming, and almost double of the idle temps.
Idle temps are around 40, gaming anywhere from 50-55 and the tests peaked around 80.

I should probably return to default clock-speeds to see if that is the cause, but it has been running stable for a very long time before starting this BSoD'ing, so I doubt it's related.

I'll try running a test with 6 threads, this shouldn't get temps as high, and I suppose hardware-check-wise it'll be identical?

CarlTR6 · 10 Nov 2010

Definitely stop overclocking and return to default values. The error code 124 is a fatal hardware error code pointing to to your hardware. Overclocking is a delicate balance of fine tuning. Any change to your system, adding hardware, adding software, installing updates, etc. can through that balance off resulting in crashes. Think of overclocking as fine tuning an automobile or motoercycle engine for racing. In racing form many variables such as temperature, altitude, humidity, etc. affect the tuning. Thus the engine has to be tweaked for the current conditions. Whereas you don't have to worry about this kind of tuning with a stock engine.