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.

Sudden reboot problem, [Dump Data]

Discussion in 'Windows XP' started by Roekemoes, 2006/04/25.

  1. 2006/04/25
    Roekemoes

    Roekemoes Inactive Thread Starter

    Joined:
    2006/04/23
    Messages:
    19
    Likes Received:
    0
    Hey guys, I've been desperate for some weeks now and finding this forum gave me a spark of hope again :)

    I've been experiencing sudden reboots, especially when gaming. No error message, no BSOD, just a reboot.

    My first guess was a heat problem, after reading this forums a bit I thought it might be a memery issue. I've run the computer with the box open but still the same problem.

    It may be usefull to add that I'm using an Nvidia GeForce3. System model: MS-6367

    I'm using a bot for a game that uses javascript, some errors occured when I started running it but when I'm just playing myself without the bot it also happens from time to time. I used Joe's guide to create a log, I just can't really find a log that holds the same date as the crash. Seems I can't find a dump file of a sudden reboot, only from a BSOD.

    Anyway here's the log:
    Opened log file 'c:\debuglog.txt'

    Microsoft (R) Windows Debugger Version 6.6.0003.5
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dmp]
    User Mini Dump File: Only registers, stack and portions of memory are available

    Comment: 'Dr. Watson generated MiniDump'
    Windows XP Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: SingleUserTS
    Debug session time: Wed Apr 19 15:06:35.000 2006 (GMT+2)
    System Uptime: not available
    Process Uptime: 0 days 9:28:58.000
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
    ............................................
    This dump file has an exception of interest stored in it.
    The stored exception information can be accessed via .ecxr.
    (818.838): Access violation - code c0000005 (first/second chance not available)
    eax=00ba3580 ebx=00431d80 ecx=0070ffdc edx=443f0004 esi=0000001c edi=0000001f
    eip=77c3745e esp=0070fef4 ebp=0070ff24 iopl=0 nv up ei pl zr na po nc
    cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
    msvcrt!_SEH_epilog+0x3:
    77c3745e 64890d00000000 mov fs:[00000000],ecx fs:003b:00000000=????????
    0:001> !analyze -v;r;kv;lmtn;.logclose;q
    *******************************************************************************
    * *
    * Exception Analysis *
    * *
    *******************************************************************************

    *** WARNING: Unable to verify checksum for fsdfwd.exe
    *** ERROR: Module load completed but symbols could not be loaded for fsdfwd.exe
    *** WARNING: Unable to verify checksum for fswscs.dll
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for fswscs.dll -
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for FSMA32.DLL -
    *** WARNING: Unable to verify checksum for fsmirror.dll
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for fsmirror.dll -

    FAULTING_IP:
    msvcrt!_SEH_epilog+3
    77c3745e 64890d00000000 mov fs:[00000000],ecx

    EXCEPTION_RECORD: ffffffff -- (.exr ffffffffffffffff)
    .exr ffffffffffffffff
    ExceptionAddress: 77c3745e (msvcrt!_SEH_epilog+0x00000003)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 00000000
    Parameter[1]: ffffffff
    Attempt to read from address ffffffff

    DEFAULT_BUCKET_ID: APPLICATION_FAULT

    PROCESS_NAME: fsdfwd.exe

    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx ". The memory could not be "%s ".

    READ_ADDRESS: ffffffff

    BUGCHECK_STR: ACCESS_VIOLATION

    LAST_CONTROL_TRANSFER: from 77c2c3e7 to 77c3745e

    STACK_TEXT:
    0070ff24 77c2c3e7 0000001c 0070ff40 77c29cd4 msvcrt!_SEH_epilog+0x3
    0070ff30 77c29cd4 0000001c 00000001 0070ff64 msvcrt!_nh_malloc+0x13
    0070ff40 004107cc 0000001c 0000001f 00431d80 msvcrt!operator new+0xf
    WARNING: Stack unwind information not available. Following frames may be wrong.
    0070ff64 0041057f 0000001f 00000000 00431db0 fsdfwd+0x107cc
    00000000 00000000 00000000 00000000 00000000 fsdfwd+0x1057f


    STACK_COMMAND: ~1s; .ecxr ; kb

    FOLLOWUP_IP:
    msvcrt!_SEH_epilog+3
    77c3745e 64890d00000000 mov fs:[00000000],ecx

    SYMBOL_STACK_INDEX: 0

    FOLLOWUP_NAME: MachineOwner

    SYMBOL_NAME: msvcrt!_SEH_epilog+3

    MODULE_NAME: msvcrt

    IMAGE_NAME: msvcrt.dll

    DEBUG_FLR_IMAGE_TIMESTAMP: 41109752

    FAILURE_BUCKET_ID: ACCESS_VIOLATION_msvcrt!_SEH_epilog+3

    BUCKET_ID: ACCESS_VIOLATION_msvcrt!_SEH_epilog+3

    Followup: MachineOwner
    ---------

    eax=00ba3580 ebx=00431d80 ecx=0070ffdc edx=443f0004 esi=0000001c edi=0000001f
    eip=77c3745e esp=0070fef4 ebp=0070ff24 iopl=0 nv up ei pl zr na po nc
    cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
    msvcrt!_SEH_epilog+0x3:
    77c3745e 64890d00000000 mov fs:[00000000],ecx fs:003b:00000000=????????
    ChildEBP RetAddr Args to Child
    0070ff24 77c2c3e7 0000001c 0070ff40 77c29cd4 msvcrt!_SEH_epilog+0x3
    0070ff30 77c29cd4 0000001c 00000001 0070ff64 msvcrt!_nh_malloc+0x13 (FPO: [Non-Fpo])
    0070ff40 004107cc 0000001c 0000001f 00431d80 msvcrt!operator new+0xf (FPO: [Non-Fpo])
    WARNING: Stack unwind information not available. Following frames may be wrong.
    0070ff64 0041057f 0000001f 00000000 00431db0 fsdfwd+0x107cc
    00000000 00000000 00000000 00000000 00000000 fsdfwd+0x1057f
    start end module name
    00400000 0044c000 fsdfwd fsdfwd.exe Tue Jun 21 14:31:17 2005 (42B80895)
    00730000 00738000 fswscs fswscs.dll Mon Apr 26 21:28:55 2004 (408D62F7)
    00840000 00853000 fsgkiapi fsgkiapi.dll Fri Jun 10 08:57:23 2005 (42A939D3)
    00b70000 00b76000 fsdfwres fsdfwres.eng Tue Jun 21 14:31:22 2005 (42B8089A)
    00c80000 00c8c000 fslsp fslsp.dll Fri Jun 10 13:15:32 2005 (42A97654)
    10000000 10006000 FSEXC FSEXC.DLL Fri Jun 03 07:32:13 2005 (429FEB5D)
    16000000 16019000 FSLD32 FSLD32.DLL Fri Jun 03 07:36:39 2005 (429FEC67)
    17000000 17016000 FSMA32 FSMA32.DLL Fri Jun 03 07:36:15 2005 (429FEC4F)
    17100000 17120000 FSTNB FSTNB.dll Fri Sep 10 08:55:49 2004 (41414FF5)
    18000000 18011000 FSPMAPI FSPMAPI.DLL Fri Jun 03 07:36:05 2005 (429FEC45)
    20000000 202c5000 xpsp2res xpsp2res.dll Wed Aug 04 09:56:41 2004 (411096B9)
    33000000 3301e000 fsmirror fsmirror.dll Mon May 02 15:31:37 2005 (42762BB9)
    5ad70000 5ada8000 uxtheme uxtheme.dll Wed Aug 04 09:56:43 2004 (411096BB)
    5b860000 5b8b4000 netapi32 netapi32.dll Wed Aug 04 09:56:28 2004 (411096AC)
    662b0000 66308000 hnetcfg hnetcfg.dll Wed Aug 04 09:56:16 2004 (411096A0)
    71a50000 71a8f000 mswsock mswsock.dll Wed Aug 04 09:59:20 2004 (41109758)
    71a90000 71a98000 wshtcpip wshtcpip.dll Wed Aug 04 09:57:49 2004 (411096FD)
    71aa0000 71aa8000 ws2help ws2help.dll Wed Aug 04 09:57:39 2004 (411096F3)
    71ab0000 71ac7000 ws2_32 ws2_32.dll Wed Aug 04 09:57:38 2004 (411096F2)
    74ed0000 74ede000 wbemsvc wbemsvc.dll Wed Aug 04 09:56:51 2004 (411096C3)
    74ef0000 74ef8000 wbemprox wbemprox.dll Wed Aug 04 09:56:50 2004 (411096C2)
    75290000 752c7000 wbemcomn wbemcomn.dll Wed Aug 04 09:56:44 2004 (411096BC)
    75690000 75706000 fastprox fastprox.dll Wed Aug 04 09:56:05 2004 (41109695)
    76080000 760e5000 msvcp60 msvcp60.dll Wed Aug 04 09:59:13 2004 (41109751)
    76360000 76370000 winsta winsta.dll Wed Aug 04 09:56:40 2004 (411096B8)
    767a0000 767b3000 ntdsapi ntdsapi.dll Wed Aug 04 09:56:57 2004 (411096C9)
    76d60000 76d79000 iphlpapi iphlpapi.dll Wed Aug 04 09:56:10 2004 (4110969A)
    76f20000 76f47000 dnsapi dnsapi.dll Wed Aug 04 09:56:45 2004 (411096BD)
    76f50000 76f58000 wtsapi32 wtsapi32.dll Wed Aug 04 09:57:55 2004 (41109703)
    76f60000 76f8c000 wldap32 wldap32.dll Wed Aug 04 09:56:43 2004 (411096BB)
    76fd0000 7704f000 clbcatq clbcatq.dll Tue Jul 26 06:39:44 2005 (42E5BE90)
    77050000 77115000 comres comres.dll Wed Aug 04 09:56:36 2004 (411096B4)
    77120000 771ac000 oleaut32 oleaut32.dll Wed Aug 04 09:57:39 2004 (411096F3)
    774e0000 7761d000 ole32 ole32.dll Tue Jul 26 06:39:47 2005 (42E5BE93)
    77b40000 77b62000 apphelp apphelp.dll Wed Aug 04 09:56:36 2004 (411096B4)
    77c00000 77c08000 version version.dll Wed Aug 04 09:56:39 2004 (411096B7)
    77c10000 77c68000 msvcrt msvcrt.dll Wed Aug 04 09:59:14 2004 (41109752)
    77d40000 77dd0000 user32 user32.dll Wed Mar 02 19:09:29 2005 (42260159)
    77dd0000 77e6b000 advapi32 advapi32.dll Wed Aug 04 09:56:23 2004 (411096A7)
    77e70000 77f01000 rpcrt4 rpcrt4.dll Wed Aug 04 09:56:30 2004 (411096AE)
    77f10000 77f57000 gdi32 gdi32.dll Thu Dec 29 03:54:35 2005 (43B34FEB)
    77fe0000 77ff1000 secur32 secur32.dll Wed Aug 04 09:56:49 2004 (411096C1)
    7c800000 7c8f4000 kernel32 kernel32.dll Wed Aug 04 09:56:36 2004 (411096B4)
    7c900000 7c9b0000 ntdll ntdll.dll Wed Aug 04 09:56:36 2004 (411096B4)
    Closing open log file c:\debuglog.txt
     
  2. 2006/04/25
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Roekemoes - Welcome to the Board :)

    Sudden reboots do not generate dump logs as you have discovered :)

    Until our resident expert on dump data happens along I suggest you test your memory using either Windows Memory Diagnostic Tool or Memtest

    BTW - clearer to just paste the dump data into a post - the Code tags are for code. I have edited you post and the thread title.
     

  3. to hide this advert.

  4. 2006/04/25
    Roekemoes

    Roekemoes Inactive Thread Starter

    Joined:
    2006/04/23
    Messages:
    19
    Likes Received:
    0
    Thanks for the warm welcome :)

    I'll run one of those memory tests this afternoon.

    As for temperature, I've looked into my bios and the system temperature is 30 degrees celcius. I don't think that's really high so I think that's not the issue.

    I'll keep you informed on the memory test. The dumplog is probably from a BSOD that I get once every few days also.

    Thanks again
     
  5. 2006/04/25
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    You can view your CPU, mobo and other temps plus voltages from within Windows using Everest or SpeedFan. Alternatively many motherboard CD's (Asus and Gigabyte to name but two) have a similar facility available to install.
     
  6. 2006/04/25
    Roekemoes

    Roekemoes Inactive Thread Starter

    Joined:
    2006/04/23
    Messages:
    19
    Likes Received:
    0
    I installed that Speedfan application but I'm a bit clueless on what the values should be. Could someone give a little input on what reasonable temperatures are?

    Edit: I'm seeing 3 values for temperatures: temp1, temp2, temp3... they're at 36, 126, 69
    I'm also seeing three fans fan1, fan2 and fan3 but only fan 3 gives a value for a RPM.

    I have 2 harddrives, they're stacked on top of eachother in my box, one is near it's max temp and the other one is average.

    Could this be the issue? That one of the harddrives isn't cooled enough?
     
    Last edited: 2006/04/25
  7. 2006/04/25
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Try Everest - it's more informative, see screenshot and ignore the fact that my CPU is running at 70 deg - it is not, Everest is not too keen on my current mobo, but has been fine on all others.
     
  8. 2006/04/25
    Roekemoes

    Roekemoes Inactive Thread Starter

    Joined:
    2006/04/23
    Messages:
    19
    Likes Received:
    0
    Last edited: 2006/04/25
  9. 2006/04/26
    Roekemoes

    Roekemoes Inactive Thread Starter

    Joined:
    2006/04/23
    Messages:
    19
    Likes Received:
    0
    Well I ran the Memtest and I didn't see any problems there.

    I really think it has something to do with the near max temperature of the second harddrive.

    Could this be the issue? Can the system suddenly reboot when a harddrive gets too hot?
     
  10. 2006/04/26
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    I would not think that your hard drive is running excessively hot - hottish, yes. Is this the drive on which you have the Operating system?

    What is of more concern is the Aux temperature shown in Everest. Normally one would expect to see a CPU temperature there - screenshot. If that is indeed the CPU it is running close to it's limit I would guess and most have overtemperature protection. What CPU are you using? - Everest should tell you if you don't know.

    It would be an idea to take the side off the case, blow out all the accumulated dust, clean off the fan blades, ensure that the CPU heat sink is free from dust between the fins, but - do not remove the heat sink.

    Try running the computer without the case side - this will not necessarily reduce temperatures as the case fans can become less effective under these circumstances. Consider running, for a trial period with a domestic fan blowing into the open case.

    FWIW I run a twin fan cooler seated directly on top of my WD hard drive to keep the temperature down to that of the two Hitachi's which are stacked above it.
     
  11. 2006/04/26
    Roekemoes

    Roekemoes Inactive Thread Starter

    Joined:
    2006/04/23
    Messages:
    19
    Likes Received:
    0
    Hi again PeteC,

    I have no clue why it isn't showing Aux instead of CPU, here is some information on the CPU I'm using:
    http://i16.photobucket.com/albums/b27/Roekemoes/CPU2.jpg

    And I actually already did have a fan blowing into the open case but that didn't solve much since it rebooted once while I was doing that.

    I'll try openingen it up and clean it intensively.
    Since English isn't my native language I don't really know what you meant by heat sink but I'll try not to remove it :rolleyes:

    Thanks again and I'll keep you informed
     
  12. 2006/04/26
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    The heat sink is the large block of finned aluminium clamped on top of the CPU with the CPU fan fixed to the top of it. It is safe to remove the fan for cleaning by removing the 4 s crews, one at each corner which also gives you access to clean the fins of the heat sink.
     
  13. 2006/04/26
    Roekemoes

    Roekemoes Inactive Thread Starter

    Joined:
    2006/04/23
    Messages:
    19
    Likes Received:
    0
    Ah thank you, I'll clean everything tonight and see if it reduces the temperature slightly.
    Was the screenshot usefull? Any clue on why it shows Aux?

    Thanks
     
  14. 2006/04/26
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    I was interested to see which CPU you were using so that I could search for an alternative temperature monitor - Everest does not appear to fully recognise the sensor information from your motherboard - I am guessing that Aux is the CPU, but I cannot be sure.
     
  15. 2006/04/27
    Roekemoes

    Roekemoes Inactive Thread Starter

    Joined:
    2006/04/23
    Messages:
    19
    Likes Received:
    0
    I've done intensive cleaning and mounted my 2 harddrives differently inside my box and this lowered the temperatures a bit.

    My harddrives now run at 34 degrees both instead of 45 and 34.
    It didn't reboot once while I had the bot run the whole night so that's a good sign :)
     
  16. 2006/04/27
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    That's an improvement - no problems at 34 degs, but what is the Aux temperature now?
     
  17. 2006/04/27
    Roekemoes

    Roekemoes Inactive Thread Starter

    Joined:
    2006/04/23
    Messages:
    19
    Likes Received:
    0
    The Aux temperature dropped slightly from 68 to 63-64.
    Still not sure it's the CPU? Perhaps it's the powersupply?
     
  18. 2006/04/27
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Possibly - have you felt it? Is it hot and have you checked that the fan is running?
     
  19. 2006/04/27
    Roekemoes

    Roekemoes Inactive Thread Starter

    Joined:
    2006/04/23
    Messages:
    19
    Likes Received:
    0
    This is what I found on the Everest forums:

    Q#18: What does the "Aux" temperature shown on the Computer / Sensor page mean?

    A#18: There is no standard for sensor registers layout, so the "Aux" temperature could show the temperature of the CPU or the motherboard, or might be a non-connected wire of the sensor chip, and so it could show a bogus value.

    The guy starting this topic asked because his Aux was 82c
     
  20. 2006/04/27
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    There is a point I have missed here - your BIOS may well show the CPU temperature. Most modern BIOS's do.
     
  21. 2006/04/27
    Roekemoes

    Roekemoes Inactive Thread Starter

    Joined:
    2006/04/23
    Messages:
    19
    Likes Received:
    0
    Well the information from the BIOS was only showing the system temperature and CPU Fan Speed.

    The system temperature was 33c which is the same as the temperature of the motherboard shown in everest so I'm not guessing the system temperature is the CPU temp.

    The powersupply isn't feeling hot at all so that's not it also.

    The last thing I can think off is the graphiccard?
     

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.