Petr Vandrovec wrote:
> Try dumping *all* MCE values, as well as a call stack. Even although
> MCE is tagged as processor context corrupt, there is rather big chance
> that stack trace will point back to the instruction which caused MCE
> (it always did in my case), especially if it is single pro
David King wrote:
CPU 0 4 northbridge TSC f03d1e587b
Northbridge Watchdog error
bit57 = processor context corrupt
bit61 = error uncorrected
bus error 'generic participation, request timed out
generic error mem transaction
generic access, level generic'
STATUS b2070f0f MCGSTATUS 4
That's
2 matches
Mail list logo
