Questions

pc shut down w/o notice

Tags:
+
0 Votes
Locked

pc shut down w/o notice

eltonpiko
hi hope one of you guys can help me out ive got a pc lga775 p4-3.0ghz ,512mb-ddr2 ,80gb-hd ,brand new powersupply, new motherboard,new ram runnig xp pro sp3 just installed. the problem is that it sudenly shutdown & restart without notice after 2 to 3 hour after turn on.iv monitor temp to see if cpu is not heating up but its working fine + i dont tink its a virus problem.by the way can the new ms sp3 cause this kind of problem?
tanx hope some can help.
  • +
    0 Votes
    ThumbsUp2

    It could very well be the power supply or an external video card that's overheating. Maybe weak RAM. Maybe components of the motherboard itself.

    What are you using to monitor the CPU for 2 to 3 hours? How do you know that it's not overheating? What do you consider normal?

    When this happens, are you running any particular program (or combination of programs) that might be stressing the computer, like a game online (ie: using the video and the NIC at same time)? Can you pin down anything at all that is always present when the shutdown comes? Problems like this are often hard to diagnose without being there.

    No, SP3 won't cause a shut down after 2 to 3 hours of running.

    +
    0 Votes
    eltonpiko

    remember iv just purchase the new motherboard ,psu,ram 1 week ago ist hard to tink these could be faulty.

    im using hardware sensors monitor to monitor the temp.and my cpu temp stay in the zone 45 to 50 degree no more than that. and i guess thats the normal temp unless the software is not good and giving me wrong resaults.

    no im not running any particular when this happens.no combine programs or game have i install only regular ones like office divx player.and im using the onboard graphics with the pc no extra divices.

    +
    0 Votes
    OH Smeg

    Quite often when you insert things into a Computer case you get Hot Zones and are not properly cooled down. When this happens things overheat and force a shut down, or if you have enabled Alarms in BIOS and have nothing connected to the Fan Take Offs they can cause a shut down through incorrect Voltages or no measurable voltage for the Fan Speed.

    If you look in BIOS you should see more than just the CPU Temp it could be one of those that is getting too hot and forcing the shutdown.

    Without knowing more about the actual computer this is very hard to identify and is part of the reason why there are Heat Sinks on parts of the M'Board not related to the CPU. Heat Sinks are also available for RAM as that can overheat while still working perfectly. It's not so much a matter of faulty parts as the complete unit not being correctly cooled or having enough cooling available to it. A good White Box computer should outlast a Brand Name computer by a factor of 2 and this is mainly due to better cooling.

    I can mount Hard Drives in such a manner that they do not get hot at all as they are sitting right behind a 120 MM Fan constantly blowing cool air on them all the time that the computer is running.

    You should suck air in at the front of a case and **** it out the back to maintain a decent Air Flow through the case.

    Col

    +
    0 Votes
    eltonpiko

    well ive got the main cpu fan and one infront pushing fresh air infront of my hd driver and one at he back sucking hot air out of the case both are conected directly on my power supply not on the motherboard.

    il try changing the ram with a better one to see if its any good.

    if it was the case of an incorect voltage or no measuring voltage for the fan in bios like you sugesed wloud it wait 3hour to find out the these ting are not correct and shut down?

    il try the few thing then il let you know if it helped. tanx

    +
    0 Votes
    OH Smeg

    You can get one here

    http://tinyurl.com/23nmq

    Download it and make a CD then boot off the CD and let the unit run for several hours to see what if anything actually happens. If nothing happens and no restarts then you can be fairly certain it is something within Windows but if it continues to reboot you should look at your Hardware first.

    Just to be on the safe side go to a Newsagent and buy a Linux Mag with a Live Linux on the Cover Disc that will remove any possibility that something on your system will affect a Linux that you have burnt to CD to be absolutely certain.

    Col

    +
    0 Votes
    nepenthe0

    http://www.gtopala.com/

    It will display processor and hard drive temperatures.

    Rick/Portland, OR

    +
    0 Votes
    Jacky Howe

    My Computer, Properties, Advanced, Startup and Recovery and untick Automatically restart. While you are there make sure that Small memory dump (64 KB) is selected and the output is %SystemRoot%\Minidump. The Blue Screen will dump the Minidump file.

    This will Blue Screen the PC. Take note of Stop 0X000000 error message and post it.

    Or if you are feeling adventurous

    Minidump Files can be found here. C:\WINDOWS\Minidump\Mini122707-02.dmp

    How to read the small memory dump files that Windows creates for debugging
    http://support.microsoft.com/kb/315263

    To download and install the Windows debugging tools, visit the following Microsoft Web site:
    http://www.microsoft.com/whdc/devtools/debugging/default.mspx

    Instructions on using Windbg.

    Open Windbg and select file, Symbol file path and brows to the Symbol folder that you have downloaded and installed Symbols to, select OK.
    Close the workpage and save the Workspace information. This should lock in the Symbol path.
    Open Windbg and select file and select Open Crash Dump then navigate to the minidump, highlight it and select Open.
    There are two ways to use !analyze -v the easiest is to click on !analyze -v under Bugcheck Analysis.
    When you have ran the initial dump if you look to the bottom of the screen you will see kd> to the right of that type in !analyze -v and press the Enter key.
    Ctrl + a will let you copy the information and paste it into notepad.

    Look to the bottom of the page for information like this. This was fixed by updating the Graphics Drivers.
    FAULTING_THREAD: 864f6a98

    DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

    CUSTOMER_CRASH_COUNT: 1

    BUGCHECK_STR: 0xEA

    PROCESS_NAME: logon.scr

    LAST_CONTROL_TRANSFER: from 00000000 to bfef0fea

    STACK_TEXT:
    f6434e6c 00000000 00000000 00000000 00000000 sgiul50!DrvBitBlt+0x585


    STACK_COMMAND: .thread 0xffffffff864f6a98 ; kb

    FOLLOWUP_IP:
    sgiul50!DrvBitBlt+585
    bfef0fea 75f9 jne sgiul50!DrvBitBlt+0x580 (bfef0fe5)

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: sgiul50!DrvBitBlt+585

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: sgiul50

    IMAGE_NAME: sgiul50.dll

    DEBUG_FLR_IMAGE_TIMESTAMP: 3b7dfec7

    FAILURE_BUCKET_ID: 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18

    BUCKET_ID: 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18

    +
    0 Votes
    nepenthe0

    I never noticed this option in the System menu before. Does this do the same thing as the Safe Mode option?

    Disable automatic restart on system failure

    If so, there's no reason to reboot into Safe Mode if one can set this switch within the System menu.

    Rick/Portland, OR

    P.S. - As I have said before, I learn something new from you every day. Thanks, my friend...

    +
    0 Votes

    You

    Jacky Howe

    only need to do it in Safe Mode if you can't access it in Normal Mode. It is a feature that I set on all PC's that I put together for clients. They can then E-Mail me the minidumps or the Stop Error: and I can go from there.

    +
    0 Votes
    eltonpiko

    ok i follow the step you sugessed i got a blue screen i went to the minidump folder there was four files i use the windbg to open it here are the result i got for each file

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


    Loading Dump File [C:\Documents and Settings\elton\Desktop\Minidump\Mini060808-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: C:\WINDOWS\Symbols
    Executable search path is:
    Unable to load image ntoskrnl.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Sun Jun 8 23:48:10.531 2008 (GMT-7)
    System Uptime: 0 days 1:47:26.204
    Unable to load image ntoskrnl.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Loading Kernel Symbols
    .............................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ...........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000000A, {c0000005, ff, 1, 80545846}

    Probably caused by : memory_corruption ( nt!MiAddValidPageToWorkingSet+46c )

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

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


    Loading Dump File [C:\Documents and Settings\elton\Desktop\Minidump\Mini060908-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: C:\WINDOWS\Symbols
    Executable search path is:
    Unable to load image ntoskrnl.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Mon Jun 9 20:47:48.593 2008 (GMT-7)
    System Uptime: 0 days 2:40:19.266
    Unable to load image ntoskrnl.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Loading Kernel Symbols
    .............................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ..........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000007F, {8, f78b4d70, 0, 0}

    Probably caused by : Unknown_Image

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

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


    Loading Dump File [C:\Documents and Settings\elton\Desktop\Minidump\Mini060908-02.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: C:\WINDOWS\Symbols
    Executable search path is:
    Unable to load image ntoskrnl.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Mon Jun 9 22:32:29.890 2008 (GMT-7)
    System Uptime: 0 days 0:42:53.562
    Unable to load image ntoskrnl.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Loading Kernel Symbols
    .............................................................................................................
    Loading User Symbols
    Loading unloaded module list
    .........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000007F, {8, f78b4d70, 0, 0}

    Probably caused by : Unknown_Image

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

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


    Loading Dump File [C:\Documents and Settings\elton\Desktop\Minidump\Mini061008-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: C:\WINDOWS\Symbols
    Executable search path is:
    Unable to load image ntoskrnl.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Tue Jun 10 17:24:23.593 2008 (GMT-7)
    System Uptime: 0 days 2:43:02.268
    Unable to load image ntoskrnl.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Loading Kernel Symbols
    ..................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    .........
    Unable to load image vinyl97.sys, Win32 error 2
    *** WARNING: Unable to verify timestamp for vinyl97.sys
    *** ERROR: Module load completed but symbols could not be loaded for vinyl97.sys
    Unable to load image kmixer.sys, Win32 error 2
    *** WARNING: Unable to verify timestamp for kmixer.sys
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000007F, {8, f78b4d70, 0, 0}

    Probably caused by : vinyl97.sys ( vinyl97+1e470 )

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

    +
    0 Votes
    Jacky Howe

    vinyl97.sys is is an audio driver.

    Update your Audio Drivers.

    +
    0 Votes
    jdmercha

    It has been my experience that a computer that overheats will shut down, it will not reboot.

    I have seen a viruse that will reboot the computer every 2 to 3 hours, and it was not detected by the local virus scanner.

    Go to the Trend Micro web site and run their free scan. Hopefully it will complete the scan before your computer shuts down. (I've had that problem too.)

    Then try booting to a CD. If you have a copy of Barts, that would be best, but the Windows CD will work too. Does the system still reboot?

    Open up the PC and point a room fan right at it. Does it still reboot?

  • +
    0 Votes
    ThumbsUp2

    It could very well be the power supply or an external video card that's overheating. Maybe weak RAM. Maybe components of the motherboard itself.

    What are you using to monitor the CPU for 2 to 3 hours? How do you know that it's not overheating? What do you consider normal?

    When this happens, are you running any particular program (or combination of programs) that might be stressing the computer, like a game online (ie: using the video and the NIC at same time)? Can you pin down anything at all that is always present when the shutdown comes? Problems like this are often hard to diagnose without being there.

    No, SP3 won't cause a shut down after 2 to 3 hours of running.

    +
    0 Votes
    eltonpiko

    remember iv just purchase the new motherboard ,psu,ram 1 week ago ist hard to tink these could be faulty.

    im using hardware sensors monitor to monitor the temp.and my cpu temp stay in the zone 45 to 50 degree no more than that. and i guess thats the normal temp unless the software is not good and giving me wrong resaults.

    no im not running any particular when this happens.no combine programs or game have i install only regular ones like office divx player.and im using the onboard graphics with the pc no extra divices.

    +
    0 Votes
    OH Smeg

    Quite often when you insert things into a Computer case you get Hot Zones and are not properly cooled down. When this happens things overheat and force a shut down, or if you have enabled Alarms in BIOS and have nothing connected to the Fan Take Offs they can cause a shut down through incorrect Voltages or no measurable voltage for the Fan Speed.

    If you look in BIOS you should see more than just the CPU Temp it could be one of those that is getting too hot and forcing the shutdown.

    Without knowing more about the actual computer this is very hard to identify and is part of the reason why there are Heat Sinks on parts of the M'Board not related to the CPU. Heat Sinks are also available for RAM as that can overheat while still working perfectly. It's not so much a matter of faulty parts as the complete unit not being correctly cooled or having enough cooling available to it. A good White Box computer should outlast a Brand Name computer by a factor of 2 and this is mainly due to better cooling.

    I can mount Hard Drives in such a manner that they do not get hot at all as they are sitting right behind a 120 MM Fan constantly blowing cool air on them all the time that the computer is running.

    You should suck air in at the front of a case and **** it out the back to maintain a decent Air Flow through the case.

    Col

    +
    0 Votes
    eltonpiko

    well ive got the main cpu fan and one infront pushing fresh air infront of my hd driver and one at he back sucking hot air out of the case both are conected directly on my power supply not on the motherboard.

    il try changing the ram with a better one to see if its any good.

    if it was the case of an incorect voltage or no measuring voltage for the fan in bios like you sugesed wloud it wait 3hour to find out the these ting are not correct and shut down?

    il try the few thing then il let you know if it helped. tanx

    +
    0 Votes
    OH Smeg

    You can get one here

    http://tinyurl.com/23nmq

    Download it and make a CD then boot off the CD and let the unit run for several hours to see what if anything actually happens. If nothing happens and no restarts then you can be fairly certain it is something within Windows but if it continues to reboot you should look at your Hardware first.

    Just to be on the safe side go to a Newsagent and buy a Linux Mag with a Live Linux on the Cover Disc that will remove any possibility that something on your system will affect a Linux that you have burnt to CD to be absolutely certain.

    Col

    +
    0 Votes
    nepenthe0

    http://www.gtopala.com/

    It will display processor and hard drive temperatures.

    Rick/Portland, OR

    +
    0 Votes
    Jacky Howe

    My Computer, Properties, Advanced, Startup and Recovery and untick Automatically restart. While you are there make sure that Small memory dump (64 KB) is selected and the output is %SystemRoot%\Minidump. The Blue Screen will dump the Minidump file.

    This will Blue Screen the PC. Take note of Stop 0X000000 error message and post it.

    Or if you are feeling adventurous

    Minidump Files can be found here. C:\WINDOWS\Minidump\Mini122707-02.dmp

    How to read the small memory dump files that Windows creates for debugging
    http://support.microsoft.com/kb/315263

    To download and install the Windows debugging tools, visit the following Microsoft Web site:
    http://www.microsoft.com/whdc/devtools/debugging/default.mspx

    Instructions on using Windbg.

    Open Windbg and select file, Symbol file path and brows to the Symbol folder that you have downloaded and installed Symbols to, select OK.
    Close the workpage and save the Workspace information. This should lock in the Symbol path.
    Open Windbg and select file and select Open Crash Dump then navigate to the minidump, highlight it and select Open.
    There are two ways to use !analyze -v the easiest is to click on !analyze -v under Bugcheck Analysis.
    When you have ran the initial dump if you look to the bottom of the screen you will see kd> to the right of that type in !analyze -v and press the Enter key.
    Ctrl + a will let you copy the information and paste it into notepad.

    Look to the bottom of the page for information like this. This was fixed by updating the Graphics Drivers.
    FAULTING_THREAD: 864f6a98

    DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

    CUSTOMER_CRASH_COUNT: 1

    BUGCHECK_STR: 0xEA

    PROCESS_NAME: logon.scr

    LAST_CONTROL_TRANSFER: from 00000000 to bfef0fea

    STACK_TEXT:
    f6434e6c 00000000 00000000 00000000 00000000 sgiul50!DrvBitBlt+0x585


    STACK_COMMAND: .thread 0xffffffff864f6a98 ; kb

    FOLLOWUP_IP:
    sgiul50!DrvBitBlt+585
    bfef0fea 75f9 jne sgiul50!DrvBitBlt+0x580 (bfef0fe5)

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: sgiul50!DrvBitBlt+585

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: sgiul50

    IMAGE_NAME: sgiul50.dll

    DEBUG_FLR_IMAGE_TIMESTAMP: 3b7dfec7

    FAILURE_BUCKET_ID: 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18

    BUCKET_ID: 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18

    +
    0 Votes
    nepenthe0

    I never noticed this option in the System menu before. Does this do the same thing as the Safe Mode option?

    Disable automatic restart on system failure

    If so, there's no reason to reboot into Safe Mode if one can set this switch within the System menu.

    Rick/Portland, OR

    P.S. - As I have said before, I learn something new from you every day. Thanks, my friend...

    +
    0 Votes

    You

    Jacky Howe

    only need to do it in Safe Mode if you can't access it in Normal Mode. It is a feature that I set on all PC's that I put together for clients. They can then E-Mail me the minidumps or the Stop Error: and I can go from there.

    +
    0 Votes
    eltonpiko

    ok i follow the step you sugessed i got a blue screen i went to the minidump folder there was four files i use the windbg to open it here are the result i got for each file

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


    Loading Dump File [C:\Documents and Settings\elton\Desktop\Minidump\Mini060808-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: C:\WINDOWS\Symbols
    Executable search path is:
    Unable to load image ntoskrnl.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Sun Jun 8 23:48:10.531 2008 (GMT-7)
    System Uptime: 0 days 1:47:26.204
    Unable to load image ntoskrnl.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Loading Kernel Symbols
    .............................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ...........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000000A, {c0000005, ff, 1, 80545846}

    Probably caused by : memory_corruption ( nt!MiAddValidPageToWorkingSet+46c )

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

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


    Loading Dump File [C:\Documents and Settings\elton\Desktop\Minidump\Mini060908-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: C:\WINDOWS\Symbols
    Executable search path is:
    Unable to load image ntoskrnl.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Mon Jun 9 20:47:48.593 2008 (GMT-7)
    System Uptime: 0 days 2:40:19.266
    Unable to load image ntoskrnl.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Loading Kernel Symbols
    .............................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ..........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000007F, {8, f78b4d70, 0, 0}

    Probably caused by : Unknown_Image

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

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


    Loading Dump File [C:\Documents and Settings\elton\Desktop\Minidump\Mini060908-02.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: C:\WINDOWS\Symbols
    Executable search path is:
    Unable to load image ntoskrnl.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Mon Jun 9 22:32:29.890 2008 (GMT-7)
    System Uptime: 0 days 0:42:53.562
    Unable to load image ntoskrnl.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Loading Kernel Symbols
    .............................................................................................................
    Loading User Symbols
    Loading unloaded module list
    .........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000007F, {8, f78b4d70, 0, 0}

    Probably caused by : Unknown_Image

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

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


    Loading Dump File [C:\Documents and Settings\elton\Desktop\Minidump\Mini061008-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: C:\WINDOWS\Symbols
    Executable search path is:
    Unable to load image ntoskrnl.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Tue Jun 10 17:24:23.593 2008 (GMT-7)
    System Uptime: 0 days 2:43:02.268
    Unable to load image ntoskrnl.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Loading Kernel Symbols
    ..................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    .........
    Unable to load image vinyl97.sys, Win32 error 2
    *** WARNING: Unable to verify timestamp for vinyl97.sys
    *** ERROR: Module load completed but symbols could not be loaded for vinyl97.sys
    Unable to load image kmixer.sys, Win32 error 2
    *** WARNING: Unable to verify timestamp for kmixer.sys
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000007F, {8, f78b4d70, 0, 0}

    Probably caused by : vinyl97.sys ( vinyl97+1e470 )

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

    +
    0 Votes
    Jacky Howe

    vinyl97.sys is is an audio driver.

    Update your Audio Drivers.

    +
    0 Votes
    jdmercha

    It has been my experience that a computer that overheats will shut down, it will not reboot.

    I have seen a viruse that will reboot the computer every 2 to 3 hours, and it was not detected by the local virus scanner.

    Go to the Trend Micro web site and run their free scan. Hopefully it will complete the scan before your computer shuts down. (I've had that problem too.)

    Then try booting to a CD. If you have a copy of Barts, that would be best, but the Windows CD will work too. Does the system still reboot?

    Open up the PC and point a room fan right at it. Does it still reboot?