Few days of BSOD getting annoyed!

L600MAT · 02 Dec 2015

Hello,

I built my new PC back in September and decided to buy Windows 10 because I brought Windows 7 when it was new and never had an issue. However Windows 10 is not working to well. From September the computer has been fine until last week, Which is when it would go to a blue screen as soon as I finished entering my password. On the 29th Nov I reinstalled completely wiping everything.

I reinstalled using every up to date driver I could possibly find and all was fine. I then let it continue to download the W10 November update. After this the blue screens returned. Now i'm not saying it was the update but may be something wasn't getting a long. The only way I could get back into Windows was to restore it to a previous point. I have no idea if the November update is still installed but I have stopped Windows update just in case, however today I have started getting random blue screens again.

It's annoying at the moment as I need to get work done.

Errors have varied from Critical Process Died, Kmode(something) TCPIP.sys, Page fault and A6210.sys which is my Netgear Wifi Adapter.

I will be grateful for any help possible.

L600MAT · 02 Dec 2015

Update: I have ran every basic test in Sea Tools on all hard drives and it has found no issues. Currently running HDTune.

axe0 · 02 Dec 2015

Hi L600MAT,

I recommend to remove ASUS AI Suite II, ASUS software is known for causing bluescreens.

Please uninstall everything of AMD using Display Driver Uninstaller and install new drivers from AMD. Be sure to ONLY install the drivers using custom/advanced options.

Code:

Probably caused by : dxgkrnl.sys

2: kd> lmvm atikmpag
start             end                 module name
fffff801`45e30000 fffff801`45eda000   atikmpag   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Wed Nov 18 03:53:38 2015 (564BE832)
    CheckSum:         000B5900
    ImageSize:        000AA000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Diagnostic Test

RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

L600MAT · 02 Dec 2015

I will remove the Asus stuff but the AMD Chipset and Drivers are the latest. Thanks for the response.

axe0 · 02 Dec 2015

Then simply reinstall :)
It could well be that the current drivers have become corrupted somehow.

L600MAT · 02 Dec 2015

Ok ill fully remove all and only install the driver without the fancy stuff.

L600MAT · 03 Dec 2015

Hi Axe,

I did the above as suggested, however sometime during the night it has happened again. I added an updated zip from this morning. Thanks in advance.

axe0 · 03 Dec 2015

Or update the drivers from your Netgear USB network adapter, or don't use it while troubleshooting.
USB network adapters should either be up to date with drivers, or it is recommended to not use them as they can give internet problems.

Code:

*** WARNING: Unable to verify timestamp for A6210.sys
*** ERROR: Module load completed but symbols could not be loaded for A6210.sys
6: kd> lmvm a6210
start             end                 module name
fffff800`db9d0000 fffff800`dbbf9000   A6210    T (no symbols)           
    Loaded symbol image file: A6210.sys
    Image path: \SystemRoot\system32\DRIVERS\A6210.sys
    Image name: A6210.sys
    Timestamp:        Thu May 28 16:28:52 2015 (55672624)
    CheckSum:         0022BB2B
    ImageSize:        00229000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

L600MAT · 03 Dec 2015

The Netgear drivers are updated. From Googleing I see their are lots of issues with adapters. I will plug it in on a cable later and see what happens. Thanks again Matt.

Edit : odd that it thinks the month is May lol.

L600MAT · 03 Dec 2015

Now plugged in on a cable. However the system crashed again but with out the BSOD just froze.