Hi guys, I have a serious problems with my windows 7 on HP pavilion dv 7! i am getting tons of BSOD in each day! upon restart, normal startup, start up repair, and last but not the least even during safe mode!! Please help me to diagnose the problem as I don't have the proper tool to read the "minidump" files! here is the link to my sky drive, please let me know if you are having trouble taking a look at it so I can upload it somewhere else: http://cid-483822cf1f02188b.skydrive.live.com/self.aspx/.Public/Minidump.rar I appreciate all the helps as I need to get back to HP if there is any HW issue! I have already sent my laptop back twice and both times they replaced the MB!!!! thanks,

Hi, I was so tired of getting so many BSOD so I decided to reinstall my windows 7! but guess what, yet blue screens! here is the link to the new dump files! http://cid-483822cf1f02188b.skydrive.live.com/self.aspx/.Public/Minidump-reinstall.rar I took out of one the RAM sticks, and yet no BS. would someone go through the dump files and let me know whether the RAM is the issue for getting all those blue screens. thx.

The bugchecks suggest memory corruption is occurring. This can be attributable to hardware failure (faulty RAM, for example), or a bad/buggy driver, or a driver that is not meant for the version of Windows you are using. General guidance for dealing with bluescreens: Consider running chkdsk on all partitions. Let chkdsk complete on each partition and see if that helps. It can be helpful to use Driver Verifier. To enable Driver Verifier... start->verifier.exe->OK->Create standard settings->Next->select driver names from a list->Next->sort by Provider->select all non-Microsoft drivers->Finish, and OK your way out of the dialog. Then, reboot and use the system as you normally would, and wait for a problem. In the event that the system does not boot completely after enabling driver verifier, boot into Safe Mode and run driver verifier, and tell it to delete the changes. Wait for a bugcheck to occur after enabling verifier as described, and then upload the dump to your SkyDrive, and provide a link. Also consider running SFC /SCANNOW. If you boot into safe mode, do you still experience bugchecks? What about if you do a clean boot, or device clean boot? Consider testing memory with Windows Memory Diagnostic or memtest86. Note that memory that passes tests is not necessarily good memory - it just hasn't failed a test. Consider systematically eliminating RAM from the system - run with a couple of modules for a while, and see how things go. Then try the other modules. Other common suggestions include ensuring drivers are up to date, as well as ensuring that you're using the latest BIOS.

Thanks... since 2 days ago that I encountered this problem I have done a series of things: - chkdsk: it never went through to the end, computer kept getting reset in btw! but on the other hand it never mentioned anything as an error till 89% 90% - verifier: I did the same steps, but yet problem existed! i even uses sigverif.exe to verify all the signatures and everything was right in the right place. - SFC: I ran a tons of them, no use. - RAM stick: I pulled out one the sticks now and it is working fine, no BS yet! (almost 3 hours) but I am not quite sure that one is the problem. I am a little skeptical about the HDD or even the nVidia card. I will update the BIOS and start the comp with full RAM. I hope this will work and solve the problem... in case of any BS I will post the dumps again... get back here as soon as I am done with the steps... cheers.

I did update the BIOS, and checked different RAM sticks combination on different sockets: - both sticks in --> BS for sure - RAM #1 in SOCKET #1 --> ok most of the time (although one BS so far) - RAM #2 in SOCKET #1 or #2 --> BS - RAM #1 in SOCKET #2 --> BS! new dump files: http://cid-483822cf1f02188b.skydrive.live.com/self.aspx/.Public/Minidump-2.rar I deleted the changes in verifier.exe but yet nothing! cheers,

The HP Pavilion DV7 is an LGA1156 based system. Keep in mind that some mobo's don't like Hyper (and sometimes 'regular') RAM in dual channel mode. Since HP aren't too keen on displaying what brand of mobo they use (they use licenced brands, meaning they hack the mobo's to alter the BIOS and stuff) I haven't got a clue how many RAM slots you have. Nor do I know what brand/type of RAM you are currently using. If by any chance it's Kingston's KHX1333C7D3K2/4G, that seems to be RAM which works only on certain mobos (especially Asus and/or Gigabyte boards have difficulties with this RAM)...

So any RAM in any socket does not cause the problems to cease. This suggests a motherboard problem or similar rather than a RAM problem, if any hardware is faulty at all. You do have some old drivers that should be updated or uninstalled/removed from the system: enecir.sys 3/7/2007 SynTP.sys 3/27/2008 jmcr.sys 10/20/2008 agrsm64.sys 11/10/2008 Rt64win7.sys 2/26/2009 In addition, the program files for the Kaspersky software seem to be relatively old. Consider uninstalling the Kaspersky software and seeing if that has an impact on system stability.

Thanks... I'll try to update all these drivers (although with HP it is not that safe to update the drivers standalone, I mean through the providers' webpage as it might cause some other problems! but I will look at HP other products to see the provided versions) as of Kaspersky, it has always been a little slow but as it is the most recent version! I don't get why they haven't thought to refresh the files. I will check this step too. I plugged both RAM sticks (2GB each) in and ran the HP startup and in-run test (@ startup) + windows memory check and both tests (quick and extensive) passed with no errors (HP version checked the memories more than 10 times!) also the HP HDD test passed with no errors but Windows chkdsk gives me an error as below (although it was an online test, as I have a deadline tomorrow and need my VPN connection I can't run CHKDSK unmount version but I will tomorrow) ** since the Memory & HDD tests performed, not the system is up and running with both RAM sticks plugged!! and no BSOD so far. The type of the file system is NTFS. WARNING! F parameter not specified. Running CHKDSK in read-only mode. CHKDSK is verifying files (stage 1 of 3)... 549376 file records processed. File verification completed. 642 large file records processed. 0 bad file records processed. 2 EA records processed. 85 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)... 36 percent complete. (543065 of 618502 index entries processed) Error detected in index $SII for file 9. 618502 index entries processed. Index verification completed. Errors found. CHKDSK cannot continue in read-only mode. P.S. due to a BIOS problem, I had to send the laptop back to HP and they did change the MB twice!!!! so I guess this is a brand new MB! (at least I hope) Cheers,

The chkdsk items seem minimal and not likely related to what you are experiencing, but would be good to address. Could be a result of the unexpected/ungraceful shutdowns. Is your DV7 one of the ones that is susceptible to the overheating nvidia GPUs, since the motherboard had to be changed? (May be/have been a class action suit about this.) Does HP support /endorse Win7 on the DV7? Did you run the Windows 7 Upgrade Advisor?

I do appreciate all your helps. :) Actually I had series of issues with that overheating issue, even now I have to let a gap be where the vent is! (I use "speedfan" to check on the temp as windows does not provide any easy sensor reading tool) the reason they changed MB was because of a BIOS update failure (HP uploaded the wrong version on the webpage!!), although I could retrieve the comp using a flash disk I preferred not to meddle due to warranty issues! but that "send back" was the root of all evil now I am dealing with. It went as a healthy boy but never came back well preserved! They do support Win7 on new DV7 models (mine is Jan 2009), and i did run upgrade advisor as I would have thought of such issues coming. But to make the long story short, I had no problem with Win7 for 3 months! Then gradually I started receiving all these BSs (tons in a day) and the BIOS failure, they replaced the MB again lots of issues with "new MB" as it was defected!!! and then they changed it for the second time and it was running nice and smooth till Friday which gave me the first BS followed by 2...50... (go on) * still no BS since morning (3 hours!) after running the tests. PS: any suggestion for the GPU overheating problem? Cheers,

Hi, After analyzing the minidump files you uploaded, I find that SYNTP.SYS and NETw5s64.sys are the possible causes. Based on the current situation, I would like to suggest you uninstall and reinstall the latest versions of Touchpad Driver and Wireless Network Card driver for Windows 7 to check the result. If it does not work, please reset BIOS to default and disable overheating to test the issue. Regards,Arthur Li - MSFT

How's the stability now? Have you had any more bugchecks? Of the latest 3, as Arthur suggested, one seemed to be caused by SynTP.sys from March of 2008. That bugcheck was "DRIVER_VERIFIER_DETECTED_VIOLATION" because syntp was "Referencing user handle as KernelMode". Another seemed to be caused by NETw5s64.sys from Jan of 2010. That bugcheck was SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION - "Special pool has detected memory corruption." Both of these bugchecks were caused when verifier picked up a driver misbehaving. However, the third of the last bugchecks was a PAGE_FAULT_IN_NONPAGED_AREA likely caused by hardware, with a fault of X64_IP_MISALIGNED. That could be a result of memory corruption. I'd suggest trying new RAM if you can, or since you've had so many problems with motherboards, reset the BIOS to default settings after noting current settings; then if the behavior persists, contact HP and see what they say. Perhaps this board is bad as well.

Yesterday I had two more BSODs, one right after the computer woke up from sleep mode (it seems sleep mode is one of the pitfalls for my problem) and another one right after the computer was restarting from the previous BSOD. By removing one of the RAM sticks now it is working although I have not tried the sleep mode yet having only one stick plugged. Here is the link to Minidumps I got yesterday: http://cid-483822cf1f02188b.skydrive.live.com/self.aspx/.Public/Minidump-3May.rar sometimes I will get the List_Corrupted kind of BSODs!! what are these categories resulted of? How about the HDD? is there any chance there is some bad sector causing all these? * I will uninstall Synaptics and the wireless network card to seek whether the problem persists! I have got tired of all these issues caused by HP and its support! how can they change a MB twice and still hooked me up with a faulty one! @Arthur: Thanks for your reply, I will go through the steps and let you know in a while. How can I reset the BIOS? you mean to set it to default values? as just recently I have updated the version.

It is unlikely that a bad sector on the HD is responsible for what you are experiencing. CHKDSK /R, manufacturer diagnostics, and the event viewer would show indications of this type of problem. Double check with these items, if you wish. The "List_Corrupted" BSODs you reference (PFN_LIST_CORRUPT?) sound like memory corruption, much like your latest two bugchecks (SYSTEM_SERVICE_EXCEPTION during a page fault and BAD_POOL_CALLER due to double free). Now that you have removed some RAM, test the issue as you normally would, then replace with the other RAM and do the same. See if you can identify if one is faulty.

I got a BSOD just after another wake up having only one RAM stick plugged!! that was supposed to be the good RAM as far as I did the tests up to now. Prior to this incident, the Wireless driver was updated to the latest version (which I guess it is the same version as before) and I un-installed the Synaptics driver. But yet I got the BSOD on one RAM. here is the dump for this one: http://cid-483822cf1f02188b.skydrive.live.com/self.aspx/.Public/Minidump-May5th.rar After the BS, I reset the BIOS to default, but I could not find the option to disable the overheating! as there are not so many parameters to be modified in BIOS these days! After restart I insert the other stick in, and now it is still working normally! god knows when it will get the next stroke. I need to make sure that the problem is caused by a HW defect and not by MS Windows or any other SW installed before I seek help from HP again. I don't wanna go through all the pain having my LP repaired there. Any suggestion on the above log? Thanks for all the help.

I think Arthur meant "overclocking" rather than overheating. Except in extremely cold environments where a tauntaun is not available, I can't see where such an "overheat" function would be useful. This last bugcheck shows that enecir.sys is implicated. The driver is old and should be removed or updated, regardless of the potential for loss of functionality. If the behavior continues after dealing with enecir.sys... Can you try to get a bluescreen to occur in safe mode, and provide a dump for that? The last dump shows several drivers that would be good to eliminate or update. If updates aren't available, you would need to disable the device/driver to remove the item as a suspect. SynTP.sys 3/27/2008 enecir.sys 4/28/2008 jmcr.sys 10/20/2008 agrsm64.sys 11/10/2008 Rt64win7.sys 2/26/2009 HpqKbFiltr.sys 4/29/2009 stwrt64.sys 5/22/2009 Also, the following third-party drivers could seemingly be eliminated at least for testing purposes: Accelerometer.sys 2/26/2010 hpdskflt.sys 2/26/2010 NETw5s64.sys 1/13/2010 nvhda64v.sys 1/28/2010 Finally, you would want to remove the Kaspersky software. Once the above items are out of the scenario, you can be even more certain that if the problem still persists, it is hardware-based. Since a bluescreen in safe mode often is indicative of a hardware problem, I would hope the safe-mode bluescreens you described would be evidence enough of some hardware issue, for HP.

Thank you... I will follow the procedures and will disable all the above drivers and remove Kaspersky and get back to you later. But meanwhile, just got another BS while it was waking up from the sleep mode, so here what happened: -The comp was running normal having both stick plugged in. I left it in sleep mode for some hours. - it took a while, 4-5 min, for the log in page to be shown and passwd can be typed. - it took about 2 3 min to load things, most of the application failed such as: google chrome, hp assistant, kaspersky, yahoo messenger. -HDD was working in a cycle! the light was on or better to say flickered with some off moment in between. -everything was slow, and boom... there it came:BS - computer restarted, BS on the welcome page. - I removed one stick, it booted up. -Took a long time and too much HDD activity to load all the start up applications and can perform normally! here is the dump file from the recent incident: http://cid-483822cf1f02188b.skydrive.live.com/self.aspx/.Public/Minidump-May6th.rar Question: if it is a HW problem, how can we explain the random behavior on RAM sticks and also why it happens for sure after each wake up no matter if there are 2 sticks or one! I hope we can find a solution to all this. Cheers,

I removed Kaspersky, tried to run a CHKDSK but it failed with an "unspecified error" in middle!!! After logging into windows, the startup was so slow and after a while the famous BS. Here is the dump file for this recent one: http://cid-483822cf1f02188b.skydrive.live.com/self.aspx/.Public/Minidump-May6-2.rar sometimes it is getting frustrating!

Just after another Sleep, computer hanged (no BS) on welcome screen. I force rastarted it into 'safe mode' but it freezed on the loading part!!! next try to get into safe mode there was a BS. here is the dump file I got from these last unfortunate happenings: http://cid-483822cf1f02188b.skydrive.live.com/self.aspx/.Public/Minidump-May7th-Probably%20safemode.rar -I ran a test on memory which result came as no error! -I am a little worried about the HDD as it does not fulfill the checks and it seems whenever the BS is about to happen, it is really busy doing stuff. :) each time BS happens, the restart will fail (several BSs at startup) for a while!

You got a bluescreen while trying to boot into safe mode. All of the latest bugchecks are related to memory corruption. This points to some hardware issue. The latest dump showed 4 third-party drivers were loaded: hpdskflt HpqKbFiltr SynTP Accelerometer Please uninstall "HP Quick Launch Buttons keyboard" . That should get rid of HpqKbFiltr and hopefully hpdskflt. Also consider uninstalling the touchpad driver and plugging in an external mouse. (That'll get rid of SynTP.) Are you able to uninstall HP Mobile Data Protection? That would get rid of Accelerometer. The above would seem to eliminate third-party software from the scenario. Ultimately, though, the nature of the memory corruption bugchecks (0x1a) seems to very strongly point to some kind of hardware failure (RAM, CPU, etc.) or misconfiguration (RAM timings in BIOS, etc). If you've stripped the system down of all unnecessary hardware and are unable to isolate/pinpoint the problem, and have stripped the system of unnecessary software (almost completely there), it would seem time to contact HP again about the problem.

Hardware issues are not covered by the above.

I removed all the above SW except HP mobile data protection as I could not locate it yet. I will get rid of that one pretty soon too. Here is the latest BS dump I just got an hour ago: http://cid-483822cf1f02188b.skydrive.live.com/self.aspx/.Public/Minidump-May7th.rar I am monitoring the sys to see removing the SW can be of any help. (seemingly Kaspersky was not the bad buddy) I am still thinking of HDD to some extent, as non of the CHKDSK tests are completing through the end! it either hangs at the beginning (at the count down) or quits unexpectedly in the middle!! also due to several BSs startup suggests windows repair as an option, but even during windows repair I got a BS!! it is ridiculous. I am thinking of other ways to check my HDD too. I will get back to you with more info and the way removing SW is going to react. @technocrate: Have done all of the steps prior sending my request to this forum. but thanks for the concern. cheers,

Corruption, again. Do you have an alternate HD you can try? Can you check the disk with manufacturer's diagnostics? Did you install Symantec/Norton software after uninstalling Kaspersky?

No alternate HD which is SATA. The quick test through HP startup (BIOS menu) shows no error. But need to run the extensive test too. Just the comp woke up from sleep mode, no BS yet!! though it took a while for it to show me the log in screen! Yep, I installed Norton instead of Kaspersky. But I have no confidence in Norton Anti-virus comparing to Kaspersky Internet Security. Will get back to you with the extensive test result and in case of any BS. Cheers,

I tried to insert the other stick in running my comp on full RAM, but there you go, BS on the startup. I removed the assumed well-operating RAM stick, running the comp on 2GB (the corrupted RAM) yet another BS on startup. I removed the assumed corrupted memory and windows showed up. Although the startup was successful but it took a long time for it to be up and running. here is the link to the latest BS I got: http://cid-483822cf1f02188b.skydrive.live.com/self.aspx/.Public/Minidump-May9th.rar maybe it can suggest that one of the sticks are gone bad! but still I cannot find the reason of other BSs though the bad memory was removed?!! and why can't I use the CHKDSK on my HDD!! Please get back to me with your opinion and ideas! I am gonna call HP care center tomorrow BTW. Cheers,

Inconclusive cause in the last dump - page fault in nonpaged area while autochk was running. It's possible some of the memory is faulty, and the other bugchecks were caused by software that has since been removed or updated. Hard to tell, until you get another bugcheck, with only the assumed good memory installed.

I will try to put it under stress to see how it goes... probably lots of sleep modes and hibernating. I think I can get in one or two days. BTW how com all the quick and extensive memory checks turned out OK? I know it just means no failure in a test, but how come in all the tests? Is there any solid test out there which shows for sure the problems with memory sticks?

I'm not aware of anything that will definitively indicate that memory is good. Memory that turns up any sort of issues in a test would seem to be forever suspect, in my eyes, and should be replaced ASAP. It may be that the memory is good, and the configuration is not correct - BIOS settings/timings, etc. It may be that there is some fault with the motherboard that is contributing to the problems you are experiencing. It is difficult to say. One would hope the manufacturer would return the system with the correct configuration, so one could hopefully eliminate that as a possibility. It may be that some other piece of hardware is faulty, and the dynamics of the failure are such that it is difficult to pinpoint. Ultimately, short of swapping hardware with known good working components, it is difficult to try to diagnose some hardware issues. It isn't always practical to have a spare everything on hand, "just in case".

That's true, but I really thought HP would return the comp back with no faulty part or issue to me! which was kind of a dream, unfortunately, as it seems they don't care that much how much consumers suffer!!! I am going to call HP today, and let you know if there is any more BS and also the result of their diagnosis! cheers,