Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

bsod help me please


  • Please log in to reply

#1
John Lauhoff

John Lauhoff

    Member

  • Member
  • PipPipPip
  • 104 posts
==================================================
Filename : ntoskrnl.exe
Address In Stack : ntoskrnl.exe+682ee
From Address : fffff800`02e50000
To Address : fffff800`0342c000
Size : 0x005dc000
Time Stamp : 0x4e02aa44
Time String : 6/22/2011 9:51:48 PM
Product Name : Microsoft® Windows® Operating System
File Description : NT Kernel & System
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Company : Microsoft Corporation
Full Path : C:\Windows\system32\ntoskrnl.exe
==================================================
and the other


==================================================
Dump File : 050112-34913-01.dmp
Crash Time : 5/1/2012 12:07:41 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+4533f
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+70590
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\050112-34913-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 7600
Dump File Size : 275,976
==================================================
another lol
==================================================
Dump File : 043012-28329-01.dmp
Crash Time : 4/30/2012 8:18:14 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`02ec33bc
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\043012-28329-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 7600
Dump File Size : 280,288
==================================================

Edited by John Lauhoff, 01 May 2012 - 06:01 PM.

  • 0

Advertisements


#2
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts

0x0000000A: IRQL_NOT_LESS_OR_EQUAL
(Click to consult the online MSDN article.)
Typically due to a bad driver, or faulty or incompatible hardware or software. Use the General Troubleshooting of STOP Messages checklist above. Technically, this error condition means that a kernel-mode process or driver tried to access a memory location to which it did not have permission, or at a kernel Interrupt ReQuest Level (IRQL) that was too high. (A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own.)



0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
(Click to consult the online MSDN article.)
The Windows kernel detected an illegal or unknown processor instruction. A Stop 0x1E condition can be caused by invalid memory and access violations similar to those that generate Stop 0xA errors. This default Windows error handler typically intercepts these problems if error-handling routines are not present in the code itself.



Did you recently update any drivers in your system?
  • 0

#3
John Lauhoff

John Lauhoff

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 104 posts
updated my graphics card but that was after idk what else i could have updated
  • 0

#4
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK are the BSOD's happening before windows boots up or after you are in windows?
  • 0

#5
John Lauhoff

John Lauhoff

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 104 posts
just random i can be playing a game most time nothing but my gf on you tube or browsing web and it does it just out of nowhere
  • 0

#6
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK then we need to check some things so please be patient. Below are two different tests I would like you to run if you would please.





Tutorial for running chkdsk in Vista\Win 7 located HERE.





A If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...


1. Download - Pre-Compiled Bootable ISO (.zip). If you prefer to use the USB version then use this link USB KEY
2. Unzip downloaded /memtest86+-4.20.iso.zip file.
3. Inside, you'll find /memtest86+-4.20.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:

Posted Image

8. Locate memtest86+-4.20.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:

Posted Image

10. Once the CD is created, boot from it, and memtest will automatically start to run. You may have to change the boot sequence in your BIOS to make it work right.

To change Boot Sequence in your BIOS

Reboot the system and at the first post screen (where it is counting up memory) start tapping the DEL button
This will enter you into the Bios\Cmos area.
Find the Advanced area and click Enter
Look for Boot Sequence or Boot Options and highlight that click Enter
Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
Change the second drive to the C or Main Drive
Once that is done then click F10 to Save and Exit
You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.


The running program will look something like this depending on the size and number of ram modules installed:


Posted Image

It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.

Posted Image

The following image is the test results area:

Posted Image

The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.
  • 0

#7
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
John Lauhoff

I have edited your post regarding this, on an existing topic by another member, on the link

http://www.geekstogo...__fromsearch__1

I have indicated on that other post the reason for the edit, but have also posted here, so that you are aware.
  • 0

#8
John Lauhoff

John Lauhoff

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 104 posts
i ran test had repair some windows files my memory test had no errors and my hdd test were fine i was playing a game and blue screened a diff one post it below thnx

==================================================
Dump File : 050312-23852-01.dmp
Crash Time : 5/3/2012 1:45:22 PM
Bug Check String : TIMER_OR_DPC_INVALID
Bug Check Code : 0x000000c7
Parameter 1 : 00000000`00000004
Parameter 2 : fffff800`00000000
Parameter 3 : 00000000`00000001
Parameter 4 : 00000000`ffffffff
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\050312-23852-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 7601
Dump File Size : 275,976
==================================================
  • 0

#9
John Lauhoff

John Lauhoff

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 104 posts
i didnt try running with just one stick of ram or swapping them out i have two 4g sticks in it
  • 0

#10
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts

0x000000C7: TIMER_OR_DPC_INVALID
(Click to consult the online MSDN article.)
A kernel timer or Delayed Procedure Call (DPC) was found somewhere in memory where it is not permitted. This is usually caused by a driver’s failure to cancel the timer or the DPC before freeing the memory in which the timer or DPC resides.


Run the memtest86 program on all 4 sticks together. That will tell you if there is even a issue with the memory at all and is quicker then option A. The last bug check suggest a driver issue could be the problem.
Did you recently update any drivers?
  • 0

Advertisements


#11
John Lauhoff

John Lauhoff

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 104 posts
i updated my graphics card installed a wireless keyboard but ill run the mem test . is there a way to find the bad driver sorry im a noob lol
  • 0

#12
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
Whileyou wait for my good colleague rshaffer61 to return to you, please post the chkdsk log.

Sorry - rshaffer61 - leave it with you see you have returned

i ran test had repair some windows files my memory test had no errors and my hdd test were fine


I wonder to which test the repair refers - ?
  • 0

#13
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Yes you can boot into windows and do the following.



Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.

Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply

http://www.resplendence.com/downloads


I would guess the video driver is the culprit but the above should tell us for sure.
  • 0

#14
John Lauhoff

John Lauhoff

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 104 posts
45 crash dumps have been found and analyzed. Only 15 are included in this report. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)

rt64win7.sys (Realtek 8101E/8168/8169 NDIS 6.20 64-bit Driver , Realtek Corporation )

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
  • 0

#15
John Lauhoff

John Lauhoff

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 104 posts
On Thu 5/3/2012 6:43:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050312-23852-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xC7 (0x4, 0xFFFFF80000000000, 0x1, 0xFFFFFFFF)
Error: TIMER_OR_DPC_INVALID
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a kernel timer or delayed procedure call (DPC) is found somewhere in memory where it is not permitted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 5/3/2012 6:43:49 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xC7 (0x4, 0xFFFFF80000000000, 0x1, 0xFFFFFFFF)
Error: TIMER_OR_DPC_INVALID
Bug check description: This is issued if a kernel timer or delayed procedure call (DPC) is found somewhere in memory where it is not permitted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 5/2/2012 10:45:26 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050212-34725-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF880049EEAC7)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 5/1/2012 9:42:56 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050112-34320-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xFC (0xFFFFF88003E93AB8, 0x80000000B24E1963, 0xFFFFF88003E938B0, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 5/1/2012 5:05:32 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050112-34913-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70590)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 5/1/2012 1:16:14 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\043012-28329-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002EC33BC)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 5/1/2012 12:12:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\043012-42759-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xA (0x1E, 0x2, 0x1, 0xFFFFF80002CA50E0)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 4/23/2012 10:55:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042312-18408-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF8B, 0x1, 0xFFFFF80002CCF682, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 4/22/2012 12:54:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042112-16801-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xA (0x60910A342, 0x2, 0x1, 0xFFFFF80002C6E2BE)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 4/22/2012 12:07:49 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042112-17690-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xA (0x48D8, 0x2, 0x0, 0xFFFFF80002D2F00E)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 4/21/2012 6:15:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042112-17706-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xA (0x75DAA2342, 0x2, 0x1, 0xFFFFF80002C682BE)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 4/16/2012 12:40:23 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041512-17394-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xC7 (0x4, 0xFFFFF88000000000, 0x1, 0xFFFFFFFF)
Error: TIMER_OR_DPC_INVALID
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a kernel timer or delayed procedure call (DPC) is found somewhere in memory where it is not permitted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 4/15/2012 5:36:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041512-16208-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xC7 (0x4, 0xFFFFF88000000000, 0x1, 0xFFFFFFFF)
Error: TIMER_OR_DPC_INVALID
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a kernel timer or delayed procedure call (DPC) is found somewhere in memory where it is not permitted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 4/15/2012 1:24:35 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041412-15756-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xA (0x631472342, 0x2, 0x1, 0xFFFFF80002C6C2BE)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 4/14/2012 12:04:25 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041312-17706-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF8B, 0x1, 0xFFFFF80002CCF682, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP