Member Avatar for PCooper

Hi,
I have a Tecra 8100 laptop. It just started having the blue screen of death upon startup. I get the Welcome to Windows XP screen (before the XP login screen) and then it goes black and I next get the BSOD with IRQL_LESS_THAN_OR_EQUAL error. I can boot and run fine in safe mode and run almost everything (except I have no sound:) the PCMCIA wireless works: I'm on the internet (I'm using the machine now.) I can use it for hours (with a greatly reduced screen size, but otherwise, no problems.)

I'm wondering if it is bad RAM or a bad sound card. Or maybe a bad driver? The last thing that I did before the problem started was that I accepted and installed some Windows Update (I also tried rolling this back but it didn't fix the problem, obviously.) I also downloaded a debug tool from microsoft but it won't run in safe mode.
Any way to figure this out without buying new RAM or a new sound card and trying them? I don't really want to spend money on a 6 year-old machine. (Though it has been wonderful!)

I replaced the processor last summer (upgrading 500 MHz to 700 MHz) and ever since I have had trouble with the modem. (It doesn't work.) But I remember it was a cheesy little card with a flimsy connection and I'm guessing it's easy to knock it loose and I wonder if the sound card is similar?

Any advice appreciated!

  • 2 Contributors
  • 1 Reply
  • 126 Views
  • 6 Hours Discussion Span
  • Latest Post Latest Post by jbennet

Dani AI

Generated

A focused, low-cost way to narrow this down without buying parts: capture what actually fails, then run two targeted hardware checks and a driver isolation pass. The stop message you quoted maps to the Windows kernel bug check for IRQL errors — a memory access at too-high IRQL — which is most often caused by a buggy kernel-mode driver or bad memory, not by an application. See Microsofts explanation for the 0x0A IRQL bug check for background and what the dump will show: .

First, get reliable evidence. Turn off automatic restart so Windows leaves a minidump, reproduce the crash, then copy the minidump from C:\Windows\Minidump. Analyze it on another machine (or with a tool) — simple GUI parsers like WhoCrashed can point to a driver, or use Microsofts debugging tools for a precise stack trace: WhoCrashed and Debugging Tools / WinDbg.

Second, test RAM before guessing replacement parts. Boot a USB/CD memtest and run several full passes; any errors point to RAM or a bad slot. Memtest86 is the standard: Memtest86. If you have more than one module, test one at a time and try different slots.

Third, isolate drivers. In Safe Mode disable non-Microsoft services/startup (msconfig) and use Device Manager to disable the onboard audio and any recently updated drivers or PCMCIA/modem devices. If a driver is implicated by the dump, run Driver Verifier to force a repeat crash for identification (but be careful — it will cause crashes and must be disabled from Safe Mode): Driver Verifier.

Backup important data before experimenting. If diagnosis points to a driver, update/roll back that driver or remove the offending device; only consider a reinstall or hardware replacement after these diagnostic steps.

Member Avatar for jbennet

if it runs in safe mode then i would say a bad driver - also you nearly always need to do a full reinstall of windows after a cpu or motherboard upgrade

and id like to add that you cant get new soundcards for laptops

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.