1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Resolved STOP Error 0x000000D1

Discussion in 'Windows XP' started by BrianC500, 2010/02/08.

Page 1 of 2
  1. 2010/02/08
    BrianC500

    BrianC500 Well-Known Member Thread Starter

    Joined:
    2010/02/02
    Messages:
    54
    Likes Received:
    1
    Hi,

    My boss has an HP Compaq DX2200MT 3.4 Pentium 4 1GB RAM running XPProSP3. He has complained of it freezing although It hasn't done it to me. The main problem is it crashes with the dreaded BSOD giving me the following message

    DRIVER_IRQL_NOT_LESS_THAN_OR_EQUAL

    THE stop error is 0X000000D1

    I've checked the page file as per Microsoft KB, I've removed the RAM and reseated it in another slot

    It still does it. Any suggestions would be very welcome
     
    BrianC500,
    #1
  2. 2010/02/08
    wildfire

    wildfire Getting Old

    Joined:
    2008/04/21
    Messages:
    4,649
    Likes Received:
    124
    Has your boss made any recent changes (added hardware/software etc) to the system?

    Try a system restore to a point before this started happening.
     
    wildfire,
    #2


  3. to hide this advert.

  4. 2010/02/08
    BrianC500

    BrianC500 Well-Known Member Thread Starter

    Joined:
    2010/02/02
    Messages:
    54
    Likes Received:
    1
    Thanks for the reply. He has added Photoshop elements about 2 months ago. He was complaining about his PC freezing and told me as an incidental that he gets the BSOD quite often and has been for some time. He isn't very good with technology and tying him down to a time frame is nigh on impossible. As far as I can gather it's been happening for about 4 months. He hasn't changed any hardware at all.
     
    BrianC500,
    #3
  5. 2010/02/08
    wildfire

    wildfire Getting Old

    Joined:
    2008/04/21
    Messages:
    4,649
    Likes Received:
    124
    Ok,

    You could try following this troubleshooting guide and letting us know how you get on or if you need further assistance. If you're not sure what you're doing then stop and post back here for help.
     
    wildfire,
    #4
  6. 2010/02/08
    BrianC500

    BrianC500 Well-Known Member Thread Starter

    Joined:
    2010/02/02
    Messages:
    54
    Likes Received:
    1
    Hi, unfortunately the debugger tool in the article you directed me to is not available, the page has moved or is no longer available. The BSOD happened again which enabled me to write down the entire stop message, it is
    STOP: 0x000000D1 (0x00000008, 0x00000002, 0x00000000, 0xF72B0C00)

    NDIS.SYS-address F72B0C00 BASE aT F729A000, DATESTAMP 48025D03

    I really appreciate your help
     
    BrianC500,
    #5
  7. 2010/02/08
    wildfire

    wildfire Getting Old

    Joined:
    2008/04/21
    Messages:
    4,649
    Likes Received:
    124
    Sorry Brian,

    It's not my area but if you follow those instructions and post logs someone may be able to assist.

    You can find the debugging tool here, download the Current Release version 6.11.1.404.
     
    wildfire,
    #6
  8. 2010/02/08
    ickymay

    ickymay Inactive

    Joined:
    2010/02/03
    Messages:
    19
    Likes Received:
    0
    if your reading from small memory dump files 256kb max then attach it and Ile run it through windows debugger and see if I can offer you some pointers :)
     
    ickymay,
    #7
  9. 2010/02/08
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,890
    Likes Received:
    387
    ickymay - only Contributing Members can make attachments and we expect Members to debug their own dump data and post the log here. Nice offer though, but if posted here for all to see all may contribute to the possible analysis, noting .....
    Brian - use either our Dump Data Collection Tool or BlueScreenView

    I doubt that either will yeild much more information than NDIS.SYS is the likely culprit.

    This KB may be of some help ....

    STOP 0x0000001D or STOP 0x000000A Stop Error Occurs in Ndis.sys
     
    PeteC,
    #8
  10. 2010/02/09
    mattman

    mattman Inactive Alumni

    Joined:
    2002/06/10
    Messages:
    8,198
    Likes Received:
    63
    When you mention "freezing ", check that the cooling system is working well, there is no dust blocking air vents or heatsink fins. Photoshop is pretty "hardware" intensive (agree Pete?).

    Also run Error Checking (CHKDSK) on the Widows drive.

    Those are mainly just to be sure the basics are covered.

    Matt
     
    mattman,
    #9
  11. 2010/02/09
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,890
    Likes Received:
    387
    Relatively so, but Elements less than the full blown Photoshop I would think.
     
    PeteC,
    #10
  12. 2010/02/16
    BrianC500

    BrianC500 Well-Known Member Thread Starter

    Joined:
    2010/02/02
    Messages:
    54
    Likes Received:
    1
    Hi Sorry for the delay in coming back to you I've been off work a few days. I've downloaded Debugwiz and also downloaded the tools it tells you to download. Debugwiz says it can't find the tools! I've also downloaded Bluescreen view and it can't find any dump files with any thing in. Sorry for being a pain, but I'm scratching my head with this.

    I have run checkdisk and also have cleared all the junk out. I've scanned for viruses, malware and everything else I can think of. It comes back clean.
     
    BrianC500,
    #11
  13. 2010/02/16
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,890
    Likes Received:
    387
    Ensure that the computer is configured to write a dump file by following the instructions from Microsoft
     
    PeteC,
    #12
  14. 2010/02/16
    BrianC500

    BrianC500 Well-Known Member Thread Starter

    Joined:
    2010/02/02
    Messages:
    54
    Likes Received:
    1
    I used blue screen view. It came up with this.

    ==================================================
    Dump File : Mini021610-01.dmp
    Crash Time : 16/02/2010 15:37:50
    Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
    Bug Check Code : 0x000000d1
    Parameter 1 : 0x00000008
    Parameter 2 : 0x00000002
    Parameter 3 : 0x00000000
    Parameter 4 : 0xf7563c00
    Caused By Driver : NDIS.sys
    Caused By Address : NDIS.sys+16c00
    File Description : NDIS 5.1 wrapper driver
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 5.1.2600.5512 (xpsp.080413-0852)
    Processor : 32-bit
    Computer Name :
    Full Path : C:\WINDOWS\minidump\Mini021610-01.dmp
    Processors Count : 2
    Major Version : 15
    Minor Version : 2600
    ==================================================

    Any help is really appreaciated.
     
    BrianC500,
    #13
  15. 2010/02/16
    wildfire

    wildfire Getting Old

    Joined:
    2008/04/21
    Messages:
    4,649
    Likes Received:
    124
    PeteC as usual was right, did you read the Knowledge Base article he posted?
     
    wildfire,
    #14
  16. 2010/02/16
    BrianC500

    BrianC500 Well-Known Member Thread Starter

    Joined:
    2010/02/02
    Messages:
    54
    Likes Received:
    1
    Blue Screen View generated this

    ==================================================
    Dump File : Mini021610-01.dmp
    Crash Time : 16/02/2010 15:37:50
    Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
    Bug Check Code : 0x000000d1
    Parameter 1 : 0x00000008
    Parameter 2 : 0x00000002
    Parameter 3 : 0x00000000
    Parameter 4 : 0xf7563c00
    Caused By Driver : NDIS.sys
    Caused By Address : NDIS.sys+16c00
    File Description : NDIS 5.1 wrapper driver
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 5.1.2600.5512 (xpsp.080413-0852)
    Processor : 32-bit
    Computer Name :
    Full Path : C:\WINDOWS\minidump\Mini021610-01.dmp
    Processors Count : 2
    Major Version : 15
    Minor Version : 2600
    ==================================================


    Many thanks
     
    BrianC500,
    #15
  17. 2010/02/16
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,890
    Likes Received:
    387
    As I suspected - no further hints other than NDIS.sys.

    The KB I posted applies to pre SP2 installs of XP - what is the level of the Service Pack on that computer?
     
    PeteC,
    #16
  18. 2010/02/16
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,890
    Likes Received:
    387
    PeteC,
    #17
  19. 2010/02/16
    BrianC500

    BrianC500 Well-Known Member Thread Starter

    Joined:
    2010/02/02
    Messages:
    54
    Likes Received:
    1
    Sorry about the double post. I read the KB article but it states that the Hotfix was included in SP2 the PC I'm havinmg the problems with already has SP3 installed. Could the original fix be corrupt?
     
    BrianC500,
    #18
  20. 2010/02/16
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,890
    Likes Received:
    387
    No - SP3 is 2 Service Packs ahead of SP1 - any issues would have been fixed long ago.

    I'm afraid you will have to do the legwork through the hits I provided in the hope that a solution crops up. I asked if BitDefender was installed....
     
    PeteC,
    #19
  21. 2010/02/16
    BrianC500

    BrianC500 Well-Known Member Thread Starter

    Joined:
    2010/02/02
    Messages:
    54
    Likes Received:
    1
    Sorry Pete. No Bitdefender isn't installed. I've had a good look through most of the links. The recurring theme seems to be on board NIC problems. I'll check that out and see how it goes. I'll keep you informed especially if it solves the problem. Thanks all for all your help so far.

    Brian
     
    BrianC500,
    #20
Page 1 of 2

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...