TechSpot

BugCheck -Event Viewer - SaveDump

By Dr-Hack
Sep 27, 2005
  1. Hello Techspot....

    I read alot of posts regarding my problem but usually i end up getting done with other peoples problem but here i had to make a new thread as i needed to provide MiniDumps ...

    My Problem is this that my computer ends up restarting in a 1 or 2 day time ... the screen changes to grey or sometimes vertical lines of some colors show up and then its a restart ..it started to happen since a week, thought its shdnt be a issue but it is :) ..

    Event Viewer .. says this
    Event ID: 1001
    Source: Save Dump
    Description:
    The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x00000e28, 0x00000002, 0x00000000, 0xff12d058). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\MEMORY.DMP.

    Searching Microsoft took me here ...
    http://support.microsoft.com/default.aspx?scid=kb;en-us;826502
    and in here it says this is some TCp/IP problem, but after reading all ur threads it doesnt seem to and there fix is available just pay them :) (as they say)

    I uploaded the Last 6 MiniDumps (after attaching i found only the last 3 are 64 Kb other are 0kb )

    I will be glad if i get any Help ...
    Thank you ...

    I am Runnin windows 2000 Server edition on a branded p3 Dell Machine ...

    Sidetopic: how can i make sure my system consumes least resources for graphics and displaying as i dont want to waste resources there just need beter perfomance (done with visual settings) and TweakUI doesnt work


    THanks again ...
     

    Attached Files:

  2. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Hi Dr-Hack,

    Your W2K has the latest patch and microsoft does not provide the corresponding symbolic file. I can't format the stack trace of your minidumps. You have to install Microsoft Debugger. Run the debugger and attach the output here.

    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:\WINNT\memory.dmp
    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:\WINNT\memory.dmp
    kd> .logopen c:\debuglog.txt
    kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
    kd> .reload;!analyze -v;r;kv;lmnt;!process.logclose;q

    You now have a debuglog.txt in c:\, open it in notepad and post to this thread.

    Debug report of your minidump

    BugCheck D1, {e28, 2, 0, ff12d058}

    kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 00000e28, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: ff12d058, address which referenced memory

    Debugging Details:
    ------------------
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    MODULE_NAME: nt
    FAULTING_MODULE: 80400000 nt
    DEBUG_FLR_IMAGE_TIMESTAMP: 427b58bb
    READ_ADDRESS: 00000e28
    CURRENT_IRQL: 2

    FAULTING_IP:
    +ffffffffff12d058
    ff12d058 ?? ???

    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: DRIVER_FAULT
    BUGCHECK_STR: 0xD1
    LAST_CONTROL_TRANSFER: from 00000000 to 80467d67

    STACK_TEXT:
    804717d0 00000000 00000e28 00000002 00000000 nt+0x67d67 <-- no symbol and unable to format stack trace

    STACK_COMMAND: .bugcheck ; kb
    FOLLOWUP_NAME: MachineOwner
    BUCKET_ID: WRONG_SYMBOLS
    Followup: MachineOwner
     
  3. Dr-Hack

    Dr-Hack TS Rookie Topic Starter

    cant I delete the POST ?
    _________________________________________________________________
    USELESS POST DEMAND FULLFILLED IN THE ATTACHMENT ON MY LAST POST
     
  4. Dr-Hack

    Dr-Hack TS Rookie Topic Starter

    cant I delete the POST ?
    _________________________________________________________________
    USELESS POST DEMAND FULLFILLED IN THE ATTACHMENT ON MY LAST POST
     
  5. Dr-Hack

    Dr-Hack TS Rookie Topic Starter

    I start copying the text , then thought i shd attach the file :) ..
    tried to follow ur steps let me know if i did something wrong..

    and thanks alot ..
     

    Attached Files:

  6. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Hi Dr-Hack,

    Can you attach the debug report of mini092005-01.dmp and mini092605-01.dmp here.
     
  7. Dr-Hack

    Dr-Hack TS Rookie Topic Starter

    minidumps

    Attached the Debugged MiniDumps

    Thank You ....
     

    Attached Files:

  8. Dr-Hack

    Dr-Hack TS Rookie Topic Starter

    i had 2 more dumps ... till now :(

    usually it happens in 1 day or in 2 .. waiting for cpc2004 final Analysis ..

    Thanks
     
  9. cuteparagb4u

    cuteparagb4u TS Rookie

    I was not able to attach the dump files

    My problem is same. So try to solve my problem
     
  10. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Hi,

    It is hardware problem. Maybe overheat. What is temperature of your CPU?
     
  11. Dr-Hack

    Dr-Hack TS Rookie Topic Starter

    cpc2004, thanks for a reply ... but i dont know a reliable 3rd party tool to monitor the temp :) .. may be u can tell me where to download then i will let u know the temp ..,

    and u saw the Dump files? so its some hardward fault ? :( ...
    Well let me know the tool, i'll give u the temp logs ....
    cant afford hardware errors :(

    Thanks...
     
  12. Dr-Hack

    Dr-Hack TS Rookie Topic Starter

    just saw an Referer from here to my site so came here..

    I have resolved the problem.it was a hardware problem :)

    actually the problem was my modem..while i checked the temperatures i got that around 48° - 54° C so i got worried
    but the solution was... I updated my Modem Driver from Windows Update and now my system is running constantly since that time :D


    coool....
    Thanks cpc2004
     
  13. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Hi,

    Thanks for your update.
     
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...