Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {403, ffffee3ffda90500, ffa00001008c4025, ffffee018d58fb18}
Probably caused by : memory_corruption
Followup: memory_corruption
Code:
0x403 = The page table and PFNs are out of sync . This is probably a hardware error, especially if parameters 3 & 4 differ by only a single bit.
Hi,
sorry about the mouse question looks like it may have been a red herring.
Ok, so going through your dump files only two drivers are mentioned as probably causes. Other culprits could be system corruption or a hardware error probably RAM. (notice the dump file I posted. It has a sub-type of 403 the meaning of this parameter is posted just below the dump)
First let's try and deal with any corruption:
File scans
Right click on the Start menu icon and from the revealed list choose 'admin command prompt'. Type:
sfc /scannow
press enter and await results
In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).
If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.
Drivers
AsIO.sys Wed Aug 22 10:54:47 2012: Asus PCProbe Utility please remove
atikmdag.sys Fri Sep 16 20:12:45 2016: AMD GPU driver. Please remove using the DDU or Display driver remover. This will clean out any corruption left behind by previous installs:
Display Driver Uninstaller (DDU) V17.0.3.1 Released. - Wagnardsoft Forum Install latest WHQL driver:
Desktop athw8x.sys Thu Jan 28 09:52:54 2016: Atheros Wireless LAN Driver. Is this something you've added yourself as I see no driver update for this on your support page. Your normal LAN drivers are Realtek.
This is one of the drivers that was a probable cause and can you post where you got the driver from?
RAM
I know you posted that you had tested the RAM before without any errors appearing. Now I've known of cases where Memtest86 wasn't picking up any errors until the sticks were tested individually.
Choose a slot (the slot closest to the cpu is usually favourite) and test each stick individually overnight. Do make sure you keep a note of which stick is which so they don'y get mixed up.
There are other things we could still try but see how you get on with the above first. Please post any new dump files.