IRQL_NOT_LESS_OR_EQUAL BSOD has been Vcore related for me with the D0. With a C0 it was VTT/DRAM voltage related or plain DRAM related (e.g., faulty ICs). Try bumping up your Vcore. I am testing 4GHz Uncore atm using DRAM at 1600MHz. I will let you know what happens. I agree though that the i7 920 D0 does seem to have weaker IMC than the Xeon parts. Try what I suggested and let me know what happens...
I'm currently at +200mV VTT and 1.6V DRAM for 4GHz Uncore. Everything else is on Auto except for Vcore which is at 1.26250V Without Vdroop and I also dropped the IOH PLL and CPU PLL voltages to 1.50000V. BCLK at 201MHz (200.5MHz effective), 21x multiplier (20x + turbo), 2:8 DRAM multiplier, 7-7-7-16-59-1T basic timings, using DRAM Ratio for MCH Strap.
Edit: Got the same IRQL_NOT_LESS_OR_EQUAL BSOD around 25th iteration, bumped the Vcore to 1.27500V and passed 50 runs of LinX. Now running x64 LinX test as well with all memory selected but I'm quite certain I will be problem free.
Edit 2: x64 Linx running just fine with all memory. Noticed a funny thing though in CPU-Z and E-LEET. My DRAM is being reported as 8GB even though I have 6GB installed in triple channel configuratin. I wonder if it is because I have a Dominator 2000MHz SPD flashed to the on-board chip?
Edit 3: Everest screen at new stable DRAM config using 4GHz Uncore...next is finding a stable Uncore combination to go with my 4.4GHz 24/7 OC. Not gonna be too much higher than current Uncore (gonna go for 20x210MHz or 4200MHz Uncore). I wonder how some of the people posting Everest screenshots are getting latencies in the 35ns range though? My timings are already pretty good I think. Are these suicide runs on DRAM with latencies below those that are stable?
I butchered the tags by inserting * in order to prevent the tag from rendering. Just a sample of how you would code up a link tag so that you can have a title as the link instead of a full URL followed by a descriptive name. Makes sense?





Reply With Quote

Bookmarks