Problems troubleshooting STOP error 0x0000000c5
in [Windows XP]
|
Prev: WMS Idle Error Message
Next: runtime error
From: BeeSodd on 21 Nov 2005 02:00 I've been getting blue screens for the past couple of weeks and I'm having trouble figuring out what to do next. Here's the error: STOP 0x000000c5 (0x00000004, 0x00000002, 0x00000001, 0x805446f3) There's some other stuff that specifically mentions possible driver issues and suggests using the special pool feature. and the info from Event Viewer: Event Type: Error Event Source: System Error Event Category: (102) Event ID: 1003 Date: 11/21/2005 Time: 1:14:44 AM User: N/A Computer: ********** Description: Error code 100000c5, parameter1 00000004, parameter2 00000002, parameter3 00000001, parameter4 805446f3. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 53 79 73 74 65 6d 20 45 System E 0008: 72 72 6f 72 20 20 45 72 rror Er 0010: 72 6f 72 20 63 6f 64 65 ror code 0018: 20 31 30 30 30 30 30 63 100000c 0020: 35 20 20 50 61 72 61 6d 5 Param 0028: 65 74 65 72 73 20 30 30 eters 00 0030: 30 30 30 30 30 34 2c 20 000004, 0038: 30 30 30 30 30 30 30 32 00000002 0040: 2c 20 30 30 30 30 30 30 , 000000 0048: 30 31 2c 20 38 30 35 34 01, 8054 0050: 34 36 66 33 46f3 So far the only thing I can find on this specific error points to driver issues. I haven't installed any new hardware recently so I'm not really sure where to start. And the only article I could find on this error says it applies to Windows 2000, not XP, so I'm not even sure I'm on the right track yet. At first I thought it might be bad RAM so I ran memtest86 for about 24 hours with no problems. I looked into updating the BIOS but I don't know if that's even what's causing the problem. I've read about the Driver Verification tool and the Special Pool Feature, which seem like they might help narrow down the possibilities, but I want to make sure I do everything right. Any suggestions would be much appreciated. Thanks. And in case it helps here's some more info: Windows XP Pro system Athlon 64 3200+ MSI K8T Neo FIS2R motherboard Mushkin LvII Black PC3200 RAM ATI Radeon 9800 Pro graphics card Lite-On 52x CDRW 160GB IDE drive 160GB SATA drive 160GB USB2.0 external drive 120GB Firewire external drive DVD-RW firewire external drive
From: Malke on 21 Nov 2005 10:15 BeeSodd wrote: > > I appreciate the help. But the first link doesn't have any > information about my specific error. And the other link has the one > article I was already able to find. As I said, the article states that > it only applies to Windows 2000 OSes. > > Even if it does apply to Windows XP I'm still not sure what to do > next. > See if this is applicable to your situation: http://support.microsoft.com/Default.aspx?kbid=887742&sd=RMVP Malke -- Elephant Boy Computers www.elephantboycomputers.com "Don't Panic!" MS-MVP Windows - Shell/User
From: BeeSodd on 21 Nov 2005 10:27 I guess it's possible but that's not the error I'm getting. So I don't see why that's more likely to be the problem than anything else. I do have AV and Firewall apps installed (Avast! and ZoneAlarm) but I'm not sure about the TDI drivers. I'll have to look into it a bit more. Should I try installing that update anyway, just to see if it helps? It's probably not gonna hurt anything right? "Malke" wrote: > BeeSodd wrote: > > > > > I appreciate the help. But the first link doesn't have any > > information about my specific error. And the other link has the one > > article I was already able to find. As I said, the article states that > > it only applies to Windows 2000 OSes. > > > > Even if it does apply to Windows XP I'm still not sure what to do > > next. > > > > See if this is applicable to your situation: > http://support.microsoft.com/Default.aspx?kbid=887742&sd=RMVP > > Malke > -- > Elephant Boy Computers > www.elephantboycomputers.com > "Don't Panic!" > MS-MVP Windows - Shell/User >
From: Malke on 21 Nov 2005 11:53 BeeSodd wrote: > I guess it's possible but that's not the error I'm getting. So I don't > see why that's more likely to be the problem than anything else. > > I do have AV and Firewall apps installed (Avast! and ZoneAlarm) but > I'm not > sure about the TDI drivers. I'll have to look into it a bit more. > > Should I try installing that update anyway, just to see if it helps? > It's probably not gonna hurt anything right? I can't answer that. I would look into testing your RAM before installing any software updates. To test your RAM, I like Memtest86+ from www.memtest.org. Obviously, you have to get the program from a working machine. You will either download the precompiled Windows binary to make a bootable floppy or the .iso to make a bootable cd. If you want to use the latter, you'll need to have third-party burning software on the machine where you download the file - XP's built-in burning capability won't do the job. In either case, boot with the media you made. The test will run immediately. Let the test run for an hour or two - unless errors are seen immediately. If you get any errors, replace the RAM. Malke -- Elephant Boy Computers www.elephantboycomputers.com "Don't Panic!" MS-MVP Windows - Shell/User
From: BeeSodd on 21 Nov 2005 12:08
From my original post: "At first I thought it might be bad RAM so I ran memtest86 for about 24 hours with no problems." So, I think I've ruled that out at this point. Again, I appreciate all the help, but this is all stuff that I've already tried or looked into and I'm still unsure of what to do next. Is there really no better way to narrow this down to a more specific issue? All I have now is that it MIGHT be a bad driver, but who knows which one? Should I mess with the Driver Verification tool? From what I've read it sounded a little risky but maybe that's just MS covering their a**es in case some inexperienced user breaks something while using it. "Malke" wrote: > BeeSodd wrote: > > > I guess it's possible but that's not the error I'm getting. So I don't > > see why that's more likely to be the problem than anything else. > > > > I do have AV and Firewall apps installed (Avast! and ZoneAlarm) but > > I'm not > > sure about the TDI drivers. I'll have to look into it a bit more. > > > > Should I try installing that update anyway, just to see if it helps? > > It's probably not gonna hurt anything right? > > I can't answer that. I would look into testing your RAM before > installing any software updates. To test your RAM, I like Memtest86+ > from www.memtest.org. Obviously, you have to get the program from a > working machine. You will either download the precompiled Windows > binary to make a bootable floppy or the .iso to make a bootable cd. If > you want to use the latter, you'll need to have third-party burning > software on the machine where you download the file - XP's built-in > burning capability won't do the job. In either case, boot with the > media you made. The test will run immediately. Let the test run for an > hour or two - unless errors are seen immediately. If you get any > errors, replace the RAM. > > Malke > -- > Elephant Boy Computers > www.elephantboycomputers.com > "Don't Panic!" > MS-MVP Windows - Shell/User > |