Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

New Build - Radeon 6870 Crashing


  • Please log in to reply
14 replies to this topic

#1 Joey129

Joey129

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:09:33 PM

Posted 21 December 2011 - 06:10 PM

Hi guys, I have recently decided to build a gaming computer for myself for the first time. On Sat 10th Dec my parts all arrived and I put the comp together, installed windows ect. Since then I have been having a ton of problems when playing games. When I'm playing games such as Empire: Total War or Starcraft 2, the screen will go black/dark blue and the audio will loop, then the computer will either restart itself or I will have to hard reset it by holding down the on/off button on the front of my case. I'm assuming its a problem with my graphics card as it only happens when I'm playing games. I have a PowerColour Radeon 6870. I have tried downloading and installing Catalyst 11.11, 11.5 and the newest 11.12. I've contacted AMD Support and their support hasn't been great, the best thing they have done is shown me how to uninstall all my drivers properly, which I have done and reinstalled the latest catalyst to no avail. I have also tried re-installing Windows, updated my BIOS to the latest version and downloaded the latest chipset driver. I'm completely stumped on what the problem could be. Sometimes I get a "The AMD Display Driver has stopped responding and has recovered successfully" message. Any help would be greatly appreciated, I've tried posting on other forums but have got no replies. I can attach my DxDiag and MSINFO if needed.

BC AdBot (Login to Remove)

 


#2 DJBPace07

DJBPace07

  • BC Advisor
  • 4,869 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:05:33 PM

Posted 21 December 2011 - 06:28 PM

Have you done any other diagnostics? Have you run Furmark? Have you run Prime95? Have you run Windows Memory Disgnostic or Memtest overnight? The issue you have could be caused by a number of things.

3939.png

 


#3 Joey129

Joey129
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:09:33 PM

Posted 21 December 2011 - 06:41 PM

I've ran windows memory diagnostic once I blue screened a couple times(The results said there were no errors). I did try getting Memtest to work but couldnt figure out how to get it to load. I'll install and try out Furmark and Prime95.

EDIT: Just did Furmark at 1920x1080 (FS) - AA:0 samples. My score was 1689 points (28FPS, 60000 ms) Max GPU Temp: 70degrees C. FPS: Min: 29, max: 30, avg: 28.
Renderer : AMD Radeon HD 6870
Drivers: Catalyst 11.12 - 8.92.111109a-129966C-ATI (11-9-2011)
Clocks: core: 900MHz, mem:1050MHz
CPU: AMD FX™-4100 Quad Core Processor
CPU Speed: 3616MHz
System Memory: 8174MB
OS: Windows 7 64-bit build 7601 [Service Pack 1]

EDIT: Just ran Prime95, ran it for 30minutes, torture test completed 14 tests 0 errors and 0 warnings.

Edited by Joey129, 21 December 2011 - 07:37 PM.


#4 killerx525

killerx525

    Bleepin' Aussie


  • Members
  • 7,220 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Melbourne, Australia
  • Local time:08:33 AM

Posted 21 December 2011 - 08:16 PM

You should run Prime95 for at least 4 to 6 hours and also monitor the temperatures of the processor while it's doing that by using HW Monitor.

>Michael 
System1: CPU- Intel Core i7-5820K @ 4.4GHz, CPU Cooler- Noctua NH-D14, RAM- G.Skill Ripjaws 16GB Kit(4Gx4) DDR3 2133MHz, SSD/HDD- Samsung 850 EVO 250GB/Western Digital Caviar Black 1TB/Seagate Barracuada 3TB, GPU- 2x EVGA GTX980 Superclocked @1360/MHz1900MHz, Motherboard- Asus X99 Deluxe, Case- Custom Mac G5, PSU- EVGA P2-1000W, Soundcard- Realtek High Definition Audio, OS- Windows 10 Pro 64-Bit
Games: APB: Reloaded, Hours played: 3100+  System2: Late 2011 Macbook Pro 15inch   OFw63FY.png


#5 Joey129

Joey129
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:09:33 PM

Posted 23 December 2011 - 09:07 AM

Ok, I've just finished running Prime95, started it at 10.02AM, just finished at 2.02PM. It ran 130 tests, 0 errors, 0 warnings. I checked the temperatures using HWMonitor every 30mins, the results are;
10:10:
CPU : 34C min 37C Max
HDD : 26C min 27C Max
GFX : 31C Min 37C Max
10.30:
Temps remained same as above.
11.00:
Temps remained same as above.
12:00
CPU : 33min 40max
HDD : 25min 28Max
GPU ; 31min 56max
12.30:
Temps stayed same
1.00:
CPU : 33min 40max
HDD : 25min 29max
GPU : 31min 57max
1.30:
Temps remained same as above.
2.00:
Temps remained same as above.

All of those are in degrees C. I guess that can rule out the CPU being the cause of the crashing?

#6 Joey129

Joey129
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:09:33 PM

Posted 23 December 2011 - 05:42 PM

So guys I think I just had a breakthrough.

When trying to load Shogun 2, it restarts, unknown to me at the time however, I was blue screening. Microsoft sneakily put in a patch that makes the computer reboot if it blue screens instead of sitting at the blue screen like it used to do. Then when I logged back on to Windows I got a "Windows has recovered from an unexpected shutdown." So I checked the problem details and noticed it said "Files that might help describe the problem C\Windows\Minidump\122311-17518-01.dmp

I then google'd how to read a dump file, I had to download and install the Windows Debugging Tools, which I did, then I had to download the symbols for the debugger to work. After that I loaded up the dump file referenced above and looked through and in it it said:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8007e8a8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR: 0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`031a85b0 fffff800`02d1fc59 : fffffa80`07e8a8d0 fffffa80`06a91040 00000000`00000011 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031a8ad0 fffff800`02bfff57 : fffffa80`07e8a8d0 fffff800`02c7a2b8 fffffa80`06a91040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031a8b00 fffff800`02b675d5 : fffff800`02cdbae0 00000000`00000001 fffffa80`07eeca40 fffffa80`06a91040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031a8b40 fffff800`02ae4001 : fffff880`010cfe00 fffff800`02b675b0 fffffa80`06a91000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031a8b70 fffff800`02d74fee : 00000000`00000000 fffffa80`06a91040 00000000`00000080 fffffa80`069f4040 : nt!ExpWorkerThread+0x111
fffff880`031a8c00 fffff800`02acb5e6 : fffff880`02f65180 fffffa80`06a91040 fffff880`02f6ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031a8c40 00000000`00000000 : fffff880`031a9000 fffff880`031a3000 fffff880`037ed400 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

Followup: MachineOwner


Notice it said "FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV" and "BUCKET_ID: X64_0x124_Authentic_AMD_PROCESSOR_BUS_PRV"? I then googled what a processor bus is, turns out the processor bus is the thing which transports data to and from devices in a computer.

Looks like my processor actually was the problem in the first place then. What do you think?

#7 DJBPace07

DJBPace07

  • BC Advisor
  • 4,869 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:05:33 PM

Posted 23 December 2011 - 09:35 PM

It could be hardware related, but in saying that, it could not only be the CPU but also the motherboard.

3939.png

 


#8 killerx525

killerx525

    Bleepin' Aussie


  • Members
  • 7,220 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Melbourne, Australia
  • Local time:08:33 AM

Posted 24 December 2011 - 05:16 AM

Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

>Michael 
System1: CPU- Intel Core i7-5820K @ 4.4GHz, CPU Cooler- Noctua NH-D14, RAM- G.Skill Ripjaws 16GB Kit(4Gx4) DDR3 2133MHz, SSD/HDD- Samsung 850 EVO 250GB/Western Digital Caviar Black 1TB/Seagate Barracuada 3TB, GPU- 2x EVGA GTX980 Superclocked @1360/MHz1900MHz, Motherboard- Asus X99 Deluxe, Case- Custom Mac G5, PSU- EVGA P2-1000W, Soundcard- Realtek High Definition Audio, OS- Windows 10 Pro 64-Bit
Games: APB: Reloaded, Hours played: 3100+  System2: Late 2011 Macbook Pro 15inch   OFw63FY.png


#9 DJBPace07

DJBPace07

  • BC Advisor
  • 4,869 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:05:33 PM

Posted 24 December 2011 - 01:18 PM

MajorGeeks has a page on decoding memory dumps, I would start there.

3939.png

 


#10 Joey129

Joey129
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:09:33 PM

Posted 24 December 2011 - 01:37 PM

Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.


Thanks

Here it is;

==================================================
Dump File : 122411-16395-01.dmp
Crash Time : 24/12/2011 00:21:24
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`07e7c038
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b16cc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+4b16cc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\122411-16395-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 122311-18376-01.dmp
Crash Time : 23/12/2011 23:26:50
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`07e0e038
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b16cc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+4b16cc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\122311-18376-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 122311-17518-01.dmp
Crash Time : 23/12/2011 21:32:36
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`07e8a8f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b16cc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+4b16cc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\122311-17518-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 122311-17612-01.dmp
Crash Time : 23/12/2011 19:33:42
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`07dcd038
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b16cc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+4b16cc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\122311-17612-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 122311-19219-01.dmp
Crash Time : 23/12/2011 15:59:46
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`07e0d038
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b16cc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+4b16cc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\122311-19219-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 122311-19656-01.dmp
Crash Time : 23/12/2011 15:56:16
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`07e25038
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b16cc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+4b16cc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\122311-19656-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 122311-22963-01.dmp
Crash Time : 23/12/2011 14:55:16
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`07b268f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b16cc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+4b16cc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\122311-22963-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 122311-18236-01.dmp
Crash Time : 23/12/2011 14:27:34
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`07dbc038
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : crashdmp.sys
Caused By Address : crashdmp.sys+1b3c5f0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+4b16cc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\122311-18236-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 122311-17206-01.dmp
Crash Time : 23/12/2011 14:23:49
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`07e4c178
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b16cc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+4b16cc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\122311-17206-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 122311-22261-01.dmp
Crash Time : 23/12/2011 09:34:14
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`07e518f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b16cc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+4b16cc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\122311-22261-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

As you can see all but one of my 10 dump files say ntoskrnl.exe is the problem driver. But what is that driver? NT Kernel + System? Also what about the other one which refers to crashdmp.sys?

EDIT: I just tried running Startup Recovery, after a while it said that a System Restore was needed, so I pressed Restore, then after a while it came up saying windows cannot automatically fix this computer, then I pressed problem details and at the bottom it said
"Root cause found: Unspecified changes to system configuation might have caused the problem.
Repair Action: System Restore
Result: Failed. Error Code = 0x490
Time Taken : 551659ms"

Any ideas? Does that help point out that ntoskrnl is the problem?

Edited by Joey129, 24 December 2011 - 05:30 PM.


#11 Joey129

Joey129
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:09:33 PM

Posted 27 December 2011 - 08:06 AM

No ideas then? Having this problem has really put me off building computers again :/

#12 DJBPace07

DJBPace07

  • BC Advisor
  • 4,869 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:05:33 PM

Posted 27 December 2011 - 03:58 PM

If you ran Prime95 for a few hours and it blue screened during the testing, that could indicate an issue with the CPU, RAM, or motherboard. Your computer should be able to run the Windows Memory Diagnostic, Memtest, or Prime95 for a few hours with no issues.

Blue screens are tricky, which is why very few people can help. Decoding them is a pain and going much further than that often requires the assistance of people more familiar of how Windows operates on a deeper system level. I once had a computer that would blue screen constantly while playing games. It would simply freeze or the computer would, rarely, blue screen. I tried everything I could think of short of replacing the motherboard. There were few indications as to what the problem was, and hardware issues often manifest themselves when software encounters a problem trying to utilize the faulty hardware. In the end, the problem was the motherboard, replacing that solved the issue.

Which parts are new? Are you still within the retailers RMA period? You may be able to exchange the hardware for an exact model, but most RMA periods are short at about a month.

3939.png

 


#13 Joey129

Joey129
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:09:33 PM

Posted 27 December 2011 - 04:06 PM

I've ran Prime95 for 4hours and it was fine throughout it. Memtest I just finished running, I let it do 6passes and there were no errors. I've also ran Windows Memory Diagnostics without trouble. All of my parts are new, they all arrived on Fri 9th Dec, I got Win 7 on the following Saturday and have been having trouble ever since. A friend of mine thinks that it is either a faulty processor or motherboard. I'll probably phone up the company I bought all the parts from tomorrow and get the processor and motherboard RMA'd.

I just didn't want to get them RMA'd, get replacements and then still have the same problem.

#14 DJBPace07

DJBPace07

  • BC Advisor
  • 4,869 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:05:33 PM

Posted 27 December 2011 - 07:12 PM

Tracking down hardware problems can be a nightmare, but if you believe it is the motherboard or CPU, go and get them RMA'd, you have nothing to lose but time.

3939.png

 


#15 Joey129

Joey129
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:09:33 PM

Posted 28 December 2011 - 02:32 PM

After speaking to the guy at ebuyer I've decided to RMA the processor because he said that BSODs that occur due to a faulty motherboard are usually from a faulty socket, which I dont have. It's being collected tomorrow by the courier. I'll post back once I get the processor back and see if that's fixed it.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users