G
Guest
I recently upgraded to XP Pro. Now, I have started to get a Stop error msg
DRIVER_IRQL_NOT_LESS_OR_EQUAL 0X000000D1(0X00000004, 0X00000002, 0X00000000,
0X81A793DC).
I have a P4 3.0 Gig (Hyperthreaduing) on a ECS PT800CE-A board, 512 Megs
DDR400 RAM, an NVidia FX5200 video card, and a Soundblaster Live sound card.
I have read through the Microsoft Knowledge base for error messages. If I
understand correctly, this one is caused by a device driver trying to access
a memory area it is not supposed to. The fixes are to check all device
drivers are signed (they are), disable System BIOS Cachable (which I did),
and try replacing components. I have tried 3 different NVidia drivers,
uninstalled the Soundblaster driver and let Windows pick it up with a
generic, and none of that has worked.
Does anyone know what exactly causes this particular error code? I
understand that somewhere there is a cross reference to the specific code
parameters, but I can't find it. It would sure help if I could find out
exactly which component/driver was at fault.
I would really appreciate any help anyone can proovide.
Thanks.
Bill.
DRIVER_IRQL_NOT_LESS_OR_EQUAL 0X000000D1(0X00000004, 0X00000002, 0X00000000,
0X81A793DC).
I have a P4 3.0 Gig (Hyperthreaduing) on a ECS PT800CE-A board, 512 Megs
DDR400 RAM, an NVidia FX5200 video card, and a Soundblaster Live sound card.
I have read through the Microsoft Knowledge base for error messages. If I
understand correctly, this one is caused by a device driver trying to access
a memory area it is not supposed to. The fixes are to check all device
drivers are signed (they are), disable System BIOS Cachable (which I did),
and try replacing components. I have tried 3 different NVidia drivers,
uninstalled the Soundblaster driver and let Windows pick it up with a
generic, and none of that has worked.
Does anyone know what exactly causes this particular error code? I
understand that somewhere there is a cross reference to the specific code
parameters, but I can't find it. It would sure help if I could find out
exactly which component/driver was at fault.
I would really appreciate any help anyone can proovide.
Thanks.
Bill.