The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Unexpected Shut Down

    Discussion in 'Windows OS and Software' started by Anggrian, Oct 5, 2010.

  1. Anggrian

    Anggrian Notebook Evangelist

    Reputations:
    0
    Messages:
    341
    Likes Received:
    0
    Trophy Points:
    30
    I left my notebook for dinner and when I get back after 30 minutes, it is already shutted down without any explanation. the Online Solution Check from windows could not find any problem so I ran WhoCrash software that detect crash and this is the result:

    Analysis
    --------------------------------------------------------------------------------

    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.


    On Tue 10/5/2010 12:41:18 PM your computer crashed
    This was likely caused by the following module: ntoskrnl.exe
    Bugcheck code: 0x9F (0x3, 0xFFFFFA80049DDA20, 0xFFFFF80000B9C518, 0xFFFFFA8008BEE6B0)
    Error: DRIVER_POWER_STATE_FAILURE
    Dump file: C:\Windows\Minidump\100510-25209-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.




    --------------------------------------------------------------------------------
    Conclusion
    --------------------------------------------------------------------------------

    1 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.





    I don't know what are the ntoskrnl.exe is and I don't even understand the conclusion. does anyone can help me with this please? :) hope this is not a big deal
     
    Anggrian, Oct 5, 2010
    #1
  2. mujtaba

    mujtaba ZzzZzz Super Moderator

    Reputations:
    4,242
    Messages:
    3,088
    Likes Received:
    500
    Trophy Points:
    151
    ntoskrnl.exe is the heart of Windows NT, the main executable module loaded in the kernel mode.

    Now it is either the fact that you have triggered a bug inside Windows (Microsoft thoroughly test their stuff) or a driver broke something and made ntoskrnl.exe cause the crash, I would start by updating the drivers, maybe that would fix the crash?
     
    mujtaba, Oct 5, 2010
    #2
  3. Anggrian

    Anggrian Notebook Evangelist

    Reputations:
    0
    Messages:
    341
    Likes Received:
    0
    Trophy Points:
    30
    wow I guess that's heavy.. fine I'll update my drivers
    thanks :D
     
    Anggrian, Oct 6, 2010
    #3