Last week I returned a New HP Pavillion p7-1231 that was randomly re-booting since it was purchased the week before. Exchanged it for another one. Did the initial install. Have connected my 2 printers (no issues). Installed firefox and chrome, and use KIS 2012 anti-virus. Ran all day yesterday and all day today without the random reboot UNTIL about 10 minutes ago - got a black screen and then the PC booted up again. SIGH. This is how the other HP did too - and gradually got worse. Per the event viewer - kernel-power event ID 41, task category 63, bugcheck 1001 and event log 6008 just prior. General description messages are very generic (rebooted from a bug check) Read TONS of items on the internet regarding this - seems to be a common issue, but no definite answer. Uploaded the minidump to SkyDrive - link https://skydrive.live.com/#cid=8EA43C0B0DFAC9B8&id=8EA43C0B0DFAC9B8!105 The dump is 050612-19796-01-dmp - would appreciate someone looking at it and interpreting the problem. Again could use some help please since I have no idea how to read this dump. My hubby is ready to return the PC for good and just live with our old PC (which is super slow). You'd think that there would be more user friendly errors. Thanks very much. Elynn Boss

Uploaded a 2nd minidump. This one is 050612-20514-01. This one just happened and I WAS NOT DOING ANYTHING. The computer was running the screen saver when the re-boot occurred. That is the first time that has happened - before it has been when I was doing something on the PC. Sure hope someone can help - Thanks again.Elynn Boss

Hi Elynn, Firstly, I suggest you test the issue in Safe Mode and Clean Boot to check the result. Meanwhile, after checking the dump file, I found the error code 0xD1 was received. You can refer to the Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL for reference. And the corrupt process is avp.exe, which is belong to Kaspersky program. I suggest you can try to update your Kaspersky antivirus program or temporarily disable it to test the issue. Hope this helps. Vincent Wang TechNet Community Support

Hi, I am glad to hear that this issue havent occurred again after update drivers, firmware and BIOS. Regarding the analyze dumpfile, you need to download the Debugging Tools for Windows from the following link: http://www.microsoft.com/whdc/devtools/debugging/default.mspx There is a tutorial in the following link on setting up WinDbg, such as setting the symbol path and utilizing the !analyze -v command: http://www.sevenforums.com/crash-lockup-debug-how/26584-2-intermediate-configuring-debugging-tools.html Hope this helps. Vincent Wang TechNet Community Support

Hi Elynn, Firstly, I suggest you test the issue in Safe Mode and Clean Boot to check the result. Meanwhile, after checking the dump file, I found the error code 0xD1 was received. You can refer to the Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL for reference. And the corrupt process is avp.exe, which is belong to Kaspersky program. I suggest you can try to update your Kaspersky antivirus program or temporarily disable it to test the issue. Hope this helps. Vincent Wang TechNet Community Support Hi - I appreciate the information. While Kaspersky may have caused the reboot, I believe that the root cause was out of date drivers, specifically for the BIOS, firmware and sound. On a brand new computer I don't think I should have had to search for new drivers - but be that as it may - I did. Downloaded new BIOS, firmware and sound drivers on Sunday. Haven't had a random reboot since. Keeping fingers crossed that this has truly resolved the problem. Now, is there a way that I can learn to read the minidump produced so that should this happen again I can determine for myself the corrupt process/program? I am a mainframe programmer so I should be able to learn how to read the minidump. Is there special software for that? Elynn Boss

Hi, I am glad to hear that this issue havent occurred again after update drivers, firmware and BISO. Regarding the analyze dumpfile, you need to download the Debugging Tools for Windows from the following link: http://www.microsoft.com/whdc/devtools/debugging/default.mspx There is a tutorial in the following link on setting up WinDbg, such as setting the symbol path and utilizing the !analyze -v command: http://www.sevenforums.com/crash-lockup-debug-how/26584-2-intermediate-configuring-debugging-tools.html Hope this helps. Vincent Wang TechNet Community Support

Hi, I am glad to hear that this issue havent occurred again after update drivers, firmware and BISO. Regarding the analyze dumpfile, you need to download the Debugging Tools for Windows from the following link: http://www.microsoft.com/whdc/devtools/debugging/default.mspx There is a tutorial in the following link on setting up WinDbg, such as setting the symbol path and utilizing the !analyze -v command: http://www.sevenforums.com/crash-lockup-debug-how/26584-2-intermediate-configuring-debugging-tools.html Hope this helps. Vincent Wang TechNet Community Support Well - its me again. Sorry to report that the random rebooting issue has not been resolved. I went a few days without it happening then it started up again. Since you said that the minidump showed that the issue was probably Kaspersky, I went to the Kaspersky support site, and followed the directions to create a full memory dump. Unfortunately, it is too big to upload to SkyDrive, and apparently too big to upload for Kaspersky support. Know anyplace I can upload the full dump? Thanks. Elynn Boss

Hi Elynn, Please contact Kaspersky support and let them give the steps for how to upload full dump file. Regards Vincent Wang TechNet Community Support

Appreciate the help. This is turning into SUCH a fiasco. Kaspersky stated that see that I only have 1.99 GB usable out of 8GB installed and I need more memory. I contacted HP support which had me restore the PC to factory. It now shows 8GB available. However, THEY took control and THEY used the Norton removal tool to remove Norton (since I don't want Norton) - (and because they told me I obviously didn't use the right tool - sigh). Well, lo and behold after THEY ran the removal tool, I now have a corrupted registry (again). AND I still don't know what caused the computer to not see that there was 8GB available. AND I still don't know what caused the random reboots. I now have a request for a call back from a 'case manager'. I am going to demand a recovery disk WITHOUT Norton. And some additional compensation since I have been without a computer for over a month, have spend numerous hours on the phone with their Tech Support, numerous hours searching the internet for solutions and posting for help and currently 8 DVD 'recovery disks' that are worthless. I may have to post again - after I get the computer up and running - because since I don't know what caused all these issues (random reboot, memory issues) they will surely occur again.Elynn Boss