BSOD's that I think are from a corrupt RAM module.

th0mas2 · 15 Jun 2012

I built my 1st PC around January as an entry level gaming PC. I started out with 4 Gigs of RAM, and all was fine. No problems when playing games, good temps, no issues at all. I then bought another of the same RAM module to make my system 8 GB. This is where I began getting BSOD's-- mostly when playing games, but some "random" ones here and there. So, I took out the new RAM module to get it ready to be returned, leaving the old module in. When I booted my system back up, I couldn't get past the login screen without a BSOD. I then tried to see if maybe the first bought module went bad, and the new is fine, so I swapped them and found the same result. I popped both of the modules in, and I could get past the login screen, but of course with the "every once and a while" BSOD's. I switched the modules to my other RAM slots (A1 and B1, to A2 and B2) and I have the same results. My motherboard does support dual channel, but I never knew if I had to enable it or it is automatically done.

BSOD's I've gotten are SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION, IRQL_NOT_LESS_OR_EQUAL, PFN_LIST_CORRUPT, and some weird things like BUGCODE_USB_DRIVER, and DRIVER_IRQL_NOT_LESS_OR_EQUAL

Windows 7 Ultimate x64
AMD Phenom x4 955 @ 3.2 GHz (no oc)
Seagate Barracuda 7200 RPM 500 GB
GeForce GTX 550 Ti (Galaxy) (HDMI output)
BioStar A870 motherboard
Corsair CX 430
8 GB (4 GB x 2) Corsair XMS 1333 MHz 240-pin (bought seperatly)

usasma · 15 Jun 2012

Run this test to see if the RAM is bad: Memory Diagnostics

As for the slots to use - each mobo is different. Read the instructions here to be sure that you're doing it correctly: A870 :: Motherboard :: BIOSTAR (Chapter 2.3 (page 8) of the larger file)

Running the last 10 memory dumps (there are 50 from 23 May to the present)

Both MSI Afterburner and Riva Tuner (along with EVGA Precision) are known to cause BSOD's on some Win7 systems. Please uninstall them immediately.

In the event that you are overclocking, please return the system to stock values and remove any overclock while we are troubleshooting. Feel free to resume the overclock once the system is stabilized.

Turn Driver Verifier off - go into verifier.exe and select "Delete existing settings" and click on "Finish" - then reboot for the settings to take effect.

XBox USB controller drivers are outdated and have caused problems recently. Please uninstall it's software and then remove the device from the system. Feel free to reinstall it once the system is stabilized.

Your Realtek audio drivers date from 2009 - please update them.

Razer drivers (danew.sys) dates from 2010 and (vHidDev.sys) dates from 2009. We have experienced some problems with Razer drivers in the past, so I'd suggest updating them if possible.

There appears to be a problem with the mcaudrv_x64.sys driver - but it's only in 2 or 3 memory dumps.
This driver belongs to ManyCam Virtual Microphone. Please uninstall it and see if that helps.

Beyond that, I have to wonder if this is a hardware problem.
I ran 10 memory dumps
They showed 5 different BSOD error codes were cited
and 7 different causes blamed

This is most likely a hardware error. They (hardware errors) are usually caused by one of these things:
- borked (broken) hardware (several different procedures used to isolate the problem device)
- overclocking - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- compatibility issues
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from Initial Hardware Diagnostics or Hardware Diagnostics ).

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:


MijXfilt.sys    Thu Nov 10 04:59:45 2011 (4EBBA091)
MpFilter.sys    Fri Mar 09 06:05:26 2012 (4F59E3F6)
RTKVHD64.sys    Thu May 31 05:21:30 2012 (4FC7381A)
RTKVHD64.sys    Wed Aug 05 05:46:28 2009 (4A7954F4)
Rt64win7.sys    Thu Feb 16 00:39:50 2012 (4F3C96A6)
STREAM.SYS      Mon Jul 13 20:06:18 2009 (4A5BCBFA)
amdxata.sys     Fri Mar 19 12:18:18 2010 (4BA3A3CA)
danew.sys       Tue Mar 23 04:37:33 2010 (4BA87DCD)
mcaudrv_x64.sys Sun Jan 29 01:54:55 2012 (4F24ED3F)
mcvidrv_x64.sys Wed Dec 14 00:44:59 2011 (4EE837DB)
nlndis.sys      Sun Feb 13 17:07:33 2011 (4D585625)
nltdi.sys       Sun Feb 13 17:07:35 2011 (4D585627)
nvhda64v.sys    Wed Apr 18 13:07:54 2012 (4F8EF4EA)
nvlddmkm.sys    Tue May 15 03:35:36 2012 (4FB20748)
speedfan.sys    Fri Mar 18 12:08:46 2011 (4D83838E)
vHidDev.sys     Mon Dec 21 08:49:58 2009 (4B2F7D06)
xusb21.sys      Wed Apr 08 10:28:44 2009 (49DCB49C)

Code:


Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061212-18470-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Tue Jun 12 15:20:26.243 2012 (UTC - 4:00)
System Uptime: 0 days 0:13:23.820
BugCheck D1, {fffff88004de3210, 2, 8, fffff88004de3210}
*** WARNING: Unable to verify timestamp for mcaudrv_x64.sys
*** ERROR: Module load completed but symbols could not be loaded for mcaudrv_x64.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : mcaudrv_x64.sys ( mcaudrv_x64+7210 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_VRF_CODE_AV_BAD_IP_mcaudrv_x64+7210
Bugcheck code 000000D1
Arguments fffff880`04de3210 00000000`00000002 00000000`00000008 fffff880`04de3210
BiosVersion = 080015 
BiosReleaseDate = 01/19/2011
SystemManufacturer = BIOSTAR Group
SystemProductName = A870
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061212-18751-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Tue Jun 12 23:54:00.957 2012 (UTC - 4:00)
System Uptime: 0 days 1:53:53.549
BugCheck A, {fffff880009e2798, 2, 1, fffff80003093f42}
Probably caused by : ntkrnlmp.exe ( nt!KiIdleLoop+d2 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  services.exe
FAILURE_BUCKET_ID:  X64_0xA_VRF_nt!KiIdleLoop+d2
Bugcheck code 0000000A
Arguments fffff880`009e2798 00000000`00000002 00000000`00000001 fffff800`03093f42
BiosVersion = 080015 
BiosReleaseDate = 01/19/2011
SystemManufacturer = BIOSTAR Group
SystemProductName = A870
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061212-18907-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Tue Jun 12 15:59:32.578 2012 (UTC - 4:00)
System Uptime: 0 days 0:38:24.780
BugCheck D1, {fffff88002d39210, 2, 8, fffff88002d39210}
*** WARNING: Unable to verify timestamp for mcaudrv_x64.sys
*** ERROR: Module load completed but symbols could not be loaded for mcaudrv_x64.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : mcaudrv_x64.sys ( mcaudrv_x64+7210 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_VRF_CODE_AV_BAD_IP_mcaudrv_x64+7210
Bugcheck code 000000D1
Arguments fffff880`02d39210 00000000`00000002 00000000`00000008 fffff880`02d39210
BiosVersion = 080015 
BiosReleaseDate = 01/19/2011
SystemManufacturer = BIOSTAR Group
SystemProductName = A870
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061212-24351-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Tue Jun 12 13:40:52.538 2012 (UTC - 4:00)
System Uptime: 0 days 1:54:51.115
BugCheck C1, {fffff98065dcef10, fffff98065dce941, 8700f0, 23}
Probably caused by : win32k.sys ( win32k!xxxMsgWaitForMultipleObjects+108 )
BUGCHECK_STR:  0xC1_23
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0xC1_23_VRF_win32k!xxxMsgWaitForMultipleObjects+108
Bugcheck code 000000C1
Arguments fffff980`65dcef10 fffff980`65dce941 00000000`008700f0 00000000`00000023
BiosVersion = 080015 
BiosReleaseDate = 01/19/2011
SystemManufacturer = BIOSTAR Group
SystemProductName = A870
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061312-17269-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Wed Jun 13 20:16:18.594 2012 (UTC - 4:00)
System Uptime: 0 days 2:14:26.170
BugCheck D1, {10, 2, 0, fffff880040567fb}
*** WARNING: Unable to verify timestamp for nltdi.sys
*** ERROR: Module load completed but symbols could not be loaded for nltdi.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : nltdi.sys ( nltdi+97fb )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_VRF_nltdi+97fb
Bugcheck code 000000D1
Arguments 00000000`00000010 00000000`00000002 00000000`00000000 fffff880`040567fb
BiosVersion = 080015 
BiosReleaseDate = 01/19/2011
SystemManufacturer = BIOSTAR Group
SystemProductName = A870
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061312-22822-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Thu Jun 14 00:33:46.811 2012 (UTC - 4:00)
System Uptime: 0 days 4:16:48.387
BugCheck C1, {fffff98033728e10, fffff98033728501, 3d01f0, 23}
Probably caused by : memory_corruption ( nt!MiCheckSpecialPoolSlop+9a )
BUGCHECK_STR:  0xC1_23
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  Skype.exe
FAILURE_BUCKET_ID:  X64_0xC1_23_VRF_nt!MiCheckSpecialPoolSlop+9a
Bugcheck code 000000C1
Arguments fffff980`33728e10 fffff980`33728501 00000000`003d01f0 00000000`00000023
BiosVersion = 080015 
BiosReleaseDate = 01/19/2011
SystemManufacturer = BIOSTAR Group
SystemProductName = A870
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061412-18298-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Thu Jun 14 14:47:02.869 2012 (UTC - 4:00)
System Uptime: 0 days 3:10:44.445
BugCheck 24, {1904fb, fffff88009fa67b8, fffff88009fa6010, fffff88001336e29}
Probably caused by : Ntfs.sys ( Ntfs! ?? ::NNGAKEGL::`string'+e9b9 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  wmplayer.exe
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_VRF_Ntfs!_??_::NNGAKEGL::_string_+e9b9
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`09fa67b8 fffff880`09fa6010 fffff880`01336e29
BiosVersion = 080015 
BiosReleaseDate = 01/19/2011
SystemManufacturer = BIOSTAR Group
SystemProductName = A870
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061412-20529-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Thu Jun 14 17:13:23.383 2012 (UTC - 4:00)
System Uptime: 0 days 2:25:42.960
BugCheck 4E, {99, 19e7cb, 3, 18cb40}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x4E_99_VRF_nt!MiBadShareCount+4c
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`0019e7cb 00000000`00000003 00000000`0018cb40
BiosVersion = 080015 
BiosReleaseDate = 01/19/2011
SystemManufacturer = BIOSTAR Group
SystemProductName = A870
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061412-27908-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Thu Jun 14 20:20:33.228 2012 (UTC - 4:00)
System Uptime: 0 days 3:06:29.804
BugCheck A, {0, 2, 0, fffff800032ecff5}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  audiodg.exe
FAILURE_BUCKET_ID:  X64_0xA_VRF_nt!KiPageFault+260
Bugcheck code 0000000A
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`032ecff5
BiosVersion = 080015 
BiosReleaseDate = 01/19/2011
SystemManufacturer = BIOSTAR Group
SystemProductName = A870
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061512-20779-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Fri Jun 15 14:20:11.116 2012 (UTC - 4:00)
System Uptime: 0 days 2:30:48.692
BugCheck C1, {fffff9802f65af20, fffff9802f65a1c1, 5540e0, 23}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+20ae89 )
BUGCHECK_STR:  0xC1_23
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0xC1_23_VRF_nvlddmkm+20ae89
Bugcheck code 000000C1
Arguments fffff980`2f65af20 fffff980`2f65a1c1 00000000`005540e0 00000000`00000023
BiosVersion = 080015 
BiosReleaseDate = 01/19/2011
SystemManufacturer = BIOSTAR Group
SystemProductName = A870
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

th0mas2 · 15 Jun 2012

I forgot to include the following:
A while back (I do not remember exactly when) I accidently installed the Windows 8 Consumer Preview over my previous Windows 7 x64 installation. After I realized that Windows 8 is shit, I reinstalled Windows 7 x64. This led to my old data being put into Windows.old, along with another windows.old (the 1st Windows 7 installation.) I tried bringing some files over and learned that some programs and such worked fine, while others had to be re downloaded and re installed. As for the slot installation--my motherboard asks for having the RAM modules in slots A1+B1 or A2+b2 for dual channel--now, I was hoping to find someone who knew a lot about the BIOS that my mobo uses :P (some version of American Megatrends) as I do not know what I am really doing in there at all, and my mobo's manual is a piece of piss explaining what different options mean in the BIOS. Because (aside from it possibly being my jacked up software installs and all that) I thought it may have something to do with settings in my BIOS (like the RAM timings and all of that) but I did not really know what to have them set too or anything. Also, when I first started investigating the problem right after I installed the new RAM, I saw many people on the internet saying to make sure I have Dual Channel enabled, or if it is enabled, try to disable it, but I see no such things in my BIOS. I don't know. It is very strange to me. I think I may do a system overhaul and reinstall everything from complete scratch if the things you recommended do not fix it. I am slowly going down the list of your suggestions. I will get back to you soon enough with results on each one. Thank you for your help so far.

usasma · 16 Jun 2012

I'm not well-versed in memory settings manipulation in the BIOS. It's my opinion that, if you set the BIOS to default/Fail Safe values that it should work as intended. If it doesn't then (again IMO) there's a problem with the motherboard.

If the mobo manual says put the RAM in A1+B1 or A2+B2 - then that's what you've gotta do.
Run the memory test from the link that I gave above.
If still concerned, run Prime95. It'll stress the memory and may give errors when Memtest doesn't.

BSOD's that I think are from a corrupt RAM module.

Variety of BSOD's after installing RAM