Sign in with
Sign up | Sign in
Your question
Solved

need help BSOD on new system

Last response: in Windows 7
Share
August 29, 2013 12:57:30 PM

I have tried everything to fix a problem with my new system but i just cant figure out whats wrong. I built a new system a little over 1 month ago with a new mobo cpu and ram, it has the same power supply hard drives and graphics card as my old system. here are the dmp files please help

http://www.4shared.com/zip/q7VjNTJG/082313-8736-01.html

new components are
Fresh installed windows 7
Asus Maximus VI hero
I7 4770k
G.Skill 16GB 2133

Old components are
xion 1000W gaming series PSU
corsair nova 128g SSD
EVGA gtx 680

I ran Memtest and got 2 errors so i RMAed the ram and am still waiting to get that back but i put my old ram that i know works in and just got another bluescreen. all drivers and the bios is up to date so i dont know what to do anymore. thanks in advance

I should also mention the bsods are seemingly random i can be watching a youtube video browsing the web or playing a game when they happen

More about : bsod system

a b $ Windows 7
August 29, 2013 6:27:59 PM

Did you load mobo drivers from the Asus web site or just off the CD that came with the Hero? Also did you update BIOS?
m
0
l
Related resources
a b $ Windows 7
August 29, 2013 6:37:11 PM

Is DRAM 1600 or better? If so, is it running under XMP?, if not, try that, if so try with DRAM voltage up + 0.05, you don't mention what model of GSkill and they have a lot of 16GB 2133 so am guessing (hoping) it's a CL9 set
m
0
l
August 29, 2013 6:42:22 PM

F3-2133C10D-16GXM is the model number for the ram i was using before i RMAed it and blue screens happened with it at 2133 and 1333 the ram i am using now is F3-12800CL9T2-24GBRL @ 1600
m
0
l
a b $ Windows 7
August 29, 2013 6:48:05 PM

The DRAM you have now won't run correctly under XMP, try it at 1600 under auto - this is a 6 stick set, and the advanced timings under XMP are for 6 sticks, since you can only run 4 they will be too high...try initially with 2 sticks under AUTO and then set freq manually to 1600 and the base spec timings
m
0
l
August 29, 2013 6:53:56 PM

alright done

i should also note that i ran memetest with this ram as well with xmp on and got no errors after 6 hours
m
0
l
a b $ Windows 7
August 29, 2013 6:59:31 PM

How old is the Xion, try raising the VCCSA + 0.06 or so, wondering if maybe a fluctuation of voltage problem
m
0
l
August 29, 2013 7:03:10 PM

its had 3 years of fairly heavy use, i have a brand new corsair TX750 that has never been used if that could be the problem
m
0
l
a b $ Windows 7
August 29, 2013 7:26:27 PM

Might give it a try, even from a bench type set up, PSU to the side of the case and leave the Xion in for the testing
m
0
l
August 29, 2013 7:33:41 PM

since i changed the ram i am just gonna leave it be until i get another bsod then ill swap the PSU. The bsod could take awhile tho cause i cant make it crash and its random
m
0
l
a b $ Windows 7
August 29, 2013 7:38:28 PM

Know how that goes ;) 
m
0
l
August 29, 2013 9:16:12 PM

alright well that didnt take long just bsoded again guess im gonna switch out the PSU now

m
0
l
a b $ Windows 7
August 29, 2013 9:20:27 PM

Will keep fingers crossed ;) 
m
0
l
August 30, 2013 12:44:01 PM

alright same BSOD again anything else?

i think i might have found a way to force the bsod the last 3 bsods happened while watching past broadcasts on twitch dosent seem to happen on live streams tho
m
0
l
a b $ Windows 7
August 30, 2013 2:19:58 PM

Could you check in the advanced/secondary timings and see what the tRFC is at
m
0
l
a b $ Windows 7
August 30, 2013 2:48:36 PM

Try setting those to 172 and see what happens
m
0
l
a b $ Windows 7
August 30, 2013 2:59:07 PM

See how it goes and let me know if it blue screens and if so what the error code is
m
0
l
August 30, 2013 3:00:23 PM

will but so far all the recent bsods have been the same as the last 2 i posted in the dmp files
m
0
l
a b $ Windows 7
August 30, 2013 3:07:27 PM

Hopefully it won't, if it does can try the DRAM voltage up another + 0.04
m
0
l
August 30, 2013 6:50:34 PM

alright bsod again

bug check code
0x00000124
parameter 1
00000000`00000000
parameter 2
fffffa80`0d26b028
parameter 3
00000000`be000000
parameter 4
00000000`0100110a
caused by driver
hal.dl
caused by address
hal.dll+12a3b
x64
crash address
ntoskrnl.exe+75b80
m
0
l

Best solution

a b $ Windows 7
August 30, 2013 7:01:59 PM

Okay try tRFC at 208 and DRAM voltage + 0.03, think that might do it, may also want vCore up just a hair + 0.006
Share
August 30, 2013 7:06:06 PM

ok so DRAM voltage should be at 1.512 now?

alright set it at tRFC 208 and voltage 1.512

m
0
l
a b $ Windows 7
August 30, 2013 8:14:09 PM

Give it a shot ;) 
m
0
l
August 30, 2013 10:45:04 PM

alright its been a few hours still no bsod gonna let it run twitch videos overnight and hope it holds up

m
0
l
a b $ Windows 7
August 30, 2013 11:29:56 PM

Keep me updated, I'm hitting the hay for a few hours, long day tomorrow ;) 
m
0
l
August 31, 2013 9:25:47 AM

12+ hours in still no bsod could be fixed just gonna keep it running for at least another 12 hours, so if this was the problem with the ram i have in now do you think this was also the problem with the ram i RMAed.
m
0
l
a b $ Windows 7
August 31, 2013 1:41:33 PM

Prob not exactly the same, but in the area i.e. need adjustments to advance timings and or voltages, give me a holler when you have the others
m
0
l
a b $ Windows 7
August 31, 2013 2:05:08 PM

Can prob go ahead and close the thread
m
0
l
!