NMI IOCK error for reason 60 on CPU 0 (i3 2100/ASUS H77M)

jiewmeng

Distinguished
May 7, 2011
147
0
18,690
My PC suddenly feels very laggy. Sometimes when I type, I suddenly get many duplicate characters. When I go into console (Ctrl+Alt+F2) I see afew messages abt NMI: IOCK error (debug interrupt?) for reason 60 on CPU 0 popping out. The reason number might be different. I am getting: dmesg output. This was on Arch Linux. But on Windows 7, I gotten 3 BSOD's by now at different times about Hardware Malfunction, NMI: Channel Check / IOCHK

Code:
[  835.524732] NMI: IOCK error (debug interrupt?) for reason 60 on CPU 0.
[  835.524737] CPU 0 
[  835.524742] Pid: 0, comm: swapper/0 Tainted: G           O 3.8.6-1-ARCH #1 System manufacturer System Product Name/P8H77-M
[  835.524745] RIP: 0010:[<ffffffff812ce36c>]  [<ffffffff812ce36c>] intel_idle+0xac/0x100
[  835.524754] RSP: 0018:ffffffff81801e38  EFLAGS: 00000046
[  835.524756] RAX: 0000000000000020 RBX: 0000000000000008 RCX: 0000000000000001
[  835.524758] RDX: 0000000000000000 RSI: ffffffff818687c0 RDI: 000000000180d000
[  835.524760] RBP: ffffffff81801e60 R08: 0000000000000003 R09: 000000000000233f
[  835.524762] R10: 0000000000000000 R11: 00000000000005ee R12: 0000000000000003
[  835.524763] R13: 0000000000000020 R14: 0000000000000003 R15: ffffffff81387f30
[  835.524766] FS:  0000000000000000(0000) GS:ffff88021ec00000(0000) knlGS:0000000000000000
[  835.524768] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  835.524770] CR2: 00007fe8f403df00 CR3: 000000000180d000 CR4: 00000000000407f0
[  835.524772] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  835.524774] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[  835.524777] Process swapper/0 (pid: 0, threadinfo ffffffff81800000, task ffffffff81815440)
[  835.524778] Stack:
[  835.524779]  0000000081801e48 ffff88021ec19f70 ffffffff818687c0 000000c2baefba76
[  835.524784]  0000000000000003 ffffffff81801e70 ffffffff81387f49 ffffffff81801ea8
[  835.524787]  ffffffff81388ae2 ffff88021ec19f70 0000000000000003 0000000000000000
[  835.524798] Call Trace:
[  835.524802]  [<ffffffff81387f49>] cpuidle_enter+0x19/0x20
[  835.524804]  [<ffffffff81388ae2>] cpuidle_wrap_enter+0x32/0x80
[  835.524805]  [<ffffffff81387f60>] cpuidle_enter_tk+0x10/0x20
[  835.524807]  [<ffffffff813886f6>] cpuidle_idle_call+0xb6/0x390
[  835.524810]  [<ffffffff8101edac>] cpu_idle+0xec/0x150
[  835.524813]  [<ffffffff814a2e3f>] rest_init+0x7f/0x90
[  835.524816]  [<ffffffff818d0c38>] start_kernel+0x3db/0x3e7
[  835.524818]  [<ffffffff818d0666>] ? repair_env_string+0x5c/0x5c
[  835.524820]  [<ffffffff818d0120>] ? early_idt_handlers+0x120/0x120
[  835.524822]  [<ffffffff818d0355>] x86_64_start_reservations+0x130/0x133
[  835.524824]  [<ffffffff818d045a>] x86_64_start_kernel+0x102/0x10f
[  835.524825] Code: 31 d2 48 83 c0 10 48 89 d1 0f 01 c8 0f ae f0 65 48 8b 04 25 f0 c6 00 00 48 8b 80 38 e0 ff ff a8 08 75 08 b1 01 4c 89 e8 0f 01 c9 <85> 1d 2e a4 59 00 75 0e 48 8d 75 dc bf 05 00 00 00 e8 9e 13 de

Its a Intel Core i3 2100 and ASUS H77M MB. I originally thought it was a SSD fault (prev post) ... Does this likely confirm CPU is faulty? What can I do? Will trying to resit the CPU in the MB help?

I think its useful to understand the cause too. since its a self built system. So I can avoid making same mistakes again? The CPU was in use for probably >1 years? The MB was replaced probably just ~6mths (guessing) due to mistake in flashing BIOS. No other major changes in hardware apart from that. CPU temps looks fine typically <40 degrees from BIOS. I noted that BIOS POST works, does this eliminate problems with CPU/MB? Its after POST, it gets stuck at blinking cursor. I tried booting from a bootable USB too. If the HDD is stuck, then USB is likely going to encounter the sme problem too.

UPDATE

I noticed that if I can get to Syslinux bootloader, after selecting an entry, I usually get Parity Error. I tried removing one RAM at a time, results are inconsistent, sometimes, I will only get a blinking cursor after POST (thus no syslinux nor partity error at all). I am thinking I might need to change some components soon. But I was hoping to isolate the problem so I dont replace working parts if possible.
 

jiewmeng

Distinguished
May 7, 2011
147
0
18,690
Btw, I also noticed that if I ever get into bootloader (syslinux) but fails to load as OS, I get "Parity Error" on screen. I guess the problem is still likely MB/CPU?

I tried once after being able to boot an bootable ISO to load memtest+ but it seems to hang doing nothing ...
 
My first guess would be a flaky motherboard. I have gotten that warning on an OLD 486 with an EGA video card with an attitude.
It generated NMIs whenever it was sent data to its registers for whatever reason.

It is a general error/warning for whenever an NMI is generated by flaky/buggy hardware.