2600K: thread loaded 100% all the time

The first thread in Windows task manager stays loaded at 100% constantly, even if I do a fresh install or roll back the bios. Even running a fresh install of windows 7 doesn't fix it as no program that I would have installed is loading the core down.

Is the chip simply bad?

Ignore everything below here as I THOUGHT prime95 was the problem.

I just got my rig up and running and while I'm testing my 2600k, I notice Prime95 is not working at 100% despite the fact that Windows task manager states all 8 threads are running at 100%.

So in 7 mintues here's how many test each worker copmleted:
1. 0
2. 6
3. 6
4. 6
5. 2
6. 7
7. 6.
8.6

So core 0 is #1&5, right? Is that core dead?! :shrug:

[IMG]http://i55.tinypic.com/4qsx0w.jpg[/IM]

I have seen this before when my overclock is unstable. I think it fails before the process initializes so it just never starts.

Well, I set the CPU speed back to stock. Still same issue.

Turned off and killed Prime95. Core 0 is still 100%. This is a new install of win 7 x64 sp1. SC2 and steam are installed along w/ itunes (and quicktime unfortuantely). Also everything on the ASRock Extreme4 disc that came w/ the board (driver-wise).

Not sure if the core is acting funky or I've overlooked something. :shrug:

http://i53.tinypic.com/abim3t.jpg






I'm somewhat inclined to install windows again.

I decided to reinstal win 7 x64 sp1.

Its 100% fresh. No drivers, nothing. Core 0 still sits at 100%.

Could be a bios update issue. I'll see if I can roll back to fix it.

What version of p95 are you using?

I deleted the partition.

Basically google prime95 and there should be a link to extreme overclockers for the download.

Prime is obviously not the issue as a fresh install still has this issue. I hope it's not the CPU and just a bios problem, I'll find out shortly.

There are plenty versions available, are you running one that's marked as stable in the MersenneForum?

Quote:

---

Originally Posted by felix_w

There are plenty versions available, are you running one that's marked as stable in the MersenneForum?

---

MersenneForum? I'm not familiar... :shrug:

Ah, just goggled it. At this point, prime 95 is not the issue. I think I should change the title as now basically, I've figured out the problem is not prime at all, but the CPU (possibly motherboard?).

Did you try disabling hyperthreading and running 4 threads?

Quote:

---

Originally Posted by dr_sharp

Did you try disabling hyperthreading and running 4 threads?

---

I'd have bought a 2500k if I wanted to do that. ;)


So I guess I have a bad CPU. 1 core stays loaded all the time. Even downgrading the bios and using stock settings doesn't fix it.

Buying second hand wasn't such a good idea.

Try other benchmarks, don't rely on just that stress test.

I test a few 2600K and no problem at all

Here's a picture of what's going on. I have IE open. Only have installed basic drivers for lan, etc that came w/ my ASRock extreme4. The cpu usage doesn't change before or after doing that.

http://i54.tinypic.com/16kx8rb.jpg

If you disable HT, does the CPU still behave in that fashion?

Quote:

---

Originally Posted by CedricFP

If you disable HT, does the CPU still behave in that fashion?

---

Yes, it does.

http://i54.tinypic.com/rkxb9s.jpg

In task manager why not click on show processes from all users so you can see what process is fully loading one of your threads? At idle CPU Usage should be showing close to 0% so there must be something running in the background.

Quote:

---

Originally Posted by unclewebb

In task manager why not click on show processes from all users so you can see what process is fully loading one of your threads? At idle CPU Usage should be showing close to 0% so there must be something running in the background.

---

I did in the 3rd post in the thread:
http://www.xtremesystems.org/forums/...01&postcount=3

Here it is again:

http://i53.tinypic.com/abim3t.jpg


Any ideas? :shurg:

But you didn't click on the "Show processes from all users" button. That will show some more stuff running on your computer.

You need to click "Show processes from all users"

Quote:

---

Originally Posted by unclewebb

But you didn't click on the "Show processes from all users" button. That will show some more stuff running on your computer.

---

Ha sorry for the confusion.

I listed the processes in order of memory usage, from highest to lowest:
http://i52.tinypic.com/969mqo.jpg

NT Kernel and System should be at 0% to 1% on an idle system.

Watch that one and do some Google searching. It's a common problem and can possibly be virus / spyware related. Look at the Network tab and see if there is a lot of unexplained activity in there.

Something is not right when CPU Usage is showing 43% but System Idle Process is showing 70%. Those two are supposed to add up to 100%.

Quote:

---

Originally Posted by unclewebb

NT Kernel and System should be at 0% to 1% on an idle system.

Watch that one and do some Google searching. It's a common problem and can possibly be virus / spyware related. Look at the Network tab and see if there is a lot of unexplained activity in there.

---

Just staring at the network load showed there's 0% usage. That's not hte problem.

I cleared the CMOS again by pulling out the battery and letting it sit 60 seconds.

My System Idle is shoing 93%, but task manager is showing 100% thread usage, which doesn't totally add up.

System is showing 3% steady. With using IE, it jumps around a tad.


Btw, I did a search that netted that result, virus, etc. I never had this issue in my 1156 system (same SSD). Even with this system working w/ a fresh install, 0 drivers isntalled, no internet connection, the problem still exists.

I find it hard to believe it's a spyware/virus.

I think you are correct - it is hardware. Do you have an extra chip or mobo to try?

Most of what I'm reading seems to point to a network driver. You can try disabling or uninstalling your Network Adapters in the Device Manager.

If that fixes the problem then try to get Windows to reload the driver for that Network Adapter.

Quote:

---

Originally Posted by unclewebb

Most of what I'm reading seems to point to a network driver. You can try disabling it.

---

This error occured before installing any drivers. I'll uninstal the driver and even disable the lan, just to see what happens. One sec....

Uninstalled the driver. CPU usage stays constant.

constant high?

You might need to try Process Explorer. It lets you dig a little deeper into what's running on your system. It's freeware.

http://technet.microsoft.com/en-us/s...rnals/bb896653

Quote:

---

Originally Posted by unclewebb

constant high?

You might need to try Process Explorer. It lets you dig a little deeper into what's running on your system. It's freeware.

http://technet.microsoft.com/en-us/s...rnals/bb896653

---

We're on the same page my friend. One step ahead of you.

Looks like the interups are the cause:
http://i56.tinypic.com/rh4rwh.jpg

I've pulled both sticks of ram. It's G.Skill 2x4gb ddr3 1600 ripjaws.

I've also put it in different slots, still the same issue.

The stuff ran fine in my AMD server. :shrug:

So why am I getting all these interups? Besides the motherboard & CPU, all parts have been in older systems. GTX 470 is confirmed to work fine, as is the ram, PSU, etc etc.

Edit:

Tried booting in safe mode. It makes no difference.

Eiither it's the motherboard or the CPU. I don't have a second motherboard or CPU to test, so I'm not sure. I'm thinking it's the CPU, just a hunch.

Do you have updated drivers installed for all of the hardware in the Device Manager? Are there any yellow exclamation points in there or hardware issues like that?

Quote:

---

Originally Posted by unclewebb

Do you have updated drivers installed for all of the hardware in the Device Manager? Are there any yellow exclamation points in there or hardware issues like that?

You could also try booting up in safe mode to see if this problem changes any.

---

Just took a look again since you brought it up. Everything appears fine.

I did try safe mode. CPU usage stayed the same.

Edit:

Took the SSD off of the hotswappable bay in my FT02. Connected it with a different, working sata cable to a SATA6 port. Boots fine. Same problem exists....

I'm going to bed sicne it's late. If anyone has ideas, I'll be back in the morning to try and figure out if it's the CPU or something else.

Latest Google suggestion: reboot with the DVD drive unplugged and anything else you can think of.

Quote:

---

Originally Posted by unclewebb

Latest Google suggestion: reboot with the DVD drive unplugged and anything else you can think of.

---

Caught this before going to bed, so this'll be my last responce until the morning

Yep, just did a restart w/ only the keyboard in both PS/2 ports, video cable and power cable. Only GTX 470 and SSD. 1 Stick of ram in last slot.

The issue remains.

This has to be hardware related. Either the board or the CPU. I can't figure out which one though.

If anyone has any ideas about how to test for that, short of buying an 1155 cpu, I'm all ears. :up:

Contact Intel. If this is the CPU, I'm sure they will have heard of this problem before. It's POSSIBLE it's the motherboard, though.

What happens if you boot up with only 2 cores?

This is 100% either motherboard or CPU, though. A new fresh install should not be doing that and safe mode is a dead giveaway.

I'd RMA the CPU first, as Intel should have had this type of problem reported on bad hardware in the past. I actually remember something like this happening to someone in the past...one core at max usage with nothing running...

Quote:

---

Originally Posted by Falkentyne

Contact Intel. If this is the CPU, I'm sure they will have heard of this problem before. It's POSSIBLE it's the motherboard, though.

What happens if you boot up with only 2 cores?

This is 100% either motherboard or CPU, though. A new fresh install should not be doing that and safe mode is a dead giveaway.

I'd RMA the CPU first, as Intel should have had this type of problem reported on bad hardware in the past. I actually remember something like this happening to someone in the past...one core at max usage with nothing running...

---

I'm much more inclined to believe it is something else: it would have to be an incredibly specific kind of damage to make the CPU flood itself with interrupts. It's much more likely a misbehaving driver or piece of hardware is the culprit, or even a microcode bug triggered by something that the OP is running. An RMA obviously wouldn't fix either.

There's an easy way to find out though: if another OS (a Linux LiveCD will do) runs without problems, it's pretty much surely a software/driver issue.

But he said this was a CLEAN windows install Clean installations don't do this. Otherwise, other people would be having the problems, since it happened in safe mode and without any drivers installed.

So this is impossible, otherwise everyone else would be having the same problem.

So it has to be a problem with the motherboard, BIOS, or hardware fault on the board, or a problem with the CPU.

I just cant remember seeing where I saw this problem before...but I do remember it was hardware caused. And it was some years ago...

Quote:

---

Originally Posted by danielkza

I'm much more inclined to believe it is something else: it would have to be an incredibly specific kind of damage to make the CPU flood itself with interrupts. It's much more likely a misbehaving driver or piece of hardware is the culprit, or even a microcode bug triggered by something that the OP is running. An RMA obviously wouldn't fix either.

There's an easy way to find out though: if another OS (a Linux LiveCD will do) runs without problems, it's pretty much surely a software/driver issue.

---

Quote:

---

Originally Posted by Falkentyne

But he said this was a CLEAN windows install Clean installations don't do this. Otherwise, other people would be having the problems, since it happened in safe mode and without any drivers installed.

So this is impossible, otherwise everyone else would be having the same problem.

So it has to be a problem with the motherboard, BIOS, or hardware fault on the board, or a problem with the CPU.

I just cant remember seeing where I saw this problem before...but I do remember it was hardware caused. And it was some years ago...

---

It's not windows creating the issue.

The first time I log into Windows w/o installing anything, drivers, programs, etc, the first thread/core sits at 100%.

Interestingly, the HT thread associated w/ the core isn't sitting at 100%.

Like I"ve said, I've reverted the bios back. No one in Ket's thread on my motherboard, ASRock Extreme4, is having this issue.


I'm down to the board/cpu as the culprit and I'm inclided to say its the cpu. The board is not throwing any error codes at me.

Do you guys have any idea as how to do some test to eliminate one or the other?

FIGURED IT OUT! (Somewhat)


I decided to try what Danielkza mentioned and installed another OS. I couldn't find my Ubuntu disk, so I tried Server 2K8.

0 CPU usage once everything loads.

I'm thinking SP1 has a driver that's installed for win 7 that screws everything up. What's odd is that it has something to do with a core driver as anything extra would be disabled in safe mode....

I'm going to try to install Win 7 x64 (no SP1) and see if there's an issue there.

Ok, reinstalled Win 7 x64 Ultimate.

This problem came back. I'm looking at a fresh install. I just logged in for the first time. Server 2k8 wasn't doing this...

I could try Pro, just to see if there's something extra in Ultimate. This is really strange.

Edit:

Win 7 pro does the same thing...

What to do? RMA the board?

There has to be a bad driver being installed automatically when you install W7. If server 2K8 is OK then that proves your hardware is OK.

Quote:

---

Originally Posted by unclewebb

There has to be a bad driver being installed automatically when you install W7. If server 2K8 is OK then that proves your hardware is OK.

---

I've done a fresh install again. Updating drivers to see if anything fixes the issue.

The MS process explorer can identify what is causing the interupt? It was late and I didn't have a chance to check it out more.

I'll try reinstalling it and see if it can point me in the right direction.

BTW, I tried disabling everything in device manager that seemed logical (not CPU, etc) and the issue persisted.

Lots of fresh installs, seem to be of no help.

Have you tried reflashing BIOS's ?
Maybe try several different BIOS versions to see if any of this changes this 100% load effect on idle.

Quote:

---

Originally Posted by Buckeye

Lots of fresh installs, seem to be of no help.

Have you tried reflashing BIOS's ?
Maybe try several different BIOS versions to see if any of this changes this 100% load effect on idle.

---

I've Reflashed a few times beteween 1.6 and 1.7 possibly 7 or 8 times at this point. I'll even clear the CMOS after. Nothing changes.

Moved to Sata 6 and disabled booting from Sata 3. No relief. I"m going to get a new PCH driver and see if that'll fix it.

I can download them again, but these are files Ket uploaded (see ASROCK Extreme 4 thread.)

Everything else is hunky dory.

Edit:

Just had an idea, but it involveds a reinstall. Be back in 30 minutes or so...

Edit 2:

Alright, tried to run win 7 in IDE mode. No change.

I reinstalled MS Process Explorer.

Under system, it gives between 9.5% and 10.5% cpu usage for Hardware Interrupts and DPCs.

Sounds like a bad driver or simply there's something wrong w/ the board?

Alright, here's some useful info. I'm not too sure what all of this means, so I need to go googling.

I have 3 errors in the Event Viewer under "Administrative Events:

Here they are in order:

Warning: The time service has set the time with offset 13511017928982584 seconds.

Error: Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

Warning: Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.

DETAIL -
1 user registry handles leaked from \Registry\User\S-1-5-21-3339601781-681715721-2370937544-1000:
Process 472 (\Device\HarddiskVolume2\Windows\System32\winlogon .exe) has opened key \REGISTRY\USER\S-1-5-21-3339601781-681715721-2370937544-1000

Error: The time service has detected that the system time needs to be changed by 8630036 seconds. The time service will not change the system time by more than 54000 seconds. Verify that your time and time zone are correct, and that the time source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->64.4.10.44:123) is working properly.

Warning: The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.

Error: Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

I had similar with a dodgy onboard audio chip. Have you tried disabling absolutely everything in bios? Audio, usb, firewire, lan - everything.

2k8 doesnt have the windows audio service, desktop composition / themes and directx as standard. Thats the only difference between it and 7 in this situation.

If disabling peripherals in bios doesnt solve it then try disabling the windows audio service in 7 and see if that does the trick. If not then disable themes and desktop composition too.

Just shooting you a few thoughts - definitely a tricky one to find the cause of. GL dude.

Quote:

---

Originally Posted by PiLsY

I had similar with a dodgy onboard audio chip. Have you tried disabling absolutely everything in bios? Audio, usb, firewire, lan - everything.

2k8 doesnt have the windows audio service, desktop composition / themes and directx as standard. Thats the only difference between it and 7 in this situation.

If disabling peripherals in bios doesnt solve it then try disabling the windows audio service in 7 and see if that does the trick. If not then disable themes and desktop composition too.

Just shooting you a few thoughts - definitely a tricky one to find the cause of. GL dude.

---

Great idea.

Thanks for the help everyone. Probably should have said this sooner.

Anyways, I'm going to go through each peripheral and see if disabling each alleviates the problem.:up:

Edit:

Alright, basically everything is shut off, even sata 3 (only using sata 6 ports). USB 2.0 and 3.0 are off as is floppy and anything else I could disable. Themes, desktop composition and windows audio are disabled.

The thread is still loaded at 100%!

This is one tricky problem.

LatencyMon can show you exactly which driver is causing an issue. Maybe it can help :)

Quote:

---

Originally Posted by Aginaridan

LatencyMon can show you exactly which driver is causing an issue. Maybe it can help :)

---

I tried this out in Win 7 Starter as well. Generates the same errors.

Here's what latency mon shows with a fresh install, no drivers:
http://i55.tinypic.com/11vp1fd.jpg

Here's after installing the following:
Realtek RTL8111E LAN
Intel Management Engine Driver v7.1.10.1065
Intel PCH Driver v9.2.0.1025
(All from Ket's link's in the ASRock Extreme4 thread.)
http://i54.tinypic.com/n5kb40.jpg

Clutching at straws really but...

Theres a newer chipset driver and management engine on the intel site. Go to the z68 board downloads and they're there.

PCI Latency timer and High precision event timer available in bios to alter?

The other alternative is build up a 2k8 r2 install and see how that fares as its closer to 7 than 2k8 is. I didnt notice before you were running original 2k8 when it worked - thats got more in common with Vista really.

Theres no chance your windows 7 disk has a virus or malware on it is there? Even if you use a legit code some of the torrent iso's are very shady.

It could even be a screwed up management engine rom on your bios chip. Is that board dual chip? If so try switching to bios 2.

Overnight cmos clear with mobo unplugged and battery terminals shorted has fixed a few odd things for me in the past. Infact my p8p67 pro was about to be rma'd but came back to life after at some point during a fortnight of cmos clear / terminals shorted. Had lost all qfan control and chassis fan channels after installing fanxpert and nothing I did would get it back to normal. I did a 3 day clear and it was still goosed. Boxed it up again with cmos set to clear and battery terminals shorted to be sent back. One last try before posting it back (2 weeks later - lazy :lol:) and it was alive. Fine ever since.

Can't think of anything else atm, if I do though i'll post up. Will be checking to see how you get on anyway as this ones a real puzzler.

Quote:

---

Originally Posted by PiLsY

Clutching at straws really but...

Theres a newer chipset driver and management engine on the intel site. Go to the z68 board downloads and they're there.

PCI Latency timer and High precision event timer available in bios to alter?

The other alternative is build up a 2k8 r2 install and see how that fares as its closer to 7 than 2k8 is. I didnt notice before you were running original 2k8 when it worked - thats got more in common with Vista really.

Theres no chance your windows 7 disk has a virus or malware on it is there? Even if you use a legit code some of the torrent iso's are very shady.

It could even be a screwed up management engine rom on your bios chip. Is that board dual chip? If so try switching to bios 2.

Overnight cmos clear with mobo unplugged and battery terminals shorted has fixed a few odd things for me in the past. Infact my p8p67 pro was about to be rma'd but came back to life after at some point during a fortnight of cmos clear / terminals shorted. Had lost all qfan control and chassis fan channels after installing fanxpert and nothing I did would get it back to normal. I did a 3 day clear and it was still goosed. Boxed it up again with cmos set to clear and battery terminals shorted to be sent back. One last try before posting it back (2 weeks later - lazy :lol:) and it was alive. Fine ever since.

Can't think of anything else atm, if I do though i'll post up. Will be checking to see how you get on anyway as this ones a real puzzler.

---

I really do appreciate the help. I've basically spent my whole weekend slaving over this issue.

A few things.

Vista x64 ultimate throws the same problem. I was considering trying an install of XP, but I think that's pushing it and honestly not useful.

I can try 2k8 R2.

I am not pirating any of these OS's. I have a technet lisence. :D Infact, the Win 7 x64 pro install was from a real MS disc, not an Iso I loaded to a USB drive.

I'm first going to install 2k8 R2, then If nothing comes up, I'll start enabling roles etc till either the bug is recreated or not.

I can try to reseat the CPU as someone has mentioned to me, but I have a hunch that's not the issue. I can pull it out anyways and inspect the pins (did this anyways when I got my board).

Beyond that, I can clear the CMOS overnight.

What you're saying is you pulled the battery and left the clear cmos short on overnight? I can do that. :up: Nothing like working while you're sleeping. :ROTF::rofl:

Edit:

I pulled 2k8 off of my server to load to my flash drive. The original file I used was 2K8 R2 SP1. I'll reload that and try to force the CPU to ramp up. Very strange.

Edit 2:

So here's the 2K8 R2 worklog of installation:
CPU USAGE while IDLING:
Fresh: 0%
Added features Wireless Lan and Desktop exerience: 0%
Added Roles File services & Remote desktop: 0%
Added DHCP Server and Print & Document services: 0%
Added Simple TCP/IP Services and Quality Windows Audio Video Experience: 0%
Added Remote Assistance & Bitlocker drive encryption: 0%
Added .NET Framwork 3.5.1: 0%
Added XPS viewer: 0%

At this point, I can't think of anything else to install off the top of my head.

I'm going to try to pull the CPU and reseat, reinstall windows and report back.

Edit 3:

I reseated the CPU. Still doing the same ol' same ol' annoying thing.

Besides letting the bios sit overnight... I am out of ideas beyond RMA for the board (and CPU if that fails).

Edit 4:

Give up, lol. No idea. I'm not even sure if it's the board or the cpu. I'm thinking RMAing the board is easier, so I'll start there.

I will try 2 more things. I am clearing the CMOS for 90 minutes, then trying it again tonight. If that fails, I'll let it sit overnight w/ the battery out and the Clear Cmos pins shorted.

Come tomorrow morning, I'll call ewiz and RMA it most likely. I wonder how well that company treats its customers? I guess we'll find out!

...

Alright, so I allowed the CMOS to clear for abou 2 hours. Rebooted and the Bios continually asked for a password. Cleared the CMOS again and I can enter the bios. Set the storage settings to AHCI, left everything else stock and I'm still getting the problem.

I can try to let the CMOS clear all night, but I have a feeling I'll be RMAing the board tomorrow.

You need to short the cmos pins AND the battery terminal pins - easiest way is to flip the battery upside down.

2k8 R2 and 7 are almost identical at an OS level. If R2 works and 7 doesnt it must be down to services as theres no difference in the way they handle hardware.

I'm as puzzled as you at this point (but probably a lot less frustrated - lol)....

You can try to play with xperf. A random video here and a random article about xperf usage.

Also try to change Windows Power settings from Balanced to High performance.

I still think that's a software/driver problem.

Thanks buddy. I just pulled the board. I'm done with it.

There has to be something inherintly wrong with the board. A fresh install shouldn't be doing this. Other's who own this board as not experiencing the same CPU usage. I actually did change the power settings from balanced to high performance since that crossed my mind. No change. This is such a unique problem, I'd just rather return the board. If I get another one and this pops up again, I can RMA the chip (I don't want to, I think it'll do 4.9ghz).

I'll still download the software so if this comes up again, I can at least directly see the cause.

This is precisely what I said. This problem is *always* a hardware issue if it happens on a new install. I mentioned that this happened to someone else some time ago and it was faulty hardware. But I don't remember if it was board or CPU. Guess we'll find out. Board does sound more likely. Keep us posted.

Its obviously that blackest of blackmarket bootleg copy of W7 that you are using. Try a legit disk. hehe :D

Quote:

---

Originally Posted by little_scrapper

Its obviously that blackest of blackmarket bootleg copy of W7 that you are using. Try a legit disk. hehe :D

---

Love the joke :rolleyes:, but this problem is super annoying.

Ewiz hopefully has a decent RMA turn around time. Claims 2 business days. I hope they are there today to recieve the RMA request since I just sent it.

Should be interesting. I'll report back later.

That isn't software. Software spreads the load across all cores unless the affinity has been locked to one core. If you run SuperPi on a dual core CPU you'll see that both cores sit at 50%, which is equal to full load on a core. Windows juggles things around.

Quote:

---

Originally Posted by [XC] Oj101

That isn't software. Software spreads the load across all cores unless the affinity has been locked to one core. If you run SuperPi on a dual core CPU you'll see that both cores sit at 50%, which is equal to full load on a core. Windows juggles things around.

---

I agree.

Locking to one thread is so odd. It affects 2 threads (1 core, 1 HT) in Prime95, but just sitting in Windows, only one is bogged down. Why 2K8 R2 isn't affected is beyond me.

I just hope the RMA process is fast (so far, it can take up to 2 business days to get one issued).

I'm tempted to order another one, but don't wnat to go to the hassle of selling the 2nd one on here.

It's probably just a fluke.

Quote:

---

Originally Posted by [XC] Oj101

That isn't software. Software spreads the load across all cores unless the affinity has been locked to one core. If you run SuperPi on a dual core CPU you'll see that both cores sit at 50%, which is equal to full load on a core. Windows juggles things around.

---

I'd say the same if the source of the load wasn't very specific: interrupts can be targeted at individual cores in a lower level than Window's scheduler, specially if they're coming from a defective driver/piece of hardware. I don't doubt the blame is on defective hardware/firmware, but it's very very unlikely the CPU is it.

Im pretty sure the last time I saw this problem was also on this forums. Rather sure it was with a core i7, but I don't remember. May have been a C2Q. I just know it was hardware related, though. Maybe a search can find it..

I ordered a new board. The 2600k doesn't have this 100% thread spike. It must be the board. Flukes happen, case closed. :up:

Glad it's fixed. Told you it was a hardware problem :)

Now I'm fighting w/ my new board, LOL, go figure. :p:

Quote:

---

Originally Posted by danielkza

I'd say the same if the source of the load wasn't very specific: interrupts can be targeted at individual cores in a lower level than Window's scheduler, specially if they're coming from a defective driver/piece of hardware. I don't doubt the blame is on defective hardware/firmware, but it's very very unlikely the CPU is it.

---

If it's a lower level than Windows scheduler can you really blame it on a virus or other piece of software running in the background?

--------

I'm glad you came right:)

I didn't even reinstall. My previous install booted up fine w/ the exactly same hardware (besides the boards). Just for everyone's edification.

I guess we'll never find out what actually was causing the problem. Glad it's solved though :clap:

A faulty board caused it?

Quote:

---

Originally Posted by [XC] Oj101

A faulty board caused it?

---

What exactly was faulty that caused a bug of such a weird nature? That's what I was wondering.