Hardware Error

armydude · May 14, 2011

EDIT** Followed the link and uploaded system health and all the minidumps basicly.

http://www.newegg.com/Product/Produ...c=OTC-Froogle-_-Video+Cards-_-EVGA-_-14130572

Above is the link to the new graphics card im buying, its a

EVGA 01G-P3-1450-TR GeForce GTS 450 (Fermi) 1GB 128-bit GDDR5 PCI Express 2.0 x16 HDCP Ready SLI Support Video Card

**

Well i've been recently getting a lot of hardware error blue screens. The minidumps should be uploaded. One of my video cards went bad(2 9500 gt sli) and I got rid of it. I'm going to get rid of the 2nd video card once I order one better to replace it. These blue screens mainly happen during or right after games.

I had over heating problems before but since then I bought a Cm Storm case. Just to rule it out i'll list but I cant remember all the fan speeds etc. I believe I have 2 140mm on the side(top blowing out, bottom blowing in with protective mesh) Top fan and back fan blowing out(standard, looks like 140mm but doesn't feel as strong as the ones I put in on side) And finally the front is all mesh with the standard about 140mm at bottom that came with, and my cpu cooler fan above it.

I'll update this once I know what new video card i'm getting and after I try it out. Any help is appreciated wether it be with the blue screens or a better air flow.

3 minidumps included, I believe 2 should be the hardware error one and 1 should be a "paged in nonpage area" something.

americancritic · May 14, 2011

Hello and welcome to the forum.

Here is what to do when uploading any BSOD reports, we will look at your report soon.

http://www.vistax64.com/crashes-debugging/282419-blue-screen-death-bsod-posting-instructions.html

armydude · May 19, 2011

I ran prime95 over night and at some point in the night I had a BSOD with a paged in non page area(minidump included). I will attempt to run memtest+ once I can get my virtual drive working again.

mgorman87 · May 19, 2011

It appears you might have a failing CPU or a bad PSU. Update the ASACPI driver and remove the program. Then run the tests and report back the results

Code:

ASACPI.sys   Mon Oct 30 22:09:12 2006 (4546B048)

A known BSOD maker in Windows 7/Vista. The pre 2009 versions of this driver is known to cause BSOD on Windows 7/Vista systems.
Download the ATK0110 utility from here - ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE.
After you install it browse to C:\windows\system32\drivers and check the properties of ASACPI.sys and make sure it now says 2009.

Please uninstall RivaTuner/EVGA Precision/MSI Afterburner (known issues w/Win7 & Vista)

Please run these tests and report back the results
1. Memtest86 - Run for 7-8 passes - RAM - Test with Memtest86+ - Windows 7 Forums
2. Prime95 - Run all three tests for 3-4 hours each or until fail - CPU - Stress Test with Prime95 - Windows 7 Forums
3. Hard drive scan usings SeaTools - SeaTools for Windows | Seagate - Both long and short tests

BSOD BUGCHECK SUMMARY

Code:

[FONT=lucida console]
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Thu May 19 09:48:46.148 2011 (UTC - 4:00)
System Uptime: 0 days 5:55:55.944
Probably caused by : ntkrnlmp.exe ( nt!ObpLookupDirectoryEntry+9f )
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!ObpLookupDirectoryEntry+9f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Sat May 14 22:38:06.323 2011 (UTC - 4:00)
System Uptime: 0 days 0:05:57.149
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
BiosReleaseDate = 08/20/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Sat May 14 19:24:08.563 2011 (UTC - 4:00)
System Uptime: 0 days 0:19:46.388
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
BiosReleaseDate = 08/20/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Sat May 14 14:48:52.373 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:07.169
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME:  AvastUI.exe
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD__UNKNOWN
BiosReleaseDate = 08/20/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Sat May 14 14:46:46.868 2011 (UTC - 4:00)
System Uptime: 0 days 0:04:44.709
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1545a )
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+1545a
BiosReleaseDate = 08/20/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Sat May 14 14:41:23.618 2011 (UTC - 4:00)
System Uptime: 0 days 0:08:08.459
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME:  L2.exe
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD__UNKNOWN
BiosReleaseDate = 08/20/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Fri May 13 04:00:18.943 2011 (UTC - 4:00)
System Uptime: 0 days 1:48:38.644
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME:  iexplore.exe
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD__UNKNOWN
BiosReleaseDate = 08/20/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Thu May 12 02:26:28.606 2011 (UTC - 4:00)
System Uptime: 0 days 1:56:47.432
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME:  MsMpEng.exe
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD__UNKNOWN
BiosReleaseDate = 08/20/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Thu May 12 00:28:13.760 2011 (UTC - 4:00)
System Uptime: 0 days 3:03:33.570
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME:  LolClient.exe
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD__UNKNOWN
BiosReleaseDate = 08/20/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Tue Apr 26 23:24:02.256 2011 (UTC - 4:00)
System Uptime: 0 days 0:26:03.082
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME:  audiodg.exe
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD__UNKNOWN
BiosReleaseDate = 08/20/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Tue Mar 29 23:01:48.918 2011 (UTC - 4:00)
System Uptime: 0 days 0:55:08.589
Probably caused by : ntkrnlmp.exe ( nt!ObpLookupDirectoryEntry+9f )
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!ObpLookupDirectoryEntry+9f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Tue Mar 29 22:05:56.747 2011 (UTC - 4:00)
System Uptime: 0 days 0:25:46.543
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
BiosReleaseDate = 08/20/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Tue Mar 29 17:11:19.048 2011 (UTC - 4:00)
System Uptime: 0 days 22:52:56.874
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC
PROCESS_NAME:  L2.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
BiosReleaseDate = 08/20/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/FONT]

armydude · May 19, 2011

I tried to download that driver, only thing it seemed I could do is copy/paste the one it gave me to my driver folder but its the same as the one I already have (2006).

richc46 · May 19, 2011

Please visit thislink: ASUSTeK Computer Inc.-Support- Drivers and Download P7P55D LE
Scroll down to the Utilities category, then scroll down to the "ATK0110driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sysfile is date stamped from 2009 or 2010 (NOT 2005).

armydude · May 19, 2011

I already did that, im not sure where you can "install" anything with this as I download it and it gives me a folder with 32/64. So I go into 64 then it shows "win7/win2000/winvista" and AsAcpiLns and install. I go into winvista and there is "asacpi/AsAcpi/Asacpi.sys" all different file types. Sadly I still dont understand how to install this.

mgorman87 · May 20, 2011

armydude said:
I already did that, im not sure where you can "install" anything with this as I download it and it gives me a folder with 32/64. So I go into 64 then it shows "win7/win2000/winvista" and AsAcpiLns and install. I go into winvista and there is "asacpi/AsAcpi/Asacpi.sys" all different file types. Sadly I still dont understand how to install this.

I'll have to check with someone to see if this ASACPI affects Vista as it does in 7 because your driver (2006) is the latest for Vista. The 2009 driver is for 7.

richc46 · May 20, 2011

The old driver does affect Vista.

mgorman87 · May 20, 2011

Ok.

@armydude, open that zip and go into the Windows 7 folder and take the ASACPI.sys and drag it into your C:\windows\system32\drivers folder and replace the old driver.

armydude · May 21, 2011

I put that file into my drivers folder and replaced the one I had. I saw somewhere that running verifier might help so I followed that and I have some minidumps of memory corruption from it(most recent might be hardware again while I was trying to get on here to post this) Id like to believe it so I can fix this already but i'm not entirely sure why a driver verifier picked up memory corruption.

On a side note I know how to make my computer blue screen with hardware error. After login if I try to run different programs at the same time while its still booting up. I would suspect this to be a memory or cpu thing but your the experts

**EDIT

Still havent been able to run memtest86+ as my daemon tools lite isnt working.

**

mgorman87 · May 21, 2011

Hmm. Don't know why I missed it the first time but you need to remove Daemon Tools. Its driver, SPTD, is a known BSOD maker in Win Vista/7. You also shouldn't be mounting Memtest. It's run when you boot your computer so you need to burn it to a disk.

After you've removed Daemon Tools run the SPTD removal tool found here DuplexSecure

BSOD BUGCHECK SUMMARY

Code:

[font=lucida console]
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Sat May 21 02:55:16.241 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:00.006
*** 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
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_64
BiosReleaseDate = 08/20/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Sat May 21 02:37:54.265 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:09.921
*** 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
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_64
BiosReleaseDate = 08/20/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Sat May 21 02:34:49.216 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:03.997
*** 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
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_64
BiosReleaseDate = 08/20/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Sat May 21 02:31:49.883 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:58.664
*** 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
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_64
BiosReleaseDate = 08/20/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Debug session time: Sat May 21 02:28:56.025 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:58.806
*** 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
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_64
BiosReleaseDate = 08/20/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

armydude · May 24, 2011

Okay I did all that and I ran memtest for some 14 passes(not like I can really use my computer atm lol) Still getting the hardware BSOD. Is there some other program I can try running instead of prime85(I think) and memtest86+? Also what would happen if one of my 2 cpu cores went or started going bad?

mgorman87 · May 24, 2011

armydude said:
Okay I did all that and I ran memtest for some 14 passes(not like I can really use my computer atm lol) Still getting the hardware BSOD. Is there some other program I can try running instead of prime85(I think) and memtest86+? Also what would happen if one of my 2 cpu cores went or started going bad?

Did you run all three Prime95 tests (Small FFTs, Large FFTs and Blend)?

armydude · May 25, 2011

Yes, I ran the first 2 for a good amount of time and I just ran the blend one for 10 hours with no errors.

armydude · May 26, 2011

If it helps at all my hardware problems occurs in safe mode aswell, just like in normal, when I try to do too many things when its still starting up. Any programs that may help test things would be appreciated, besides prime85 and memtest86+.

mgorman87 · May 27, 2011

armydude said:
If it helps at all my hardware problems occurs in safe mode aswell, just like in normal, when I try to do too many things when its still starting up. Any programs that may help test things would be appreciated, besides prime85 and memtest86+.

Could be power supply related. What type of PSU do you have?

armydude · Jun 18, 2011

I believe 650w power supply, but I think I figured out what is wrong which is why im posting btw.

I followed some stuff online and went in and changed my computer to only use 1 core of my 2 cores. It does not blue screen anymore, but just moves very very very slow. Slow enough to not be able to play games and yeah, any suggestions will be helpful but im looking into maybe getting a quad core at some point.

Regardless thanks for all the help you guys gave

You might see me on here or another site once I upgrade to troubleshoot.

Hardware Error

Attachments

My Computer

My Computer

Attachments

My Computer

BSOD Squad

My Computer

My Computer

My Computer

My Computer

BSOD Squad

My Computer

My Computer

BSOD Squad

My Computer

Attachments

My Computer

BSOD Squad

My Computer

My Computer

BSOD Squad

My Computer

My Computer

My Computer

BSOD Squad

My Computer

My Computer