[Need help] How likely to get a bad CPU?

[xorbe]

Yeah, there was a rash of faulty skylakes reported in small numbers in each forum it seems.

 

[Parn]

Jeez... without any serious competition from AMD, Intel is getting so lazy that their QA has also gone down the toilet.

 

[Vayra86]

post the frigging BSOD code ffs
and the minidump ///
you don't have a bad cpu ... that doesn't happen ever ...

Stop jumping to conclusions and blanket statements.

Things in tech change all the time.

Kind regards, my sig.

 

[crazyeyesreaper]

Yeah i had a junk 6700K retail chip BSOD on OS install only bios was fine. Did an RMA through Intel new chip works fine no problems the BSODs pointed to memory however multiple memory kits same issue. Eventually turned out to be a bum memory controller on the CPU.

 

[overclocking101]

i had an i5 750 years ago that did this, wish I had seen this thread sooner. Glad you got it sorted

 

[zakuta]

Owner of faulty i5 6600K reporting from Finland.

New build:
Asus Z170 Pro Gaming
i5 6600k
Kingston Fury HyperX 2 x 4 GB
Seasonic 650W PSU
Samsung 250GB SSD-drive
Asus Geforce GTX-970

I make this short: almost the same story/did the same tests as the OP except i got BSOD's "machine check exception" and "clock watchdog timeout". Finally i bought new i5 6600k processor, installed it and voilá; no more BSOD's.
So the faulty one is going back to retailer tomorrow.

I didn't overclock the old one, it actually worked for one day after build (i played games, surfed in the internet etc.) and the next day bluescreens started to happen.

I was extremely careful when installing cpu in the socket, so i don't think i would have damaged it somehow.

I know this forum is old, but I have the same problem with an i5-9400F, I have already tried updating the BIOS, changing the disk and ram, flashing the bios.

In Windows I constantly get the MACHINE_CHECK_EXCEPTION, and sometimes the CLOCK_WATCHDOG_TIMEOUT, while in Linux the usage and the temperature go up for everything.

I have had this problem since the first day I assembled and installed the PC:
- MSI Z370-A Pro
- i5-9400F
- Kingston 2x8GB 2666MHz
- ASUS Geforce GTX 1660 Ti
- Sentey 550W 80+
- HP S700 500GB (SSD)
- Seagate Barracuda 1TB (HDD)


About 3 days ago the processor reached 93°C with a minimum graphics game, that's why I started to worry

 

[Nuckles56]

Holy necro batman...

 

[Vayra86]

I know this forum is old, but I have the same problem with an i5-9400F, I have already tried updating the BIOS, changing the disk and ram, flashing the bios.

In Windows I constantly get the MACHINE_CHECK_EXCEPTION, and sometimes the CLOCK_WATCHDOG_TIMEOUT, while in Linux the usage and the temperature go up for everything.

I have had this problem since the first day I assembled and installed the PC:
- MSI Z370-A Pro
- i5-9400F
- Kingston 2x8GB 2666MHz
- ASUS Geforce GTX 1660 Ti
- Sentey 550W 80+
- HP S700 500GB (SSD)
- Seagate Barracuda 1TB (HDD)


About 3 days ago the processor reached 93°C with a minimum graphics game, that's why I started to worry

Increase VCCSA voltage a bit, watchdog timeouts are scheduler/system agent related sometimes.

Or alternatively run stock settings. This sounds like you have a bad overclock running.

 

[P4-630]

Or alternatively run stock settings. This sounds like you have a bad overclock running.

- i5-9400F

Uhm .. He has a locked CPU.

 

[zakuta]

Increase VCCSA voltage a bit, watchdog timeouts are scheduler/system agent related sometimes.

Or alternatively run stock settings. This sounds like you have a bad overclock running.

Hmm .. I use the default settings in the BIOS, it is also a processor that is not unlocked for overclocking.

The voltage is set like this automatically: (Sorry for the poor quality of the image)

 

[Vayra86]

I am not that familiar with i5-F CPUs, I know the multiplier is locked, but are the voltage settings? Either way, when they say auto, it should just work fine out of the box and could be reason for RMA, if you get similar errors on a normal Windows 10 install with no tweaks.

Its merely a suggestion based on my experience with Coffee Lake. Disregard it anyway, because 1.168V is on the high side especially given your pretty regular memory and no OC.

93C is hot though, Tjunction is 100C so a hot summer day can put your system beyond temp limits. Maybe the solution is hidden in there - lowering temps will reduce current leakage and may also avoid the BSOD. Still however does not remove the grounds you have here for RMA if it happens on a stock situation.

 

[zakuta]

I am not that familiar with i5-F CPUs, I know the multiplier is locked, but are the voltage settings? Either way, when they say auto, it should just work fine out of the box and could be reason for RMA, if you get similar errors on a normal Windows 10 install with no tweaks.

Its merely a suggestion based on my experience with Coffee Lake. Disregard it anyway, because 1.168V is on the high side especially given your pretty regular memory and no OC.

93C is hot though, Tjunction is 100C so a hot summer day can put your system beyond temp limits. Maybe the solution is hidden in there - lowering temps will reduce current leakage and may also avoid the BSOD. Still however does not remove the grounds you have here for RMA if it happens on a stock situation.

I did several clean installs of Windows and it was always the same, blue screen that made the pc unusable.

Searching about the problem I came across this forum, so I thought I should buy a new processor.

Right now I am using Linux since it is the only system where I can use it, but it still reaches very high temperatures and use, and every so often the computer restarts itself.

I am not that familiar with i5-F CPUs, I know the multiplier is locked, but are the voltage settings? Either way, when they say auto, it should just work fine out of the box and could be reason for RMA, if you get similar errors on a normal Windows 10 install with no tweaks.

Its merely a suggestion based on my experience with Coffee Lake. Disregard it anyway, because 1.168V is on the high side especially given your pretty regular memory and no OC.

93C is hot though, Tjunction is 100C so a hot summer day can put your system beyond temp limits. Maybe the solution is hidden in there - lowering temps will reduce current leakage and may also avoid the BSOD. Still however does not remove the grounds you have here for RMA if it happens on a stock situation.

I lowered the CPU SA to 1,050, which according to the BIOS, is the default. The processor temperature does not drop below 75°C, and puts these peaks up to 85°C playing GTA V in story mode (graphics at maximum). I know that Intel's stock cooler is not very good, but is this temperature normal? I did the test from Linux, but I have a 240GB SSD with Windows 10 so I could also try it.

I also checked the temperatures at the beginning, when the only thing that opens is Steam it reaches 70°C, and without anything open it does not drop below 45°C

 

[Vayra86]

And how are the crashes now with the lower voltage? If you crash less, might very well be temp related but 84C is well within safe limits.

Is, by any chance, some sort of multi core enhancement setting (auto OC) active on the motherboard? Was a thing with coffee lake CPUs getting Z-boards with stock settings that activated all core OC. That would also answer why the auto voltage was rather high on SA.

The stock Intel cooler with an i5-F, well it can't be great so you should expect something along the lines of 80C indeed and perhaps even into 90C regions at full sustained loads, but voltage obviously matters a lot here.

 

[zakuta]

And how are the crashes now with the lower voltage? If you crash less, might very well be temp related but 84C is well within safe limits.

Is, by any chance, some sort of multi core enhancement setting (auto OC) active on the motherboard? Was a thing with coffee lake CPUs getting Z-boards with stock settings that activated all core OC. That would also answer why the auto voltage was rather high on SA.

The stock Intel cooler with an i5-F, well it can't be great so you should expect something along the lines of 80C indeed and perhaps even into 90C regions at full sustained loads, but voltage obviously matters a lot here.

On Linux it crashed only a few times, so I decided to use another SSD that already had Windows installed. In Task Manager, processes such as "Windows Update Host Service", "Windows Compatibility Telemetry" or "wsappx" were using a lot of processor from time to time. And even the browser reached up to 50% at startup and 30% on some pages.

I decided to install BlueScreenView to see what the blue screen problem was and I found that it was the "ntoskrnl.exe", as seen in the image.

It's been about 10 minutes with the system on and nothing has failed yet, but it still makes me very nervous since it always crashes out of nowhere

On Linux it crashed only a few times, so I decided to use another SSD that already had Windows installed. In Task Manager, processes such as "Windows Update Host Service", "Windows Compatibility Telemetry" or "wsappx" were using a lot of processor from time to time. And even the browser reached up to 50% at startup and 30% on some pages.

I decided to install BlueScreenView to see what the blue screen problem was and I found that it was the "ntoskrnl.exe", as seen in the image.

It's been about 10 minutes with the system on and nothing has failed yet, but it still makes me very nervous since it always crashes out of nowhere

Update: I was able to install CSGO and play without problems (Before it crashed in the main menu)

Temperatures are not that hot anymore unless you put the game on unlimited FPS.

The only thing I see weird are these voltages (As seen in the first image using OpenHardwareMonitor)

On Linux it crashed only a few times, so I decided to use another SSD that already had Windows installed. In Task Manager, processes such as "Windows Update Host Service", "Windows Compatibility Telemetry" or "wsappx" were using a lot of processor from time to time. And even the browser reached up to 50% at startup and 30% on some pages.

I decided to install BlueScreenView to see what the blue screen problem was and I found that it was the "ntoskrnl.exe", as seen in the image.

It's been about 10 minutes with the system on and nothing has failed yet, but it still makes me very nervous since it always crashes out of nowhere


Update: I was able to install CSGO and play without problems (Before it crashed in the main menu)

Temperatures are not that hot anymore unless you put the game on unlimited FPS.

The only thing I see weird are these voltages (As seen in the first image using OpenHardwareMonitor)

I was about 15 minutes, when I changed the resolution to 16:10 the processor went up to 80°C at once, then I tried to put it in 4: 3 and there the blue screen jumped

 

[Vayra86]

On Linux it crashed only a few times, so I decided to use another SSD that already had Windows installed. In Task Manager, processes such as "Windows Update Host Service", "Windows Compatibility Telemetry" or "wsappx" were using a lot of processor from time to time. And even the browser reached up to 50% at startup and 30% on some pages.

I decided to install BlueScreenView to see what the blue screen problem was and I found that it was the "ntoskrnl.exe", as seen in the image.

View attachment 185544
View attachment 185545
It's been about 10 minutes with the system on and nothing has failed yet, but it still makes me very nervous since it always crashes out of nowhere


Update: I was able to install CSGO and play without problems (Before it crashed in the main menu)

Temperatures are not that hot anymore unless you put the game on unlimited FPS.

The only thing I see weird are these voltages (As seen in the first image using OpenHardwareMonitor)
View attachment 185585


I was about 15 minutes, when I changed the resolution to 16:10 the processor went up to 80°C at once, then I tried to put it in 4: 3 and there the blue screen jumped

View attachment 185597

Display output changes causing bsods... Okay.

This is a big can of worms Can you test without the dedicated GPU and/or was this running over the IGP? I'd want to exclude the GPU first now.

 

[zakuta]

Some big problem must have. The temperatures are also very unstable, I just touched to install the Nvidia drivers next to the Geforce Experience and suddenly the processor temperature rose to 65-70°C
Also, this processor does not have integrated graphics.


Today or tomorrow I plan to take it to the store where I bought most of the components so you can check it well.

Right now I am only using Edge, OpenHardwareMonitor and installing the Nvidia drivers and it already sets these temperatures:

Display output changes causing bsods... Okay.

This is a big can of worms Can you test without the dedicated GPU and/or was this running over the IGP? I'd want to exclude the GPU first now.

The strange thing is that playing there are no temperatures or use that high, but when I do an activity such as opening or closing a program it jumps up.

Some big problem must have. The temperatures are also very unstable, I just touched to install the Nvidia drivers next to the Geforce Experience and suddenly the processor temperature rose to 65-70°C
Also, this processor does not have integrated graphics.


Today or tomorrow I plan to take it to the store where I bought most of the components so you can check it well.

Right now I am only using Edge, OpenHardwareMonitor and installing the Nvidia drivers and it already sets these temperatures:

The strange thing is that playing there are no temperatures or use that high, but when I do an activity such as opening or closing a program it jumps up.

This keeps getting better .. I opened the CSGO directly from Geforce Experience, and while loading the casual game, all the cores went to 100% .. followed with a bsod "CLOCK_WATCHDOG_TIMEOUT"

Some big problem must have. The temperatures are also very unstable, I just touched to install the Nvidia drivers next to the Geforce Experience and suddenly the processor temperature rose to 65-70°C
Also, this processor does not have integrated graphics.


Today or tomorrow I plan to take it to the store where I bought most of the components so you can check it well.

Right now I am only using Edge, OpenHardwareMonitor and installing the Nvidia drivers and it already sets these temperatures:

The strange thing is that playing there are no temperatures or use that high, but when I do an activity such as opening or closing a program it jumps up.


This keeps getting better .. I opened the CSGO directly from Geforce Experience, and while loading the casual game, all the cores went to 100% .. followed with a bsod "CLOCK_WATCHDOG_TIMEOUT"

I was playing about 15 minutes without problems, I did ALT + TAB to see the temperatures and it threw blue screen.

I already updated the drivers and did a SFC / scannow, but still the same

 

[zakuta]

Some big problem must have. The temperatures are also very unstable, I just touched to install the Nvidia drivers next to the Geforce Experience and suddenly the processor temperature rose to 65-70°C
Also, this processor does not have integrated graphics.


Today or tomorrow I plan to take it to the store where I bought most of the components so you can check it well.

Right now I am only using Edge, OpenHardwareMonitor and installing the Nvidia drivers and it already sets these temperatures:



View attachment 185661


The strange thing is that playing there are no temperatures or use that high, but when I do an activity such as opening or closing a program it jumps up.


This keeps getting better .. I opened the CSGO directly from Geforce Experience, and while loading the casual game, all the cores went to 100% .. followed with a bsod "CLOCK_WATCHDOG_TIMEOUT"View attachment 185663


I was playing about 15 minutes without problems, I did ALT + TAB to see the temperatures and it threw blue screen.View attachment 185666

I already updated the drivers and did a SFC / scannow, but still the same

In a couple of hours I was going to take the PC to the store where I bought the components so they checked it, but first I wanted to use the "Intel Proccesor Diagnostic Tool", and these were the temperatures during the frequency test. So I can only say XD