Multiple BSOD's on new machine

[Danny72170]

Recently bought a new machine (my first with Windows 7) and have gotten a series of BSOD's. I've attached the dump info and other info requested in the sticky post on this forum.

Computer specs according to Newegg.com (where I bought the machine) are as follows:
CyberpowerPC
Model Gamer Xtreme 1093
Type Gaming
Processor Intel Core i7-960 3.2GHz
Processor Main Features 64 bit Quad-Core Processor
Memory 6GB (3x2GB) DDR3 1333
Hard Drive 1TB (1 x 1TB) SATA-II 3.0Gb/s 7200RPM HDD
Optical Drive 1 24X DVD±R/±RW Dual Layer Drive
Graphics NVIDIA Geforce GTX 460 1GB PCI-Express Graphics
Audio Sound card - Integrated
Ethernet Gigabit Ethernet
Power Supply 700W
Keyboard Xtreme Gear USB Keyboard
Mouse Xtreme Gear USB Mouse
Operating System Windows 7 Home Premium 64-bit
Special Features Coolermaster HAF 912 Gaming Tower

Trying to research it myself I kept coming to the conclusion that it was a ram or video card (driver or the card itself) problem but I'm not a troubleshooter and know just enough to know I don't know much. Please help if you can and let me know if you need more info.

 

[JMH]

Recently bought a new machine (my first with Windows 7) and have gotten a series of BSOD's. I've attached the dump info and other info requested in the sticky post on this forum.

Computer specs according to Newegg.com (where I bought the machine) are as follows:
CyberpowerPC
Model Gamer Xtreme 1093
Type Gaming
Processor Intel Core i7-960 3.2GHz
Processor Main Features 64 bit Quad-Core Processor
Memory 6GB (3x2GB) DDR3 1333
Hard Drive 1TB (1 x 1TB) SATA-II 3.0Gb/s 7200RPM HDD
Optical Drive 1 24X DVD±R/±RW Dual Layer Drive
Graphics NVIDIA Geforce GTX 460 1GB PCI-Express Graphics
Audio Sound card - Integrated
Ethernet Gigabit Ethernet
Power Supply 700W
Keyboard Xtreme Gear USB Keyboard
Mouse Xtreme Gear USB Mouse
Operating System Windows 7 Home Premium 64-bit
Special Features Coolermaster HAF 912 Gaming Tower

Trying to research it myself I kept coming to the conclusion that it was a ram or video card (driver or the card itself) problem but I'm not a troubleshooter and know just enough to know I don't know much. Please help if you can and let me know if you need more info.

Hi Danny and welcome

Easy and straight forward. These crashes point to your MacAffee. Remove and replace it with Microsoft Security Essentials and the Windows firewall.


How to uninstall or reinstall supported McAfee consumer products using the McAfee Consumer Products Removal tool (MCPR.exe)

http://www.microsoft.com/security_essentials/

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\JMH\Desktop\Windows_NT6_BSOD_jcgriff2\050611-24796-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02e05000 PsLoadedModuleList = 0xfffff800`0304ae90
Debug session time: Fri May  6 17:10:49.088 2011 (GMT-4)
System Uptime: 0 days 3:31:44.104
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff880010888da, fffff88008211ab0, 0}

Probably caused by : mfehidk.sys ( mfehidk+d8da )

Followup: MachineOwner
---------

 

[usasma]

I was composing my post while JMH was posting. Please follow their directions first.

First, please open Device Manager and check under the Network Adapters section.
Right click on each of the following devices and select "Uninstall":
- Teredo
- ISATAP
- 6to4
- unknown

If needed, these devices will return when you reboot. In most cases they aren't needed and won't come back (so don't worry about them).

6 memory dumps from 25 Apr to 07 May 2011
3 different BSOD error codes
3 different causes are blamed - and 4 of the 6 are directly blaming your McAfee security software
The last 3 memory dumps are VERIFIER_ENABLED_VISTA_MINIDUMP's
Please be sure to STOP Driver Verifier from running (by selecting the "Delete existing settings" in the first screen)

To skip over all the extra info - my suspicion is that there's a corruption of your McAfee security program. Please do the following:

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 consumer products using the McAfee Consumer Products Removal tool (MCPR.exe)
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's

OLDER DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please update these drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers:

[FONT=lucida console]
amdxata.sys       Fri Mar 19 12:18:18 2010 (4BA3A3CA) - Windows Update will take care of this
mfehidk.sys       Wed Oct 06 15:55:49 2010 (4CACD445)
mfewfpk.sys       Wed Oct 06 15:56:04 2010 (4CACD454)
GEARAspiWDM.sys   Mon May 18 08:17:04 2009 (4A1151C0)
mfenlfk.sys       Wed Oct 06 15:56:13 2010 (4CACD45D)
mfefirek.sys      Wed Oct 06 15:59:47 2010 (4CACD533)
mfeavfk.sys       Wed Oct 06 15:56:49 2010 (4CACD481)
cfwids.sys        Wed Oct 06 16:00:36 2010 (4CACD564)
mfeapfk.sys       Wed Oct 06 15:56:26 2010 (4CACD46A)
nvhda64v.sys      Thu Mar 03 10:59:02 2011 (4D6FBAC6)
nvhda64v.sys      Tue Mar 09 20:48:17 2010 (4B96FA61)
mferkdet.sys      Wed Oct 06 15:57:05 2010 (4CACD491)
nvlddmkm.sys      Mon Jun 14 00:53:52 2010 (4C15B5E0)
nvBridge.kmd      Mon Jun 14 00:50:31 2010 (4C15B517)
Rt64win7.sys      Fri Jan 21 02:34:00 2011 (4D3936E8)
hiber_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113) - This will be updated after Windows Update updates the dumpata.sys file.
hiber_atapi.sys   Mon Jul 13 19:19:47 2009 (4A5BC113) - This will be updated after Windows Update updates the atapi.sys file.
hiber_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) - This will be updated after Windows Update updates the dumpfve.sys file.
[/FONT]

http://www.carrona.org/dvrref.html#amdxata.sys
http://www.carrona.org/dvrref.html#mfehidk.sys
http://www.carrona.org/dvrref.html#mfewfpk.sys
http://www.carrona.org/dvrref.html#GEARAspiWDM.sys
http://www.carrona.org/dvrref.html#mfenlfk.sys
http://www.carrona.org/dvrref.html#mfefirek.sys
http://www.carrona.org/dvrref.html#mfeavfk.sys
http://www.carrona.org/dvrref.html#cfwids.sys
http://www.carrona.org/dvrref.html#mfeapfk.sys
http://www.carrona.org/dvrref.html#nvhda64v.sys
http://www.carrona.org/dvrref.html#nvhda64v.sys
http://www.carrona.org/dvrref.html#mferkdet.sys
http://www.carrona.org/dvrref.html#nvlddmkm.sys
http://www.carrona.org/dvrref.html#nvBridge.kmd
http://www.carrona.org/dvrref.html#Rt64win7.sys
http://www.carrona.org/dvrref.html#hiber_dumpata.sys
http://www.carrona.org/dvrref.html#hiber_atapi.sys
http://www.carrona.org/dvrref.html#hiber_dumpfve.sys

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sat May  7 11:50:26.522 2011 (UTC - 4:00)
System Uptime: 0 days 1:00:36.538
Probably caused by : hardware ( afd!AfdTLCompleteBufferUserReceive+159 )
BUGCHECK_STR:  0x1E_c000001d
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
Bugcheck code 0000001E
Arguments ffffffff`c000001d fffff880`0ae14bc0 00000000`00000000 00000000`00000000
BiosVersion = V8.14
BiosReleaseDate = 11/02/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3208
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Fri May  6 17:10:49.088 2011 (UTC - 4:00)
System Uptime: 0 days 3:31:44.104
Probably caused by : mfehidk.sys ( mfehidk+d8da )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x3B
PROCESS_NAME:  wmpnetwk.exe
FAILURE_BUCKET_ID:  X64_0x3B_VRF_mfehidk+d8da
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`010888da fffff880`08211ab0 00000000`00000000
BiosVersion = V8.14
BiosReleaseDate = 11/02/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3208
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Tue May  3 20:30:28.443 2011 (UTC - 4:00)
System Uptime: 0 days 1:45:41.443
Probably caused by : mfehidk.sys ( mfehidk+d8de )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x3B
PROCESS_NAME:  nvSCPAPISvr.ex
FAILURE_BUCKET_ID:  X64_0x3B_VRF_mfehidk+d8de
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`0108d8de fffff880`07892ab0 00000000`00000000
BiosVersion = V8.14
BiosReleaseDate = 11/02/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3208
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Fri Apr 29 18:33:47.585 2011 (UTC - 4:00)
System Uptime: 0 days 0:47:44.710
Probably caused by : mfehidk.sys ( mfehidk+d8da )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  mcshield.exe
FAILURE_BUCKET_ID:  X64_0x3B_mfehidk+d8da
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`011628da fffff880`0906fb10 00000000`00000000
BiosVersion = V8.14
BiosReleaseDate = 11/02/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3208
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Tue Apr 26 15:54:02.508 2011 (UTC - 4:00)
System Uptime: 0 days 5:12:22.524
*** WARNING: Unable to verify timestamp for mfehidk.sys
*** ERROR: Module load completed but symbols could not be loaded for mfehidk.sys
Probably caused by : mfehidk.sys ( mfehidk+48204 )
BUGCHECK_STR:  0x4E_2
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  rift.exe
FAILURE_BUCKET_ID:  X64_0x4E_2_mfehidk+48204
Bugcheck code 0000004E
Arguments 00000000`00000002 00000000`0018301a 00000000`001bffff 00000000`00000001
BiosVersion = V8.14
BiosReleaseDate = 11/02/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3208
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Mon Apr 25 19:00:51.728 2011 (UTC - 4:00)
System Uptime: 0 days 4:48:48.744
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`0016601a 00000000`00000002 00000000`00000001
BiosVersion = V8.14
BiosReleaseDate = 11/02/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3208
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/FONT]

 

[Danny72170]

Thank you. I've followed your instructions. Hopefully this will fix the problem with the BSOD's.

I would have never guessed the antivirus program was the problem.

I do have another problem but it's less severe than the BSOD's so while I have you here. When I turn the computer on it loads up fine until after the screen saying starting windows and then the only thing that will come up is the wallpaper. No taskbar or icons. I can get around this by hitting the sleep button on my keyboard and letting it go into sleep mode. Then when I wake it up it comes up to the desktop like normal. Not too big of a deal compared to my other troubles but I was wondering if there's a setting in Windows or something else making it load Windows but only show the wallpaper and nothing else.

 

[Danny72170]

A couple more questions. I downloaded the Microsoft Security Essentials and I'm running a scan with it before I redownload Mcafee.

First question: I Mcafee necessary if I have MSE?
Second Question: Can both run together? Or should I uninstall MSE before reinstalling Mcafee?

 

[usasma]

NEVER run 2 antivirus (or firewalls) at the same time!!!

Update the drivers that I suggested in my previous post. In particular, update the video, storage, and chipset drivers. If the problem still happens, post back and we'll try other stuff.

 

[Danny72170]

Can I run MSE as my antivirus or should I reinstall macafee? If MSE is fine then I assume the drivers related to macafee in your previous post are unnecessary, correct? Also, are the dates listed in the links for the drivers the latest version?

 

[usasma]

I prefer MSE myself (and run it on all of my systems)
If you stay with MSE, then the McAfee drivers are unneeded and can be removed (using the tool I suggested).

As for the dates, drivers aren't usually listed by date - rather they're listed by the package/vefsion that they're installing. The individual drivers within the package can have different dates - so it's important to be sure that you get the latest package.

 

[Danny72170]

New BSOD

Got another BSOD today (5/9). I've removed macafee including using the removal tool like you said and reinstalled the drivers (all of them I think). I've enclosed a new crash report zip file that includes today's crash. The blue screen came up with a different error than what was usually coming up (PFN List Corrupt instead of System Service Exception)

 

[usasma]

This memory dump still blames a system service (it's in the stack text), so I have to wonder if we've fixed things.
There is (IMO) still a hint of networking in the dump files, so I'd have to wonder about your networking card/drivers.

3 things to try (try the last one first):
- updating your networking drivers from the Realtek website: Realtek
- try another network card (they're relatively cheap, about $15 at most major US retailers). Besides, it's always good to have a spare on hand in case your current card dies.
- running Driver Verifier according to these instructions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, 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).

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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\050911-16156-01.dmp]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Mon May  9 14:58:16.885 2011 (UTC - 4:00)
System Uptime: 0 days 3:48:43.885
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  rift.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`0006f2a7 00000000`00000002 00000000`0006f1a6
BiosVersion = V8.14
BiosReleaseDate = 11/02/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3208
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/FONT]

 

[Danny72170]

I set up driver verifier as you said and got a BSOD when windows restarted. The screen went by fast and the only info I saw before it restarted was IRQL and some other stuff I didn't get a chance to read. On the restart after the BSOD it ran repair and windows restarted. I've attached the file requested and made sure driver verifier is off.

I did notice in the bugcheck summary in your post rift.exe. Rift was the game I was playing when nearly every BSOD happened (one happened while I was playing dominoes on pogo.com and once while on facebook playing games). Seeing this is an online game (an MMO) it might be relevant if the problem is the network card or its driver.

Since the BSOD happened on the restart I never got a chance to try playing Rift or do anything else. I figured I'd wait for you before I screw around too much.

 

[usasma]

I'm running a bit late for work, but here's what I have so far...
Rift isn't an issue, especially since it doesn't always occur. Rather it's likely to be a piece of hardware that Rift uses - just like the other processes.

Don't forget to turn Driver Verifier off.

Driver Verifier points at Pool Corruption as the cause. Since it doesn't name a 3rd party driver (that's what the settings are used for), then it's likely that a 3rd party driver isn't at fault. But since it crashed anyway, there must be another cause.

The most common cause is hardware, with the next most common being Windows (and malware).

The easiest thing to rule out would be Windows - but that'll require a wipe of your hard drive and a reinstall of Windows.

Instead of that, I'd first suggest these free hardware diagnostics:

I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Free Online AntiMalware Scanners (read the details at the link)

Then, if the above tests pass, I'd try these free stress tests:

FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
NOTE: Set the alarm to go off at 90ºC. Then watch the system from that point on. If the system doesn't display a temperature, watch it constantly and turn it off at the first sign of video problems. DO NOT leave it it unmonitored, it can DAMAGE your video card!!!
- Click "Quit" to exit

Prime95 download site: Free Software - GIMPS
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight please run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
More details on the use of this test: Torture test your CPU with Prime95

Two other video stress tests (may be more stressful than FurMark):
Video Memory stress Test - МИРNVIDIA / Утилиты / VMT
Artifact Locator - МИРNVIDIA / Утилиты / Artifact Locator
Sorry, but I don't read the language that this website is made in.

Another interesting test that just came to my attention: Download - OCCT Website english
USE AT YOUR OWN RISK - program doesn't have a whole bunch of safety features to protect you from yourself!

BSOD BUGCHECK SUMMARY

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\050911-25515-01.dmp]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Mon May  9 21:57:02.250 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:13.265
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+f33 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_VRF_nt!ExDeferredFreePool+f33
Bugcheck code 0000000A
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`02ee3015
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[Danny72170]

It may take me a while to get some blank cd's for the memory test as I will need assistance from a friend or family member to go buy them or have someone buy them for me.

I did run a malware scan using bitdefender and nothing bad was found.

I'll get back to you when I have run the memory test.

 

[usasma]

While waiting you can try the built in Windows 7 memory diagnostic (not as accurate IMO, but better than nothing): http://www.sevenforums.com/tutorials/715-memory-diagnostics-tool.html

 

[Danny72170]

I ran the windows memory test several times when I first started getting the BSOD's and no errors were found.

I did find some blank disks and ran the memtest86+ test. I did 7 passes and 5 errors were found, all happened on test #5. One on the 2nd pass, 3 on the 3rd and one on the on the 5th. all but one were in the low 3000 Mb section of the memory the other in the 600 Mb section. I have 6 gb in 3 2gb sticks.

The test run took 8 hours so I didn't get a chance to try the HD test, i'll do that tomorrow.

 

[usasma]

Don't worry about the Hard Drive test yet, first you've gotta figure out which of the 3 sticks is spitting out the errors in MemTest86+ (see steps 6a through 10).

 

[Danny72170]

Too late, I did the HD test earlier today and got nothing for errors as far as I could see. I'll start the memory tests tomorrow.

 

[Danny72170]

Ok so far I've done memory tests with each DIMM in the computer alone in what the memtest designated as slot 0. All 3 went through 7 passes each and no errors were found on amy of them. These tests take so long so I'll run the memtests of each of the other slots tomorrow.

 

[Danny72170]

Ok i've tested each slot using the same DIMM each time and all 3 tests passed with no errors in 7 passes each.

 

[usasma]

The most likely possibility here is that one of the sticks wasn't seated well and it caused the errors.

Just to be sure I'd run the following free stress test for 24 hours (using the BLEND test) to be sure:

Prime95 download site: http://www.mersenne.org/freesoft/
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. (run all 3 tests if you find a problem with the Blend test and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
More details on the use of this test: Torture test your CPU with Prime95