BSOD while playing games

[supjeremiah]

Sometimes I can go for a few hours without it happening and sometimes it will happen after only a few minutes.

The BSOD has been different on multiple occasions. The old one was IRQL_less_or_equal or something along those lines and the new and more consistent one is STOP: 0x0000001E (0x00000000000000000, 0x00000000000000000, 0x00000000000000000)

This has only happened while I'm gaming but it happens with any game. All my driver's are updated. I'm not tech savvy so if anyone could help I would really appreciate it.

I just bought this PC less than a month ago. Here's a link to it:

ULTRA BLACK 4.0GHz OVERCLOCKED PC - AMD Phenom II X6, Genuine Windows 7 HP 64-bit, AMD RADEON HD6850 1GB, AMD VISION BLACK, LIQUID COOLED, ASUS M4A89GTD, 8GB DDR3, HYBRID HDD, Corsair 600T Case, USB3 at TigerDirect.com

 

[supjeremiah]

I've attached the things I was told to. If I haven't done so properly please let me know.

 

[usasma]

Missing perfmon report. Not essential for me, but others may want to see it.

Most likely a hardware problem, with compatibility issues following closely behind. But this depends on what settings that you used for Driver Verifier. Please explain how you ran Driver Verifier.

More to follow....

 

[usasma]

Please update these drivers:
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) - Update with Windows Update
PxHlpa64.sys  Tue Jun 23 19:16:35 2009 (4A416253)
AtiPcie64.sys Wed Mar 10 09:33:45 2010 (4B97ADC9)
usbfilter.sys Wed Dec 15 05:34:49 2010 (4D0899C9)
ASACPI.sys    Wed Jul 15 23:31:29 2009 (4A5E9F11)
aswTdi.SYS    Mon Jul 04 07:35:26 2011 (4E11A57E)
aswSnx.SYS    Mon Jul 04 07:36:55 2011 (4E11A5D7)
AsIO.sys      Thu Apr 22 07:18:03 2010 (4BD0306B)
Rt64win7.sys  Sun May 30 23:46:43 2010 (4C033123)
amdiox64.sys  Thu Feb 18 10:17:53 2010 (4B7D5A21)
AtihdW76.sys  Wed Nov 17 07:02:04 2010 (4CE3C43C)
RTKVHD64.sys  Fri Mar 26 06:30:50 2010 (4BAC8CDA)
aswSP.SYS     Mon Jul 04 07:36:52 2011 (4E11A5D4)
KmxAMRT.sys   Fri Sep 17 09:31:50 2010 (4C936DC6)
kmxcfg.sys    Tue Jun 01 17:15:00 2010 (4C057854)
nusb3xhc.sys  Thu Feb 10 00:52:33 2011 (4D537D21)
nusb3hub.sys  Thu Feb 10 00:52:32 2011 (4D537D20)
kmxagent.sys  Fri Mar 05 16:36:06 2010 (4B917946)
atikmpag.sys  Tue Mar 08 23:17:42 2011 (4D76FF66)
[/font]

http://www.carrona.org/dvrref.html#amdxata.sys
http://www.carrona.org/dvrref.html#PxHlpa64.sys
http://www.carrona.org/dvrref.html#AtiPcie64.sys
http://www.carrona.org/dvrref.html#usbfilter.sys
http://www.carrona.org/dvrref.html#ASACPI.sys
http://www.carrona.org/dvrref.html#aswTdi.SYS
http://www.carrona.org/dvrref.html#aswSnx.SYS
http://www.carrona.org/dvrref.html#AsIO.sys
http://www.carrona.org/dvrref.html#Rt64win7.sys
http://www.carrona.org/dvrref.html#amdiox64.sys
http://www.carrona.org/dvrref.html#AtihdW76.sys
http://www.carrona.org/dvrref.html#RTKVHD64.sys
http://www.carrona.org/dvrref.html#aswSP.SYS
http://www.carrona.org/dvrref.html#nusb3xhc.sys
http://www.carrona.org/dvrref.html#nusb3hub.sys
http://www.carrona.org/dvrref.html#atikmpag.sys

Please run Driver Verifier using 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 "Special Pool" and "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__\072411-18408-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 24 20:27:20.473 2011 (UTC - 4:00)
System Uptime: 0 days 0:19:23.597
Probably caused by : Ntfs.sys ( Ntfs!NtfsCheckAttributeRecord+8f )
DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
PROCESS_NAME:  where.exe
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsCheckAttributeRecord+8f
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`0c13c9c8 fffff880`0c13c220 fffff880`012acc5f
BiosVersion = 1606   
BiosReleaseDate = 08/24/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072411-18626-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 24 20:07:09.501 2011 (UTC - 4:00)
System Uptime: 0 days 0:48:52.625
Probably caused by : memory_corruption ( nt!MiCheckAging+5d )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  iw4mp.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!MiCheckAging+5d
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02c9ed3d 00000000`00000000 00000000`00137671
BiosVersion = 1606   
BiosReleaseDate = 08/24/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072411-23212-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 24 19:17:23.214 2011 (UTC - 4:00)
System Uptime: 0 days 2:07:14.978
Probably caused by : memory_corruption ( nt!MiCheckAging+5d )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  iw4mp.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!MiCheckAging+5d
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02cdad3d 00000000`00000000 00000000`00031262
BiosVersion = 1606   
BiosReleaseDate = 08/24/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072411-17316-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 24 17:09:20.898 2011 (UTC - 4:00)
System Uptime: 0 days 1:48:29.022
Probably caused by : hardware ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  iw4mp.exe
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = 1606   
BiosReleaseDate = 08/24/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072411-21278-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 24 15:19:54.365 2011 (UTC - 4:00)
System Uptime: 0 days 1:49:22.561
Probably caused by : memory_corruption ( nt!MiCheckAging+ce )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  League of Lege
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!MiCheckAging+ce
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02c90dae 00000000`00000000 ffffffff`ffffffff
BiosVersion = 1606   
BiosReleaseDate = 08/24/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\070811-21060-01.dmp]
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Fri Jul  8 18:54:20.530 2011 (UTC - 4:00)
System Uptime: 0 days 2:43:54.795
Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+80 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  UmxAgent.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KiCommitThreadWait+80
Bugcheck code 0000000A
Arguments ffffffff`ffffffeb 00000000`00000002 00000000`00000001 fffff800`02cce840
BiosVersion = 1606   
BiosReleaseDate = 08/24/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\070811-17284-01.dmp]
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Fri Jul  8 06:23:02.536 2011 (UTC - 4:00)
System Uptime: 0 days 12:14:44.800
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4894 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_91
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  AgeOfConan.exe
FAILURE_BUCKET_ID:  X64_0xc4_91_nt!_??_::FNODOBFM::_string_+4894
Bugcheck code 000000C4
Arguments 00000000`00000091 00000000`00000000 fffffa80`09ac9060 00000000`00000000
BiosVersion = 1606   
BiosReleaseDate = 08/24/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\070311-16894-01.dmp]
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Sun Jul  3 08:28:52.999 2011 (UTC - 4:00)
System Uptime: 0 days 10:33:29.468
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+167 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  LoLLauncher.ex
FAILURE_BUCKET_ID:  X64_0x50_nt!KiSystemServiceExit+167
Bugcheck code 00000050
Arguments fffff880`16551d98 00000000`00000000 fffff800`02cd4ac2 00000000`00000002
BiosVersion = 1606   
BiosReleaseDate = 08/24/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\070111-17550-01.dmp]
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Fri Jul  1 21:49:52.482 2011 (UTC - 4:00)
System Uptime: 1 days 1:40:06.386
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+167 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  LoLLauncher.ex
FAILURE_BUCKET_ID:  X64_0x50_nt!KiSystemServiceExit+167
Bugcheck code 00000050
Arguments fffff87f`d5fd5d98 00000000`00000000 fffff800`02c73ac2 00000000`00000005
BiosVersion = 1606   
BiosReleaseDate = 08/24/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\063011-16988-01.dmp]
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Thu Jun 30 03:27:14.192 2011 (UTC - 4:00)
System Uptime: 0 days 7:31:40.456
Probably caused by : hardware ( nt!KiDeferredReadyThread+31e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
Bugcheck code 0000000A
Arguments fffff800`4c009d8f 00000000`00000002 00000000`00000000 fffff800`02c841fe
BiosVersion = 1606   
BiosReleaseDate = 08/24/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[usasma]

OOPS! Forgot this:

We troubleshoot overclocked systems by resetting them to default values (NO overclock) and seeing if they still BSOD.
If they do, then we proceed with troubleshooting hardware/software issues.

If they stop BSODing, then it's the overclock that's at fault - so we have to take a different direction in troubleshooting that.

 

[supjeremiah]

My rig came overclocked pre-built as you can see from the link I provided. I have no idea how to set it back to original either.

Also, I'm working on updating the drivers with the links you provided but I'm running into some problems. I'll get back to you if I can't figure it out.

 

[usasma]

First off, what settings did you use to run Driver Verifier? Are you now using the settings that I suggested?

I haven't overclocked a system since 2000. I'm not real well versed in the latest techniques.
The point of removing the overclock is to see if the overclock is stable AND to see if the stress of the overclock has damaged anything on the system. Repeated stress (such as an overclock) reduces the life of the system components - so it's not unusual for hardware failures to occur.

If we don't get rid of the overclock, we'll eventually end up with a hardware problem that we can't solve. At that point we start looking at replacing parts. And that can get rather expensive if it's just the overclock that causing the problem. I'd suggest contacting SystemMax to see what the actually did to overclock the system (and if you're covered under any sort of warranty). Even if they just provide a link, we can use that to figure out how to "unoverclock" your system.

 

[supjeremiah]

I switched driver verifier to the settings you detailed. I haven't gotten a BSOD yet. I did however get one while I was trying to update the last driver on the list. I didn't have time to see what the STOP message was though.

Also, regarding the list of drivers. It seems that half of the listed are ATI drivers whilst the other half is the Avast anti virus I just downloaded the other day. Anytime I go to download new drivers for the ATI it downloads a Catalyst program which automatically updates the drivers for me but then according to the dump they're not updated. Avast I'm just not sure how to update so is there a better antivirus program you would suggest? (free).

 

[supjeremiah]

So with the new verifier settings I bsod'd almost immediately upon starting up a game. I got the usual bsod but before my PC would even start windows it bsod'd again. So then I ran in windows repair and did a system restore. I ran the dump collection and attached. Again I'm not sure if I did any of this right as I really am ignorant when it comes to tech stuff.

 

[usasma]

Updating drivers isn't all that easy, but you're doing a fine job with that.
In general, if the drivers are from 2009 or later, they're usually Win7 compatible
And, if you've installed drivers over the old ones, then you've also probably overwritten any errors that may have existed in the original drivers. So that takes care of most of the issues that we're looking to fix.

So, stick with what you've got. Video and antivirus drivers are the most problematic to update, but yours look current enough to not worry about.

You're doing just fine with the tech stuff here. It's a learning experience, so you're gonna be a bit lost until (and if) you hang around here for a long, long time. But that's what we're here for - to help you through the learning process and with solving your problems.

The memory dumps point to hardware problems (including the Driver Verifier memory dump) - so it's time to start looking at hardware. Here's a list of free diagnostics and stress tests. At a minimum, please do the hard drive, MemTest, antimalware, FurMark, and Prime 95 tests. Please post back the results of each test.

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 Resources (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

More Video Stress Tests:
1. Thanks to VirGnarus for finding this test: https://simtk.org/home/memtest
2. 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.
3. Another interesting test that came to my attention: Download - OCCT Website english
USE AT YOUR OWN RISK - the program doesn't have a whole bunch of safety features to protect you from yourself!

CPU Stress Tests:
- http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=19182&lang=eng
- 7Byte : Hot CPU Tester Pro
- 7Byte : BurnIn64
- CPU Stress test - Overclock.net - Overclocking.net
- Fossil Free Online CPU Load or Stress Test.
- CPU Stability Test description, System Resources Tune-Up. Downloads List By All Time Popularity | PCWorld | PCWorld
- CPU Stress test - Overclock.net - Overclocking.net
- |MG| CPU Stability Test 6.0 Download
- LinX - A simple Linpack interface

BSOD BUGCHECK SUMMARY

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072511-17596-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Jul 25 18:03:47.318 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:27.442
[COLOR=Red]Probably caused by : hardware ( nt!MiFreeWsleList+2af )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
[/COLOR]BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
Bugcheck code 0000000A
Arguments 00000000`00000088 00000000`00000002 00000000`00000001 fffff800`02c80c8b
BiosVersion = 1606   
BiosReleaseDate = 08/24/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072511-18080-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Jul 25 03:58:46.885 2011 (UTC - 4:00)
System Uptime: 0 days 5:22:26.009
Probably caused by : hardware ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  iw4mp.exe
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = 1606   
BiosReleaseDate = 08/24/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072411-24570-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 24 22:35:30.684 2011 (UTC - 4:00)
System Uptime: 0 days 2:07:20.448
Probably caused by : dxgkrnl.sys ( dxgkrnl!DxgkEscape+10f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  iw4mp.exe
FAILURE_BUCKET_ID:  X64_0x3B_dxgkrnl!DxgkEscape+10f
Bugcheck code 0000003B
Arguments 00000000`80000003 fffff880`0447a9f3 fffff880`08b40e90 00000000`00000000
BiosVersion = 1606   
BiosReleaseDate = 08/24/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072411-18626-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 24 20:07:09.501 2011 (UTC - 4:00)
System Uptime: 0 days 0:48:52.625
Probably caused by : memory_corruption ( nt!MiCheckAging+5d )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  iw4mp.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!MiCheckAging+5d
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02c9ed3d 00000000`00000000 00000000`00137671
BiosVersion = 1606   
BiosReleaseDate = 08/24/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072411-23212-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 24 19:17:23.214 2011 (UTC - 4:00)
System Uptime: 0 days 2:07:14.978
Probably caused by : memory_corruption ( nt!MiCheckAging+5d )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  iw4mp.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!MiCheckAging+5d
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02cdad3d 00000000`00000000 00000000`00031262
BiosVersion = 1606   
BiosReleaseDate = 08/24/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072411-21278-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 24 15:19:54.365 2011 (UTC - 4:00)
System Uptime: 0 days 1:49:22.561
Probably caused by : memory_corruption ( nt!MiCheckAging+ce )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  League of Lege
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!MiCheckAging+ce
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02c90dae 00000000`00000000 ffffffff`ffffffff
BiosVersion = 1606   
BiosReleaseDate = 08/24/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[supjeremiah]

Thanks for the update! May be a day or two before my next reply as I need to go into town for blank disks. A friend of mine told me he had similar problems and that he replaced his RAM and that fixed it. However he also said he had 1 consistent BSOD where as I have had many different ones so we'll see!

 

[usasma]

Not a problem, I'll be notified when you reply next.
Good luck!

 

[supjeremiah]

Hey so I finally have been able to run a memtest last night. It went for 8 passes and I'm not sure what I was supposed to be looking for in particular but I ended up with over 1 million errors, which doesn't sound good at all. A friend of mine suggested buying new ram entirely and replacing it all as testing to find out which ram out of 8190 mb would be difficult. I took a picture of the memtest screen with my cell phone and can upload that if you need it.

 

[usasma]

1 million errors!!! Wow!!!
Start with Step 6 in my link below to test the individual stick(s) and slots
Here's the link: Memory Diagnostics

 

[supjeremiah]

I tested every stick in every slot and the memtest would spit out errors as soon as it hit 30% during the first pass for each stick. I guess I'm going to dig up my old packaging and send it in to whomever covers my warranty. I was hoping it wouldn't come to this. Thanks for your help though!