BSOD Bug check error?

BriT

BriT

BriT

Soldato
Joined
27 Jun 2005
Posts
5,192
Location
Reading
Hi guys.

I've had this error three times since March 2014, specifically 27/03/14, 06/06/14 and recently today.

Here's the BSOD text :

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xfffffa8007620028, 0x00000000be000000, 0x000000000100110a). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 062314-7051-01.

Any ideas?
 
its an "uncorrectable" error which means a hardware error has occurred.

sadly it does tend to mean there is a hardware problem but not always. the ATI 14.4vdriver is know to cause this randomly for example

have you updated hardware or drivers recently? network card driver cards can cause this so try new drivers for them.
 
Last edited:
124 error is not enough cpu voltage firstly,if that don't cure it touch more memory controller voltage
 
Thanks for your reply's always welcome :)

Could it be the RAM? I've had my overclock since i bought my Haswell chip when it came out but i will bump the voltage up a bit like you said. Also will update my graphics card drivers. How much voltage should i increase?
 
Last edited:
try cpu v first,one two clicks more

then if still crashing try vtt I think it is on haswell not sure,again one two clciks more
 
OK increased the core voltage from 1.2 to 1.21 see if that helps. Although since the BSOD's were so far apart i probably know if its stable for awhile or until it bsods again.
 
OK happened twice this week now getting annoying!, Ive incremented the cpu v to 1.25. could it be the graphics card not being stable also? Memory isn't overclocked. Could be bad memory?
 
Last edited:
Has the motherboard got profiles?

Try saving current set up, then revert to stock.

Painful I know but see if the error occurs at stock just to rule CPU O/C in/out. You can always then load the profile again later.
 
Thanks, will try but its so random. Even when the CPU isn't doing much. Ordered a USB stick so i can run memtest.
 
IIRC 124 is one of those annoying ones that is usually due to not enough vcore but can sometimes be caused by the delta between IMC, VTT (sometimes known as SA or VCSSA, etc.) and the vcore being "out of whack".

Unfortunately this can also happen in even rarer circumstances if the ratios between them are too close but mostly (in the odd time it is the problem) due to the gaps between them being too big.

I don't know how true it is with today's CPUs but generally the guideline is that the vcore shouldn't be more than 0.3v (300mV) offset from the VTT/IMC and that neither of those 2 if you have independent control of them should be more than 0.1v apart or something like that.

If your using say 1.2vcore and your CPU is "somewhere" around 1.2v and using default VTT of 0.95xxx or whatever it is then there is the possibility there of exceeding that 0.3v number sometimes when either the CPU voltage goes high and/or VTT drooping - it could be enough for stability just to increase VTT LLC 1 notch (but be careful playing with LLC especially for VTT/IMC as you can easily prematurely degrade the CPU if you go too far with that).

EDIT: Still not 100% on that 0.3v number but it originally came from someone who works at Intel so I'm assuming its not complete BS.
 
Last edited:
Whats your cpu input voltage? On haswell this should be set at least 0.5v higher than vcore. Ie for mine, 1.3 vcore = 1.8 on input voltage. Input voltage on gigabyte boards is known as VRIN.
 
well hasn't happened again after 2 hours of far cry 3 and 1 hour of MW3 so just gonna leave it. Found this program called reg cure pro but not paying £18 for it. Are there any free software like it? Thanks setter have changed the VRIN.
 
are all the sata ports intel on that board? idk without googling,if you have any asmedia or marvell sata ports try it on those

EDIT: that ssd uses a marvell controller so should be ok, but f4 is related to hdd/ssd
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom