Hidclass BSOD

ba12348 · 20 Jan 2017

So I posted another thread on this forum a while ago because of BSODs after a hardware upgrade, and after not finding anything with memtest or driver verifier, I installed a new SSD (which had been on my todo list anyway), clean install of windows, fresh drivers for everybody, and chalked it up to ghosts in the machine when the crashes stopped. I went several weeks without issue, then experienced two crashes in quick succession, both while playing Watchdogs 2, which frankly has so many other issues that I just figured it was taking the whole computer with it when it crashed.

Fast forward to last night when I got home from work and woke my computer up to a black "your computer has restarted unexpectedly" screen. Hmm. So I enabled driver verifier, shut the computer down, and went to sleep. This morning I started the computer, put my password in, and instant BSOD. Good! I think... This cycle repeats itself 2 or 3 times before I try safe mode, which gets me to the login screen, but shuts down WITHOUT a BSOD before I can enter my password, the computer restarts as if nothing happened,and back to normal mode login screen. The computer is perfectly happy to sit there at the login screen, but entering the password crashes it. I get into the system restore menu (F8), and neither my keyboard or mouse do anything, well they both have drivers so I go dig out an old keyboard from the basement, it works, and load a system restore from last night, which brings us to now.

-keyboard is a Logitech G110 which I've been using for ~6 years now without issue.
-mouse is a Logitech G400s, which is closer to 4 years old.
-A Logitech G930 (I like Logitech stuff, even if their customer support sucks) is installed but not currently plugged in, and has not been plugged in when any of the crashes occurred, I've been using it for about 4 years as well.
-All 3 use Logitech Gaming Software, though none require it, it just enables some things like programmable buttons.
-And for completeness sake the monitor is an LG 24GM77 which I've been using for about 2 years now.

ICIT2LOL · 21 Jan 2017

Hello ba12348 now there is a very common dump in thsoe files ntoskrnl.exe and this could be just about anything but there are also bug checks pointing to the memory being out of whack

Code:

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
	contains the address of the PFN for the corrupted page table page.
	On a 32 bit OS, parameter 2 contains a pointer to the number of used
	PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa80020ae460
Arg3: 000000000000ffff
Arg4: 0000000000000000

Code:

BugCheck 1A, {41790, fffffa80020ae460, ffff, 0}

Basically the same thing - so it might be as well to run a memtest first up so this pre wriiten ditty
MEMTEST
Now to make absolutely we are on the same page the memtest linked here is the*only*one we recommend and it MUST be run for at least 8 passes or you may as well not bother. It is rather lengthy and best left for a downtime for that machine - overnight is good. Having said that you can stop the test if errors show up while you are around and then it is a matter of tracking down the bad stick of RAM.* RAM - Test with Memtest86+

ba12348 · 22 Jan 2017

Alrighty, I'll run it again. Computer's got 32 gigs of ram though so this will be a while...

ICIT2LOL · 22 Jan 2017

Afraid so ba12348 a tedious and if errors do come up it then means trying to find the bad stick/s and again it takes a long time but it is worth it in the end.