XP errors

[Admiral]

STOP 0x000000c5 (0x00000000, 0x00000002, 0x00000001, 0x80537213)

From now and then I get that error, with slight variations of the first line inside the brackets.

I tryed searching Microsoft's Knowledge Base and found nothing.
Can anyone tell me what's with these errors ?

[Jammrock]

What's the error string? It'll be a series of words in all caps seperated by underscores (_). I.E. KMODE_EXCEPTION_NOT_HANDLED.

Jammrock

[Admiral]

Ups !
forgot to write that down

I'll report back after the next blue screen

[Kosh Naranek]

As jammrock says .. the ErrorString can give a valuable hint as to the reason for the crash.

[orangejulius]

Did you recently install any new drivers?

[The PIT]

Nothing better than writing the error down and Microsoft doesn't even know about it.

[Novdid]

That wouldn't surprise me, we're beta testers, all of us.

[Admiral]

Did you recently install any new drivers?

Nvidia 29.40 beta drivers, though the 28.32 WHQL yeld the same result.

Let's wait for the error string.
Man, I can't belive I'm actually growing impatient about a blue screen happening .

[Gurm]

Nvidia's detonators, on some boards, still produce that from time to time. If it's anything about nv4disp.dll, or an infinite loop, there are fixes available from most of the major nvidia fansites.

Will Nvidia fix it themselves? Nope.

Nvidia = shit. Always has, always will.

- Gurm

[Admiral]

There doesn't appear to be any error string:

"Technical Information:

*** STOP 0x000000c5 (0x000c4040, 0x00000002, 0x00000001, 0x80537213) "

The other stuff is just troubleshooting advice.

There is supposedly a log (minidump) created by windows but it's made of "dmp" files and I don't know how to visualize them.

[Jammrock]

TechNET has an entry for that, but it's for Win2k. Usually the Win2k and WinXP entries are fairly similar or can give you insight as to what the general cause may be. The most common cause of the error in Win2k is a faulty LogiTech mouse driver installation. See TechNet articles Q302971 and Q255151.

There is no information specific to WinXP listed anywhere in TechNet or Winblows support. Your best guess is to remove the nVidia drivers. Once they are removed, search your C:\Windows\system32\ folder for residue nVidia files. The best way is to unzip the drivers and look for specific filename beginnings, like nv4*.*. Clean it out, roll back to an older version of the driver that used to work and see if that fixes it.

Jammrock