BSOD messages / system crashes

Associate
Joined
3 Jan 2012
Posts
39
I've just built a new PC (
OcUK HD 7970 3072MB GDDR5 PCI-Express Graphics Card
Intel Core i5-2500K 3.30GHz (Sandybridge) Socket LGA1155 Processor - Retail
ADATA S511 120GB SATA 6Gb/s Solid State Drive - Retail with Acronis True Image
Team Xtreem 16GB (4x4GB) DDR3 PC3-17000C9 2133MHz Dual/Quad Channel Kit (TXD316G2133HC9NQC-L)
Gigabyte Z68XP-UD3P Intel Z68 (Socket 1155) DDR3 Motherboard
BitFenix Colossus Red LED Big Tower Windowed Case - Black
XFX 850W XXX Edition Modular '80 Plus Silver' Power Supply
Corsair Hydro H80 High Performance Liquid CPU Cooler (Socket LGA775/LGA1155/LGA1156/LGA1366/LGA2011/AM2/AM3) (CWCH80)
Sony Optiarc AD-7280S 24x DVD±RW SATA ReWriter (Black) - OEM
BitFenix Spectre 140mm Fan - Black
OcUK 30cm Cold Cathode 2-in-1 Kit - Red
)

and overclocked it to 4.6GHz (from 3.3) using the turbo feature

Its been running more or less without issue: except now, for a series of BSODs that I've experienced today.

The BSOD messeges are listed below (the messages returned after starting the PC up again)
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 2057

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA800DE4B028
BCP3: 00000000BE200000
BCP4: 000000000005110A
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\030212-19312-01.dmp
C:\Users\CPRobertson\AppData\Local\Temp\WER-59935-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt





Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 2057

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF880011C0909
BCP3: FFFFF8800A7276A0
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\030212-18174-01.dmp
C:\Users\CPRobertson\AppData\Local\Temp\WER-23446-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Is there anything obvious that might be wrong? How do I go about figuring out where this problems is?


Ps - My apologies if I've put this thread in the wrong forum - wasnt sure if it was a software issue or whether it belonged somewhere else entirely...
 
CPU VCore is set to "Auto" and displaying 1.2V on Bios
CPU PLL is at 1.8V - again set to auto
everything else is set to auto - the only thing I changed was the turbo mode (and earlier on the clock multiplier - that was before I touched the turbo)(decided to run turbo since I wouldn't be needing the extra processing power most of the time - set all values to 46 (except max power/current which I left at auto) and put the clock multiplier back to 33 (the default)

DRAM is currently running at 1.5V

Channel A/B Data and Address VRef are all at 0.75 - again on auto.
Extreme memory profile = auto
performance enhance = turbo
DDR Voltage is 1.5V
VTT voltage is at 1.05
Memory frequency is at 1333MHz



The first BSOD happened when I was playing skyrim - the PC was sitting fine at 35-48 degrees even during torture tests with prime95)

are you wanting me to upload the minidump files anywhere btw?


--- edit
will try changing the ram about if it happens again - I've reduced the overclocking to 4.4GHz (using turbo again) and reset everything else.
--- edit
will up the DRAM as suggested xD
 
Last edited:
is the "auto" selection on the CPU voltage not upping the voltage when it hits turbo mode then? If so - its a little misleading xD

Will do, about to restart the PC


-- edit
default value for cpu voltage was 1.35V anyway xD - couldnt read my handwriting xD
 
Last edited:
well, it hasn't crashed again - hopefully that will be the last of it - I'll post back if there are any problems (going to run a Prime95 torture test later on this evening)
 
Back
Top Bottom