bsod help

[hollo321]

hi guys, ive been battling this issue for a few months now trying to figure out with no luck. Im getting bsod's minimum 3 times a day when producing, different bsod's-system_service_exception, driver_irql_not_less_or_equal...

just did a clean reinstall of window7, tried moving scope cards around...out of ideas and dead in the water, hoping someone can help
i discovered oddly that theres a few certain adern flexor3 patches that will consistantly give me this bsod everytime i load, i took a pic of it below
i also attached pics of my irq's theres only one conflicting with scope card: intel 82801 pci bridge 244e, cant disable it since wont recognize scope cards if i do...
ne ideas?

thnks

[astroman]

imho the cards are configured perfectly with their own IRQ 17 and 18 - don't see any sharing on the screenshot...
do you happen to use Modular IV as a shell for Flexor ? it's not bulletproof yet, I've had it crashing with bsods occasionally, too.
Some Adern stuff may be a little 'demanding', too.
3 times a day for Mod IV wouldn't make me concerned about the installation at all.
If you absolutely need the offending patches, make a screenshot (if they load at all) and rebuild them from scratch.
Sometimes patch gets corrupted during use.

cheers, Tom

[hollo321]

using modular 3, these patches that i found this consistant bsod are stock factory flexor3 patches, doesnt happen with all patches, just a couple like some granular patches this is happening with. As soon as i load the patch bsod every time. This never happened before i remember loading these patches a year ago with no bsods.
bsods becoming way unbearable man, like every hour or so , just working in cubase not playing with ne scope devices i will bsod as well...

[garyb]

is Scope running as administrator?

[ChrisWerner]

Got similar screens with my cards few years back, it seems it happen over night then the screens came up.
Upgrading my PSU helped.

[astroman]

... bsods becoming way unbearable man, like every hour or so , just working in cubase not playing with ne scope devices i will bsod as well...

my comment above (about 3 failures per day) were based running a system 24/7 as mine is constantly on...
Chris' hint about the PSU is a good one. RAMs are also worth checking in that case.

cheers, Tom

[hollo321]

thnks for replys guys, running in administrator, about power supply ive gotta 650w corsair, and if not mistaken if it was the power supply causing the bsod it will just shut off not give computer to dump files e.c.t?
for sure not the ram or cpu-replaced both recently and same issue, thinking mayb mobo


ga-ex58-ud4
990x
24gb ram
win7 64 bit
1 scope pro 2nd gen
1 scope home 2nd gen
8800gt

[Music Manic]

driver_irql_not_less_or_equal = Corrupt Drivers

[hollo321]

what driver(s) should i check out?
i just reinstalled all motherboard drivers,
reinstalled graphics driver
reinstalled scope many times
running latest bios, all optimized defaults
and im almost positive now issue not with the scope cards themselves, since just reinstalled scope with just 1 of the scope cards, scope pro card-same issue, then took that scope pro card and put in another pc, which caused no bsods.

[astroman]

that a driver is reported 'corrupted' (or handled like this, or fails) can have various sources.
The most simple one the file itself is damaged, but that's rather unlikely (with multiple installs).
As the driver is loaded to memory a 'powerspike' (or other mess) from the PSU can change memory bits, which is almost certainly fatal for that kind of software (hence the hint to the PSU).
In your case that's also unlikely because the Corsair is rather new and a quality product.
As you said it's running on a different system, the source is probably the chipset communication.
It's all pretty fast stuff today with lots of cached data and instructions. A small side effect can bring this down.
There's also a chance that the memory modules aren't properly driven, and as mass products I wouldn't hold my breath on any brand.
You can't beat statistics in this domain. Failure rarely happens, but it can...
I wouldn't invest too much extra time (as you tried all the obvious already) - motherboards/memory are just too cheap today.

cheers, Tom

[ChrisWerner]

If you can, try to borrow a PSU from a friend and just try, but I have great respect on the corsair PSU, they are good and I have one too. But the symptoms your PC has, are exact the same before I changed my PSU.

Maybe you can borrow some RAM too for testing or if you have some RAM slots free buy some so the money isn't really lost.
I would go for the MOBO latest.

good luck

[garyb]

yes, the power supply is suspect as is the memory.
you can romove all but one stick and see if the trouble goes away. if not, then try just the other stick.

[Music Manic]

Physically delete the drivers just to make sure, but as the guys said, it could be memory or Power supply.

It will most probably be memory if you get the exact same address on each crash.

Try this to verify:

http://www.memtest.org/

All the guys here are great with their advice.

[hollo321]

thnks ill give em a sweep tonight, try to borow a power supply n hopefully catch the b,

[hollo321]

tried renewing drivers, left only 1 stick of ram and did the memtest all night with no errors, hooked up another power supply..guess all thats left is a sik mother to repalce
thnks for all the guidence, looking foward to being able focus on music again

[hollo321]

i decided to try one more thing before throwing in the towel, the other computer that i tried the scope card and worked perfectly was a 32 bit system. So i tried now doing a fresh reinstall of windows 7 32bit and scope in 32 bit on my comp, and no bsods. Then did another reinstall of windows back to 64 bit and bsods back again, so looks like im having this issue only in 64 bit. What does this mean?

[garyb]

what version of Scope are you using?

[hollo321]

newest ones from soniccore site, been testing with SCOPE PCI v5.1.2709 64 Bit and SCOPE PCI v5.1.2709 32 Bit

[garyb]

well, then, i don't know.

it's possible that something in those patches is not 64bit compatible, but i haven't heard any other complaints.

[dante]

Well, you have one more thing to try. 64 bit on the other system.

If it BSOD's on other system running 64 bit, then could be like garyb said about one of the Scope patches not being 64bit compatible. If it doesn't, then seems more likely something between Scope, windows 64 bit and that particular PC (maybe mobo like you said, since you seem to have eliminated RAM and PSU).