Long time reader, first post! This place has been a great resource, and I’ve really appreciated all the time/effort you’ve all provided to keep me thoroughly educated the past few years: thank you for that!

Good advice I have been given here - mix a stiff drink before continuing, this has gotten pretty lengthy! 

Been living in love with my TR3AP four years now. Gone around the world a few times, but it’s been babied and is mostly a home network nerve center. It’s lean and mean since day 1; a minimum TSR’s loaded and plenty of HDD space for virtual mem maintained. 512mb added in the past 18mos ‘was’ the only Hware updgrade.

Over the last 6mos it’s been presenting the ambiguous IRQ_NOT_LESS_OR_EQUAL BSD followed by a system reboot. Nothing significant added/rem apart from memory almost a year before, but it was the first place I started to look. Extensive Google research taught me it’s definitely not the more specific DRIVER_IRQ_NOT_YADDA_YADDA. In cases with hand built PC’s memory ECC, or mismatched mem speed (as well as a handful of Hware specific issue are known to exhibit this issue), but nothing about this Sony configuration has been detailed. Though a few Sony cases are documented, they’ve not had to go through the extensive troubleshooting I have to return to the same place each time…

Being in high-tech and PC software development since ‘95 I’m fairly proficient with all things hardware, OS related, so want to ask if something has been overlooked here?

Error occurs under all scenarios:
- Both 512mb sticks and both mem bays have been tested seperately
- Memcheck x86 ran with no errors generated
- Replaced NTKRNL.SYS (WinDBG dump report)
- Uninstalled Norton AV (Event viewer error reported with NETEVENT.DLL)
- Fresh factory (Sony) HDD restore
- Stand alone XP Pro fresh install
[Both fresh OS test-cases were run before/after HDD/mem upgrades. Each continued to exhibit the error, either after a clean setup that ran for up to a day, or mid setup—reboot cycle that never allows setup to complete]
- Changed out the Toshiba 40gb for the newer Toshiba 60gb given it had exhibited knocking and perf issues for 12mos, so figured it possibly directly related
- Failing that, changed out the two mismatched mem sticks with new matching 512mb sticks

Over the course of the Hware upgrades I’ve stripped this to the metal—> rebuilt—> stripped—> had a stiff drink—> examined all parts for scorched PCB—> rebuilt, and received the same error after a few minutes of running fresh, third party app-less XP installs. Given the scenarios laid out here and the multitude of test-cases exhibiting the same error, I’m at a total loss to guess what else! Short of an EC error that only a few more hours with a multimeter and logging will provide…

Anyone more informed on this? Guess I’m just looking to know definatively that I haven’t been blind to the obvious, and my next post ‘‘TR3 Parts!’’ can be duly constructed. 

As you were men, and thanks.

It’s been a week and no help yet. I’m still fighting the urge to buy a new kit, part this one out, or otherwise give in to this issue with out more fight! Off to create an Ubuntu.boot.iso and give a good alternative OS a chance. Might be inspired enough to write all about it… Might just get out to buy a Vaio P instead

Bummer, dude.

I have a TR1A and TR1AP.  One has 512, the other 1GB.  I have upgraded both to a Samsung 32GB SSD and love them both.  The TR1A, though, exhibits the same behavior.  Can’t recall the exact error messages now, but basically if it is moved, jostled or twisted it bluescreens and reboots.

I have enough hardware laying around so that it is not a priority and the TR1AP is working fine.  I, too, have done the memory test, swapped out the HD, reseated the memory, etc.  Don’t feel bad, I have a new Z on the way

My next step was going to be to remove the memory, HD, entire motherboard and reassemble, thinking that there is a loose connection somewhere.  If that fails, it could possibly be a loose/broken connection on the motherboard.  Replacements can be found and this process isn’t so hard, really.  If you’ve owned a TR for long, I’m sure you’re familiar with its innards!

Good luck, and keep us posted.

Thanks trapper. I recall an old 505 developing the move and die issue, turned out the be the keyboard cross-phase and shorting. A replacement cured that trick.  This one exhibits w/out interaction. Banging on it has only been used to retain my sanity It’s been torn down to the board, spun around, inspected, and rebuilt (x2!). Reviving and running for a time with the same end result.

If it were an Electrical Circuit issue then Ubuntu should fail as well. So far a 1+weeks in and that OS runs w/out so much as a slowdown. 1gb ram and all original parts and both 8.04 & 8.10 run well enough to consider divorcing windows on this machine for good.

http://www.siliconpopculture.com/forum/viewthread/7094/#56451