Read Exstensively AgentGod and anyone else as v3 is harder testing:
I done a lot of hair pulling out on v3 to get system stable on it ..... as you know v1 and v2 were np's. I figured it was the coding of the error results ... i thought that was the issue for the BSOD's i got after trying v3 out.
I tried the modded version you PM me and it also BSOD, but in 9 min instead of 3 secs of the Non modded v3.
So after the modded one BSOD i knew then that the binaries in v3 is a ball breaker and tougher on system stability.
So i tried to figure out what my BSOD could mean and it was the infamous 0x00000124 error, which can happen due to video drivers or sound drivers, but it can also happen with OCing an as to what .. usually voltage some way or another and as to which one or which ones it maybe is trial and error.
So i was pulling my hair out and i figured well it has to do with calculations between memory and NB or it was a PLL issue.
Here is what i did and i used v3 initial released one for all tests and used MAX memory available = around 2900-3000 in tests out of 4GB that i have thats like 74-75% of memory being tested:
Initial PLL was at 1.54v and NB was at 1.22v ..... v1 and v2 passed np's 5-10 loops many times.
Here what i tested with:
PLL was at 1.54v
NB was at 1.22v, tried to 1.26v = BSOD in 3 min
PLL was at 1.54v, tried 1.56v
NB was at 1.22v, tried to 1.26v = NO BSOD, but only got 4 x 5 tests passed
PLL was at 1.54v, tried 1.56v
NB was at 1.22v, tried to 1.28v = NO BSOD, but Again only got 4 x 5 tests passed
PLL was at 1.54v, tried 1.58
NB was at 1.22, tried to 1.26 = NO BSOD, but only got 1 x 5 tests passed
So i was stuck and thinking what the heck is wrong here....
Now i happen to read JohnZS post about he had to up his Vdimm for v3 to pass successfully.
I got to thinking about this a lot .. like 10 mins or so and i remembered something about my modules and how others stated about these modules using to high of a voltage on OC or even the stock voltage for around 1000mhz can cause some stability issues in programs.
Well sure enough i am @ 901 mhz and the ram is 1000mhz memory and at that speed (1000mhz) the vdimm according to G.skill is 2.0-2.1v max.
Well i was using 2.0 volts in the bios (actual = 2.04v) as i figured 901mhz is close to 1000mhz and all my voltages prior to changing them 1-2 hours ago .. were/are memtest86+ stable, Orthos Blend Stable 11hrs 5min (i stopped program as it is good enough usually for me) and stable in Linpack versions 1 and 2.
Well i was like WTF maybe i damaged something:
Well low and behold i was remembering about to high volts can cause issues just as much as to low of vdimm volts can.
So i lowered the Vdimm to 1.96v in Bios and kept the NB at 1.26v and the PLL at 1.56v as those settings stopped the BSOD issue as using 1.28 NB never did anything better.
Well i loaded v3 up ... the inital release one and set it MAX and turned error detection on..... set passes to 5 loops.
I waited the 15 min and i was crossing my fingers cause if it failed again i was going to smoke all my cigarettes before payday...
And guess what ,,,,,, she passed all 5 passes and here is the pic to show it:
This program is a system ball breaker for sure.... Now i guess 1.26 NB and 1.56 PLL is safe guys?
I will test longer as i like 5-10 loops for best results and i will test a few times, tommorow and next day after as you never ... the bugger may go unstable ...
I have updated my Signature to reflect new Template with New Settings.
![]()





Reply With Quote

Bookmarks