smithers

jmitchel, I agree with the comment about diagnostic software not really being able to simulate what windows does to hardware. The IBM diagnostics software did have a burn-in option which basically works the computer for a specified interval, it runs the memory, HD, cpu, ram, cdrom and floppy under an intense load ... it didnt' freeze or crash. Yesterday I downloaded a SUSE Linux Live CD and ran that for 10 - 15 mins and it didn't freeze or crash on me ... I am willing to bet that it's something windows-related, now what that is I don't know... Sampson, yes all the computer is up to date with the latest bios and firmware fixes. I will keep plugging away and hopefully figure something out, please keep the suggestions coming!

Hi, I come seeking expert advice, I have taxed my computer knowledgibility in solving this problem. I have an IBM T41 (2373-7FU)Laptop. So far I've tried installing Windows 2000, Windows XP and Windows 2003 on this computer and no matter which of the 3 operating systems I install I always encounter bluescreens indicating a 0x0000000A IRQL_NOT_LESS_OR_EQUAL to error. My first thought was that it was a hardware problem (probably RAM), I ran 3 sets of diagnostics software: memtest86, fore-front group's the troubleshooter and the IBM PC Doctor Diagnostics ... the hardware passed with each set of diagnostics. My next guess was that it must be a software-related issue. I've searched around google&microsoft but cannot find a solution to this problem. The stop error mentions no conflicting device driver or file causing the errors. The bluescreens seem to happen randomely (ie: when I open messenger, surfing the web or just running a virus scan when I go to bed) I've read that it might be driver related so I tried both the IBM device drivers from the IBM website and the Microsoft Windows Update drivers, this was done on fresh reinstallations of Windows for each set of drivers ... the results is the same IRQL error above. I thought that it might be a heat-related issue so I throttled the CPU speeds in the power management section of the BIOS to their lowest settings ... that didn't help either. The Event Log doesn't list anything in red that could give me a clue. I really don't know what else to try ...