Reliability History Hardware Error Unknown Cause

Bit of an update. Ever since I installed the latest CU, all the phantom hardware errors in Reliability History have vanished. Wonder if the latest update resolved it?

AntJac said:

Bit of an update. Ever since I installed the latest CU, all the phantom hardware errors in Reliability History have vanished. Wonder if the latest update resolved it?

Thanks for updating us - I'll keep an eye on mine then. I can't tell on my rig yet because this phantom error is a weekly event and I don't think enough time has ticked by since this last cumulative update. Keeping my fingers crossed!

Sadly still an issue for me, it took 8 days but on both machines the phantom hardware error appeared in the reliability history today. Oh well, it was nice to have some hope for a while!!

Yep happened to me today too!

same issue also for me

Bug Check String: SESSION_HAS_VALID_POOL_ON_EXIT
Bug Check Code: 0x000000ab
Parameter 1: 00000000`00000001
Parameter 2: 00000000`000001d0
Parameter 3: 00000000`000001d0
Parameter 4: 00000003`00000003
Cause By Driver: ntoskrnl.exe
Cause By Address: ntoskrnl.exe+3d7d37

Not a truly BSoD, as previously reported by other users it is showed only in reliability history and it seems to occur (often but not always) switching user..

10 Pro X64 14393.576, Radeon Crimson ReLive Edition 16.12.2 (but it occurred also with previous buld).

If i'm not wrong, i bumped into this issue starting from build 351 (as per Scottyboy99 report)

Sorry for my poor english

Got another hardware error message today

any news?

Not much to report really. It still happens on both my machines approx. 7 days apart between each instance on the reliability history. Still totally in the dark over the cause. If I wasn't so finicky and didn't keep looking in the reliability history I'd be none the wiser because I see no detrimental effects on the machines! Maybe the creators update will put an end to it when it releases but I'm not holding out hopes. MS doesn't seem to address bugs or glitches quickly at all prefer pretending that they do not exist!

ok txs, i'll avoid to switch user continuing instead to reboot if i really have to change logged user...

I was receiving a hardware related error prior to installing Update for Windows (KB3216755) on 01-30-2017. I have not had this issue pop up since the update.