Windows 7: Multiple BSODs, ntoskrnl.exe only apparent connection

ILikeEggs · 17 Jul 2012

Running Windows 7 Home Premium 64-bit, Full Retail version
System hardware is roughly 4 months old: hardware details should be attached to this profile.
Age of OS installation is about a week (attempted a complete reinstall to fix the issue)

First experienced BSODs a few weeks ago while playing Minecraft; since then have had many crashes, only a few of which have successfully written to a dump file. BSOD occurs mostly while playing any kind of game, from Minecraft to Facebook games. Crashes (many without associated dump files) have happened from just after POST, working in BIOS, or literally any time that the computer is on.

BlueScreenView seems to indicate that ntoskrnl.exe seems the be the center of the problem, though there are a few UnknownModules that have arisen; I've flashed the BIOS to the most recent version and updated video card drivers, but ntoskrnl.exe continues to show up in dumps. I've tried Driver Verifier 3 times, each time experiencing a total system freeze after logging in; after leaving it for hours, it apparently crashes and reboots, since I always find it back on the log in screen.

After some crashes, a "DQS training failed on previous boot" message displays: if this indicates a memory issue either in incompatibility or just a bad stick/slot, I'm afraid I'll have no way of checking due to the system crashing so often, making a memtest86 test seemingly impossible to properly execute.

I hope that the information provided is enough to help solve the issue(s) at hand. If anything additional is needed, just say the word! I'll be logging of for the night for now, but I'll be checking back throughout the day tomorrow. Thanks in advance to anyone who can help!

usasma · 18 Jul 2012

Memtest runs from a bootable CD/USB drive and runs outside of Windows.
Have you tried to run Memtest? If so, does the system crash even though it's not in Windows?
If that's so, then this is a hardware problem that needs to be investigated.

Please attempt to run these free diagnostics to help rule out some of the more common problems: Initial Hardware Diagnostics Please be sure to let us know the results - especially of the anti-malware tests

MSINFO32 shows one of the BSOD's blaming McAfee. Please try this:

Quote:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the McAfee from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of McAfee using this free tool: How to uninstall or reinstall supported McAfee products using the McAfee Consumer Products Removal tool (MCPR.exe) (This link has changed a lot. If it doesn't work, search for McAfee Consumer Products Removal Tool)
- IMMEDIATELY install and update the free antivirus, then check to ensure that the Windows Firewall is turned on.
- check to see if this fixes the BSOD's
NOTE: NEVER run more than 1 anti-virus, firewall, Internet Security/Security Center application at the same time.

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 Windows 7 systems.

Quote:

Please uninstall all AMD/ATI video stuff from Control Panel...Programs...Uninstall a program
Then, download (but DO NOT 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)
Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure

If the device (AODDriver or AODDriver4.01) remains a problem, 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 safely 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.

IMO there's some serious damage to the OS here. If it's not due to hardware, then it's most likely (again IMO) to be due to malware.

If the above steps don't stop the BSOD's, please zip up and upload any new memory dumps with your next post - and we'll see what we can figure out from there.

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:


AODDriver2.sys Tue Mar 06 04:55:00 2012 (4F55DEF4)
AtihdW76.sys   Thu Feb 23 07:30:12 2012 (4F463154)
AtihdW76.sys   Wed Nov 17 07:02:04 2010 (4CE3C43C)
MOBK.sys       Thu Dec 31 22:20:07 2009 (4B3D69E7)
McPvDrv.sys    Wed Mar 30 17:00:49 2011 (4D939A01)
Rt64win7.sys   Fri Jun 10 02:33:15 2011 (4DF1BAAB)
amdiox64.sys   Thu Feb 18 10:17:53 2010 (4B7D5A21)
amdxata.sys    Fri Mar 19 12:18:18 2010 (4BA3A3CA)
atikmdag.sys   Mon Jun 11 12:59:31 2012 (4FD623F3)
atikmdag.sys   Tue Apr 19 21:53:29 2011 (4DAE3C99)
atikmpag.sys   Mon Jun 11 12:26:14 2012 (4FD61C26)
atikmpag.sys   Tue Apr 19 21:22:32 2011 (4DAE3558)
cfwids.sys     Mon Feb 13 18:40:56 2012 (4F399F88)
g?            Fri May 04 04:18:59 2012 (4FA390F3)
g?            Sat Feb 05 11:52:49 2011 (4D4D8061)
g?            Sat Nov 20 08:00:25 2010 (4CE7C669)
kdcom.d?l      Sat Feb 05 11:52:49 2011 (4D4D8061)
mfeapfk.sys    Mon Feb 13 18:37:01 2012 (4F399E9D)
mfeavfk.sys    Mon Feb 13 18:37:27 2012 (4F399EB7)
mfefirek.sys   Mon Feb 13 18:40:07 2012 (4F399F57)
mfehidk.sys    Mon Feb 13 18:36:14 2012 (4F399E6E)
mfenlfk.sys    Mon Feb 13 18:36:45 2012 (4F399E8D)
mfewfpk.sys    Mon Feb 13 18:36:29 2012 (4F399E7D)

Code:


Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\071112-28236-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Wed Jul 11 11:48:27.660 2012 (UTC - 4:00)
System Uptime: 0 days 0:06:05.205
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+52a )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x1E
FAILURE_BUCKET_ID:  X64_0x1E_nt!PoIdle+52a
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\071112-36207-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Wed Jul 11 09:01:35.400 2012 (UTC - 4:00)
System Uptime: 0 days 0:03:11.945
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for mfefirek.sys
*** ERROR: Module load completed but symbols could not be loaded for mfefirek.sys
Probably caused by : mfefirek.sys ( mfefirek+3968a )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  McSvHost.exe
FAILURE_BUCKET_ID:  X64_0x1E_mfefirek+3968a
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = 080015 
BiosReleaseDate = 08/11/2010
SystemManufacturer = ECS
SystemProductName = A885GM-A2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\071312-22120-01.dmp]
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`0027dc50
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`0027dc50
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Fri Jul 13 05:47:42.743 2012 (UTC - 4:00)
System Uptime: 0 days 9:59:12.288
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`0027dc50
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`0027dc50
BugCheck 7E, {ffffffffc0000005, fffff88004d29097, fffff8800332b9e8, fffff8800332b240}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x7E
Bugcheck code 0000007E
Arguments ffffffff`c0000005 fffff880`04d29097 fffff880`0332b9e8 fffff880`0332b240
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\071512-18345-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Jul 15 15:53:04.610 2012 (UTC - 4:00)
System Uptime: 0 days 0:19:40.780
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
BugCheck 7F, {8, 80050031, 6f8, fffff80002a9d542}
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+52a )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0x7f_8_nt!PoIdle+52a
Bugcheck code 0000007F
Arguments 00000000`00000008 00000000`80050031 00000000`000006f8 fffff800`02a9d542
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\071512-21434-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Jul 15 23:17:41.207 2012 (UTC - 4:00)
System Uptime: 0 days 0:03:04.377
BugCheck 3B, {c0000005, fffff80002d549ae, fffff88008e66720, 0}
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1de )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  TeaTimer.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!CmpKcbCacheLookup+1de
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02d549ae fffff880`08e66720 00000000`00000000
BiosVersion = 080015 
BiosReleaseDate = 08/11/2010
SystemManufacturer = ECS
SystemProductName = A885GM-A2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\071612-16801-01.dmp]
*** WARNING: Unable to verify timestamp for g?
*** ERROR: Module load completed but symbols could not be loaded for g?
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Mon Jul 16 19:03:22.264 2012 (UTC - 4:00)
System Uptime: 0 days 0:23:23.809
*** WARNING: Unable to verify timestamp for g?
*** ERROR: Module load completed but symbols could not be loaded for g?
*** WARNING: Unable to verify timestamp for g?
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
BugCheck 135, {ffffffffc0000005, fffff8800952b790, fffff8800110a2f0, fffff8a000086c70}
Probably caused by : g?_ ( nt+7f1c0 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x135
Bugcheck code 00000135
Arguments ffffffff`c0000005 fffff880`0952b790 fffff880`0110a2f0 fffff8a0`00086c70
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\071612-17050-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Mon Jul 16 17:56:45.278 2012 (UTC - 4:00)
System Uptime: 0 days 2:01:00.823
*** WARNING: Unable to verify timestamp for Unknown_Module_fffff880`0400b010
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_fffff880`0400b010
BugCheck 34, {50853, fffff88003193868, fffff880031930c0, fffff880012260ce}
Probably caused by : Unknown_Module_fffff880_0400b010 ( Unknown_Module_fffff880_0400b010+2737e2 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x34
FAILURE_BUCKET_ID:  X64_0x34_Unknown_Module_fffff880_0400b010+2737e2
Bugcheck code 00000034
Arguments 00000000`00050853 fffff880`03193868 fffff880`031930c0 fffff880`012260ce
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\071612-18080-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Mon Jul 16 21:16:34.415 2012 (UTC - 4:00)
System Uptime: 0 days 2:12:12.586
BugCheck A, {ffffe680, 8, 1, fffff80002ae0f8f}
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0xA
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
Bugcheck code 0000000A
Arguments 00000000`ffffe680 00000000`00000008 00000000`00000001 fffff800`02ae0f8f
BiosVersion = 080015 
BiosReleaseDate = 08/11/2010
SystemManufacturer = ECS
SystemProductName = A885GM-A2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\071612-19640-01.dmp]
*** WARNING: Unable to verify timestamp for Unknown_Module_665d99a8`00043161
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_665d99a8`00043161
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Jul 15 23:55:50.618 2012 (UTC - 4:00)
System Uptime: 0 days 0:12:27.163
*** WARNING: Unable to verify timestamp for Unknown_Module_665d99a8`00043161
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_665d99a8`00043161
BugCheck 7E, {ffffffffc0000005, fffff88004a49098, fffff88005f9b9e8, fffff88005f9b240}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x7E
Bugcheck code 0000007E
Arguments ffffffff`c0000005 fffff880`04a49098 fffff880`05f9b9e8 fffff880`05f9b240
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

ILikeEggs · 19 Jul 2012

The system hasn't actually crashed outside of Windows, but it does freeze up seemingly indefinitely; a number of times in BIOS/after POST (mostly right before SATA check or after "DQS training failed" messages).

As I type this, Memtest86+ is frozen at WallTime 13:06, pass #0 20% complete, 100% through test 5, with 574720 errors found. The area that normally displays the error information is a solid red box. The red + in Memtest86+ is still flashing, strangely.

As soon as I get back into Windows, I'll remove the McAfee and AMD components and replace them as you specified, as well as upload the 1 new memory dump that's occurred; though I've had 2 BSODs, errors 0x1b and 0x1e, only the 0x1e was fully written to memory dump before it shut down. No idea why it failed to do so on the 0x1b, since they both happened while playing Minecraft.

I've tried digging through the BIOS to find any overclocking utilities that may be switched on, but no luck; the closest I've come otherwise is having the video card's fan run a bit faster than stock via MSI Afterburner(which I removed after seeing in another thread that Afterburner is known to cause problems).

After letting Memtest86 sit frozen for close to an hour now, I think I'm going to throw in the towel and reset the system, and see if I can get in Windows long enough to at least pull the memory dump to upload it. I'll post back with the dump file as soon as I have it for uploading.

ILikeEggs · 20 Jul 2012

Update: after a few more failed Memtest attempts(making it as far as test #7, then freezing or halting due to unexpected error), it seems leaving it overnight somehow did the trick; when I came back to it, it had performed 8 successful passes, with about 50% into the 9th. 0 errors detected throughout all scans as well. I only had 1 RAM stick in (previous attempts were with both 4GB sticks), so maybe that indicates a problem with either the second stick or the slot it was in; I'll find out tonight/tomorrow since I'll be running another test, with the sticks swapped.

SeaTools from Seagate came up with no errors on the hard drive.

I ran the computer through as many of the linked anti-malware tests as I could:

F-secure came up with a single tracking cookie.
Trendmicro, Bitdefender, Eset, Mcafee, Kaspersky, and Panda all came up clean.
Avast's single file scanner seemed impractical to use to scan my entire computer.
ca and ewido came up with page/server not found.
Window security's trojan scanner crashed IE after getting to ~2-4% complete every time in 10 attempts.

Windows Security Essentials also came up 100% clean when I scanned after removing all McAfee off the computer.

I tore out and reinstalled just the chipset and video drivers from AMD; however, I found in device manager that the Overdrive driver somehow got reinstalled anyway, so I removed it again just to make sure it won't cause an issue.

Finally, I zipped up all the memory dumps in the minidump folder, which are in the attachment. It seems that my previous post was perhaps mistaken, since I see neither of the mentioned error code 0x1b or 0x1e dumps that occurred from Minecraft. However, there is a code 0x3b caused by Ntfs.sys and ntoskrnl.exe.

I believe that that covers everything you needed me to do, though if there's anything else, I'll get you what you need as best I can of course!

usasma · 21 Jul 2012

If you're getting memory errors in MemTest86+, then it's most likely your RAM that's the problem.
Follow the procedure from Step 6 onward to isolate which sticks/slots are at fault ( Memory Diagnostics )

You can also run Prime95 to see if it spits out errors (it's listed on the Hardware Diagnostics page also).
Errors when running the Blend test usually indicates a RAM problem
Errors running the Small FFT or Large FFT tests are usually other things (CPU cache or the memory controller) - but they still can be caused by RAM also.

Don't worry about the memory dumps right now - the RAM problems in MemTest86+ are the main concern right now.

ILikeEggs · 21 Jul 2012

I've tested the sticks individually, both coming up as good after 7 passes each, and using just the first stick I checked the second slot which also came up good. I've been working on these tests ever since the first time it came up with solid red in the errors box (that seemed like the logical next step).

Prime95 is downloaded and running a blend test now, so I'll let it sit for a few hours and check to see if it's giving any errors...

On a hunch, I checked to see if the RAM and motherboard were compatible(via checking the motherboard's manual). Due to the RAM not being listed in the Qualified Vendor List, either in the shipped manual or the online version, I'm beginning to think a simple hardware incompatibility could be one of persisting issues... I'll wait till the results from Prime95 show up before I start jumping to any conclusions though.

karlsnooks · 22 Jul 2012

Info on your memory:

# **********************INSTRUCTIONS**************************
# STEP 1 ** RUN POWERSHELL AS ADMINISTRATOR ******************
# ************************************************************
#
# WIN key | type POWERSHELL | do NOT hit ENTER |
# in the PROGRAMS list, right-click on WINDOWS POWERSHELL |
# choose "Run as administrator" |
# Click on the YES button (if such appears)
#
# WIN key = key with Microsoft log on top
#
# for the guru:
# WIN | type POWERSHELL | CTRL+SHIFT+ENTER key combo | ALT+Y keycombo
# ************************************************************
# STEP 2 ** COPY AND PASTE ***********************************
# ************************************************************
#
# COPY the script using CTRL+C,
# COPY every line of script down thru both EXIT statements
#
# PASTE into Powershell
#----Right-Click at the PowerShell Prompt
#----(Ctrl+V does not work)
#
# Start copying with first script line without a # at start of the line
# Note: Actually, you can paste the entire file if you rather
#-------Lines starting with a # are ignored by PowerShell
# ************************************************************
# STEP 3 ** SCRIPT OUTPUT & SCRIPT PURPOSE *******************
# ************************************************************
# --The script output and purpose is given at the very front of the script
#
# --The script output and purpose is given at the very front of the script
#
# ************************************************************
# ***************** NOTE - POWERSHELL VERSION*****************
# if you receive this error msg:
#--The system can not find the path specified
# you may need to update your PowerShell
# you must be using Powershell 2.0 or later.
#
# To determine your Powershell version:
#---Run PowerShell
#---enter $host.version
#---you should see at least:
# Major Minor Build Revision
# ----- ----- ----- --------
# 2......0......-1.....-1
#
# If you do not see the above, update your Vista/Win 7.
# ************************************************************
# *************** NOTE - EXECUTION POLICY*********************
# If you haven't set the execution policy, you may need to:
#---Run PowerShell
#---enter SET-EXECUTIONPOLICY -EXECUTIONPOLICY REMOTESIGNED
# ************************************************************

Script:

  # ***********************************************
# OUTPUT: MemInfo.TXT file on your desktop
# contains info about your memory
# ***********************************************

function get-ID { 
  param ([string]$title, [int]$arraycnt, [int]$arrayndx) 
  $id = " " + $title + " "
  If ($arraycnt -ne 1) {$id = $id + [string]$arrayndx + " "}
  $id }
function get-title { param ([string]$id) 
  $hashes = ([int](51 - $id.length)/2)
  $hashstr = '#' * $hashes
  $title = $hashstr + $id + $hashstr
  If ($title.length -le 51) {$title += "#"}
  $title  }
$sterne = "*" * 79
$obj = New-Object PSObject
$os = gwmi win32_operatingsystem
$id = get-id "OS" 1 0

$PhyMemArray = @(gwmi win32_PhysicalMemoryArray)
$cnt = $phymemarray.count
for ($ndx=1; $ndx -le $cnt; $ndx++) {
  $d = $phymemarray[$ndx -1]
  $id = get-id "PHYSICAL MEMORY ARRAY" $cnt $ndx
  $obj | add-member -membertype noteproperty -name ( Get-title $Id ) -value $sterne
  $obj | add-member -membertype noteproperty -name (" Maximum Memory Capacity") -value([string][int]($d.maxcapacity/1048576) + " GB")
  $obj | add-member -membertype noteproperty -name (" Number of Memory Devices") -value($d.memorydevices)
}

$arr = @(gwmi win32_PhysicalMemory)
$cnt = $arr.count
for($i=1; $i -le $cnt; $i++){
  $d = $arr[$i-1]
  $id = get-id "PHYSICAL MEMORY" $cnt $i
  $obj | add-member -membertype noteproperty -name (get-title $id) -value $sterne
  $obj | add-member -membertype noteproperty -name ($id + "Bank Label") -value($d.banklabel)
#  $obj | add-member -membertype noteproperty -name ($id + "Tag") -value($d.tag)
  $obj | add-member -membertype noteproperty -name ($id + "Manufacturer") -value($d.manufacturer)
  $obj | add-member -membertype noteproperty -name ($id + "Part Number") -value($d.partnumber)
  $obj | add-member -membertype noteproperty -name ($id + "Serial Number") -value($d.serialnumber)
  $obj | add-member -membertype noteproperty -name ($id + "Capacity") -value([string][int]($d.capacity/1073741824) + " GB")
  $obj | add-member -membertype noteproperty -name ($id + "Device Locator") -value($d.devicelocator)
  $obj | add-member -membertype noteproperty -name ($id + "Data Width") -value($d.datawidth)
  $obj | add-member -membertype noteproperty -name ($id + "Speed") -value($d.speed)
}

$Arr = @(gwmi win32_memoryarray)
$cnt = $arr.count
for($i=1; $i -le $cnt; $i++){
  $d = $arr[$i-1];
  $id = get-id "MEMORY ARRAY" $CNT $I
  $obj | add-member -membertype noteproperty -name (get-title $id) -value $sterne
  $obj | add-member -membertype noteproperty -name ($id + "Device ID") -value($d.deviceid)
  $obj | add-member -membertype noteproperty -name ($id + "Starting Address") -value($d.startingaddress)
  $obj | add-member -membertype noteproperty -name ($id + "Ending Address") -value($d.endingaddress)
}

$Arr = @(gwmi win32_memorydevice)
$cnt = $arr.count
for($i=1; $i -le $cnt; $i++){
  $d = $arr[$i-1];
  $id = get-id "MEMORY DEVICE" $cnd $i
  $obj | add-member -membertype noteproperty -name (get-title $id) -value $sterne
#  $obj | add-member -membertype noteproperty -name ($id + "Device ID") -value($d.deviceid)
  $obj | add-member -membertype noteproperty -name ($id + "Starting Address") -value($d.startingaddress)
  $obj | add-member -membertype noteproperty -name ($id + "Ending Address") -value($d.endingaddress)
}
$obj > $env:userprofile\desktop\MemInfo.txt

EXIT
EXIT

ILikeEggs · 22 Jul 2012

After finding PowerShell and verifying that it's version information matched what you posted, I ran the script, and the file it created is in the attachment. I'm not going to pretend to understand exactly what the script did, but hopefully the information in the text file will be of use to you!

karlsnooks · 22 Jul 2012

Yes, your memory is not correct for your motherboard.

Be sure and buy ram that your manufacturer has listed as compatible.
Do not trust the words of any electronics/computer store or department.

ILikeEggs · 25 Jul 2012

Payday just came, so the proper replacement memory is on it's way. I checked between the manual, and the manufacturer of both the motherboard and the replacement ram to be sure that the sticks I'd selected were still compatible. If these new ones don't resolve the issue, I'll be sure to post back here. Thanks again to both of you for your help, users usasma and karlsnooks!

Windows 7: Multiple BSODs, ntoskrnl.exe only apparent connection

Multiple BSODs, ntoskrnl.exe only apparent connection problems?