If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
STOP: 0x000000D1 (0x00000081, 0x00000002, 0x00000000, 0x8A5BA588)
I am getting this error message
DRIVER_IRQL_NOT_LESS_OR_EQUAL blah blah STOP: 0x000000D1 (0x00000081, 0x00000002, 0x00000000, 0x8A5BA588) When I suspend my computer and resume this happens randomly - sometimes after the first resume, sometimes after I have suspended and resumed a few times - but it always happens. I just changed a setting in my BIOS in power management "allow HDD power down in suspend" to enable suspending my computer (before it would suspend but not power up). I am thinking that perhaps a setting in the BIOS is causing this error message. Does anyone have an idea? This is Windows XP Pro SP2. I have an ECS A939 Motherboard with BIOS v 1.1K (just updated it), 2GB DDR RAM, and an Athlon X2 3800+ proc. nForce drivers are latest version. |
Ads |
#2
|
|||
|
|||
0x000000D1 (0x00000081, 0x00000002, 0x00000000, 0x8A5BA588)
Hi
Please try the following link to Jim Eshelman's web page - right hand column (D1) http://aumha.org/win5/kbestop.htm -- Will Denny MS-MVP Windows Shell/User Please reply to the News Groups "dalewb" wrote in message ... I am getting this error message DRIVER_IRQL_NOT_LESS_OR_EQUAL blah blah STOP: 0x000000D1 (0x00000081, 0x00000002, 0x00000000, 0x8A5BA588) When I suspend my computer and resume this happens randomly - sometimes after the first resume, sometimes after I have suspended and resumed a few times - but it always happens. I just changed a setting in my BIOS in power management "allow HDD power down in suspend" to enable suspending my computer (before it would suspend but not power up). I am thinking that perhaps a setting in the BIOS is causing this error message. Does anyone have an idea? This is Windows XP Pro SP2. I have an ECS A939 Motherboard with BIOS v 1.1K (just updated it), 2GB DDR RAM, and an Athlon X2 3800+ proc. nForce drivers are latest version. |
#3
|
|||
|
|||
0x000000D1 (0x00000081, 0x00000002, 0x00000000, 0x8A5BA588)
Just for the sake of anyone looking for a solution to this problem, I *might*
have found it in the website just mentioned by Will (above): "The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by caused by faulty or mismatched RAM, or a damaged pagefile." I have two RAM modules in my computer - they were bought a year apart from the same vendor (Crucial) and are the same speed and everything (but physically one is nearly twice as big as the other). But if I understand RAM correctly, it is better to buy them in "matched pairs." So this could be the source of my problem, but one I wouldn't be able to solve as I don't have another $225 laying around to purchase a 2GB matched pair bundle. "Will Denny" wrote: Hi Please try the following link to Jim Eshelman's web page - right hand column (D1) http://aumha.org/win5/kbestop.htm -- Will Denny MS-MVP Windows Shell/User Please reply to the News Groups /q |
#4
|
|||
|
|||
0x000000D1 (0x00000081, 0x00000002, 0x00000000, 0x8A5BA588)
Just for the sake of anyone looking for a solution to this problem, I *might*
have found it in the website just mentioned by Will (above): "The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by caused by faulty or mismatched RAM, or a damaged pagefile." I have two RAM modules in my computer - they were bought a year apart from the same vendor (Crucial) and are the same speed and everything (but physically one is nearly twice as big as the other). But if I understand RAM correctly, it is better to buy them in "matched pairs." So this could be the source of my problem, but one I wouldn't be able to solve as I don't have another $225 laying around to purchase a 2GB matched pair bundle. "Will Denny" wrote: Hi Please try the following link to Jim Eshelman's web page - right hand column (D1) http://aumha.org/win5/kbestop.htm Will Denny MS-MVP Windows Shell/User Please reply to the News Groups |
#5
|
|||
|
|||
0x000000D1 (0x00000081, 0x00000002, 0x00000000, 0x8A5BA588)
dalewb wrote:
| Just for the sake of anyone looking for a solution to this problem, I *might* | have found it in the website just mentioned by Will (above): | | "The most typical cause is a bad device driver (one that uses improper | addresses). It can also be caused by caused by faulty or mismatched RAM, or a | damaged pagefile." | | I have two RAM modules in my computer - they were bought a year apart from | the same vendor (Crucial) and are the same speed and everything (but | physically one is nearly twice as big as the other). But if I understand RAM | correctly, it is better to buy them in "matched pairs." So this could be the | source of my problem, but one I wouldn't be able to solve as I don't have | another $225 laying around to purchase a 2GB matched pair bundle. | | "Will Denny" wrote: | || Hi || || Please try the following link to Jim Eshelman's web page - right hand column || (D1) || || http://aumha.org/win5/kbestop.htm || || Will Denny || MS-MVP Windows Shell/User || Please reply to the News Groups | /q Well....I went off to the repair shop as a result of the 0X0000008E 0xc000005 0x0002003 0xf79De2D8 0x00000000 'stop error' and I went to Jim Eschelman's web page(which translated at MSkb315335 to be driver issue, Ram module or configuration, hardware or Bios) The computer has spontaneously rebooted two days in a row plus the check the harddrive utility and no report so I unchecked the 'automatic reboot' feature. Then I got the actual stop error and the repair person agreed that the machine should go in for an inspection. Repair person took ram sticks out and switched positions (it is a matched pair) It wasn't the Ram The Bios was checked and then the harddrive (new Samsung in March 06-so 6 months old) with no virus/spam etc. At that moment the harddrive stopped reading. Reinstall was not possible either. A replacement Western Digital drive was installed. So my past week has been reinstalling and redoing all the fine tweaks since it wasn't possible to transfer any file settings. The upside was that the Windows certification went through with hardly a blip and included a Thank youlol Plus the repair person made me a slipstreamed Xp with updates since my Xp is pre sp1. So...stop errors are worth investigating grin Rose |
#6
|
|||
|
|||
0x000000D1 (0x00000081, 0x00000002, 0x00000000, 0x8A5BA588)
Might just remove one or the other mem modules and see if the problem
subsides in the short term.. You don't mention what your using DDR400/333/266 unbuffered DDR SDRAM.. You also don't mention your Video cards specs either, have you been swaping out video cards..? Sound & video card drivers up to date..? New hardware drivers(Nvidia chipset, Lan, IDE,and Raid drivers) are all posible suspects.. http://www.ecs.com.tw/ECSWeb/Product...ailName=Manual Got the manual and NVRAID user guide..? http://www.winsupersite.com/showcase...p_sg_clean.asp Did you load the raid drivers during the XP installation..? See link above.. j;-j "dalewb" wrote: Just for the sake of anyone looking for a solution to this problem, I *might* have found it in the website just mentioned by Will (above): "The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by caused by faulty or mismatched RAM, or a damaged pagefile." I have two RAM modules in my computer - they were bought a year apart from the same vendor (Crucial) and are the same speed and everything (but physically one is nearly twice as big as the other). But if I understand RAM correctly, it is better to buy them in "matched pairs." So this could be the source of my problem, but one I wouldn't be able to solve as I don't have another $225 laying around to purchase a 2GB matched pair bundle. "Will Denny" wrote: Hi Please try the following link to Jim Eshelman's web page - right hand column (D1) http://aumha.org/win5/kbestop.htm Will Denny MS-MVP Windows Shell/User Please reply to the News Groups |
Thread Tools | |
Display Modes | |
|
|