i7 2600k BSOD possible degradation?

christian5011

Reputable
Feb 8, 2016
7
0
4,510
Hello guys,

Well its my first post here because normally I find an answer in other people posts, but this time I can't find a solution to my problem. Also first of all sorry for my english.

I will leave here my pc specs:
- CPU: Intel Core i7 2600K
- MB: ASRock Z77 Extreme4-M
- GPU: Gigabyte GeForce GTX 570 OC 1280MB GDDR5
- RAM: G.Skill Ripjaws X DDR3 2133 8GB 2x4GB CL9
- PS: Corsair GS800 V2 800W Gaming Series

My problem is that Im having WHEA_UNCORRECTABLE_ERROR, since last week. The weird thing is that its not on load as I would expect, it's when Im just browsing the internet or whatching a film. I had the procesor with OC since the last 8 months without any problem, at 4.4ghz and with the vcore at 1.3v (wich I dont think its something crazy). I leave here a link to the BSOD details (sorry they are on spanish but I think its easy to understand): BSOD LINK

After these BSOD I've put the CPU on stock clock and then I never got another BSOD except when trying to install VirtualBox, I don't know if this is related with the main problem but its also weird, I couldn't install it, every time I tried I got a BSOD like when I had the CPU OCed. This is not really important but I will leave it here just in case its usefull information.

I've shearched some answers and some people pointed out that it could be CPU degradation, but I dont know how it can happen if I never had high temperature or high voltage to the CPU. Max temps dont even pass 65ºC.

Thanks for your help, and fell free to ask if you need more information.
 

Tradesman1

Legenda in Aeternum
Might try running Check disk and scandisk - scandisk runs fairly quickly but Checkdisk I normally run overnight for Scandisk go to the command Prompt as admin and run the command SFC /SCANNOW for checkdisk same at the Command Prompt as Admin run CHKDSK /F /R it will ask if you want to run at next boot, say Yes and reboot
 

christian5011

Reputable
Feb 8, 2016
7
0
4,510

I've run scandisk and no problem here:
------------------------------------------------------------------------------------------------
Code:
C:\WINDOWS\system32>sfc /scannow

Iniciando examen en el sistema. Este proceso tardará algún tiempo.

Iniciando la fase de comprobación del examen del sistema.
Se completó la comprobación de 100%.

Protección de recursos de Windows no encontró ninguna infracción
de integridad.
------------------------------------------------------------------------------------------------

I will run the check disk now and I will post the result.

Thank you
 

christian5011

Reputable
Feb 8, 2016
7
0
4,510

Okey Im going to increase a bit the vcore and check if it crash (the less I can raise it is 0.05v). I will answer if it crash or not, but I can't know it doing stress test or something because it doesn't crash doing that.

And I use the offset method.
 

christian5011

Reputable
Feb 8, 2016
7
0
4,510


Ok here are the CHKDSK results (sorry they are on spanish...):
Code:
Comprobando el sistema de archivos en C:
El tipo del sistema de archivos es NTFS.

Se ha programado una comprobación del disco.
Windows comprobará ahora el disco.                                        

Etapa 1: Examen de la estructura básica del sistema de archivos...
  277760 registros de archivos procesados.                                                         Comprobación de archivos completada.
  3842 registros de archivos grandes procesados.                          0 registros de archivos no válidos procesados.                     
Etapa 2: Examen de la vinculación de nombres de archivos...
  344678 entradas de índice procesadas.                                                        Comprobación de índices completada.
  0 archivos no indizados examinados.                                  0 archivos no indizados recuperados en objetos perdidos.                   
Etapa 3: Examen de los descriptores de seguridad...
Liberando 875 entradas de índice no usadas del índice $SII del archivo 0x9.
Liberando 875 entradas de índice no usadas del índice $SDH del archivo 0x9.
Liberando 875 descriptores de seguridad no usados.
Comprobación de descriptores de seguridad completada.
  33460 archivos de datos procesados.                                    CHKDSK está comprobando el diario USN...
  41015680 bytes de USN procesados.                                                            Se ha completado la comprobación del diario USN.

Etapa 4: Búsqueda de clústeres incorrectos en los datos del archivo de usuario...
  277744 archivos procesados.                                                                Comprobación de datos de archivo completada.

Etapa 5: Búsqueda de clústeres incorrectos disponibles...
  43657544 clústeres disponibles procesados.                                                        La comprobación del espacio disponible se completó.

Se examinó el sistema de archivos sin encontrar problemas.
No se requieren más acciones.

 219263999 KB de espacio total en disco.
  44148208 KB en 139464 archivos.
     92880 KB en 33461 índices.
         0 KB en sectores defectuosos.
    392731 KB en uso por el sistema.
El archivo de registro ha ocupado      65536 kilobytes.
 174630180 KB disponibles en disco.

      4096 bytes en cada unidad de asignación.
  54815999 unidades de asignación en disco en total.
  43657545 unidades de asignación disponibles en disco.

Información interna:
00 3d 04 00 68 a3 02 00 ae 1a 05 00 00 00 00 00  .=..h...........
1c 01 00 00 4e 00 00 00 00 00 00 00 00 00 00 00  ....N...........

Windows ha finalizado la comprobación del disco.
Espere mientras se reinicia el sistema.

It seems that there aren't errors on the disk.
 

christian5011

Reputable
Feb 8, 2016
7
0
4,510


Yes, I have the last BIOS update (1.80) and drivers. No I don't have any new hardware, about software I dont think so, but I install and unistall a lot of programs so...

Btw, since I raised de vcore a bit it hasn't crashed. It's been only a day though.
 

Tradesman1

Legenda in Aeternum
Any power outages or surges recently? Might have thrown the BIOS off, also could be the PSU getting weak and not putting out the power it used to, had that happen on a rig a few years back, drove me crazy for a few days and finally broke it down through it on the bench and plugged into a test PSU and all was fine. Back to the PSU it was with and problems back.
 

christian5011

Reputable
Feb 8, 2016
7
0
4,510

Well there has been a blackout like a month ago I dont know if it could be that. The PSU I think its fine, I've tested the voltages and it doesn't drop or anything on load, but I dont have a test PSU to compare...

Yesterday I did a 3 hours full load stress test and it was absolutley fine, but today again on light work a new BSOD... CLOCK_WATCHDOG_TIMEOUT.
I leave the results here (again, its the first BSOD on the pdf, the second one its not from now...): BSOD

I dont know what is going on... this CPU always has been a beast on overclock...

Thanks for your replies and help btw :)

P.S.: I've installed MSI Afterburner like a month ago, could be that? I dont know if it has something to do, just crossed my mind... A long time ago Afterburner causes me constants BSOD, could be this again...
 

christian5011

Reputable
Feb 8, 2016
7
0
4,510

I didn't post anything because I wanted to do a lot of testing before answering again. I've unistalled msi afterburner and it still crashed. I did a clean windows install, and still crashed, I tried turning off LLC and still crashed.

I've done a lot of testing and nothing worked out, overclocking the cpu caused a bsod in less than 2 days.

Now the thing I would want to know is if the cpu is the failing part or its the mobo, because if its the mobo I could search for an other one, still better than upgrading to the new socket.

But if the failing component is the cpu and I buy a new mobo it will be wasted money... I dont have any other pc with lga 1155 to test the cpu so I dont know what to do...