Server locks up again

I deliberately reimage the server, and I touch nothing - no new packages, I dont' even logon. I check the login: prompt appears and that is it....

within 48 hours of the supposed hardware test, the server locks up again - again the softlock CPU error appears in the logs:

"My server is still causing problems and locking up.

The logs state that the server stopped responding:

Jan 3 20:27:19 s15278325 kernel: BUG: soft lockup detected on CPU#0!
Jan 3 20:27:19 s15278325 kernel:
Jan 3 20:27:19 s15278325 kernel: Call Trace:
Jan 3 20:27:19 s15278325 kernel: [] softlockup_tick+0xfa/0x120
Jan 3 20:27:19 s15278325 kernel: [] __do_softirq+0x5f/0xd0
Jan 3 20:27:19 s15278325 kernel: [] update_process_times+0x57/0x90
Jan 3 20:27:19 s15278325 kernel: [] smp_local_timer_interrupt+0x34/0x60
Jan 3 20:27:19 s15278325 kernel: [] smp_apic_timer_interrupt+0x59/0x80
Jan 3 20:27:19 s15278325 kernel: [] default_idle+0x0/0x50
Jan 3 20:27:19 s15278325 kernel: [] apic_timer_interrupt+0x66/0x70
Jan 3 20:27:19 s15278325 kernel: [] datagram_poll+0x0/0xf0
Jan 3 20:27:19 s15278325 kernel: [] default_idle+0x29/0x50
Jan 3 20:27:19 s15278325 kernel: [] cpu_idle+0x5c/0x80
Jan 3 20:27:19 s15278325 kernel: [] start_kernel+0x225/0x230
Jan 3 20:27:19 s15278325 kernel: [] _sinittext+0x162/0x170
Jan 3 20:27:19 s15278325 kernel:
Jan 4 06:01:04 s15278325 dhclient: DHCPREQUEST on eth0 to 87.*.*.* port 67
Jan 4 06:01:47 s15278325 last message repeated 3 times

Also according to dmesg:

BUG: soft lockup detected on CPU#0!

Call Trace:
[] softlockup_tick+0xfa/0x120
[] __do_softirq+0x5f/0xd0
[] update_process_times+0x57/0x90
[] smp_local_timer_interrupt+0x34/0x60
[] smp_apic_timer_interrupt+0x59/0x80
[] default_idle+0x0/0x50
[] apic_timer_interrupt+0x66/0x70
[] datagram_poll+0x0/0xf0
[] default_idle+0x29/0x50
[] cpu_idle+0x5c/0x80
[] start_kernel+0x225/0x230
[] _sinittext+0x162/0x170

This server still has a problem and I need this sorted out. I understand that you have ran a full test on the hardware and have found no problems, however as you can see from the logs there is still a problem. I need this rectified – if you do not have the skills to resolve this issue then please escalate it urgently to a senior admin.

Kind regards

Netwarriors"