system reboting and freezing.

  1. #11
    tias2001 is offline Junior Member

    Re: system reboting and freezing.

    Hi there,

    The reboot may be due to system overheating.. (i.e fan failure) go into your bios and look at the system temperatures of the cpu and motherboard - if they are over 50deg C then there may be a problem. - If your bios doesnt display temeratures then download a program that can test them for you like motherboard monitor (google it)

    Also in System in the control panels click on the advanced tab - click on settings for startup and recovery and untick automatically restart.

    Regards
    Mathias


  2. #12
    walterj is offline Full Member
    Hi Mathias
    No go on fan and heat. Fan is working and did ran for over a week with cover removed. Also I have Antec power supply 380W in place of original so there is no problem in this area. Walter
    Last edited by walterj; 18-08-2006 at 07:42 PM.

  3. #13
    jephree is offline ¨*·.¸ «.·°·..·°·.» ¸.·*¨
    Post more dumps as you get them.

    Everything so far points to memory but it's hard to pin point the where and the what as there are many sources and uses of various memory in that box.

    Again comparing the dumps might shed some light.

  4. #14
    walterj is offline Full Member
    [Hi Jephree
    here is a dump. This one is from Dr Watson Walter
    Attached Files

  5. #15
    tias2001 is offline Junior Member
    Hi walter,

    have you tried testing your ram with memtest?

    If not try that as the first log you posted does have a memory corruption error in it,,,

    http://www.memtest86.com

    Mathias

  6. #16
    jephree is offline ¨*·.¸ «.·°·..·°·.» ¸.·*¨
    Quote Originally Posted by walterj
    [Hi Jephree
    here is a dump. This one is from Dr Watson Walter
    That last dump was just the preliminary data.

    When you copy the log it is best to select all (Ctrl A) then copy (Ctrl C) and paste (Ctrl V).

    Or else the log was cut off some other way.


    Also I would suggest this change:

    Right click My Computer then click Properties

    Advanced > Startup and Recovery > Settings

    Write debugging information

    Set to Kernal Memory Dump



    Last edited by jephree; 20-08-2006 at 12:35 AM.

  7. #17
    walterj is offline Full Member
    Quote Originally Posted by tias2001
    Hi walter,

    have you tried testing your ram with memtest?

    If not try that as the first log you posted does have a memory corruption error in it,,,

    http://www.memtest86.com

    Mathias
    Hi Mathias
    did ran 8/18
    Hi Jephree
    Ran memory test. made 3 passes. came out OK.
    What is the next step. Thanks

  8. #18
    walterj is offline Full Member
    Quote Originally Posted by jephree
    That last dump was just the preliminary data.

    When you copy the log it is best to select all (Ctrl A) then copy (Ctrl C) and paste (Ctrl V).

    Or else the log was cut off some other way.


    Also I would suggest this change:

    Right click My Computer then click Properties

    Advanced > Startup and Recovery > Settings

    Write debugging information

    Set to Kernal Memory Dump



    Hi Jephree
    Will set the setings for dumps.
    Walter

  9. #19
    walterj is offline Full Member
    Hi Jephree
    yesterday at 20:58 system restarted, that generated 2 dumps . one went into \windows\memory.dmp. this one is debuglog.txt
    second went to \minidump\mini082006-02.dmp. that is debuglog1.txt
    Thanks Walter
    Attached Files

  10. #20
    jephree is offline ¨*·.¸ «.·°·..·°·.» ¸.·*¨
    At this point I would suggest a diagnostic process of elimination.

    Your errors continue to point to hardware and especially memory although this can still be triggered by drivers (software).

    To eliminate software issues start turning off programs that automatically run. You can try this manually (for example I would turn off all Norton Products). Right click the icons in the System Tray (lower right) and choose EXIT. On a more advanced level you can go to start Run.. msconfig | Startup. Here you can uncheck all or selectively uncheck programs from starting. You can always go back here and recheck. On reboot you will be warned that you are starting in a Diagnostic Mode. Just check (I know) Don't show me this again.

    A final software check would be to reinstall XP from scratch. If that continues to crash you can pretty much focus on a hardware issue.

    As to hardware checks I would remove the second stick of RAM as a first test. Next start removing drives (other than your boot C: drive). etc etc.

    Just to give you an idea of an approach. Please post more dumps and advise on progress.

    Your last dumps (although pointing to a hardware failure) were last dealing with Norton before the crash.

+ Reply to Thread
Page 2 of 6 FirstFirst 1 2 3 4 5 6 LastLast