Hp Envy Dv7t 7200 Overheating

[cooperbeaman]

I bought my laptop 2 years ago and until about 2 months ago, i never experienced a problem like this. My laptop will get extremely hot even when i'm not gaming and it will burn me when i try to use it. I have tried vaccuming the vents and it still overheats. Is there a way i can fix this and if so is it a hardware or software issue (is it dust or something within the computers operating system)? Thank you for your help.

my laptop is an hp envy Dv7t-7200: 

http://h10025.www1.hp.com/ewfrf/wc/product?product=5328068&lc=en&cc=us&dlc=en

whats going on here, this never used to happen?

thanks in advance for any help.:smileywink:

[Sparkles1]

Hi cooperbeaman,

Welcome to the HP Forums!

I would like to take a moment and thank you for using the forum, it is a great place to find answers.

For you to have the best experience in the HP forum, I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More.

I understand that you are experiencing an overheating issue, and that cleaning the vents did not help.  Here is a link to Troubleshooting an Overheating and Auto Shutdown Issue to assist you.

[cooperbeaman]

Another related issue (symptom of the overheating) i am experiencing with my laptop is that it will randomlly shut down and instead of shutting down normally when the laptop overheats, it will go into a reboot loop where the mouse is still showing on the screen and the screen goes from off (completely black) to the lighter black/grayish color when it first starts up. The reeboot loops occur randomly but they usually occur within 2-5 hours of each other. i am not sure if the reboot loop is caused by the computer getting to hot or a virus or something else, however, I would be very greatful if someone could tell me what is going on and how i can fix this without bringing it to a computer repair shop or shipping it back to HP under warranty to get replaced (also preferrably without refreshing or restoring my laptop (starting it over)).

If it helps, about a month ago, i switched from kaspersky to malwarebytes security software and pretty much ever since then, I have been experiencing this problem with my laptop.

Thank you to anyone who can help me!:smileywink:

Here is the event properties for the event 41/reboot loop error (if they are connected to each other)

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 3/22/2014 3:13:12 PM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (2)
User: SYSTEM
Computer: CoopersenvyDv7t
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>3</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2014-03-22T22:13:12.882039500Z" />
<EventRecordID>78266</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>CoopersenvyDv7t</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">0</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">1</Data>
<Data Name="PowerButtonTimestamp">130399789608881024</Data>
<Data Name="BootAppStatus">0</Data>
</EventData>
</Event>

[Sparkles1]

Hi cooperberman,

I hope you had an enjoyable weekend.

Are you still having an overheating issue?  Have checked to see if your system requires a bios update as there is two listed on the software and driver page for you unit. The latest version is VersionF.29, 6.56M. Here is a document to assist you, if it is not up to date. Updating the BIOS . You can also test for hardware failure. Testing for Hardware Failures (Windows 7, Vista).  If all the hardware passes,  and updates are done and you are still having an issue, you can run the built in troubleshooter to try and resolve the issue.

Press the Windows key + C to open charms

Type troubleshoot performance and press enter

Follow the on screen prompts.

You can do a system restore back to a known good time. Using Microsoft System Restore (Windows 😎

You can also do a system recovery back to factory.  Performing an HP System Recovery (Windows 😎 During the recovery process you will be prompted to do a backup, so that your data is not lost.  If you have not done one previously, I would strongly recommend that you do it now.  Here is a link on restoring your files after the recovery. Restoring Files that were Backed Up Using HP Recovery Manager (Windows 8).

You can always call HP support as you stated.

Please call HP technical support at 800-474-6836. If you live outside the US/Canada Region, please click the link below to get the support number for your region.HP Technical Support Sitemap

[cooperbeaman]

is their a guide for how to clean the internal fan(s) on my exact model because all i did before was clean/vaccum the external vents. If i was able to clean the internal fan of dust, then i would be able to tell if it was a hardware or software(OS) issue.

[Sparkles1]

Hi cooperbearman.

Here is a link to the HP ENVY dv7 Notebook PC Maintenance and Service Guide,to assist with opening up the notebook to clean it.  Continuing to use the notebook and letting it overheat can cause damage. If your notebook has the vents on the bottom of the unit,  it is important not to rest it on a soft surface while in use. A laptop has it's vents on the side thus allow airflow while resting on your lap. This is not the case with yours as it is a notebook and needs to have airflow from the bottom.

Please note on  page 81, the  section on the fan/heat sync assembly for guidance on cleaning. Here are two  Youtube  videos  on cleaning the cpu fans. This one uses compressed air,( this is not for your model) but you will grasp the concepts. clean fan/heatsink. The next one is more involved Cleanning cpu fan. 

If you computer is in warranty, I would call HP Technical support to ensure that your warranty does not become void. Please call HP technical support at 800-474-6836. If you live outside the US/Canada Region, please click the link below to get the support number for your region. HP Technical Support Sitemap

 You may also want to try reseating the ram as sometimes it does make a dfference.  If the issue persists try testing the ram by removing one and then try rebooting. Then just swap it to test the other ram chips.

Once you have resolved the issue, if your system still goes into a reboot loop you may need to do a Windows repair, as auto shutdowns can cause corruption.

[cooperbeaman · Accepted solution]

I brought my laptop to a laptop repair store and they cleaned out the air vents with a special compressed air type thing and corrected my stupid mistake of turning off the "fan always on" setting in the bios. now my laptop never goes past 70 C when im doing internet browsing and other things and never past 80 when playing games. it also doesn't get scalding hot or even preety hot anymore after they fixed it. however, the only issue i am still having is the laptop will crash randomly but much less frequently than it used to. i'm not sure if it is heat related or something else but i do have the "whocrashed" analysis of the dump file and it mentioned something about the "ntkrnlmp.exe" module causing the problem. im wondering if i can prevent the computer from crashing using this information and more specifically find out what is causing it, any help would be appreciated, i'm close to fully solving the problem, all thats left is preventing it from crashing. mabey it involves copying over the file with a non-corrupt version if it is indeed corrupted (thats one of the things someone did to fix a similar error i saw while doing research on how to fix this error)

System Information (local)

---

computer name: COOPERSENVYDV7T
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: HP ENVY dv7 Notebook PC, Hewlett-Packard, 181F
CPU: GenuineIntel Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8473825280 total
VM: 2147352576, free: 1928949760

---

Crash Dump Analysis

---

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 4/4/2014 12:59:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040314-8484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8007F18880, 0xFFFFF8800096F7F0, 0xFFFFFA8008267650)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 that cannot be identified at this time.



On Fri 4/4/2014 12:59:47 AM 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: 0x9F (0x3, 0xFFFFFA8007F18880, 0xFFFFF8800096F7F0, 0xFFFFFA8008267650)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 that cannot be identified at this time.

---

Conclusion

---

2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually 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.

[Sparkles1]

HI cooperbeaman,

Thank you for your reply.

I see you took the notebook to the repair shop and they cleaned it properly for you. They changed the setting to fan alway on and your heat issue has been alleviated. However you are getting a crash dump  with a "driver poer state failure" error.

I suggest you reinstall the orignial drivers from the recovery manager.Using Recovery Manager to Restore Software and Drivers (Windows 😎. Once you have completed that task, run   The HP Support Assistant,to look for any updates and install them. Please make sure you have done all your Windows updates.  Please let me know the results.

[cooperbeaman]

i recently updated all my outdated drivers with a 3rd party program (can't remember the name right now) and i haven't run into the shutdown/ error in 3 days so far. I think updating all the old drivers may have done the trick but i'm still curious about what was causing the computer to shut down (and go into a reboot loop), in simple terms, what does the "whocrashed" error report mean, what was wrong with those drivers?

[Sparkles1]

Hi cooperbeaman,

Thank you for your reply.

The crash dump error you received, is usually caused by a corrupt or out of date driver.  Once you updated the driver, the issue was overcome.