1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Computer restarting instead of shutting down - running windows 8 pro

Discussion in 'Software' started by matthew1404, Dec 2, 2012.

  1. matthew1404

    matthew1404 New Member

    2
    0
    1
    Hi

    I have a HP Touchsmart 520 running Windows 8 Professional. When I choose shutdown, the computer intermittently reboots instead of shutting down. When I log onto the computer, I receive a message saying windows encountered a problem.

    I have installed all up-to-date drivers and done windows updates, however this issue is still happening.

    Please find the dmp file attached...hopefully this helps

    Thanks
     

    Attached Files:

  2. wagnerk
    Highly Decorated Member Award

    wagnerk aka kitkatninja Moderator

    10,831
    357
    341
    Hi Matthew,

    I would strongly recommend introducing yourself here on the forums first of all and contribute before asking if anyone will download a zip file from someone who has only posted 1 thing here.

    Just a security precaution.

    -Ken
     
    Certifications: CITP, PGCert, BSc, HNC, LCGI, PTLLS, MCT, MCITP, MCTS, MCSE, MCSA:M, MCSA, MCDST, MCP, MTA, MCAS, MOS (Master), A+, N+, S+, ACA, VCA, etc... & 2nd Degree Black Belt
    WIP: PGDip
  3. ade1982

    ade1982 Megabyte Poster Forum Leader

    566
    12
    52
    what happens if you run "shutdown -s"
     
  4. dmarsh

    dmarsh Terabyte Poster

    3,782
    302
    184
    Is it a 32 bit or 64 bit install of the OS ?

    Why don't you try debugging it yourself using WinDbg and Microsoft symbol server ?

    Clint Boessen's Blog: How to Analyse a Dump File

    This is what I got :-

    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    SESSION_HAS_VALID_POOL_ON_EXIT (ab)
    Caused by a session driver not freeing its pool allocations prior to a
    session unload. This indicates a bug in win32k.sys, atmfd.dll,
    rdpdd.dll or a video driver.
    Arguments:
    Arg1: 0000000000000001, session ID
    Arg2: 0000000000000220, number of paged pool bytes that are leaking
    Arg3: 0000000000000000, number of nonpaged pool bytes that are leaking
    Arg4: 0000000000000002, total number of paged and nonpaged allocations that are leaking.
    nonpaged allocations are in the upper half of this word,
    paged allocations are in the lower half of this word.

    Debugging Details:
    ------------------


    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xAB

    PROCESS_NAME: csrss.exe

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from fffff80125676c2a to fffff801250f1d40

    STACK_TEXT:
    fffff880`19245ab8 fffff801`25676c2a : 00000000`000000ab 00000000`00000001 00000000`00000220 00000000`00000000 : nt!KeBugCheckEx
    fffff880`19245ac0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x3619a


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt! ?? ::NNGAKEGL::`string'+3619a
    fffff801`25676c2a cc int 3

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt! ?? ::NNGAKEGL::`string'+3619a

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 5063f8c8

    FAILURE_BUCKET_ID: X64_0xAB_nt!_??_::NNGAKEGL::_string_+3619a

    BUCKET_ID: X64_0xAB_nt!_??_::NNGAKEGL::_string_+3619a

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

    1. Have you updated your video drivers ?
    2. Do you have any devices with issues in Device Manager ?
    3. Have you tried running a memory test ?
    www.memtest.org
    4. Try using microsofts DriverVerifier.
    5. Manually check all drivers and look for new versions on manufacturer websites, Windows Update and WHQL drivers aren't always the best drivers for your hardware.
    6. Consider allocating a page file at least as big as your physical memory and switching from a mini-dump to a full dump so that next time you can debug properly. Also disable automatically reboot on kernel crash in windows, this way you can read the blue screen of death.
     
    Last edited: Dec 2, 2012
    Certifications: CITP, BSc, HND, SCJP, SCJD, SCWCD, SCBCD, SCEA, N+, Sec+, Proj+, Server+, Linux+, MCTS, MCPD, MCSA, MCITP, CCDH
  5. shadowwebs

    shadowwebs Megabyte Poster Forum Leader

    841
    10
    76
    I am not familiar with Windows 8 at this moment in time... have you tried looking at the event log to see what may have flagged up the cause?

    The event log should always be the first place to look as should be mentioned what caused it and then you can go from there.
     
    Certifications: compTIA A+, Apple Certified Technical Coordinator 10.10 (OS X Yosemite, Server and Support)

Share This Page

Loading...