Windows XP STOP: Errors

GiganticDays · January 17th, 2003, 06:53 AM

Gigabyte GA-7VKMLS mobo
Athlon XP1800 CPU
256Mb PC133 RAM
40GB Maxtor 5400rpm HDD or 40Gb 7200rpm IBM HDD
52x CD ROM

Built the above for a friend before Christmas but recently he's been getting spontaneous reboots. Got steadily worse over the past weeks until he couldn't boot up without it rebooting as soon as Windows began to load.
I have it at home at the moment and have done the following:-

Tested RAM with Memtest86 for 4 hours - no errors
Removed Modem
Swapped Hard drive (hence the two types mentioned in the spec)
Completely clean-installed WIndows XP Pro
Disabled both COM ports, onboard sound and LAN

None of the above seemed to work.

I've disabled automatic reboot on errors and got the following error codes:-

MEMORY_MANAGEMENT
STOP: 0x0000001A (0x00000781, oxC03102EC, ox80832358, 0x80832368)

After removing the modem I got the following error:-

IRQ_NOT_LESS_OR_EQUAL
STOP: 0x0000000A (parameters - can't remember exactly what)

I have just tried running the PC at 100MHz clock speed and cannot seem to generate the error again, however I noticed that after I reinstalled Windows the PC started up ok, but if it was switched off for a while (say 10 minutes) it would get the error again. So I'm not yet sure if running at 100MHz solves the problem (of course it's no solution at al really).

muno · January 17th, 2003, 06:57 AM

If it has ran overheated for weeks the anything could be damaged.

IRQ_... errors are usually due to invalid drivers.

If the system overheats, the hdd could get corrupted - possibly causing even valid drivers to fail.
-M

GiganticDays · January 17th, 2003, 07:01 AM

Don't think it's a heat problem; the CPU temp is being reported at around 46 deg C which is fine, and it has an AMD-approved heatsink/fan. Actually what seems to happen is that it boots up OK if it has been running for a while - it's only when booting from cold, having been switched off for a while, that it displays the error.

GiganticDays · January 17th, 2003, 07:27 AM

OK so running at 100MHz doesn't solve the problem. I let the PC stand, switched off, for 30mins then rebooted and got the following BSOD:-

The problem seems to be caused by the following file: Ntfs.sys
An attempt was made to write to read-only memory.
Blah blah blah
STOP: 0x000000BE (0xC71E6808, 0x02261121, 0xFA2FB858, 0x0000000B)
Ntfs.sys - Address F9D8751A base at F9D61000, Datestamp 3c587aa0

This is the 3rd different BSOD I've had so I think there's something more fundamental than a device driver problem or a corrupt system file.

GiganticDays · January 17th, 2003, 07:51 AM

Sorry people, misled you slightly here, I've tried so many configurations that I missed the fact that I'd changed the jumper back to 133MHz when I got the last error. It seems that running at 100MHz is OK - a clue?

Detritus · January 17th, 2003, 07:55 AM

I noticed you didn't try swapping the powersupply, possibility?

GiganticDays · January 17th, 2003, 08:10 AM

Detritus
I haven't swapped the PSU yet, but I've been using these PSUs now for around 4 months - they're Codegen 300W units and I've built much more power-hungry systems around them with no problems. I'll give it a go though.

muno · January 17th, 2003, 08:17 AM

Perhaps you're unaware that at least one Codegen 300W model (300X) is defective.

Umm. That is, in europe and Finland.

It's not enough for the system anyhow, I ran a similar system with that specific PSU. The 12V spec was at ~13V all the time.
-M

muno · January 17th, 2003, 08:19 AM

Cr?p, I can't edit to attach a file. Here is the plating of the defective model.
-M

GiganticDays · January 17th, 2003, 08:24 AM

Thanks Muno, the PSU I have is plated almost exactly as your picture except the model number is 200X; I do hope this doesn't mean it has a 200W PSU. Having said all that, I have been using this case for months now (all from same supplier) and haven't had any PSU problems.