Jump to content

So basically I started getting this blue screen on my PC . My specs are :

Corsair 400 

Seasonic SSR 650W

Gigabyte H110M-A

I7 6700K

Asus Strix 1070 

Team Vulcan 16GB

240GB SSD

1TB HDD 

So I recently bought a new CPU . No issues for a while . I got rid of my 6600K for some more performance . Anyways everything was fine . Installed new ram sticks from Team Vulcan . Old ram was from Crucial . Okay no issues . Got a new heat set from Asus and installed the drivers for wireless connection . They are the Asus Strix Wireless . No issues . I've been gaminf for a whole week without issues . Gaming load all day but now all of a sudden this is happening . Someone please help me :( the game will just lock up and then I get a blue screen 

Link to comment
https://linustechtips.com/topic/715585-bdo-appearing-says-clock_watchdog_timeout/
Share on other sites

Link to post
Share on other sites

5 minutes ago, The_Dylmyster said:

Is the BIOS up to date becasue with the skylake i7s you need a BIOS update that fixes the microcode! Also have you actually seen a good performance improvement witht he new i7?

I'm looking here . http://www.gigabyte.us/products/product-page.aspx?pid=5589#bios

I see the newest one . I don't believe I have that newest bios version but I have the one below it . The newest bios update fixes this ? .

And yes the i7 is great . If I can stop these blue screens ....

Link to post
Share on other sites

8 minutes ago, The_Dylmyster said:

don't run that as it can damage a CPU but if the update doesnt fix it you could just pull one module of ram out test it, then do it with the other stick(s)

How could it damage my cpu? I've got a Cryorig H5 Universal btw. I also have my old set of ram still 

Link to post
Share on other sites

3 minutes ago, The_Dylmyster said:

it is made to stress CPUs very hard and you should only use it if you want to show off an awesome overclock or something like that!

But shouldn't I use it to stress my CPU and ram to see faulty areas ?

Link to post
Share on other sites

1 minute ago, The_Dylmyster said:

Also how often does the blue screen show up and how long after boot?

I'll try updating the bios tomorrow along with updating my GPU drivers. I feel like this is a pretty good bet since I didn't make any major hardware changes lately . It late right now . The blue screens took place after a while of using my pc . I got two of them today while gaming. I'll give this a shot though and keep yoy updated . Happy New Year BTW! 

Link to post
Share on other sites

14 hours ago, aisle9 said:

Your overclock is unstable. Up the voltage or drop the clock. Should take care of it.

Why just assume someone is a noob at overclocking when they haven't said anything about their system being overclocked?

Link to post
Share on other sites

6 hours ago, Mac070 said:

I'm not overclocking anything . 

My bad, then. You've got a 6700K and a BSOD I've only come across while overclocking, so it seemed like a logical step to take. Have you tried anything else since then, and is the problem still ongoing?

 

36 minutes ago, The_Dylmyster said:

Why just assume someone is a noob at overclocking when they haven't said anything about their system being overclocked?

Go back and reread my post. Where, exactly, did I call anyone a noob, or even hint at someone being a noob for that matter? I've only encountered that BSOD when my overclock was unstable, and because the OP had a 6700K, the logical assumption on my part was that it was an unstable OC. You don't have to be a noob to have an unstable OC, nor do you have to be a noob to stumble across a new and exciting BSOD that you've never hit before.

 

You do, however, have to be an absolute noob in a tech forum to call out someone who's offering help for, you know, offering help.

I enjoy buying junk and sinking more money than it's worth into it to make it less junk.

Link to post
Share on other sites

1 hour ago, aisle9 said:

My bad, then. You've got a 6700K and a BSOD I've only come across while overclocking, so it seemed like a logical step to take. Have you tried anything else since then, and is the problem still ongoing?

 

Go back and reread my post. Where, exactly, did I call anyone a noob, or even hint at someone being a noob for that matter? I've only encountered that BSOD when my overclock was unstable, and because the OP had a 6700K, the logical assumption on my part was that it was an unstable OC. You don't have to be a noob to have an unstable OC, nor do you have to be a noob to stumble across a new and exciting BSOD that you've never hit before.

 

You do, however, have to be an absolute noob in a tech forum to call out someone who's offering help for, you know, offering help.

Im just saying that you should ask what clock speed they are running it on before you say that its an unstable overclock.

Link to post
Share on other sites

On 1/1/2017 at 7:15 PM, The_Dylmyster said:

Im just saying that you should ask what clock speed they are running it on before you say that its an unstable overclock.

Erm... Well I don't want to argue but I'm not overclocking . You guys are just trying to help but anyways I swapped my memory out and it was working longer than before . But I just got another BSOD that said Whea_Uncorrectable_Error. 

On 1/1/2017 at 5:50 PM, aisle9 said:

My bad, then. You've got a 6700K and a BSOD I've only come across while overclocking, so it seemed like a logical step to take. Have you tried anything else since then, and is the problem still ongoing?

 

Go back and reread my post. Where, exactly, did I call anyone a noob, or even hint at someone being a noob for that matter? I've only encountered that BSOD when my overclock was unstable, and because the OP had a 6700K, the logical assumption on my part was that it was an unstable OC. You don't have to be a noob to have an unstable OC, nor do you have to be a noob to stumble across a new and exciting BSOD that you've never hit before.

 

You do, however, have to be an absolute noob in a tech forum to call out someone who's offering help for, you know, offering help.

Know anything about the whea_Uncorrectable_error?

 

Link to post
Share on other sites

On 1/1/2017 at 7:15 PM, The_Dylmyster said:

Im just saying that you should ask what clock speed they are running it on before you say that its an unstable overclock.

Erm... Well I don't want to argue but I'm not overclocking . You guys are just trying to help but anyways I swapped my memory out and it was working longer than before . But I just got another BSOD that said Whea_Uncorrectable_Error. 

On 1/1/2017 at 5:50 PM, aisle9 said:

My bad, then. You've got a 6700K and a BSOD I've only come across while overclocking, so it seemed like a logical step to take. Have you tried anything else since then, and is the problem still ongoing?

 

Go back and reread my post. Where, exactly, did I call anyone a noob, or even hint at someone being a noob for that matter? I've only encountered that BSOD when my overclock was unstable, and because the OP had a 6700K, the logical assumption on my part was that it was an unstable OC. You don't have to be a noob to have an unstable OC, nor do you have to be a noob to stumble across a new and exciting BSOD that you've never hit before.

 

You do, however, have to be an absolute noob in a tech forum to call out someone who's offering help for, you know, offering help.

Know anything about the whea_Uncorrectable_error?

 

Link to post
Share on other sites

4 hours ago, Mac070 said:

Know anything about the whea_Uncorrectable_error?

 

That's another one I've only seen when overclocking. Are you sure there's not a random setting in BIOS that would trigger an overclock? Do you have XMP turned on?

I enjoy buying junk and sinking more money than it's worth into it to make it less junk.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×