Bluescreen, XP restart problem. Driver_IRQL error. Please Help

[AntMan]

First of thanks for taking the time to view this thread.

We have 4 IBM computers in our office. Old style PIII's 667 MHz each, all with 2 sticks of 128 megs of RDRAM.

The boards they came with have built in Video (S3 Savage 4) and Audio. They also all have linksys network cards in one of the 5 pci sluts the motherboards have.


These computers seamed to work fine for the longest time. But recently with one program in partiticular they just crash and restart the computer. If I turn off the Automatic Restart feature in Windows XP. I get a blue screen memory dump error. Error is as fallows:

Driver_IRQL_NOT_LESS_OR_EQUAL
STOP 0x00000001 ( 0x00000002 --> x3)

The program that causes these computers to crash the most is called "My Track". A stock tracking/trading program that is widely used. This program works on every other computer we have tried it on, and untill recently has worked on all of the 4 IBM's we have. But now the program loads, and trys to connect to the server. The Second it does it crashes the intire computer. E-Trade spreadsheets have also tended to cause the same error every so often.

My guess is it has to do with very complex number crushing, mainly b/c that's what these programs do.


We haven't added anything new to any of the computers, and we've run all the latest Norton Antivirus scans on all the computers.

I don't know what else to try, so please if you can help with this problem in any way, It would be greatly apreciated.

Thanks Again
Antmanz

 

[AntMan]

anyone ?

 

[AntMan]

^

 

[Miramonti]

Problem is you're not using this.

(the best imo )

What operating system are you using? Microsoft recommends upgrading the service pack with Win2k in that support sheet link. This type of error is a real pain is the buttox tho.

I started getting it previously on w2k and it was because my cpu was overheating causing drivers to fail. Its got something to do with the network/tcpip usually, so make sure you've got the latest drivers of them too. Mytrack could have changed something on their servers regarding the way the info in the packets are communicated or something like that too, so I'd check and see if there is a yahoogroups forum for them to see if others are talking about it too. I'm pretty sure it doesn't have anything to do with the number crunching, except if the calculations are tying up the processor too much and causing the datafeed to go on hold and perhaps this is messing up the tcp/ip flo or something.

 

[AntMan]

Thanks jjsole for the response. I've tried a few other things with no luck.


Again we are using windows xp.. I filled out a support request with myTrack but no response yet.

 

[Steven the Leech]

Just a thought. but may be that more RAM may be needed for the program. May be worth a test on one machine to see if that fixes the problem.

 

[Miramonti]

I wonder if it will run in "safe mode with networking" without any conflicts. (I don't think I can access the internet in safemode w/ntwk tho)

If that doesn't work, maybe try to start XP with as few services as possible, especially any 3rd party proggies, and see if you can troubleshoot that way.

Depending on how much flexibility you have, and how determined you are to get this working, a reinstall of XP might be an option to. Once you get XP and the hardware installed properly your next installation could be MyTrack - then test it - then install programs incrementally, testing mytrack along the way. I'm sure this is the last think you want to do tho, but if you can't isolate the issue another way, it might be your only option. Use ghost or driveimage tho in case you want to completely revert back at some point.

Interesting tho that Etrade spreadsheets occasionally crash it. You might try sisoft sandra and run the "burn in" mode for a while and see how much stability you have without using these programs.

p.s. Steven's suggestion is a good one regarding memory too, especially running XP. Easy enough to temporarily swipe some from one of the machines.

 

[GaiDaigoji]

I was getting this error and it ended up being a bad stick of RAM.

~David

 

[AntMan]

Thanks guys for all the suggestions. I will try a few of these tomorrow when I get the chance. Again thank you!

Also it's not a bad stick of ram, since we've tried 8 diff DIMMS.

It could be that there is not enough ram, but a computer with half the CPU and only 128MB of ram runs this program just fine ;(