Heya,
My grandfather's computer (a Dell Dimension 5150) running Windows XP Home (Dutch version) has been showing some strange behavior lately. Whenever he puts a (possibly damaged) cd in the disk drive his computer BSOD's with the attached message. What I could find on aumha.org/a/stop.htm the 0xD1 stop message indicates a high chance of a faulty driver. As the BSOD only occurs when inserting a cd it seems likely that this is indeed the problem. When the ('bad') cd is in the drive as the computer boots there is no problem, the crash only occurs when the cd is inserted as the user is logged in.
I searched for 'atapi.sys' which is apparently a MS driver, so advice on disabling non-MS drivers doesn't seem appropriate. Is there something I could give a try to fix this problem? I have attached a 'screenshot' of the BSOD (luckily the old man knows how to work a digital camera), and the dumps I could find in "C:/Windows/Minidump/". As far as I know those are all the result of inserting a cd.
Note: When the cd is in the drive already it is possible to read the cd's contents and even install programs from it. (I have tried this with 2 cd's so far.)
Note: I recently reinstalled his pc with a legit version of windows.
Thank you for your time,
Alturin.
PS: I just noticed I'm not allowed to post images or attachments.
So here's the BSOD message:
*** STOP: 0x000000D1 (0x00000003, 0x00000002, 0x00000000, 0xF73A07D8)
*** atapi.sys - Address F73A07D8 base at F739A000, DateStamp 41107b4d
Curiously though, there is no reference of "IRQL_NOT_LESS_OR_EQUAL" which I see other people post about.
My grandfather's computer (a Dell Dimension 5150) running Windows XP Home (Dutch version) has been showing some strange behavior lately. Whenever he puts a (possibly damaged) cd in the disk drive his computer BSOD's with the attached message. What I could find on aumha.org/a/stop.htm the 0xD1 stop message indicates a high chance of a faulty driver. As the BSOD only occurs when inserting a cd it seems likely that this is indeed the problem. When the ('bad') cd is in the drive as the computer boots there is no problem, the crash only occurs when the cd is inserted as the user is logged in.
I searched for 'atapi.sys' which is apparently a MS driver, so advice on disabling non-MS drivers doesn't seem appropriate. Is there something I could give a try to fix this problem? I have attached a 'screenshot' of the BSOD (luckily the old man knows how to work a digital camera), and the dumps I could find in "C:/Windows/Minidump/". As far as I know those are all the result of inserting a cd.
Note: When the cd is in the drive already it is possible to read the cd's contents and even install programs from it. (I have tried this with 2 cd's so far.)
Note: I recently reinstalled his pc with a legit version of windows.
Thank you for your time,
Alturin.
PS: I just noticed I'm not allowed to post images or attachments.
So here's the BSOD message:
*** STOP: 0x000000D1 (0x00000003, 0x00000002, 0x00000000, 0xF73A07D8)
*** atapi.sys - Address F73A07D8 base at F739A000, DateStamp 41107b4d
Curiously though, there is no reference of "IRQL_NOT_LESS_OR_EQUAL" which I see other people post about.