Getting excess BSOD errors MEMORY_MANAGEMENT

Nolollygaggin · 28 Mar 2012

Hey sevenforums, Ive recently been getting a BSOD error that ive attached minidumps for. It usually occurs when i play a certain game but recently its been happening for everything. I cant virus scan without it blue screening, nor can i do system restore. Ive tried sfc /scannow but it says "Windows Resource Protection could not perform the requested operation" after about 10%. I tried startup repair but it blue screens that too. Please help me thanks

Nolollygaggin · 28 Mar 2012

Sorry forgot specs

Processor: AMD Phenom II N620 Dual Core
Graphics: ATI Mobility Radeon HD 4200

( Rest are here HP Pavilion dv6-3000 Entertainment Notebook PC series - HP Pavilion dv6-3025dx Entertainment Notebook PC Product Specifications - c02204326 - HP Business Support Center )

usasma · 28 Mar 2012

Please provide this information for a complete analysis of your issues: https://www.sevenforums.com/crashes-d...tructions.html

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Win7 systems.

Please uninstall all AMD/ATI video stuff from Control Panel...Programs...Uninstall a program
Then, download and install a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page)
- Select the "Custom" installation option and don't let it install AMD OverDrive or the VISION Engine Control Center
Then use the ATI uninstall manager to uninstall the Catalyst Control Center (CCC).

If the device (AODDriver or AODDriver4.01) remains a problem in perfmon /report, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Uninstall". Reboot for changes to take affect.

Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

There is a possibility that this is caused by hardware, so please try the first 3 diagnostics from this page (memory, hard drive, and anti-malware): Hardware Diags )

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:


amdxata.sys       Fri Mar 19 12:18:18 2010 (4BA3A3CA)
atikmpag.sys      Tue Feb 14 21:13:12 2012 (4F3B14B8)
hpdskflt.sys      Fri May 13 14:47:02 2011 (4DCD7CA6)
AtiPcie.sys       Mon Aug 24 04:25:26 2009 (4A924E76)
SynTP.sys         Fri Sep 10 21:09:32 2010 (4C8AD6CC)
Accelerometer.sys Fri May 13 14:47:02 2011 (4DCD7CA6)
AODDriver2.sys    Mon Dec 19 02:30:03 2011 (4EEEE7FB)
AtihdW76.sys      Tue Dec 06 04:14:25 2011 (4EDDDCF1)
amdiox64.sys      Thu Feb 18 10:17:53 2010 (4B7D5A21)
dvmio.sys         Tue Nov 10 23:38:32 2009 (4AFA3FC8)
GEARAspiWDM.sys   Mon May 18 08:17:04 2009 (4A1151C0)
usbfilter.sys     Tue Dec 22 03:26:22 2009 (4B3082AE)
athrx.sys         Tue Jan 10 23:47:50 2012 (4F0D1476)
atikmdag.sys      Tue Feb 14 21:51:52 2012 (4F3B1DC8)
Sftfslh.sys       Mon Sep 13 18:03:14 2010 (4C8E9FA2)
Sftplaylh.sys     Mon Sep 13 18:03:15 2010 (4C8E9FA3)
stwrt64.sys       Thu Jul 22 03:25:34 2010 (4C47F26E)
rtsuvc.sys        Thu Feb 04 10:09:13 2010 (4B6AE319)
Sftvollh.sys      Mon Sep 13 18:02:56 2010 (4C8E9F90)
Sftredirlh.sys    Mon Sep 13 18:03:26 2010 (4C8E9FAE)
mbam.sys          Wed Nov 02 09:07:48 2011 (4EB140A4)
aswSP.SYS         Tue Mar 06 19:04:03 2012 (4F56A5F3)
aswTdi.SYS        Tue Mar 06 19:01:56 2012 (4F56A574)
aswSnx.SYS        Tue Mar 06 19:04:05 2012 (4F56A5F5)
aswrdr2.sys       Tue Mar 06 19:02:19 2012 (4F56A58B)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032812-21013-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Mar 28 00:16:38.355 2012 (UTC - 4:00)
System Uptime: 0 days 0:09:08.791
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  DVMExportServi
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`029751f0 00000000`0000ffff 00000000`00000000
BiosVersion = F.28
BiosReleaseDate = 04/11/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032812-22120-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Mar 28 00:07:01.032 2012 (UTC - 4:00)
System Uptime: 0 days 0:05:49.468
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ipoint.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`029c3370 00000000`0000ffff 00000000`00000000
BiosVersion = F.28
BiosReleaseDate = 04/11/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032712-22713-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Mar 27 23:32:04.875 2012 (UTC - 4:00)
System Uptime: 0 days 0:38:46.311
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`028d4930 00000000`0000ffff 00000000`00000000
BiosVersion = F.28
BiosReleaseDate = 04/11/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032712-23119-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Mar 27 22:44:32.016 2012 (UTC - 4:00)
System Uptime: 0 days 0:03:28.452
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  schtasks.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`02919870 00000000`0000ffff 00000000`00000000
BiosVersion = F.28
BiosReleaseDate = 04/11/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032712-23415-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Mar 27 22:40:31.158 2012 (UTC - 4:00)
System Uptime: 0 days 0:03:17.594
Probably caused by : Ntfs.sys ( Ntfs!NtfsPagingFileIo+155 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x24
PROCESS_NAME:  taskhost.exe
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsPagingFileIo+155
Bugcheck code 00000024
Arguments 00000000`000c08a5 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = F.28
BiosReleaseDate = 04/11/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032712-19297-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Mar 27 21:57:55.198 2012 (UTC - 4:00)
System Uptime: 0 days 0:05:21.634
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  dw20.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`027d3fb0 00000000`0000ffff 00000000`00000000
BiosVersion = F.28
BiosReleaseDate = 04/11/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032712-19219-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Mar 27 21:47:14.316 2012 (UTC - 4:00)
System Uptime: 0 days 0:03:28.736
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+7271 )
BUGCHECK_STR:  0x1a_31
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  HPSF.exe
FAILURE_BUCKET_ID:  X64_0x1a_31_nt!_??_::NNGAKEGL::_string_+7271
Bugcheck code 0000001A
Arguments 00000000`00000031 fffffa80`05a2e4e0 fffff880`09b26000 fffff8a0`0c5cf117
BiosVersion = F.28
BiosReleaseDate = 04/11/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032712-18860-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Mar 27 21:35:27.793 2012 (UTC - 4:00)
System Uptime: 0 days 0:07:12.229
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  regedit.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`027d2ab0 00000000`0000ffff 00000000`00000000
BiosVersion = F.28
BiosReleaseDate = 04/11/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032712-54522-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Mar 27 21:26:08.861 2012 (UTC - 4:00)
System Uptime: 0 days 0:28:17.297
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  wmpnscfg.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`028ddb70 00000000`0000ffff 00000000`00000000
BiosVersion = F.28
BiosReleaseDate = 04/11/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032712-51059-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Mar 27 20:31:29.033 2012 (UTC - 4:00)
System Uptime: 0 days 2:57:28.453
Probably caused by : ntkrnlmp.exe ( nt!KeAcquireInStackQueuedSpinLock+5f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  aswBoot.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KeAcquireInStackQueuedSpinLock+5f
Bugcheck code 0000000A
Arguments 00000000`00000080 00000000`00000002 00000000`00000001 fffff800`032dec1f
BiosVersion = F.28
BiosReleaseDate = 04/11/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032612-29889-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Mar 26 18:50:17.695 2012 (UTC - 4:00)
System Uptime: 0 days 14:52:21.116
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteScb+71 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsDeleteScb+71
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`02fcb768 fffff880`02fcafc0 fffff880`012c9b15
BiosVersion = F.28
BiosReleaseDate = 04/11/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032612-18751-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Mar 26 03:57:28.356 2012 (UTC - 4:00)
System Uptime: 0 days 0:02:39.792
Probably caused by : win32k.sys ( win32k!xxxDestroyThreadInfo+66c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  wmpnscfg.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k!xxxDestroyThreadInfo+66c
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff960`0014943c fffff880`085b2f80 00000000`00000000
BiosVersion = F.28
BiosReleaseDate = 04/11/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Nolollygaggin · 28 Mar 2012

Okay thanks for the quicky reply. I installed catalyst CC quite some time ago as an update. I think my problems started there now that i think back. Ill do all the instructions posted and post back.

Nolollygaggin · 28 Mar 2012

I cant get through a uninstall without blue screens V___V Ill try the hardware tests

usasma · 28 Mar 2012

Backup anything that you can't bear to lose. This won't be likely to destroy data, but it may prevent you from getting back into Windows for a bit.
Next, go to Start...All Programs...Maintenance...Create a System Repair Disc and create a System Repair disk
Test the disk to make sure it works.
Create a System Restore point (you'll use the System Repair disk to access System Restore if it's necessary)

Go to Device Manager (devmgmt.msc)...View...Show hidden devices
Locate the AODDriverxxxxxx entry and disable it (right click on it)

Go to Services (services.msc)
Locate the AOD service and disable it

Go to C:\Windows\System32\drivers
Locate AODDriver2.sys - rename it to AODDriver2.BAD

Reboot the system to see if that helps
If the system doesn't boot, the boot with the System Repair disk and use System Restore to set the system back to the previous restore point. That should enable the system to boot.

Nolollygaggin · 28 Mar 2012

I was looking and i have a separate internal recovery drive. Imma do a factory restore and report back to you if it worked.

Nolollygaggin · 28 Mar 2012

Okay ive narrowed it down. Its a ram problem. I tried to factory restore my C drive with HP recovery and it blue screened even after the drive formatting. So should i get new ram?

usasma · 29 Mar 2012

If you think it's RAM, run this free memory test: Memory Diagnostics
If that gives nothing, then try Prime95 (it stresses the RAM). Hardware Diags

Nolollygaggin · 19 Apr 2012

Sorry for the REALLY late reply. Havent had access in a while. But im running memtest now. And within the first 15 minutes i have 47k errors

. What to do now?