Hi guys!
My notebook specifications are:
HP Pavilion dv4 Notebook PC
Windows 7 X-86
AMD Turion II Dual-Core Mobile M500, 2200 Mhz, 2 cores
BIOS: Insyde F.17
I've been having a lot of problems with my notebook for about 4 months now, and I have read multiple forums to try to fix things, but I'm running out of ideas now...
I started getting BSOD whenever my mom would play those facebook or zynga games. I took it to a repair center, and they changed the hard drive, because it had a problem, and cleaned the fans.
It got back from the repair, but the problems continued, but now is happening every time, sometimes not doing anything, it just restarts with the BSOD.
Here's what I've already done:
- Did the Memory Test for about 14 hours, no errors were found;
- I've updated all the drivers with Driver Booster;
- I've updated Flash Player, Shockwave Player;
- I updated the BIOS. I had the F.04 version, the latest was F.18. But the computer shut down after the update and honestly I don't remember what else happened, so then I tried to install the previous version, F.17, and the same thing happened, so I just left it alone;
- I tried to update AMD graphics driver. The computer shut down after the installation was completed, so I don't know if it was successful. For a few days, no BSOD, but then the party was over. So I uninstalled everything, so I could do a fresh install but got a blue screen. I had to restore the computer to the last known configuration, and when I tried to install the driver again, I got an error message. Don't know what to do there.
- I ran Driver Verifier, and got a whole bunch of information I don't know what to do with. The prints screens are here: https://www.dropbox.com/s/iv93q3z0mjpc5j9/DriverVerifier.zip
In the end of this post, there is a report from WhoCrached (I've already uninstalled Avast BackUp.)
Could someone please try to help me? I've had this notebook since 2009, never had any problems with it, but this year it decided to test my patience.
I don't want to take it back to the repair center, because they kept saying the computer was fine, when it wasn't.
I apologize for the huge post. Whatever extra information is needed, please let me know!
WhoCrashed log:
System Information (local)
computer name: CAROL-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: HP Pavilion dv4 Notebook PC, Hewlett-Packard, 3642
CPU: AuthenticAMD AMD Turion(tm) II Dual-Core Mobile M500 AMD586, level: 16
2 logical processors, active mask: 3
RAM: 3754106880 total
VM: 2147352576, free: 1942130688
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 22/11/2013 16:45:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112213-19858-01.dmp
This was probably caused by the following module: avastbackup.sys (avastBackUp+0x3A75)
Bugcheck code: 0x44 (0xFFFFFFFF882B3A38, 0xEAE, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
file path: C:\Windows\system32\drivers\avastbackup.sys
product: Mozy
company: Mozy, Inc.
description: Mozy Change Monitor Filter Driver
Bug check description: This indicates that a driver has tried to requested an IRP be completed that is already complete.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: avastbackup.sys (Mozy Change Monitor Filter Driver, Mozy, Inc.).
Google query: Mozy, Inc. MULTIPLE_IRP_COMPLETE_REQUESTS
On Fri 22/11/2013 16:45:47 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: avastbackup.sys (avastBackUp+0x3A75)
Bugcheck code: 0x44 (0xFFFFFFFF882B3A38, 0xEAE, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
file path: C:\Windows\system32\drivers\avastbackup.sys
product: Mozy
company: Mozy, Inc.
description: Mozy Change Monitor Filter Driver
Bug check description: This indicates that a driver has tried to requested an IRP be completed that is already complete.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: avastbackup.sys (Mozy Change Monitor Filter Driver, Mozy, Inc.).
Google query: Mozy, Inc. MULTIPLE_IRP_COMPLETE_REQUESTS
On Thu 21/11/2013 18:46:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112213-19578-01.dmp
This was probably caused by the following module: volmgr.sys (volmgr+0x183A)
Bugcheck code: 0x44 (0xFFFFFFFF866E0008, 0xEAE, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
file path: C:\Windows\system32\drivers\volmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Volume Manager Driver
Bug check description: This indicates that a driver has tried to requested an IRP be completed that is already complete.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 19/11/2013 16:09:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111913-13728-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x7F7EE)
Bugcheck code: 0xD1 (0x706E5046, 0x2, 0x1, 0xFFFFFFFF8C6FA636)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.
On Tue 19/11/2013 11:59:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111913-19765-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8D879)
Bugcheck code: 0x1A (0x41287, 0x318B48C1, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
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 that cannot be identified at this time.
On Mon 18/11/2013 22:22:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111913-16099-01.dmp
This was probably caused by the following module: hal.sys (hal+0x19196)
Bugcheck code: 0xD1 (0x4F8B087D, 0x2, 0x1, 0xFFFFFFFF8B836108)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hal.sys .
Google query: hal.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Mon 18/11/2013 22:20:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111813-16536-01.dmp
This was probably caused by the following module: partmgr.sys (partmgr+0x124B)
Bugcheck code: 0xD1 (0x9CC62, 0x2, 0x1, 0xFFFFFFFF8C69424B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\partmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Partition Management Driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Mon 18/11/2013 20:16:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111813-21434-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x2298DC)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF830688DC, 0xFFFFFFFFA53E88F0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.
Conclusion
8 crash dumps have been found and analyzed. 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:
avastbackup.sys (Mozy Change Monitor Filter Driver, Mozy, Inc.)
hal.sys
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.
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.
My notebook specifications are:
HP Pavilion dv4 Notebook PC
Windows 7 X-86
AMD Turion II Dual-Core Mobile M500, 2200 Mhz, 2 cores
BIOS: Insyde F.17
I've been having a lot of problems with my notebook for about 4 months now, and I have read multiple forums to try to fix things, but I'm running out of ideas now...
I started getting BSOD whenever my mom would play those facebook or zynga games. I took it to a repair center, and they changed the hard drive, because it had a problem, and cleaned the fans.
It got back from the repair, but the problems continued, but now is happening every time, sometimes not doing anything, it just restarts with the BSOD.
Here's what I've already done:
- Did the Memory Test for about 14 hours, no errors were found;
- I've updated all the drivers with Driver Booster;
- I've updated Flash Player, Shockwave Player;
- I updated the BIOS. I had the F.04 version, the latest was F.18. But the computer shut down after the update and honestly I don't remember what else happened, so then I tried to install the previous version, F.17, and the same thing happened, so I just left it alone;
- I tried to update AMD graphics driver. The computer shut down after the installation was completed, so I don't know if it was successful. For a few days, no BSOD, but then the party was over. So I uninstalled everything, so I could do a fresh install but got a blue screen. I had to restore the computer to the last known configuration, and when I tried to install the driver again, I got an error message. Don't know what to do there.
- I ran Driver Verifier, and got a whole bunch of information I don't know what to do with. The prints screens are here: https://www.dropbox.com/s/iv93q3z0mjpc5j9/DriverVerifier.zip
In the end of this post, there is a report from WhoCrached (I've already uninstalled Avast BackUp.)
Could someone please try to help me? I've had this notebook since 2009, never had any problems with it, but this year it decided to test my patience.
I don't want to take it back to the repair center, because they kept saying the computer was fine, when it wasn't.
I apologize for the huge post. Whatever extra information is needed, please let me know!
WhoCrashed log:
System Information (local)
computer name: CAROL-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: HP Pavilion dv4 Notebook PC, Hewlett-Packard, 3642
CPU: AuthenticAMD AMD Turion(tm) II Dual-Core Mobile M500 AMD586, level: 16
2 logical processors, active mask: 3
RAM: 3754106880 total
VM: 2147352576, free: 1942130688
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 22/11/2013 16:45:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112213-19858-01.dmp
This was probably caused by the following module: avastbackup.sys (avastBackUp+0x3A75)
Bugcheck code: 0x44 (0xFFFFFFFF882B3A38, 0xEAE, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
file path: C:\Windows\system32\drivers\avastbackup.sys
product: Mozy
company: Mozy, Inc.
description: Mozy Change Monitor Filter Driver
Bug check description: This indicates that a driver has tried to requested an IRP be completed that is already complete.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: avastbackup.sys (Mozy Change Monitor Filter Driver, Mozy, Inc.).
Google query: Mozy, Inc. MULTIPLE_IRP_COMPLETE_REQUESTS
On Fri 22/11/2013 16:45:47 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: avastbackup.sys (avastBackUp+0x3A75)
Bugcheck code: 0x44 (0xFFFFFFFF882B3A38, 0xEAE, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
file path: C:\Windows\system32\drivers\avastbackup.sys
product: Mozy
company: Mozy, Inc.
description: Mozy Change Monitor Filter Driver
Bug check description: This indicates that a driver has tried to requested an IRP be completed that is already complete.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: avastbackup.sys (Mozy Change Monitor Filter Driver, Mozy, Inc.).
Google query: Mozy, Inc. MULTIPLE_IRP_COMPLETE_REQUESTS
On Thu 21/11/2013 18:46:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112213-19578-01.dmp
This was probably caused by the following module: volmgr.sys (volmgr+0x183A)
Bugcheck code: 0x44 (0xFFFFFFFF866E0008, 0xEAE, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
file path: C:\Windows\system32\drivers\volmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Volume Manager Driver
Bug check description: This indicates that a driver has tried to requested an IRP be completed that is already complete.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 19/11/2013 16:09:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111913-13728-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x7F7EE)
Bugcheck code: 0xD1 (0x706E5046, 0x2, 0x1, 0xFFFFFFFF8C6FA636)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.
On Tue 19/11/2013 11:59:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111913-19765-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8D879)
Bugcheck code: 0x1A (0x41287, 0x318B48C1, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
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 that cannot be identified at this time.
On Mon 18/11/2013 22:22:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111913-16099-01.dmp
This was probably caused by the following module: hal.sys (hal+0x19196)
Bugcheck code: 0xD1 (0x4F8B087D, 0x2, 0x1, 0xFFFFFFFF8B836108)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hal.sys .
Google query: hal.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Mon 18/11/2013 22:20:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111813-16536-01.dmp
This was probably caused by the following module: partmgr.sys (partmgr+0x124B)
Bugcheck code: 0xD1 (0x9CC62, 0x2, 0x1, 0xFFFFFFFF8C69424B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\partmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Partition Management Driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Mon 18/11/2013 20:16:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111813-21434-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x2298DC)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF830688DC, 0xFFFFFFFFA53E88F0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.
Conclusion
8 crash dumps have been found and analyzed. 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:
avastbackup.sys (Mozy Change Monitor Filter Driver, Mozy, Inc.)
hal.sys
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.
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.
