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.

blue screen with error message

Discussion in 'Windows XP' started by kenton, 2005/10/25.

  1. 2005/10/25
    kenton

    kenton Inactive Thread Starter

    Joined:
    2004/01/21
    Messages:
    158
    Likes Received:
    0
    Windows XP home edition.

    Sometimes my PC show blue screen with error message and stop responding(hangs), so restart required. Here is possible error log from Event viewer:

    Event Type: Error
    Event Source: System Error
    Event Category: (102)
    Event ID: 1003
    Date: 2005.10.25.
    Time: 13:27:09
    User: N/A
    Computer: NIK
    Description:
    Error code 1000000a, parameter1 00000166, parameter2 00000002, parameter3 00000000, parameter4 804e5433.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 53 79 73 74 65 6d 20 45 System E
    0008: 72 72 6f 72 20 20 45 72 rror Er
    0010: 72 6f 72 20 63 6f 64 65 ror code
    0018: 20 31 30 30 30 30 30 30 1000000
    0020: 61 20 20 50 61 72 61 6d a Param
    0028: 65 74 65 72 73 20 30 30 eters 00
    0030: 30 30 30 31 36 36 2c 20 000166,
    0038: 30 30 30 30 30 30 30 32 00000002
    0040: 2c 20 30 30 30 30 30 30 , 000000
    0048: 30 30 2c 20 38 30 34 65 00, 804e
    0050: 35 34 33 33 5433
     
    Last edited: 2005/10/25
  2. 2005/10/25
    Newt

    Newt Inactive

    Joined:
    2002/01/07
    Messages:
    10,974
    Likes Received:
    2
    Next time it happens, please copy down the information in the top section of the Blue Screen including the numbers and the error. It will probably be something like IRQL_NOT_LESS_OR_EQUAL or some similar gibberish in all caps with _ between the words.
     
    Newt,
    #2

  3. to hide this advert.

  4. 2005/10/26
    cpc2004

    cpc2004 Inactive

    Joined:
    2005/07/08
    Messages:
    366
    Likes Received:
    0
    Hi,

    Probably the culprit is faulty ram. Run memtest or install Microsoft debugging tools and use it format the minidumps.

    Debugging Tools from Microsoft
    1) Create folder c:\symbols
    2) Download and install the http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
    3) Locate your latest memory.dmp file- C:\WINDOWS\Minidump\Mini011005-01.dmp or whatever
    4) open a CMD prompt and cd\program files\debugging tools for windows\
    5) type the following stuff:

    Code:
    c:\program files\debugging tools>kd -z C:\WINDOWS\Minidump\Mini011005-01.dmp
    kd> .logopen c:\debuglog.txt
    kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
    kd> .reload;!analyze -v;r;!thread;lmnt;.logclose;q

    You now have a debuglog.txt in c:\, open it in notepad and post to this thread.
     
  5. 2005/10/27
    kenton

    kenton Inactive Thread Starter

    Joined:
    2004/01/21
    Messages:
    158
    Likes Received:
    0
    Hi,

    is there a sence take out a memory stick from socket, then insert it back, before installing debugging tool?
     

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.