Tech Support Forum banner

HP Pavilion DV3 - Help!! (Bluescreen)

4465 Views 5 Replies 2 Participants Last post by  reventon
Hi all! I hope you guys can figure this one out - because its so troubling :(. I'm doing this to help a friend.

She has a HP Pavilion DV3 Laptop and it ALWAYS gets random 'bluescreens' and says something like "dumping physical memory'. This happens at LEAST 10 times a day, and it gets really frustrating because it was sent in to fix for about 4 times. The rep people said they replaced the hard drive (yeah okay) and such so that it will operate properly without blue screening.

It's been a month (since she sent it in) and she just got her laptop back and it continues to do that! Does anyone know how to fix this? It's getting really hopeless because we think that the 'rep' people are just saying that they fixed it.. please help! Very much appreciated :smile:

- HEA

Status
Not open for further replies.
1 - 6 of 6 Posts
Hi,

Could you please go to the folder C:\Windows\Minidump copy any files you find in that folder to a zip file, then upload that zip file to your next post.

EDIT: If the laptop is running Vista or 7 then ignore the above and follow these instructions instead: http://www.techsupportforum.com/f21...-posting-instructions-452654.html#post2545708

Still attach the zip file to your next post in this thread
Hi, thanks for replying.

I tried to compress the 'minidump' folder but it won't let me. I am on the admin. account, and it gave me an error message: 'File not found, or no read permission.' I'm going to attach the screenshot of what it says.. I can't really do much because these error messages ALWAYS come up!

Attachments

See less See more
Hi,

I thought you were running XP as that is what it says under your name. No matter, we have a different way of doing things for Vista/7

Please follow these instructions: http://www.techsupportforum.com/f21...-posting-instructions-452654.html#post2545708

Attach the zip file to your next post here please
Ok, here are the attached files as requested

Attachments

Hi,

You have quite a range of BSODs, usually this means that there is a hardware fault.

I did notice that a lot of Hard Drive related drivers were mentioned. Because of this you should do the following:

  • START -> type cmd.exe -> Right-click -> run as admin -> type sfc /scanonce -> restart computer.
  • START -> type cmd.exe -> Right-click -> run as admin -> type chkdsk /r /f -> Press Y at prompt -> restart computer.

Also run this physical hard drive diagnostic tool: Seagate | SeaTools

There is a possibility that a third party driver is causing all this, however it has not been named yet in the dumps. Run driver verifier to try and get it to show itself.

Driver Verifier
I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Regards,
Reventon

BUGCHECK SUMMARY
Code:
[font=lucida console]
Built by: 6002.18209.amd64fre.vistasp2_gdr.100218-0019
Debug session time: Thu Jul 15 20:03:14.191 2010 (GMT+12)
System Uptime: 0 days 0:16:16.912
BugCheck D1, {98, 6, 8, 98}
Probably caused by : msahci.sys ( msahci!AhciCompleteRequest+22 )
PROCESS_NAME:  System
BUGCHECK_STR:  0xD1
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 6002.18209.amd64fre.vistasp2_gdr.100218-0019
Debug session time: Wed Jul 14 17:53:56.863 2010 (GMT+12)
System Uptime: 0 days 3:24:48.029
BugCheck 1E, {ffffffffc0000005, fffff80001e64b85, 0, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+195 )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 6002.18209.amd64fre.vistasp2_gdr.100218-0019
Debug session time: Wed Jul 14 14:28:35.943 2010 (GMT+12)
System Uptime: 0 days 1:21:44.662
BugCheck 1E, {ffffffffc0000005, fffff80001eb69fa, 1, 5a}
Probably caused by : hardware ( nt!KiChainedDispatch+2a )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 6002.18209.amd64fre.vistasp2_gdr.100218-0019
Debug session time: Mon Jul 12 13:58:25.916 2010 (GMT+12)
System Uptime: 0 days 0:04:17.495
BugCheck 1E, {ffffffffc0000005, fffff80001f05fed, 0, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+107dd )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 6002.18209.amd64fre.vistasp2_gdr.100218-0019
Debug session time: Sun Jul 11 20:13:23.264 2010 (GMT+12)
System Uptime: 0 days 0:00:10.982
BugCheck 50, {fffffa6003aa5108, 0, fffffa600320fe7c, 2}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_QueryPciBusInterface+cc )
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 6002.18209.amd64fre.vistasp2_gdr.100218-0019
Debug session time: Sun Jul  4 15:59:39.609 2010 (GMT+12)
System Uptime: 0 days 0:16:42.314
BugCheck 24, {1904aa, fffffa6006776c98, fffffa6006776670, fffff80001f0dfed}
Probably caused by : Ntfs.sys ( Ntfs!NtfsMapStream+5d )
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 6002.18209.amd64fre.vistasp2_gdr.100218-0019
Debug session time: Thu Jul  1 14:26:47.042 2010 (GMT+12)
System Uptime: 0 days 4:36:47.567
BugCheck 50, {fffffc12ea00001b, 0, fffff80001f06f28, 7}
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+3c8 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 6002.18209.amd64fre.vistasp2_gdr.100218-0019
Debug session time: Mon Jun 21 10:46:53.892 2010 (GMT+12)
System Uptime: 0 days 0:00:44.640
BugCheck D1, {28, 2, 0, fffffa60012ebe13}
Probably caused by : CLASSPNP.SYS ( CLASSPNP!TransferPktComplete+194 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 6001.22636.amd64fre.vistasp1_ldr.100218-0019
Debug session time: Fri Jun 18 16:26:56.410 2010 (GMT+12)
System Uptime: 0 days 0:00:53.128
BugCheck A, {a0, c, 1, fffff80001e6c322}
Probably caused by : ecache.sys ( ecache!EcCacheIoWatchdog+35a )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 6001.22636.amd64fre.vistasp1_ldr.100218-0019
Debug session time: Wed Jun 16 15:47:31.757 2010 (GMT+12)
System Uptime: 0 days 0:15:51.478
BugCheck A, {38b, c, 0, fffff80001c9f7be}
Probably caused by : dxgkrnl.sys ( dxgkrnl!DxgkWaitForVerticalBlankEvent+530 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 6001.22636.amd64fre.vistasp1_ldr.100218-0019
Debug session time: Tue Jun 15 14:14:00.406 2010 (GMT+12)
System Uptime: 0 days 0:11:27.160
BugCheck 1E, {ffffffffc0000005, fffffa8000000010, 1, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+23657 )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨[/font]
uliahci.sys
See less See more
1 - 6 of 6 Posts
Status
Not open for further replies.
Top