bluescreen WEHA_UNCORRECTABLE_ERROR wtf?

[VeryDogeTV]

Hello!

 

Just a few minutes ago i gained a Bluescreen 3 Times with " WHEA_UNCORRECTABLE_ERROR " ( sounds dangerous to me <:D )

after the 3rd time ( Now ) it kinda works, but im not sure.

Just to make sure i wanted to ask you guys if its anything dangerous, did i do something wrong etc...

Google dose'nt help me really here.

Thanks for answers!

 

 

 

 

[NinjaJc01]

3 minutes ago, VeryDogeTV said:

Hello!

 

Just a few minutes ago i gained a Bluescreen 3 Times with " WHEA_UNCORRECTABLE_ERROR " ( sounds dangerous to me <:D )

after the 3rd time ( Now ) it kinda works, but im not sure.

Just to make sure i wanted to ask you guys if its anything dangerous, did i do something wrong etc...

Google dose'nt help me really here.

Thanks for answers!

 

 

 

 

https://msdn.microsoft.com/en-us/library/windows/hardware/ff557321(v=vs.85).aspx

Find out which code it is, if it happens again, and that will show you why it bluescreened.

[VeryDogeTV]

Just now, NinjaJc01 said:

https://msdn.microsoft.com/en-us/library/windows/hardware/ff557321(v=vs.85).aspx

Find out which code it is, if it happens again, and that will show you why it bluescreened.

there is no code, just some text that my PC crashed and then this WHEA stuff

[NinjaJc01]

1 minute ago, VeryDogeTV said:

there is no code, just some text that my PC crashed and then this WHEA stuff

There would be an error code, like 0x01 or something.

[VeryDogeTV]

1 minute ago, NinjaJc01 said:

There would be an error code, like 0x01 or something.

it just happened again. hold on i try and get the picture

[NEDIX]

As far as I can tell this is CPU related. Do you overclock/overvolt? "These parameter descriptions apply if the processor is based on the x64 architecture, or the x86 architecture that has the MCA feature available (for example, Intel Pentium Pro, Pentium IV, or Xeon)." source

[NinjaJc01]

Just now, VeryDogeTV said:

it just happened again. hold on i try and get the picture

Thank you.

[VeryDogeTV]

1 minute ago, NinjaJc01 said:

There would be an error code, like 0x01 or something.

[VeryDogeTV]

Just now, NEDIX said:

As far as I can tell this is CPU related. Do you overclock/overvolt? "These parameter descriptions apply if the processor is based on the x64 architecture, or the x86 architecture that has the MCA feature available (for example, Intel Pentium Pro, Pentium IV, or Xeon)." source

i did some overclocking just minutes before the first bluescreen, but then i instantly reset everything

[NinjaJc01]

1 minute ago, NEDIX said:

As far as I can tell this is CPU related. Do you overclock/overvolt? "These parameter descriptions apply if the processor is based on the x64 architecture, or the x86 architecture that has the MCA feature available (for example, Intel Pentium Pro, Pentium IV, or Xeon)." source

Not always. It depends on the code the error provides. One code means that it was the CPU, another means PCI etc.

[NinjaJc01]

1 minute ago, VeryDogeTV said:

Damn Windows 8/8.1/10...

[NinjaJc01]

Just now, NinjaJc01 said:

Damn Windows 8/8.1/10...

 

2 minutes ago, VeryDogeTV said:

it just happened again. hold on i try and get the picture

 This bug check is typically related to physical hardware failures. It can be heat related, defective hardware, memory or even a processor that is beginning to fail or has failed. If over-clocking has been enabled, try disabling it. Confirm that any cooling systems such as fans are functional. Run system diagnostics to confirm that the system memory is not defective. It is less likely, but possible that a driver is causing the hardware to fail with this bug check.

[VeryDogeTV]

1 minute ago, NinjaJc01 said:

Damn Windows 8/8.1/10...

Win 10

[NinjaJc01]

1 minute ago, VeryDogeTV said:

Win 10

I'm damning the three of them, but yeah...

System specs? Overclocking?

[VeryDogeTV]

2 minutes ago, NinjaJc01 said:

Damn Windows 8/8.1/10...

 

2 minutes ago, NinjaJc01 said:

Not always. It depends on the code the error provides. One code means that it was the CPU, another means PCI etc.

 

 

[VeryDogeTV]

1 minute ago, NinjaJc01 said:

I'm damning the three of them, but yeah...

System specs? Overclocking?

GTX 1070

i5 4690k

16 GB DDR3 RAM

2x HDD 2TB

and other stuff

[NinjaJc01]

1 minute ago, VeryDogeTV said:

GTX 1070

i5 4690k

16 GB DDR3 RAM

2x HDD 2TB

and other stuff

Overclocks?

[VeryDogeTV]

2 minutes ago, NinjaJc01 said:

I'm damning the three of them, but yeah...

System specs? Overclocking?

 

7 minutes ago, NEDIX said:

As far as I can tell this is CPU related. Do you overclock/overvolt? "These parameter descriptions apply if the processor is based on the x64 architecture, or the x86 architecture that has the MCA feature available (for example, Intel Pentium Pro, Pentium IV, or Xeon)." source

 

[VeryDogeTV]

Just now, NinjaJc01 said:

Overclocks?

None. Just automatic Boost on CPU, it goes up to 3.8 

[NEDIX]

Event Viewer might give you more details. Look under the System tab under "Windows Logs".

[VeryDogeTV]

1 minute ago, NEDIX said:

Event Viewer might give you more details. Look under the System tab under "Windows Logs".

Event Viewer just crashes as soon as i click something

[VeryDogeTV]

4 minutes ago, NEDIX said:

Event Viewer might give you more details. Look under the System tab under "Windows Logs".

now it opened, but i dont see any fishy.

[NEDIX]

0.77GHz is most likely just a throttling power saving feature. Don't think we're going to be able to help you. Try playing around with NB/SB/RAM/CPU voltages (bump in very very small increments).

[VeryDogeTV]

1 minute ago, NEDIX said:

0.77GHz is most likely just a throttling power saving feature. Don't think we're going to be able to help you. Try playing around with NB/SB/RAM/CPU voltages (bump in very very small increments).

 

8 minutes ago, NinjaJc01 said:

Overclocks?

 

Should i be worried??

 

[NEDIX]

Just now, VeryDogeTV said:

Should i be worried??

Nah all of those probably come down to the same hardware error. Sift through there and see if you can find something that correlates to your problem. Remember the time when you get another crash, that way you can just scroll back and see what happened right before the BSOD.