locked
Pc restarts its own. RRS feed

  • Question

  • My pc restarts on its own whenever i am playing games like Assassins creed or smaller like this day mounte & blade.Sometimes it happens while i am watching youtube videos.I have downloaded WhoCrashed and on every restart ntoskerne.exe is the cause of it.Here are two dmp files describing the problem.
    Please help me fix.

    ==================================================
    Dump File         : 120413-13322-01.dmp
    Crash Time        : 4/12/2013 8:55:47 μμ
    Bug Check String  : 
    Bug Check Code    : 0x00000124
    Parameter 1       : 00000000`00000000
    Parameter 2       : fffffa80`05c7a8f8
    Parameter 3       : 00000000`00000000
    Parameter 4       : 00000000`00000000
    Caused By Driver  : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+52ebc9
    File Description  : 
    Product Name      : 
    Company           : 
    File Version      : 
    Processor         : x64
    Crash Address     : ntoskrnl.exe+52ebc9
    Stack Address 1   : 
    Stack Address 2   : 
    Stack Address 3   : 
    Computer Name     : 
    Full Path         : C:\Windows\Minidump\120413-13322-01.dmp
    Processors Count  : 3
    Major Version     : 15
    Minor Version     : 9200
    Dump File Size    : 262.144
    Dump File Time    : 4/12/2013 8:55:50 μμ
    ==================================================
    
    ==================================================
    Dump File         : 120413-12667-01.dmp
    Crash Time        : 4/12/2013 3:24:55 μμ
    Bug Check String  : 
    Bug Check Code    : 0x00000124
    Parameter 1       : 00000000`00000000
    Parameter 2       : fffffa80`05c9a8f8
    Parameter 3       : 00000000`00000000
    Parameter 4       : 00000000`00000000
    Caused By Driver  : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+52ebc9
    File Description  : 
    Product Name      : 
    Company           : 
    File Version      : 
    Processor         : x64
    Crash Address     : ntoskrnl.exe+52ebc9
    Stack Address 1   : 
    Stack Address 2   : 
    Stack Address 3   : 
    Computer Name     : 
    Full Path         : C:\Windows\Minidump\120413-12667-01.dmp
    Processors Count  : 3
    Major Version     : 15
    Minor Version     : 9200
    Dump File Size    : 262.144
    Dump File Time    : 4/12/2013 3:24:58 μμ
    ==================================================
    

    Wednesday, December 4, 2013 7:18 PM

All replies

  • If its crashing automatically, its likely that you have auto restart turned on, first thing you should do is go to control panel->system->advanced system settings->startup and recovery->uncheck automatically restart.What will happen is when the pc crashes, instead of restarting you'll get a bsod, which will contain error codes that can be helpful to resolving the issue. Write these down and post back with them.

    Second check your windows event log. look for a message around unexpected restart and look back in the logs for an error or warning and see what it says.

    Third, check your hardware. Did you recently install or remove a piece of hardware from your pc? Do you have another video card, psu, or motherboard to test with?

    Wednesday, December 4, 2013 8:25 PM
  • Also, get the contents of those dump files, put them in a zip file and put them on rapidshare or skydrive and link that in your post.
    Wednesday, December 4, 2013 9:11 PM
  • Please follow our instructions for finding and uploading the files we need to help you fix your computer.  They can be found here
    If you have any questions about the procedure please ask

    *

    Stop 0x124 is a hardware error
    If you are overclocking try resetting your processor to standard settings and see if that helps.
    If you continue to get BSODs here are some more things you may want to consider.
    This is usually heat related, defective hardware, memory or even processor though it is"possible" that it is driver related (rare).

    Stop 0x124 - what it means and what to try

    Synopsis:
    A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.
    Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.


     Generic "Stop 0x124" Troubleshooting Strategy:

    1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable ways.
    2) Ensure that the machine is adequately cooled.
     If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.
    3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware.
    It is good practice to run the latest drivers anyway.
    4) Update the motherboard BIOS according to the manufacturer's instructions and clear the CMOS.
    Their website should provide detailed instructions as to the brand and model-specific procedure.
    5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug).
    At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.
    6) Attempt to (stress) test those hardware components which can be put through their paces artificially.
    The most obvious examples are the RAM and HDD(s).
    For the RAM, use the 3rd-party memtest86 utility to run many hours worth of testing. (6-8 passes to stress the ram out)
    For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors".
    Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is free from defects - only that none were encountered during the test passes.
    7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications, games, utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc.
    Should that fail to mitigate the 0x124 problem, jump to the next steps.
    If you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether the machine is still free from 0x124 crashes.
    Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
    If stop 0x124 errors persist despite the steps above, and the hardware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events.
    Be aware that attempting the subsequent hardware troubleshooting steps may, in some cases, void your warranty:
    8) Clean and carefully remove any dust from the inside of the machine.
    Reseat all connectors and memory modules.
    Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.
    9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed.
    Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.

    Should you find yourself in the situation of having performed all of the steps above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware.


    Wanikiya and Dyami--Team Zigzag

    Wednesday, December 4, 2013 10:52 PM
  • Hi,

    As the suggestion above, the cause of the pc restart its own is that Windows 7 is set by default to automatically restart the operating system after a system failure. For more Intuitive view, you can refer to the following KB.

    How to resolve automatic restarts problem when Windows 7 experiences an error (Easy Fix Article - Written by MVP)

    http://support.microsoft.com/kb/2621246/en-us

    But regarding the unexpectedly shuts off. Did the pc overheating when the issue happened?

    If yes, dust can be a real issue, especially you need to take care of the laptop fan.

    if you are confident to do it by yourself, just pop open the laptop, or look up how to clean it online. 

    But the best choice is go to a store for cleaning.

    If it is not the issue, please follow the suggestions above to upload the dump files for further help.

    Hope this helps,


    Ada Liu
    TechNet Community Support

    Thursday, December 5, 2013 5:49 AM
  • Here are the files that you requested:
    Minidump:http://rapidshare.com/share/EA576234DC5E5D91D569CC2BDF7C8050
    MSinfo32:http://rapidshare.com/share/57D5FF03683423E7874683E603343B2D
    System Informarion:http://rapidshare.com/share/EB323BB024D57BC60D1DF8A3C00E1F5F
    Thursday, December 5, 2013 9:17 AM
  • Great ill review those as soon as I can. You didn't answer any of my other questions though. Did you see anything in your windows event logs? Did you replace any pieces of hardware recently? Do you have any other hardware to test? Is this a desktop or a laptop?

    Thursday, December 5, 2013 6:22 PM
  • This must be very ipmportant.
    Its an warning status event that is associated with kernel.
    ==================================================
    Record Number     : 10834
    Log Type          : System
    Event Type        : Warning
    Time              : 5/12/2013 6:09:50 μμ
    Source            : Microsoft-Windows-Kernel-PnP
    Category          : 212
    Event ID          : 219
    User Name         : SYSTEM
    Computer          : Simiskos
    Event Data Length : 0
    Record Length     : 460
    Event Description : 
    ==================================================
    117
    WpdBusEnumRoot\UMB\2&37c186b&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_GENERIC&PROD_USB_SM_READER&REV_1.02#058F312D81B&2#
    3221226341
    14
    \Driver\WudfRd
    0
    .

    This event seems to happened 4 minutes after my crash.
    Thursday, December 5, 2013 8:37 PM
  • These happen just when the crash occurs.

    ==================================================
    Record Number     : 10649
    Log Type          : System
    Event Type        : Information
    Time              : 5/12/2013 1:11:01 μμ
    Source            : Microsoft-Windows-FilterManager
    Category          : 0
    Event ID          : 6
    User Name         : SYSTEM
    Computer          : Simiskos
    Event Data Length : 0
    Record Length     : 260
    Event Description : 0x0
    6
    0
    6
    aswSnx
    2013-11-06T14:37:52.000000000Z

    ==================================================

    ==================================================
    Record Number     : 10648
    Log Type          : System
    Event Type        : Error
    Time              : 5/12/2013 1:11:01 μμ
    Source            : Microsoft-Windows-Kernel-General
    Category          : 0
    Event ID          : 6
    User Name         : SYSTEM
    Computer          : Simiskos
    Event Data Length : 0
    Record Length     : 192
    Event Description : 0xc000014d
    0

    ==================================================

    ==================================================
    Record Number     : 10647
    Log Type          : System
    Event Type        : Information
    Time              : 5/12/2013 1:11:01 μμ
    Source            : Microsoft-Windows-Ntfs
    Category          : 0
    Event ID          : 98
    User Name         : SYSTEM
    Computer          : Simiskos
    Event Data Length : 0
    Record Length     : 196
    Event Description : C:
    \Device\HarddiskVolume2
    0

    ==================================================
    Thursday, December 5, 2013 9:34 PM
  • Simiskos

    Information and warnings are not particularly important the errors and critical errors are.  Did you do any of the 124 troubleshooting?


    Wanikiya and Dyami--Team Zigzag

    Friday, December 6, 2013 2:14 AM