Sli Hack causing "Crazy" issues with win 7

[xargon15]

Ok, so here's the issue, and i REALLY need some help finding a solution or else i'm going to go mad.

First my build
gigabyte GA-890FXA-UD5 (Rev2.0 F2 bios(i didn't like F6 because they got rid of .5 multiplier increases so i stuck with this))
Phenom II 1090T AMD AM3 CPU OC in bios 4.0GHZ (200mhz, 20x multi, 1.35vcore)
16GB G.Skill Ripjaws (2x4 sets) 1333mhz memory (not OC'ed)
Corsair H70 cooling (idle 16c, load 32c) Push/Pull w/duct 3x250CFM fans
Windows 7 Pro 64Bit
2xGTS250 MSI Twin-Frozr 1GB Video Cards (using asus sli bridge)
Drivers 257.15 Installed
Sli-hack v1.0 rev33.22 installed
Rosewill BRONZE Series RBR1000-M 1000W PSU

Ok, i can't think of anything else of uber importance to include in that build but if you need other parts of mine just let me know.

Problem: I have done 2 re-installs of windows in order to try and figure this out and yet can not. I BSOD randomly while CPU Stress Testing on my Sli Hack files...

While using OCCT to stress test my CPU, i'll get anywhere from 5-15minutes into the test (OCCT-linpack or OCCT regular) and i'll BSOD from a "un-correctable hardware error" or "IRQL driver not blah blah blah". After rebooting i'll pull up both the event viewer, action center, and bluescreenviewer and they reference the following:

Event Viewer: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xfffffa8010c62028, 0x00000000b204a000, 0x0000000000000175).
Action Center: PX Engine problem of some sort (i know, this is related to roxio, however in this case it's not)
Bluescreenviewer: Ntoskrnp.exe & Halsli.dll both will show up either seperate or together when the BSOD occurs.

Now, going back to the action center note. Yes, PX Engine is a Roxio software thing, however everytime i have a BSOD on my Sli Hack files, it shows an issue cooresponding at the same time for PX Engine... I don't have roxio programs on my computer...

Now for the Sli Hack. The way i've installed it (please correct me if i'm wrong) is i've done a full re-install, installed video drivers (257.15) right off the bat, rebooted, installed sli hack, rebooted, gone into the sli hack windows, turned on sli, rebooted back into same windows setup, and then i've been running it.

My questions, Why am i having a BSOD on my sli hack while CPU Stress Testing? Why does it show PX Engine? Is this just windows not sure what to call the problem so it picks something random? Or do i have another underlying problem going on here possibly? And last but not least, How can i fix this and make it work?

I've been at this for months on my own, i'm ready for some assistance, please help if you can. Thanks!

 

[johnspack]

I don't think the slihack has anything to do with it. To make sure, just boot with the non sli enabled entry, and run the same tests. Something you should have done anyways to rule out the sli stuff. I have been using slihack for a long time, and have never had a cpu issue because of it.

 

[xargon15]

I'm currently finishing up a 2 pass run on my memory using memtest86+ to find out if it's that by chance. No errors so far, 13hrs into it. After that i was going to go to a single card setup, and try the OCCT tests again under the sli windows bootup and see if it happens again. I'll run it twice, once with each card to see if that makes a difference, and then if all is well i'll do it your way.

When i do what you suggest however, would i need to take off my sli bridge to run under normal windows setup? Or would it not make a difference?

 

[newtekie1]

It won't make a difference.

 

[xargon15]

Ok, tried original windows 7 installation without the hack turned on and OCCT still failed however i'm not showing the sli hack in BSOD viewer, in fact there wasn't a BSOD, only straight up black screen reboot 3 minutes in. So i'm going with bad OC in my case here. And will continue to tweak, and post again when i get it stable

 

[xargon15]

Ok, now i'm back to square one. I tried a couple more OCCT tests, and they will fail 2-3 minutes in, never going above 30c, and i just got an uncorrectable hardware error under hal.dll. Any ideas?

 

[JD15]

Is your Vcore still 1.35?

 

[dark2099]

every time ive run into a 124 BSOD, no matter if i am on a intel 775, 1156, or 1366, havent clocked an amd in a while, but it was always CPU volts, or other important volts that help stabilize CPU

 

[xargon15]

I haven't had a chance to put more time in it this week, but i will try a few more volts into it, probably up to 1.4 and see if that helps any tonight. i'll update afterwards.

One of my fans on one of my video cards went out however, so i'm on a single card video card setup right now until a replacement fan comes in. So i can't really test out the SLI Hack on my setup until that happens.

 

[Flibolito]

Your temps are good so definitely tweak those voltage as I agree that seems to be the problem. The might be more to it than just Vcore try giving the RAM a tiny bit more and the other settings as well, there is tons of info out there on which voltages require change to run that chip @4GHz, you can then turn down the voltages one at a time to see which one causes the BSOD and then you can retweak the other settings.

I find it best to give it some stick and then work backwards by lowering them till its unstable rather than working upwards as this saves time. Just be careful and you can always make profiles of saves setting in the bios for settings that seam to work well. If not AMDoverdrive might save time just to find stable windows settings which can then be adjusted in the bios.

 

[xargon15]

So i think i managed to get the CPU stable last night. Bumped my dram voltage up to 1.57 (recommended 1.51), cpu is now a 1.475 (i had already bumped up to 1.4 and forgot but it still wasn't stable), and my cpu pll is up to 2.63 to help to stabilize as well.

My northbridge i gave a little jump to 2400mhz, with a voltage of 1.23.

i think what my biggest problem however WERE my temps, but not on the CPU, but on the motherboard. I've got a great fan setup and case, with airflow out the roof, however i took off the heatsink on the NB/SB area and found very dry cracked thermal paste, so i reapplied it onto both of those. Temps are a little high running OCCT on a small data set run, but i have to re-do burn in on my paste, so i'm not worried about the temporary higher temps for the longer term coolness.

Before this reapply i was seeing random black screens popping up, then my desktop would return, and i would about 30 seconds later go into a random reboot without BSOD or windows pop-up showing problem. NB was showing 53c, which is why i started to worry about temps. (that was under normal data set on OCCT as well).

If all goes well after the burn in, i might try another couple of multiplier marks, maybe even downgrade my bios to F1, i've heard it's more stable than F2 on the UD5, and give a few ticks to FSB clock speed.

 

[xargon15]

Ok, it's been a while since i've been able to post on here about what's going on. But the issue still persists.

Current setup of hardware hasn't changed.
CPU setup is as follows:
4.407GHZ 20.5x215mhz 1.575vcore
twin GTS250 @ 750MHZ/1800 & 1150MHZ memory

I'm running 266.58 drivers, with sli hack v1.0 final.

Now i'm still seeing from time to time a "irql_not_less_or_equal" BSOD in regards to ntoskrnp.exe which is one of the files modded by the SLI HACK, and at the exact same time this happens a PX Engine error pops up in my windows security center.

Any ideas?

This is a fresh install of windows 7 pro 64bit, and i've only seen the bsod once so far, and i re-installed the hack, however i don't want to see it again, and i'd like to figure out what might be going on.

 

[johnspack]

Try slihack 1.2beta and 267.46 driver. Working great for me under win7 64, of course your system is different, so not sure.

 

[xargon15]

Do you have a link for the 1.2 Beta?
I've been to the sli hack homepage and i didn't see it there.
i'm willing to give it a shot to see if it's more stable, it seems like my system doesn't like the 1.0 version, 0.9, or 0.8.

 

[johnspack]

It's in anatolymik's sig if you follow the slihack thread! http://www.xdevs.com/sli/SLIPatch_v1.2_beta.exe

 

[xargon15]

Ok, i have version 1.2 installed, still running 266.58 drivers, i haven't seen any kind of issues popping up yet.

 

[xargon15]

So i just finished a run of 3D Mark Vantage on my computer. I'm running end game specs of:

4.305GHZ 1090T
210x20.5 FSB
V.Core 1.575
HT - 2100mhz
NB - 2310mhz
Memory clocks loosened from 9-9-9-24 to 10-10-10-26
My video cards are sitting at 755/1812/1135 (GTS250)
I'm running 266.58 drivers
sli hack 1.2 beta

And my results (with Physx running on GPU) are:
GPU:12603
CPU:44495
Total: 15335

It looks like everything is doing a-ok now. thanks for the help everyone.

 

[bokou]

mind if I ask.. what's the slihack and what does it do?

 

[xargon15]

The Sli-Hack is a small bit of software that is used to make it so any (still being tested on many) AMD style boards that are usually incapable of supporting a SLI configuration and only Crossfire-X can support SLI based graphics cards in SLI setup, 2/3/4 the SLI hack helps make this possible.

http://www.techpowerup.com/forums/showthread.php?t=60844&highlight=sli

The above link is the on going support for SLI Hack as a whole and what they've come up with up to date. Check it out.

 

[bokou]

oh that's wicked... always hated the idea that if you had an AMD board and wanted to run two nvidia cards you'd be stuck having to buy a new board that was "sli ready!!"