- HP Support Forum Home
- >
- Laptop & Notebook
- >
- Lockups/Freezes
- >
- Re: Laptop will not turn off
HP Support Forums
Join in the conversation.
- Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
Laptop will not turn off
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
01-10-2011 05:37 AM
I have a HP Pravilion dv5 and have only had it since Christmas. Just recently when I go to shut down it will not. I can use sleep,hibernate and all the other options but will not go to shutdown. Any suggestions?
Solved! Go to Solution.
Re: Laptop will not turn off
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
01-10-2011 08:03 AM
Do you have any USB devices attached?
http://support.microsoft.com/kb/315664
________________________________________________________________________________________________________
Re: Laptop will not turn off
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
01-11-2011 01:27 PM
No USB, I went in and hit restore and that took care of the problem, just not sure what cased it to start with. Thanks
Re: Laptop will not turn off
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
01-11-2011 02:30 PM
I just Purchased 2 TouchSmart TM2T-2150 Tablets. One of then has an issue not shutting down. I get a Blue Screen error. The Dump Report Says:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\011111-37377-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. **
Executable search path is:
* Symbols can not be loaded because symbol path is not initialized.
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0321d000 PsLoadedModuleList = 0xfffff800`0345ae50
Debug session time: Tue Jan 11 16:09:29.640 2011 (UTC - 6:00)
System Uptime: 0 days 1:10:50.170
* Symbols can not be loaded because symbol path is not initialized. *
*
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 1000009F, {4, 258, fffffa80041a4b60, fffff80005da0510}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** Your debugger is not using the correct symbols ***
***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work.
***
*** Type referenced: nt!_ETHREAD ***
*** Your debugger is not using the correct symbols ***
***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work.
***
*** Type referenced: nt!_ETHREAD ***
*** Your debugger is not using the correct symbols ***
***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work.
***
*** Type referenced: nt!_TRIAGE_9F_PNP ***
*** Your debugger is not using the correct symbols ***
***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work.
***
*** Type referenced: nt!_TRIAGE_PNP_DEVICE_COMPLETION_QUEUE
*** Your debugger is not using the correct symbols ***
***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work.
***
*** Type referenced: nt!_TRIAGE_PNP_DEVICE_COMPLETION_REQUEST
*** Your debugger is not using the correct symbols ***
***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work.
***
*** Type referenced: nt!_KPRCB ***
*** Your debugger is not using the correct symbols ***
***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work.
***
*** Type referenced: nt!KPRCB ***
*** Your debugger is not using the correct symbols ***
***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work.
***
*** Type referenced: nt!_KPRCB ***
*** Your debugger is not using the correct symbols ***
***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work.
***
*** Type referenced: nt!KPRCB ***
*** Your debugger is not using the correct symbols ***
***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work.
***
*** Type referenced: nt!_KPRCB ***
*** Your debugger is not using the correct symbols ***
***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work.
***
*** Type referenced: nt!_KPRCB ***
*** Your debugger is not using the correct symbols ***
***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work.
***
*** Type referenced: nt!_KPRCB ***
*** Your debugger is not using the correct symbols ***
***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work.
***
*** Type referenced: nt!_KPRCB ***
***
**************************************************
Probably caused by : ntoskrnl.exe ( nt+765da )
Followup: MachineOwner
---------
this happend whether or not I have USB devices attahced.
