BSOD - Can't trace the driver.

[Shovel]

Ello.

Win XP Home (SP1), 512 MB DDR 333, AMD Athlon XP 2100+, VIA KT400.

My Dad plays one game. Championship Manager 4. It's patched up (for that's worth that that game), but of late he's getting recurring BSODs in play.

The error is:

IRQL_NOT_LESS_OR_EQUAL

Stop: 0x0000000A (0x40000024, 0x0000002, 0x00000000, 0x806AD190)

Which, natch, is pretty useless. I googled, but to no avail. So I set the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\TrackLockedPages Registry DWORD which is supposed to spit out the problem driver name on BSODs, at the expense of system performance.

Anyway, the error popped up again today and the fucking thing didn't give me a driver name. I doubled checked that they DWORD was still set and it was, therefore I'm now totally stumped as to how to debug it any further, and the bloody Sports Interactive/CM forums require admin authorisation before you can even search their tech support forums. Which is shit, frankly.

Anyway, can anyone offer some more debugging ideas? I don't the time to spend hours and hours sorting this out.

Ta very much,

Ben

 

[jaba]

Quick search popped up this:

http://www.annoyances.org/exec/forum/winxp/t1022109789

It seems to say its a hardware conflict with two devices trying to use the same IRQ...have you installed any new hardware lately?

 

[Tom]

I get the same error when I try and get my cpu to run at the proper speed.

 

[Shovel]

Sadly, we've not installed anything new hardware wise. In fact, when this problem first cropped up it hadn't even had drivers changed (was a few weeks before I came from home Uni). So no new hardware, nor any hardware related changes at all. This problem hadn't occured with CM4 at any point before, nor has it been reported with any other program.

 

[Vae]

I've had what I think is a similar problem. The info I was reading on the net pointed towards an IRQ conflict or a memory failure. Try downloading and using memtest to test the memory.

In my case I think I've narrowed it down to being poor thermal conductivity between my heatsink and cpu which might be another explanation.

 

[MrBlack]

I might be over-generalising here, but IRQ conflicts don't really happen very often these days, unless you're using some old scary hardware (difficult when there's no such thing as ISA slots any more). ACPI and all that.

Trouble is: IRQL BSODs crop up in all sorts of places. Memtesting your box is always a good start. Leave it running overnight to be certain. Links can be found at www.bootdisk.com somewhere (also an ace, useful site for other stuff)

There's a slim chance of a heat issue. CM4 is pretty CPU intensive, I'm told. (not much of a drain on your video card, though ) Run the HW monitoring tools for your mobo in the background with logging turned on, then review them after a crash. Try a few other heavy load games/benchmarkers to see if you can get it to fall over elsewhere.

If that lot fails, I find a swift kicking helps.

 

[fatbusinessman]

If that lot fails, I find a swift kicking helps.

*delivers a swift kicking to MrBlack*