Well, it was 'different' this morning...
Within 3 minutes the computer rebooted without warning. Then, on the reboot, in less that a minute as it was coming up, a BSOD. DRIVER_IRQL_NOT_LESS_OR_EQUAL (BTHPORT.SYS) and the dump NEVER finished, stuck at 45%?
Running DUMPCHK tells me the dump is corrupt as well. About all that is useful out of it is:
===========
BugCheck D1, {1400d58f, 2, 0, fffff8017ba41edf}
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
ReadControl failed - kernel symbols must be loaded first
.
.
.
===========================
From THIS it seems IRQ2 was trying to do a READ? Only do not know 'who' was on IRQL 2?
Event log as usual shows nothing? At least nothing that is always there.
BTHPORT.SYS is BlueTooth, and my mouse and keyboard connect that way. I have the latest Logitech drivers, and these devices have been on the system from day 1 without a problem.
I've seen too many different 'files' and BSOD's to beleive this one is 'real'.
Since I've rebooted 45 minutes ago the computer is working fine. I think the BSOD is bogus. Especially since if didn't complete the dump so the true culprit could be found.
Just the fact that the computer works correctly after the BSOD should rule out something? If h/w I'd expect it to happen again. If s/w, well it is possible it is a timing issue, but why does it always work correctly AFTER the first instance and rebooted? Doesn't make sense?